Highlighted
Rookie

Multiple T3 and T4 Timeouts Occurring in Short Bursts

I'm getting mutiple T3 and T4 timeouts. They come in bursts, where I'll get like 5 or 6 in an hour and then it will be good for a few hours and then it'll start up again.

 

Of course I've googled every error in the log and poured through these forums but every scenerio seems to be sort of unique, and no fixes that I have seen have done the trick so hopefully someone can help or offer advice. I've tried contacting support and they "sent signals" to my modem and have "tried altering the settings".  That did nothing. Then a tech came out amd said he can't do anything because I have my own modem and router configeration. He barely looked around at all, said "you're probably bottlnecking and need a new modem" and then left. So I'm less than convinced with that answer.  I mean, maybe he's right but I wasn't sold.

 

I'm using an ARRIS SURFboard SB6141 and an ASUS RT-N66U, if it helps. Thanks to anyone who can help or offer some advice. This has been going on for a few weeks and it's getting out of control. 

 

Here are my logs and signals:

Apr 16 2018 23:27:386-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=20:3d:66:06:05:ba;CMTS-MAC=00:01:5c:67:f8:4a;CM-QOS=1.1;CM-VER=3.0;
Apr 16 2018 23:27:385-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=20:3d:66:06:05:ba;CMTS-MAC=00:01:5c:67:f8:4a;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:233-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=20:3d:66:06:05:ba;CMTS-MAC=00:01:5c:67:f8:4a;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:176-NoticeN/ACable Modem Reboot due to T4 timeout ;CM-MAC=20:3d:66:06:05:ba;CMTS-MAC=00:01:5c:67:f8:4a;CM-QOS=1.1;CM-VER=3.0;
Apr 16 2018 23:26:493-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=20:3d:66:06:05:ba;CMTS-MAC=00:01:5c:67:f8:4a;CM-QOS=1.1;CM-VER=3.0;
Apr 16 2018 23:12:256-NoticeI502.0Received REG-RSP while in REG-HOLD1 state;CM-MAC=20:3d:66:06:05:ba;CMTS-MAC=00:01:5c:67:f8:4a;CM-QOS=1.1;CM-VER=3.0;
Apr 16 2018 23:12:225-WarningU102.0TCS Partial Service;CM-MAC=20:3d:66:06:05:ba;CMTS-MAC=00:01:5c:67:f8:4a;CM-QOS=1.1;CM-VER=3.0;
Apr 16 2018 23:12:225-WarningU103.0Initializing Channel Timeout Expires - Time the CM can perform initial ranging on all upstream channels in the TCS has expired;CM-MAC=20:3d:66:06:05:ba;CMTS-MAC=00:01:5c:67:f8:4a;CM-QOS=1.1;CM-VER=3.0;
Apr 16 2018 23:11:553-CriticalR06.0Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=20:3d:66:06:05:ba;CMTS-MAC=00:01:5c:67:f8:4a;CM-QOS=1.1;CM-VER=3.0;
Apr 16 2018 23:11:543-CriticalR03.0Ranging Request Retries exhausted;CM-MAC=20:3d:66:06:05:ba;CMTS-MAC=00:01:5c:67:f8:4a;CM-QOS=1.1;CM-VER=3.0;
Apr 16 2018 23:11:533-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=20:3d:66:06:05:ba;CMTS-MAC=00:01:5c:67:f8:4a;CM-QOS=1.1;CM-VER=3.0;
Apr 16 2018 23:11:226-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=20:3d:66:06:05:ba;CMTS-MAC=00:01:5c:67:f8:4a;CM-QOS=1.1;CM-VER=3.0;
Apr 16 2018 23:11:225-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=20:3d:66:06:05:ba;CMTS-MAC=00:01:5c:67:f8:4a;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:176-NoticeN/ACable Modem Reboot due to T4 timeout ;CM-MAC=20:3d:66:06:05:ba;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Apr 16 2018 23:10:343-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=20:3d:66:06:05:ba;CMTS-MAC=00:01:5c:67:f8:4a;CM-QOS=1.1;CM-VER=3.0;
Apr 16 2018 23:09:375-WarningU102.0TCS Partial Service;CM-MAC=20:3d:66:06:05:ba;CMTS-MAC=00:01:5c:67:f8:4a;CM-QOS=1.1;CM-VER=3.0;
Apr 16 2018 23:09:375-WarningU103.0Initializing Channel Timeout Expires - Time the CM can perform initial ranging on all upstream channels in the TCS has expired;CM-MAC=20:3d:66:06:05:ba;CMTS-MAC=00:01:5c:67:f8:4a;CM-QOS=1.1;CM-VER=3.0;
Apr 16 2018 23:08:366-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=20:3d:66:06:05:ba;CMTS-MAC=00:01:5c:67:f8:4a;CM-QOS=1.1;CM-VER=3.0;
Apr 16 2018 23:08:365-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=20:3d:66:06:05:ba;CMTS-MAC=00:01:5c:67:f8:4a;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:176-NoticeN/ACable Modem Reboot due to T4 timeout ;CM-MAC=20:3d:66:06:05:ba;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

 

Channel ID15 16 17 18 20 21 22 24 
Frequency711000000 Hz 717000000 Hz 723000000 Hz 729000000 Hz 741000000 Hz 747000000 Hz 753000000 Hz 765000000 Hz 
Signal to Noise Ratio37 dB 37 dB 37 dB 37 dB 37 dB 37 dB 37 dB 37 dB 
Downstream ModulationQAM256 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  0 dBmV  0 dBmV  1 dBmV  0 dBmV  1 dBmV  1 dBmV  

 

Upstream Bonding Channel Value
Channel ID34 36 35 33 
Frequency24200000 Hz 37000000 Hz 30600000 Hz 19400000 Hz 
Ranging Service ID14330 14330 14330 14330 
Symbol Rate5.120 Msym/sec 2.560 Msym/sec 5.120 Msym/sec 2.560 Msym/sec 
Power Level50 dBmV 51 dBmV 51 dBmV 51 dBmV 
Upstream Modulation[3] QPSK
[1] 16QAM
[2] 64QAM
 
[3] QPSK
[1] 16QAM
[2] 64QAM
 
[3] QPSK
[1] 16QAM
[2] 64QAM
 
[3] QPSK
[2] 16QAM
 
Ranging StatusSuccess Success Success Success 

 

Signal Stats (Codewords) Bonding Channel Value
Channel ID15 16 17 18 20 21 22 24 
Total Unerrored Codewords38529012 38537325 38553723 38545540 38518707 38523399 38524383 38520355 
Total Correctable Codewords27 53 12 11 17 
Total Uncorrectable Codewords1573 1379 1365 1371 1531 1592 1606 1575 
2 REPLIES
Community Manager

Re: Multiple T3 and T4 Timeouts Occurring in Short Bursts

@andrewsd

 

We apologize for any service issues. T3 and T4 errors do require a technician.  We would suggest having another technician out.  For assistance, we encourage you to contact our Social Media Customer Care team:

 

Twitter: @Ask_Spectrum
Facebook: https://www.facebook.com/Spectrum

 

 

Spectrum-Social Media Customer Care

Established Sharer

Re: Multiple T3 and T4 Timeouts Occurring in Short Bursts

As @James_M suggested, you do need a tech visit to locate and repair the cause of those T3 and T4 signal failures, which means that your modem lost signal from the head-end for three or more seconds each time. 

I see that the levels of all four uplink channels are extremely high.   You also have higher than normal (but not fatal) counts of incoming uncorrectible packet data errors.  The combination suggests too much loss in your home cabling or a bad drop cable outdoors.  Could also be caused by a loose cable connector outdoors that intermittently vibrates in high winds or when a big truck drives by. 

The internet modem must be connected directly to the incoming drop cable unless you pay for both TV and internet.  If you do subscribe to both, the modem connects to one port of a two-way splitter fed by the drop cable, and the second port goes to your set-top converter or DVR.  No customer-installed 4-way splitters or inline booster amplifiers are recommended for this application.