Forum Discussion
Ideally you should have zero PostRS errors on the circuit. These are packets that have to be re-transmitted as they cannot be corrected, unlike PreRS errors. So, there is an issue on the circuit, possibly noise ingress. Also you have 18 T3 timeouts, which IMHO should be lower.
Post the network log as well for completeness and comment, and setup a BQM to monitor the state of the circuit www.thinkbroadband.com/ping
When done, post a link to the shared live graph. It may show more information.
All you can do is make sure the connections are "finger" tight from the Hub to the outside omnibox on the wall.
Otherwise, wait here a day or two for a VM Mod to pick this up and discuss.
- Sdavlaws2 years agoTuning in
Thanks for looking the network log is below, I'll get a BQM set up
15-11-2023 00:45:05 notice REGISTRATION COMPLETE - Waiting for Operational status 15-11-2023 00:44:59 warning REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 15-11-2023 00:44:54 notice DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 15-11-2023 00:44:51 notice TLV-11 - unrecognized OID;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 15-11-2023 00:44:48 warning DHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 15-11-2023 00:44:46 notice Honoring MDD; IP provisioning mode = IPv4 15-11-2023 00:44:31 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 15-11-2023 00:44:27 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 15-11-2023 00:44:26 critical Cable Modem Reboot because of - Reboot UI 29-10-2023 12:57:00 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 29-10-2023 12:57:00 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 29-10-2023 12:57:00 critical 16 consecutive T3 timeouts while trying to range on upstream channel 4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 29-10-2023 12:55:00 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 29-10-2023 12:53:16 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 29-10-2023 12:53:00 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 29-10-2023 12:52:46 critical No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 29-10-2023 12:52:36 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 29-10-2023 12:52:25 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 29-10-2023 12:52:19 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 29-10-2023 12:52:17 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 12-10-2023 19:45:57 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 12-10-2023 19:45:56 critical Cable Modem Reboot because of - HW or Power-On Reset 12-10-2023 18:41:18 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 12-10-2023 18:41:17 critical Cable Modem Reboot because of - HW or Power-On Reset 03-10-2023 03:19:04 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 03-10-2023 03:18:58 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 03-10-2023 03:18:57 critical Cable Modem Reboot because of - Software_Upgrade 25-09-2023 21:00:51 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 25-09-2023 21:00:01 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 25-09-2023 20:59:57 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 15-08-2023 03:18:19 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; 04-07-2023 11:04:58 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; - Daniel_Et2 years agoForum Team
Hi Sdavlaws, thank you for your post.
We're sorry to hear about the problems you've been having with your broadband service 😔
I've taken a look on our side, but I cannot see anything that could explain these.
How have things been since you last posted? Advice on how to fix internet problems can be found here.
Please pop back to us at your earliest convenience.
Thank you for your support Adduxi 👍
Regards,
Daniel- Sdavlaws2 years agoTuning in
Since my most recent modem reboot, the error rate has lowered still getting pre RS errors but nothing post RS, The DOCSIS 3.1 uncorrectable errors is still climbing though up to 24k now.
Related Content
- 5 months ago
- 3 months ago
- 5 months ago
- 4 months ago
- 2 years ago