SYNC Timing Synchronization failure - Loss of Sync - Slow Speeds, Drops, etc
Hello, I have the "Ultimate" Internet tier and over the last few days, my service has been atrociously bad. There are times when I get close to the speeds I am paying for and other times not even close. I was wondering if my power levels on my modem were in-spec? Also, seeing quite a few of the following log messages in my modem: SYNC Timing Synchronization failure - Loss of Sync Started Unicast Maintenance Ranging - No Response received - T3 time-out MDD message timeout Downstream Bonded Channels Channel Lock Status Modulation Channel ID Frequency Power SNR Corrected Uncorrectables 1 Locked QAM256 22 909000000 Hz 8.7 dBmV 39.0 dB 164583 338195 2 Locked QAM256 1 783000000 Hz 10.2 dBmV 39.9 dB 0 0 3 Locked QAM256 2 789000000 Hz 10.2 dBmV 39.8 dB 0 0 4 Locked QAM256 3 795000000 Hz 10.0 dBmV 39.7 dB 0 0 5 Locked QAM256 4 801000000 Hz 10.1 dBmV 39.8 dB 0 0 6 Locked QAM256 5 807000000 Hz 10.0 dBmV 39.8 dB 0 0 7 Locked QAM256 6 813000000 Hz 9.9 dBmV 39.8 dB 0 0 8 Locked QAM256 7 819000000 Hz 9.9 dBmV 39.8 dB 0 0 9 Locked QAM256 8 825000000 Hz 10.0 dBmV 39.9 dB 0 0 10 Locked QAM256 17 879000000 Hz 9.5 dBmV 39.5 dB 4 0 11 Locked QAM256 18 885000000 Hz 9.4 dBmV 39.4 dB 1 0 12 Locked QAM256 19 891000000 Hz 9.2 dBmV 39.3 dB 3 0 13 Locked QAM256 20 897000000 Hz 9.2 dBmV 39.3 dB 2 0 14 Locked QAM256 21 903000000 Hz 8.4 dBmV 39.0 dB 182726 774664 15 Locked QAM256 23 915000000 Hz 9.0 dBmV 39.0 dB 201227 812336 16 Locked QAM256 24 921000000 Hz 8.9 dBmV 38.8 dB 612277 1054773 Upstream Bonded Channels Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 2 5120 Ksym/sec 23300000 Hz 37.7 dBmV 2 Locked TDMA and ATDMA 1 2560 Ksym/sec 18400000 Hz 38.3 dBmV 3 Locked ATDMA 3 5120 Ksym/sec 29800000 Hz 39.8 dBmV 4 Locked ATDMA 4 5120 Ksym/sec 36300000 Hz 41.3 dBmV Current System Time:Sat Oct 14 11:56:41 20172.2KViews0likes1Comment
Multiple Errors on my Docsis 3.0 model with Cox
I have noticed some speed issues with my Cox Internet connection so I logged in to look at the logs on the modem and found the following errors which are repeating every day. Before I call support and get told nothing is wrong I was hoping for some expert direction from the collective within the forum. Apr 13 2017 07:17:29 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0; Apr 13 2017 07:12:30 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0; Apr 13 2017 07:12:30 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0; Apr 13 2017 07:12:15 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0; Apr 13 2017 07:11:45 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0; Apr 13 2017 07:11:45 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0; Apr 13 2017 07:11:30 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0; Apr 13 2017 07:10:15 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0; Apr 13 2017 07:10:15 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0; Apr 13 2017 07:09:45 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0; Apr 13 2017 06:56:33 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0; Apr 13 2017 06:56:33 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0; Apr 13 2017 06:56:18 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0; Apr 13 2017 06:55:48 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0; Apr 13 2017 06:55:48 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0; Apr 13 2017 06:55:33 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0; Apr 13 2017 06:54:18 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0; Apr 13 2017 06:54:18 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0; Apr 13 2017 06:53:48 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0; Apr 13 2017 06:40:36 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0;1.3KViews0likes1Comment
