T4 Timeout and 24mhz noise

TWC techs were out poking the tombstones in yards. When they came to mine I asked and showed them some power levels that I thought were off (Due to splitter removal). They said they were trying to track down noise- and I said "hah, I bet it's me, as it's always my fault".

 

It was. It's always my fault.

 

There was a large spike of noise around the 24mhz, and it had started 2 days prior. I just installed a new switch (cisco) at that time. I offered to reboot and unplug stuff, but no avail- once it disappeared it was gone for good.

 

Since then I've had tons of reboots and various errors. Not sure what to ask for here- somewhere I have a spare modem but I haven't hooked it up given how long it took last time to have service provision it.

 

Downstream Bonding Channel Value
Channel ID14 16 17 18 19 20 21 22 
Frequency609000000 Hz 621000000 Hz 627000000 Hz 633000000 Hz 639000000 Hz 645000000 Hz 651000000 Hz 657000000 Hz 
Signal to Noise Ratio37 dB 37 dB 38 dB 38 dB 38 dB 38 dB 38 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
10 dBmV  10 dBmV  11 dBmV  11 dBmV  11 dBmV  10 dBmV  10 dBmV  9 dBmV  

 

Upstream Bonding Channel Value
Channel ID
Frequency19400000 Hz 37000000 Hz 30600000 Hz 24200000 Hz 
Ranging Service ID14304 14304 14304 14304 
Symbol Rate2.560 Msym/sec 5.120 Msym/sec 5.120 Msym/sec 5.120 Msym/sec 
Power Level42 dBmV 43 dBmV 43 dBmV 42 dBmV 
Upstream Modulation[3] QPSK
[2] 16QAM
 
[3] QPSK
[1] 16QAM
[2] 64QAM
 
[3] QPSK
[1] 16QAM
[2] 64QAM
 
[3] QPSK
[1] 16QAM
[2] 64QAM
 
Ranging StatusSuccess Success Success Success 

 

Signal Stats (Codewords) Bonding Channel Value
Channel ID14 16 17 18 19 20 21 22 
Total Unerrored Codewords1290747756 1289769782 1289786624 1289778399 1289760371 1289761747 1289759601 1289764018 
Total Correctable Codewords34 329 19 2058 195 25 10 
Total Uncorrectable Codewords486 488 609 525 675 666 628 603 

 

Time Priority Code Message

Apr 27 2019 00:33:516-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=38:6b:bb:7f:58:60;CMTS-MAC=00:01:5c:89:86:52;CM-QOS=1.1;CM-VER=3.0;
Apr 27 2019 00:33:515-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=38:6b:bb:7f:58:60;CMTS-MAC=00:01:5c:89:86:52;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:176-NoticeN/ACable Modem Reboot due to T4 timeout ;CM-MAC=38:6b:bb:7f:58:60;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Apr 27 2019 00:32:583-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=38:6b:bb:7f:58:60;CMTS-MAC=00:01:5c:89:86:52;CM-QOS=1.1;CM-VER=3.0;
Apr 26 2019 19:31:436-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=38:6b:bb:7f:58:60;CMTS-MAC=00:01:5c:89:86:52;CM-QOS=1.1;CM-VER=3.0;
Apr 26 2019 19:31:435-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=38:6b:bb:7f:58:60;CMTS-MAC=00:01:5c:89:86:52;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:166-NoticeN/ACable Modem Reboot due to T4 timeout ;CM-MAC=38:6b:bb:7f:58:60;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Apr 26 2019 19:30:523-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=38:6b:bb:7f:58:60;CMTS-MAC=00:01:5c:89:86:52;CM-QOS=1.1;CM-VER=3.0;
Apr 26 2019 19:30:223-CriticalR05.0Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=38:6b:bb:7f:58:60;CMTS-MAC=00:01:5c:89:86:52;CM-QOS=1.1;CM-VER=3.0;
Apr 26 2019 19:29:444-ErrorC701.0DBC-ACK not received;CM-MAC=38:6b:bb:7f:58:60;CMTS-MAC=00:01:5c:89:86:52;CM-QOS=1.1;CM-VER=3.0;
Apr 26 2019 18:49:326-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=38:6b:bb:7f:58:60;CMTS-MAC=00:01:5c:89:86:52;CM-QOS=1.1;CM-VER=3.0;
Apr 26 2019 18:49:325-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=38:6b:bb:7f:58:60;CMTS-MAC=00:01:5c:89:86:52;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:166-NoticeN/ACable Modem Reboot due to T4 timeout ;CM-MAC=38:6b:bb:7f:58:60;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Apr 26 2019 18:48:403-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=38:6b:bb:7f:58:60;CMTS-MAC=00:01:5c:89:86:52;CM-QOS=1.1;CM-VER=3.0;
Apr 26 2019 18:48:103-CriticalR05.0Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=38:6b:bb:7f:58:60;CMTS-MAC=00:01:5c:89:86:52;CM-QOS=1.1;CM-VER=3.0;
Apr 26 2019 18:47:424-ErrorC701.0DBC-ACK not received;CM-MAC=38:6b:bb:7f:58:60;CMTS-MAC=00:01:5c:89:86:52;CM-QOS=1.1;CM-VER=3.0;
Apr 26 2019 18:47:423-CriticalR05.0Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=38:6b:bb:7f:58:60;CMTS-MAC=00:01:5c:89:86:52;CM-QOS=1.1;CM-VER=3.0;
Apr 26 2019 13:41:033-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=38:6b:bb:7f:58:60;CMTS-MAC=00:01:5c:89:86:52;CM-QOS=1.1;CM-VER=3.0;
Apr 26 2019 13:37:476-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=38:6b:bb:7f:58:60;CMTS-MAC=00:01:5c:89:86:52;CM-QOS=1.1;CM-VER=3.0;
Apr 26 2019 13:37:475-WarningZ00.0

MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=38:6b:bb:7f:58:60;CMTS-MAC=00:01:5c:89:86:52;CM-QOS=1.1;CM-VER=3.0;

 

Apr 26 2019 13:41:033-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=38:6b:bb:7f:58:60;CMTS-MAC=00:01:5c:89:86:52;CM-QOS=1.1;CM-VER=3.0;
Apr 26 2019 13:37:476-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=38:6b:bb:7f:58:60;CMTS-MAC=00:01:5c:89:86:52;CM-QOS=1.1;CM-VER=3.0;
Apr 26 2019 13:37:475-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=38:6b:bb:7f:58:60;CMTS-MAC=00:01:5c:89:86:52;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:166-NoticeN/ACable Modem Reboot due to T4 timeout ;CM-MAC=38:6b:bb:7f:58:60;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Apr 26 2019 13:36:573-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=38:6b:bb:7f:58:60;CMTS-MAC=00:01:5c:89:86:52;CM-QOS=1.1;CM-VER=3.0;
Apr 26 2019 12:30:153-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=38:6b:bb:7f:58:60;CMTS-MAC=00:01:5c:89:86:52;CM-QOS=1.1;CM-VER=3.0;
Apr 26 2019 12:26:523-CriticalR06.0Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=38:6b:bb:7f:58:60;CMTS-MAC=00:01:5c:89:86:52;CM-QOS=1.1;CM-VER=3.0;
Apr 26 2019 12:26:523-CriticalR03.0Ranging Request Retries exhausted;CM-MAC=38:6b:bb:7f:58:60;CMTS-MAC=00:01:5c:89:86:52;CM-QOS=1.1;CM-VER=3.0;
Apr 26 2019 12:26:273-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=38:6b:bb:7f:58:60;CMTS-MAC=00:01:5c:89:86:52;CM-QOS=1.1;CM-VER=3.0;
Apr 26 2019 11:24:233-CriticalR06.0Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=38:6b:bb:7f:58:60;CMTS-MAC=00:01:5c:89:86:52;CM-QOS=1.1;CM-VER=3.0;
Apr 26 2019 11:24:233-CriticalR03.0Ranging Request Retries exhausted;CM-MAC=38:6b:bb:7f:58:60;CMTS-MAC=00:01:5c:89:86:52;CM-QOS=1.1;CM-VER=3.0;
Apr 26 2019 11:23:573-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=38:6b:bb:7f:58:60;CMTS-MAC=00:01:5c:89:86:52;CM-QOS=1.1;CM-VER=3.0;
Apr 26 2019 11:18:563-CriticalR06.0Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=38:6b:bb:7f:58:60;CMTS-MAC=00:01:5c:89:86:52;CM-QOS=1.1;CM-VER=3.0;
Apr 26 2019 11:18:563-CriticalR03.0Ranging Request Retries exhausted;CM-MAC=38:6b:bb:7f:58:60;CMTS-MAC=00:01:5c:89:86:52;CM-QOS=1.1;CM-VER=3.0;
Apr 26 2019 11:18:313-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=38:6b:bb:7f:58:60;CMTS-MAC=00:01:5c:89:86:52;CM-QOS=1.1;CM-VER=3.0;
Apr 25 2019 16:51:213-CriticalR06.0Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=38:6b:bb:7f:58:60;CMTS-MAC=00:01:5c:89:86:52;CM-QOS=1.1;CM-VER=3.0;
Apr 25 2019 16:51:213-CriticalR03.0Ranging Request Retries exhausted;CM-MAC=38:6b:bb:7f:58:60;CMTS-MAC=00:01:5c:89:86:52;CM-QOS=1.1;CM-VER=3.0;
Apr 25 2019 16:50:563-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=38:6b:bb:7f:58:60;CMTS-MAC=00:01:5c:89:86:52;CM-QOS=1.1;CM-VER=3.0;
Apr 25 2019 16:07:026-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=38:6b:bb:7f:58:60;CMTS-MAC=00:01:5c:89:86:52;CM-QOS=1.1;CM-VER=3.0;
Apr 25 2019 16:07:025-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=38:6b:bb:7f:58:60;CMTS-MAC=00:01:5c:89:86:52;CM-QOS=1.1;CM-VER=3.0;
1 REPLY 1
Proven Sharer

Re: T4 Timeout and 24mhz noise

Sounds like they might have fixed what they came out looking for, but then created a new problem just for you (maybe a few neighbors too).  Your modem is reporting lots of both uncorrected and correctable packet frame errors on several of the assigned downstream channels.  A T4 error denotes the loss of downstream data sync on a (one or more) DS channel for more than 3 seconds.

The drops and reboots of your modem are probably caused by a loose, corroded, or broken cable connector in the pedestal feeding your drop cable.  Call them up and set up a home service call.  Tell them to come out and fix whatever they broke last week, and remember to insist on a credit on your monthly bill.