Highlighted
Not applicable

Constant T3 and T4 Timeouts

Hi Guys,

 

I would like your opinion on my logs/signal. I've been getting constant T3 and T4 Timeouts, I've had 4 techs come out in the past, they checked the wires and said everything was good. Support has said they sent refresh signals and it shouldn't happen anymore, still happening. I have even replaced my modem and still getting this issue. If you guys don't mind looking at my logs/signals and helping me out. Thanks.

 

I also have saved snips of previous logs if you need those too.

 

Time Priority Code Message
Jan 13 2018 11:58:156-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:01:5c:67:92:63;CM-QOS=1.1;CM-VER=3.0;
Jan 13 2018 11:58:155-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:01:5c:67:92:63;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:176-NoticeN/ACable Modem Reboot due to power reset ;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jan 13 2018 08:57:483-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:01:5c:67:92:63;CM-QOS=1.1;CM-VER=3.0;
Jan 13 2018 08:54:156-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:01:5c:67:92:63;CM-QOS=1.1;CM-VER=3.0;
Jan 13 2018 08:54:155-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:01:5c:67:92:63;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:176-NoticeN/ACable Modem Reboot due to T4 timeout ;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jan 13 2018 08:53:213-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:01:5c:67:92:63;CM-QOS=1.1;CM-VER=3.0;
Jan 13 2018 08:47:316-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:01:5c:67:92:63;CM-QOS=1.1;CM-VER=3.0;
Jan 13 2018 08:47:315-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:01:5c:67:92:63;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:273-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:01:5c:67:92:63;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:176-NoticeN/ACable Modem Reboot due to T4 timeout ;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jan 13 2018 08:46:303-CriticalR05.0Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:01:5c:67:92:63;CM-QOS=1.1;CM-VER=3.0;
Jan 13 2018 08:46:303-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:01:5c:67:92:63;CM-QOS=1.1;CM-VER=3.0;
Jan 13 2018 08:46:303-CriticalR06.0Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:01:5c:67:92:63;CM-QOS=1.1;CM-VER=3.0;
Jan 13 2018 08:46:303-CriticalR03.0Ranging Request Retries exhausted;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:01:5c:67:92:63;CM-QOS=1.1;CM-VER=3.0;
Jan 13 2018 08:46:293-CriticalR05.0Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:01:5c:67:92:63;CM-QOS=1.1;CM-VER=3.0;
Jan 13 2018 08:46:293-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:01:5c:67:92:63;CM-QOS=1.1;CM-VER=3.0;
Jan 13 2018 08:46:283-CriticalR05.0Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:01:5c:67:92:63;CM-QOS=1.1;CM-VER=3.0;
Jan 13 2018 08:46:283-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:01:5c:67:92:63;CM-QOS=1.1;CM-VER=3.0;

 

Downstream Bonding Channel Value
Channel ID23 24 25 26 27 28 31 32 
Frequency651000000 Hz 657000000 Hz 663000000 Hz 669000000 Hz 675000000 Hz 681000000 Hz 699000000 Hz 705000000 Hz 
Signal to Noise Ratio38 dB 38 dB 38 dB 38 dB 38 dB 38 dB 38 dB 38 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
6 dBmV  6 dBmV  6 dBmV  6 dBmV  6 dBmV  6 dBmV  6 dBmV  6 dBmV  

 

Upstream Bonding Channel Value
Channel ID42 44 43 41 
Frequency24000000 Hz 36800000 Hz 30400000 Hz 19200000 Hz 
Ranging Service ID11464 11464 11464 11464 
Symbol Rate5.120 Msym/sec 5.120 Msym/sec 5.120 Msym/sec 2.560 Msym/sec 
Power Level38 dBmV 39 dBmV 39 dBmV 38 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 ID23 24 25 26 27 28 31 32 
Total Unerrored Codewords37602136 37618443 37611145 37626638 37593026 37596214 37596616 37598058 
Total Correctable Codewords46 20 24 13 20 
Total Uncorrectable Codewords1415 1449 571 1361 1460 679 1411 1459 

 

 

 

6 REPLIES
Expert

Re: Constant T3 and T4 Timeouts

Nothing they tell you on the phone as to sending anything to the modem will fix the coaxuial issues you're having. Looks like some bad connectoions, ingress from TV ch 49-50 or 4G LTE phones.

Good luck getting TWC out, much less Spectrum to track down and repair line issues allong the streets. I assume they already replaced everything from the modem to the street.

 

Not applicable

Re: Constant T3 and T4 Timeouts

Hi MsRaye,

 

I don't have TV or Phone with Spectrum,  I only have Internet service.  If you don't mind, how do you tell there's ingress. 

 

When the techs came out they replaced my wire from my modem to the box that plugged into the side of my wall. That box seems to hold all the connections as there are more cables. Is there anything I can do or say that'll help fix this issue?

 

Thanks for helping me out.

Not applicable

Re: Constant T3 and T4 Timeouts

I got another T4. Here are the signals and logs.

 

Downstream Bonding Channel Value
Channel ID20 21 22 24 26 27 28 29 
Frequency633000000 Hz 639000000 Hz 645000000 Hz 657000000 Hz 669000000 Hz 675000000 Hz 681000000 Hz 687000000 Hz 
Signal to Noise Ratio38 dB 38 dB 38 dB 38 dB 38 dB 38 dB 38 dB 38 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
7 dBmV  7 dBmV  8 dBmV  8 dBmV  7 dBmV  7 dBmV  7 dBmV  7 dBmV  

 

Upstream Bonding Channel Value
Channel ID42 44 43 41 
Frequency24000000 Hz 36800000 Hz 30400000 Hz 19200000 Hz 
Ranging Service ID8258 8258 8258 8258 
Symbol Rate5.120 Msym/sec 5.120 Msym/sec 5.120 Msym/sec 2.560 Msym/sec 
Power Level38 dBmV 38 dBmV 38 dBmV 37 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 ID20 21 22 24 26 27 28 29 
Total Unerrored Codewords36912979 36920494 36929472 36899905 36895423 36897892 36896690 36897065 
Total Correctable Codewords13 17 14 45 21 
Total Uncorrectable Codewords654 1299 524 1456 646 632 1362 655 

 

Jan 13 2018 21:31:566-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:01:5c:67:92:63;CM-QOS=1.1;CM-VER=3.0;
Jan 13 2018 21:31:565-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:01:5c:67:92:63;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:176-NoticeN/ACable Modem Reboot due to T4 timeout ;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jan 13 2018 21:31:053-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:01:5c:67:92:63;CM-QOS=1.1;CM-VER=3.0;
Jan 13 2018 21:30:353-CriticalR05.0Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:01:5c:67:92:63;CM-QOS=1.1;CM-VER=3.0;
Jan 13 2018 21:30:004-ErrorC701.0DBC-ACK not received;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:01:5c:67:92:63;CM-QOS=1.1;CM-VER=3.0;
Jan 13 2018 11:58:156-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:01:5c:67:92:63;CM-QOS=1.1;CM-VER=3.0;
Jan 13 2018 11:58:155-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:01:5c:67:92:63;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:176-NoticeN/ACable Modem Reboot due to power reset ;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jan 13 2018 08:57:483-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:01:5c:67:92:63;CM-QOS=1.1;CM-VER=3.0;
Jan 13 2018 08:54:156-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:01:5c:67:92:63;CM-QOS=1.1;CM-VER=3.0;
Jan 13 2018 08:54:155-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:01:5c:67:92:63;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:176-NoticeN/ACable Modem Reboot due to T4 timeout ;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jan 13 2018 08:53:213-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:01:5c:67:92:63;CM-QOS=1.1;CM-VER=3.0;
Jan 13 2018 08:47:316-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:01:5c:67:92:63;CM-QOS=1.1;CM-VER=3.0;
Jan 13 2018 08:47:315-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:01:5c:67:92:63;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:273-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:01:5c:67:92:63;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:176-NoticeN/ACable Modem Reboot due to T4 timeout ;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jan 13 2018 08:46:303-CriticalR05.0Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:01:5c:67:92:63;CM-QOS=1.1;CM-VER=3.0;
Jan 13 2018 08:46:303-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:01:5c:67:92:63;CM-QOS=1.1;CM-VER=3.0;
Expert

Re: Constant T3 and T4 Timeouts

They should of replaced all the connectors inside and outside... You're getting broadcast TV ingress...  Modem has skipped over several channels due to interference.

 Something is corroded, loose, chewed up, probably outside

 

Not applicable

Re: Constant T3 and T4 Timeouts

Thanks Ms. Raye, 

 

I will contact Spectrum and hope to get this fixed. I will keep this updated.

Not applicable

Re: Constant T3 and T4 Timeouts

Hey MsRaye,

 

Called spectrum this morning and while on call my modem was resetting. Support got a tech to come out, they said there was a bent cable at my J Box that was causing the issue. I'm going to post my signal page and logs. 


Downstream Bonding Channel Value
Channel ID22 15 16 17 19 20 23 24 
Frequency645000000 Hz 603000000 Hz 609000000 Hz 615000000 Hz 627000000 Hz 633000000 Hz 651000000 Hz 657000000 Hz 
Signal to Noise Ratio38 dB 37 dB 37 dB 37 dB 38 dB 38 dB 38 dB 38 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
7 dBmV  7 dBmV  7 dBmV  7 dBmV  7 dBmV  7 dBmV  7 dBmV  7 dBmV  

 

Upstream Bonding Channel Value
Channel ID42 44 43 41 
Frequency24000000 Hz 36800000 Hz 30400000 Hz 19200000 Hz 
Ranging Service ID12286 12286 12286 12286 
Symbol Rate5.120 Msym/sec 5.120 Msym/sec 5.120 Msym/sec 2.560 Msym/sec 
Power Level38 dBmV 38 dBmV 39 dBmV 37 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 ID22 15 16 17 19 20 23 24 
Total Unerrored Codewords72845200 72854733 72860939 72838391 72835163 72837887 72867379 72832804 
Total Correctable Codewords118 21 102 21 25 40 32 62 
Total Uncorrectable Codewords1898 613 2517 601 705 626 696 1557 

 

Jan 16 2018 14:49:126-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:01:5c:67:92:63;CM-QOS=1.1;CM-VER=3.0;
Jan 16 2018 14:49:125-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:01:5c:67:92:63;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:176-NoticeN/ACable Modem Reboot due to power reset ;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:02:583-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:01:5c:67:92:63;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:01:485-WarningR09.0B-INIT-RNG Failure - Retries exceeded;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:01:5c:67:92:63;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:01:393-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:01:5c:67:92:63;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:176-NoticeN/ACable Modem Reboot due to power reset ;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:02:063-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:01:5c:67:92:63;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:01:595-WarningR09.0B-INIT-RNG Failure - Retries exceeded;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:01:5c:67:92:63;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:01:503-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:01:5c:67:92:63;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:176-NoticeN/ACable Modem Reboot due to power reset ;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:01:5c:67:92:63;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:03:033-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:01:5c:67:92:63;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:01:565-WarningR09.0B-INIT-RNG Failure - Retries exceeded;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:01:5c:67:92:63;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:01:533-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:01:5c:67:92:63;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:166-NoticeN/ACable Modem Reboot due to T4 timeout ;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jan 16 2018 14:30:093-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:01:5c:67:92:63;CM-QOS=1.1;CM-VER=3.0;
Jan 16 2018 14:29:393-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:01:5c:67:92:63;CM-QOS=1.1;CM-VER=3.0;
Jan 16 2018 14:27:426-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:01:5c:67:92:63;CM-QOS=1.1;CM-VER=3.0;
Jan 16 2018 14:27:425-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:01:5c:67:92:63;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:176-NoticeN/ACable Modem Reboot due to T4 timeout ;CM-MAC=04:4e:5a:35:d9:10;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;