Skip to main content
ambee's profile

ambee

New Contributor

 • 

2 Messages

Closed

Consistent T3/T4 Timeout Errors

Hello,

We've been experiencing consistent T3 timeout errors over the past week during the morning and evening hours.  This is leading to only 1 of 4 upstream channels being connected in most cases.  And starting today, they've gotten significantly worse to the point where the cable modem is even having a hard time staying connected and we're seeing T4 errors as well.

Here's the most recent information from our cable modem:

Apr 14 2017 19:15:44 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:30:24:f3;CMTS-MAC=50:57:a8:89:9f:b4;CM-QOS=1.1;CM-VER=3.0;
Apr 14 2017 19:15:44 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=b8:16:19:30:24:f3;CMTS-MAC=50:57:a8:89:9f:b4;CM-QOS=1.1;CM-VER=3.0;
Apr 14 2017 19:15:43 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:30:24:f3;CMTS-MAC=50:57:a8:89:9f:b4;CM-QOS=1.1;CM-VER=3.0;
Apr 14 2017 19:15:43 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=b8:16:19:30:24:f3;CMTS-MAC=50:57:a8:89:9f:b4;CM-QOS=1.1;CM-VER=3.0;
Apr 14 2017 19:15:43 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:30:24:f3;CMTS-MAC=50:57:a8:89:9f:b4;CM-QOS=1.1;CM-VER=3.0;
Apr 14 2017 19:15:43 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=b8:16:19:30:24:f3;CMTS-MAC=50:57:a8:89:9f:b4;CM-QOS=1.1;CM-VER=3.0;
Apr 14 2017 19:15:42 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:30:24:f3;CMTS-MAC=50:57:a8:89:9f:b4;CM-QOS=1.1;CM-VER=3.0;
Apr 14 2017 19:15:42 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=b8:16:19:30:24:f3;CMTS-MAC=50:57:a8:89:9f:b4;CM-QOS=1.1;CM-VER=3.0;
Apr 14 2017 19:15:42 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:30:24:f3;CMTS-MAC=50:57:a8:89:9f:b4;CM-QOS=1.1;CM-VER=3.0;
Apr 14 2017 19:15:42 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=b8:16:19:30:24:f3;CMTS-MAC=50:57:a8:89:9f:b4;CM-QOS=1.1;CM-VER=3.0;
Apr 14 2017 19:15:41 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:30:24:f3;CMTS-MAC=50:57:a8:89:9f:b4;CM-QOS=1.1;CM-VER=3.0;
Apr 14 2017 19:15:41 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=b8:16:19:30:24:f3;CMTS-MAC=50:57:a8:89:9f:b4;CM-QOS=1.1;CM-VER=3.0;
Apr 14 2017 19:15:40 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:30:24:f3;CMTS-MAC=50:57:a8:89:9f:b4;CM-QOS=1.1;CM-VER=3.0;
Apr 14 2017 19:15:40 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=b8:16:19:30:24:f3;CMTS-MAC=50:57:a8:89:9f:b4;CM-QOS=1.1;CM-VER=3.0;
Apr 14 2017 19:15:39 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:30:24:f3;CMTS-MAC=50:57:a8:89:9f:b4;CM-QOS=1.1;CM-VER=3.0;
Apr 14 2017 19:15:39 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=b8:16:19:30:24:f3;CMTS-MAC=50:57:a8:89:9f:b4;CM-QOS=1.1;CM-VER=3.0;
Apr 14 2017 19:15:38 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:30:24:f3;CMTS-MAC=50:57:a8:89:9f:b4;CM-QOS=1.1;CM-VER=3.0;
Apr 14 2017 19:15:38 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=b8:16:19:30:24:f3;CMTS-MAC=50:57:a8:89:9f:b4;CM-QOS=1.1;CM-VER=3.0;
Apr 14 2017 19:15:37 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:30:24:f3;CMTS-MAC=50:57:a8:89:9f:b4;CM-QOS=1.1;CM-VER=3.0;
Apr 14 2017 19:15:37 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=b8:16:19:30:24:f3;CMTS-MAC=50:57:a8:89:9f:b4;CM-QOS=1.1;CM-VER=3.0;
This page provides information about the current upstream and downstream signal status of your Cable Modem.

DOWNSTREAM

DownstreamBonding Channel Value
Channel ID 198  193  194  195  196  197  199  200 
Frequency 435000000 Hz  405000000 Hz  411000000 Hz  417000000 Hz  423000000 Hz  429000000 Hz  441000000 Hz  447000000 Hz 
Signal to Noise Ratio 39 dB  38 dB  38 dB  38 dB  39 dB  39 dB  39 dB  39 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
0 dBmV   0 dBmV   0 dBmV   0 dBmV   0 dBmV   0 dBmV   1 dBmV   1 dBmV  

UPSTREAM

UpstreamBonding Channel Value
Channel ID 3  1  2  4 
Frequency 29800000 Hz  18400000 Hz  23300000 Hz  36300000 Hz 
Ranging Service ID 716  716  716  716 
Symbol Rate 5.120 Msym/sec  2.560 Msym/sec  5.120 Msym/sec  5.120 Msym/sec 
Power Level 48 dBmV  46 dBmV  46 dBmV  47 dBmV 
Upstream Modulation [3] 16QAM
[3] 64QAM
 		 [3] QPSK
[2] 16QAM
[3] 64QAM
 		 [3] 16QAM
[3] 64QAM
 		 [3] 16QAM
[3] 64QAM
 
Ranging Status Aborted  Success  Aborted  Aborted 

SIGNAL STATS (CODEWORDS)

Signal Stats (Codewords)Bonding Channel Value
Channel ID 198  193  194  195  196  197  199  200 
Total Unerrored Codewords 153890536  153900602  153909316  153918382  153885570  153886921  153889413  153918299 
Total Correctable Codewords 14  0  0  0  8  9  7  18 
Total Uncorrectable Codewords 667  560  1392  1416  1586  1479  1499  1584 

Please help.

Discussions

 • 

Updated 

1.8K

3

0

0

ChrisL

Former Moderator

 • 

7.1K Messages

@ambee

I see where several were logged yesterday although all looks well now. Are you still experiencing any issues?

0

0

ambee

New Contributor

 • 

2 Messages

Good morning Chris,

It was working great early this morning but then we had another round of T3 errors which resulted in only 1/4 upstream channels being connected again.  A power-cycle of the modem did fix the issue this time though.  

Here's the most recent set of logs post power cycle:

Apr 15 2017 10:09:23 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=b8:16:19:30:24:f3;CMTS-MAC=50:57:a8:89:9f:b4;CM-QOS=1.1;CM-VER=3.0;
Apr 15 2017 10:09:23 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=b8:16:19:30:24:f3;CMTS-MAC=50:57:a8:89:9f:b4;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:24 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:30:24:f3;CMTS-MAC=50:57:a8:89:9f:b4;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:15 6-Notice N/A Cable Modem Reboot due to power reset ;CM-MAC=b8:16:19:30:24:f3;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Apr 15 2017 10:01:44 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:30:24:f3;CMTS-MAC=50:57:a8:89:9f:b4;CM-QOS=1.1;CM-VER=3.0;
Apr 15 2017 10:01:44 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=b8:16:19:30:24:f3;CMTS-MAC=50:57:a8:89:9f:b4;CM-QOS=1.1;CM-VER=3.0;
Apr 15 2017 10:01:43 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:30:24:f3;CMTS-MAC=50:57:a8:89:9f:b4;CM-QOS=1.1;CM-VER=3.0;
Apr 15 2017 10:01:43 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=b8:16:19:30:24:f3;CMTS-MAC=50:57:a8:89:9f:b4;CM-QOS=1.1;CM-VER=3.0;
Apr 15 2017 10:01:43 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:30:24:f3;CMTS-MAC=50:57:a8:89:9f:b4;CM-QOS=1.1;CM-VER=3.0;
Apr 15 2017 10:01:43 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=b8:16:19:30:24:f3;CMTS-MAC=50:57:a8:89:9f:b4;CM-QOS=1.1;CM-VER=3.0;
Apr 15 2017 10:01:43 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:30:24:f3;CMTS-MAC=50:57:a8:89:9f:b4;CM-QOS=1.1;CM-VER=3.0;
Apr 15 2017 10:01:43 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=b8:16:19:30:24:f3;CMTS-MAC=50:57:a8:89:9f:b4;CM-QOS=1.1;CM-VER=3.0;
Apr 15 2017 10:01:43 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:30:24:f3;CMTS-MAC=50:57:a8:89:9f:b4;CM-QOS=1.1;CM-VER=3.0;
Apr 15 2017 10:01:42 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=b8:16:19:30:24:f3;CMTS-MAC=50:57:a8:89:9f:b4;CM-QOS=1.1;CM-VER=3.0;
Apr 15 2017 10:01:41 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:30:24:f3;CMTS-MAC=50:57:a8:89:9f:b4;CM-QOS=1.1;CM-VER=3.0;
Apr 15 2017 10:01:41 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=b8:16:19:30:24:f3;CMTS-MAC=50:57:a8:89:9f:b4;CM-QOS=1.1;CM-VER=3.0;
Apr 15 2017 10:01:41 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:30:24:f3;CMTS-MAC=50:57:a8:89:9f:b4;CM-QOS=1.1;CM-VER=3.0;
Apr 15 2017 10:01:41 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=b8:16:19:30:24:f3;CMTS-MAC=50:57:a8:89:9f:b4;CM-QOS=1.1;CM-VER=3.0;
Apr 15 2017 10:01:40 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:30:24:f3;CMTS-MAC=50:57:a8:89:9f:b4;CM-QOS=1.1;CM-VER=3.0;
Apr 15 2017 10:01:40 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=b8:16:19:30:24:f3;CMTS-MAC=50:57:a8:89:9f:b4;CM-QOS=1.1;CM-VER=3.0;

Thank you for the help.

0

0

ChrisL

Former Moderator

 • 

7.1K Messages

@ambee

You can try bypassing any cable splitters you may have and see if that helps. Another option is to see if the modem works better on a different cable outlet. Should those ideas fail to correct the problem it may be necessary to schedule a technician to come out and troubleshoot further.

0

0

Related Content

  • Closed

    0

    0

  • Closed

    1

    0

  • Closed

    0

    0

  • Closed

    2

    0

  • Closed

    0

    0

Recent Discussions

View More

Loading...