Forum Discussion

ykc's avatar
ykc
New Contributor

No Ranging Response received - T3 time-out

I got this error 5 or 6 times a day. Cox technician came out and tried to fix it 2 times. It got worst the last fix. I got the errors every hour. I had to switch out to my old router. It seemed like it only reboot 2 times within a 8 hour period. I scheduled another technician to come out. I have no hope that they can fix my problem. The following is my cable log. I need help.

TimePriorityCodeMessage
Sep 02 2015 00:18:51 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=e8:6d:52:6f:8d:7e;CMTS-MAC=00:21:d8:d1:51:74;CM-QOS=1.1;CM-VER=3.0;
Sep 02 2015 00:18:51 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=e8:6d:52:6f:8d:7e;CMTS-MAC=00:21:d8:d1:51:74;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:20 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=e8:6d:52:6f:8d:7e;CMTS-MAC=00:21:d8:d1:51:74;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:15 6-Notice N/A Cable Modem Reboot due to T4 timeout ;CM-MAC=e8:6d:52:6f:8d:7e;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Sep 02 2015 00:18:06 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=e8:6d:52:6f:8d:7e;CMTS-MAC=00:21:d8:d1:51:74;CM-QOS=1.1;CM-VER=3.0;
Sep 02 2015 00:18:06 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=e8:6d:52:6f:8d:7e;CMTS-MAC=00:21:d8:d1:51:74;CM-QOS=1.1;CM-VER=3.0;
Sep 02 2015 00:18:06 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=e8:6d:52:6f:8d:7e;CMTS-MAC=00:21:d8:d1:51:74;CM-QOS=1.1;CM-VER=3.0;
Sep 02 2015 00:18:01 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=e8:6d:52:6f:8d:7e;CMTS-MAC=00:21:d8:d1:51:74;CM-QOS=1.1;CM-VER=3.0;
Sep 02 2015 00:18:01 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=e8:6d:52:6f:8d:7e;CMTS-MAC=00:21:d8:d1:51:74;CM-QOS=1.1;CM-VER=3.0;
Sep 02 2015 00:18:01 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=e8:6d:52:6f:8d:7e;CMTS-MAC=00:21:d8:d1:51:74;CM-QOS=1.1;CM-VER=3.0;
Sep 02 2015 00:18:01 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=e8:6d:52:6f:8d:7e;CMTS-MAC=00:21:d8:d1:51:74;CM-QOS=1.1;CM-VER=3.0;
Sep 02 2015 00:18:00 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=e8:6d:52:6f:8d:7e;CMTS-MAC=00:21:d8:d1:51:74;CM-QOS=1.1;CM-VER=3.0;
Sep 02 2015 00:17:51 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=e8:6d:52:6f:8d:7e;CMTS-MAC=00:21:d8:d1:51:74;CM-QOS=1.1;CM-VER=3.0;
Sep 02 2015 00:17:51 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=e8:6d:52:6f:8d:7e;CMTS-MAC=00:21:d8:d1:51:74;CM-QOS=1.1;CM-VER=3.0;
Sep 02 2015 00:17:51 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=e8:6d:52:6f:8d:7e;CMTS-MAC=00:21:d8:d1:51:74;CM-QOS=1.1;CM-VER=3.0;
Sep 01 2015 22:10:49 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=e8:6d:52:6f:8d:7e;CMTS-MAC=00:21:d8:d1:51:74;CM-QOS=1.1;CM-VER=3.0;
Sep 01 2015 22:10:49 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=e8:6d:52:6f:8d:7e;CMTS-MAC=00:21:d8:d1:51:74;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:02:54 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=e8:6d:52:6f:8d:7e;CMTS-MAC=00:21:d8:d1:51:74;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:02:54 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=e8:6d:52:6f:8d:7e;CMTS-MAC=00:21:d8:d1:51:74;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:02:52 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=e8:6d:52:6f:8d:7e;CMTS-MAC=00:21:d8:d1:51:74;CM-QOS=1.1;CM-VER=3.0;
DownstreamBonding Channel Value
Channel ID 73  74  75  76  77  78  79  80 
Frequency 819000000 Hz  825000000 Hz  831000000 Hz  837000000 Hz  843000000 Hz  849000000 Hz  855000000 Hz  861000000 Hz 
Signal to Noise Ratio 38 dB  38 dB  38 dB  38 dB  37 dB  38 dB  37 dB  37 dB 
Downstream Modulation QAM256  QAM256  QAM256  QAM256  QAM256  QAM256  QAM256  QAM256 
Power Level
The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading
-2 dBmV   -2 dBmV   -2 dBmV   -2 dBmV   -2 dBmV   -2 dBmV   -3 dBmV   -3 dBmV  

UpstreamBonding Channel Value
Channel ID 1  2  3  4 
Frequency 17800000 Hz  21100000 Hz  26000000 Hz  32500000 Hz 
Ranging Service ID 2  2  2  2 
Symbol Rate 2.560 Msym/sec  2.560 Msym/sec  5.120 Msym/sec  5.120 Msym/sec 
Power Level 39 dBmV  38 dBmV  37 dBmV  40 dBmV 
Upstream Modulation [3] QPSK
[5] 16QAM
 		 [3] QPSK
[2] 16QAM
[3] 64QAM
 		 [3] 16QAM
[3] 64QAM
 		 [3] 16QAM
[3] 64QAM
 
Ranging Status Success  Success  Success  Success 

Signal Stats (Codewords)Bonding Channel Value
Channel ID 73  74  75  76  77  78  79  80 
Total Unerrored Codewords 1314287674  1313603877  1313612067  1313620694  1313595707  1313596886  1313597879  1313599130 
Total Correctable Codewords 15  5  2  0  18  15  11  16 
Total Uncorrectable Codewords 1587  1353  1419  1438  1583  1494  1582  1404 

cable modem
connectivity
cox coxsupport
coxsupport

5 Replies

Sort By
Most LikedOldestNewest
Replies have been turned off for this discussion
  • ChrisL's avatar
    ChrisL
    Former Moderator
    @ykc

    This error message basically indicates that a timeout occurred in upstream communication between the modem and us.  This will most commonly be the result of a signal or modem problem that often benefits from having a technician come out and troubleshoot further.  You can also try inspecting all of your cable lines for damage or loose fittings and try bypassing any extra cable splitters to see if you get any improvement.  Note a few T3 events occurring occasionally is common and shouldn't disrupt connectivity.  When the become frequent and numerous that is when you'll start seeing noticeable effects.

  • ykc's avatar
    ykc
    New Contributor

    The modem went up and down multiple time yesterday. Sometime it went out for more than an hour. It was stable after 8:00pm. Is something happening during a daytime in Cox network? I showed the log too last technician but he did not bother to look at it. What should I tell the next technician? I had a Motorola Surfboard SB6141 for 6 months. Do I need a new modem?The following is my new logs.

    TimePriorityCodeMessage
    Sep 02 2015 20:44:09 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=e8:6d:52:6f:8d:7e;CMTS-MAC=00:21:d8:d1:51:74;CM-QOS=1.1;CM-VER=3.0;
    Sep 02 2015 20:44:09 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=e8:6d:52:6f:8d:7e;CMTS-MAC=00:21:d8:d1:51:74;CM-QOS=1.1;CM-VER=3.0;
    Jan 01 1970 00:00:27 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=e8:6d:52:6f:8d:7e;CMTS-MAC=00:21:d8:d1:51:74;CM-QOS=1.1;CM-VER=3.0;
    Jan 01 1970 00:00:14 6-Notice N/A Cable Modem Reboot due to T4 timeout ;CM-MAC=e8:6d:52:6f:8d:7e;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
    Sep 02 2015 20:43:20 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=e8:6d:52:6f:8d:7e;CMTS-MAC=00:21:d8:d1:51:74;CM-QOS=1.1;CM-VER=3.0;
    Sep 02 2015 20:43:20 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=e8:6d:52:6f:8d:7e;CMTS-MAC=00:21:d8:d1:51:74;CM-QOS=1.1;CM-VER=3.0;
    Sep 02 2015 20:43:20 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=e8:6d:52:6f:8d:7e;CMTS-MAC=00:21:d8:d1:51:74;CM-QOS=1.1;CM-VER=3.0;
    Sep 02 2015 20:43:15 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=e8:6d:52:6f:8d:7e;CMTS-MAC=00:21:d8:d1:51:74;CM-QOS=1.1;CM-VER=3.0;
    Sep 02 2015 20:43:15 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=e8:6d:52:6f:8d:7e;CMTS-MAC=00:21:d8:d1:51:74;CM-QOS=1.1;CM-VER=3.0;
    Sep 02 2015 20:43:14 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=e8:6d:52:6f:8d:7e;CMTS-MAC=00:21:d8:d1:51:74;CM-QOS=1.1;CM-VER=3.0;
    Sep 02 2015 20:43:14 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=e8:6d:52:6f:8d:7e;CMTS-MAC=00:21:d8:d1:51:74;CM-QOS=1.1;CM-VER=3.0;
    Sep 02 2015 20:43:14 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=e8:6d:52:6f:8d:7e;CMTS-MAC=00:21:d8:d1:51:74;CM-QOS=1.1;CM-VER=3.0;
    Sep 02 2015 20:43:05 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=e8:6d:52:6f:8d:7e;CMTS-MAC=00:21:d8:d1:51:74;CM-QOS=1.1;CM-VER=3.0;
    Sep 02 2015 20:43:05 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=e8:6d:52:6f:8d:7e;CMTS-MAC=00:21:d8:d1:51:74;CM-QOS=1.1;CM-VER=3.0;
    Sep 02 2015 20:43:05 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=e8:6d:52:6f:8d:7e;CMTS-MAC=00:21:d8:d1:51:74;CM-QOS=1.1;CM-VER=3.0;
    Sep 02 2015 20:14:56 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=e8:6d:52:6f:8d:7e;CMTS-MAC=00:21:d8:d1:51:74;CM-QOS=1.1;CM-VER=3.0;
    Sep 02 2015 20:13:59 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=e8:6d:52:6f:8d:7e;CMTS-MAC=00:21:d8:d1:51:74;CM-QOS=1.1;CM-VER=3.0;
    Sep 02 2015 18:37:49 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=e8:6d:52:6f:8d:7e;CMTS-MAC=00:21:d8:d1:51:74;CM-QOS=1.1;CM-VER=3.0;
    Sep 02 2015 18:37:49 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=e8:6d:52:6f:8d:7e;CMTS-MAC=00:21:d8:d1:51:74;CM-QOS=1.1;CM-VER=3.0;
    Jan 01 1970 00:34:47 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=e8:6d:52:6f:8d:7e;CMTS-MAC=00:21:d8:d1:51:74;CM-QOS=1.1;CM-VER=3.0;
    Downstream Bonding Channel Value
    Channel ID 74  73  75  76  77  78  79  80 
    Frequency 825000000 Hz  819000000 Hz  831000000 Hz  837000000 Hz  843000000 Hz  849000000 Hz  855000000 Hz  861000000 Hz 
    Signal to Noise Ratio 38 dB  38 dB  38 dB  38 dB  38 dB  38 dB  37 dB  37 dB 
    Downstream Modulation QAM256  QAM256  QAM256  QAM256  QAM256  QAM256  QAM256  QAM256 
    Power Level
    The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading
    		-1 dBmV   -1 dBmV   -1 dBmV   -1 dBmV   -2 dBmV   -2 dBmV   -2 dBmV   -3 dBmV  

    Upstream Bonding Channel Value
    Channel ID 1  2  3  4 
    Frequency 17800000 Hz  21100000 Hz  26000000 Hz  32500000 Hz 
    Ranging Service ID 2  2  2  2 
    Symbol Rate 2.560 Msym/sec  2.560 Msym/sec  5.120 Msym/sec  5.120 Msym/sec 
    Power Level 39 dBmV  39 dBmV  38 dBmV  40 dBmV 
    Upstream Modulation [3] QPSK [5] 16QAM   [3] QPSK [2] 16QAM [3] 64QAM   [3] 16QAM [3] 64QAM   [3] 16QAM [3] 64QAM  
    Ranging Status Success  Success  Success  Success 

    Signal Stats (Codewords)Bonding Channel Value
    Channel ID 74  73  75  76  77  78  79  80 
    Total Unerrored Codewords 1708929115  1708945606  1708937511  1708954322  1708920888  1708921796  1708922868  1708924044 
    Total Correctable Codewords 14  1  1  0  15  12  19  11 
    Total Uncorrectable Codewords 1694  1477  1395  1399  1419  1558  1568  1447 
  • ChrisL's avatar
    ChrisL
    Former Moderator
    @ykc

    The technicians have test equipment for checking the signal levels and quality so I'm thinking the technician was expecting to find the problem that way.  One possibility too is the modem itself.  If no signal issue can be found the technician should have a spare test modem he/she can try testing with.

  • ykc's avatar
    ykc
    New Contributor

    But the modem was good for last month. It happened right after they came to service the line with new fitting.

  • ChrisL's avatar
    ChrisL
    Former Moderator
    @ykc

    Absent of a technician coming out to test all of this I can only speculate as to possible causes.  It's going to come down to a signal, modem, or problem with both.  The challenging part of figuring this out is a problem with either signal or modem will affect both.  The way you determine which is at fault is to replace the modem if no signal issues are found.