Highlighted
Rookie

t4 errors and connection drops.

Having a ton of resets lately.  Modem is only a year or two old so Im not sure its it. Its very random. I logged into the modem and it drops a lot. Does this look like the line or the modem?  I only have it coming out of the wall to a 2 way spiitter so it can go to my TV 

 

Model Name: SB6141
Vendor Name: ARRIS Group, Inc. 
Firmware Name: SB_KOMODO-1.0.7.0-SCM00-NOSH
Boot Version: PSPU-Boot(25CLK)(W) 1.0.12.18m5
Hardware Version: 8.0
Serial Number: 397179526629317301012022
Firmware Build Time: Jul 22 2016 08:13:57

 

 

Seeing lots of errors in my log 

May 02 2018 19:18:246-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=10:05:b1:f7:2c:39;CMTS-MAC=00:01:5c:92:0a:64;CM-QOS=1.1;CM-VER=3.0;
May 02 2018 19:18:245-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=10:05:b1:f7:2c:39;CMTS-MAC=00:01:5c:92:0a:64;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:176-NoticeN/ACable Modem Reboot due to power reset ;CM-MAC=10:05:b1:f7:2c:39;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
May 02 2018 19:16:353-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:05:b1:f7:2c:39;CMTS-MAC=00:01:5c:92:0a:64;CM-QOS=1.1;CM-VER=3.0;
May 02 2018 19:16:325-WarningT202.0Lost MDD Timeout;CM-MAC=10:05:b1:f7:2c:39;CMTS-MAC=00:01:5c:92:0a:64;CM-QOS=1.1;CM-VER=3.0;
May 02 2018 19:16:303-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:05:b1:f7:2c:39;CMTS-MAC=00:01:5c:92:0a:64;CM-QOS=1.1;CM-VER=3.0;
May 02 2018 19:16:295-WarningT202.0Lost MDD Timeout;CM-MAC=10:05:b1:f7:2c:39;CMTS-MAC=00:01:5c:92:0a:64;CM-QOS=1.1;CM-VER=3.0;
May 02 2018 19:16:295-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=10:05:b1:f7:2c:39;CMTS-MAC=00:01:5c:92:0a:64;CM-QOS=1.1;CM-VER=3.0;
May 02 2018 19:16:233-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:05:b1:f7:2c:39;CMTS-MAC=00:01:5c:92:0a:64;CM-QOS=1.1;CM-VER=3.0;
May 02 2018 19:16:073-CriticalT05.0SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=10:05:b1:f7:2c:39;CMTS-MAC=00:01:5c:92:0a:64;CM-QOS=1.1;CM-VER=3.0;
May 02 2018 17:07:393-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=10:05:b1:f7:2c:39;CMTS-MAC=00:01:5c:92:0a:64;CM-QOS=1.1;CM-VER=3.0;
Apr 30 2018 11:30:546-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=10:05:b1:f7:2c:39;CMTS-MAC=00:01:5c:92:0a:64;CM-QOS=1.1;CM-VER=3.0;
Apr 30 2018 11:30:545-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=10:05:b1:f7:2c:39;CMTS-MAC=00:01:5c:92:0a:64;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:176-NoticeN/ACable Modem Reboot due to T4 timeout ;CM-MAC=10:05:b1:f7:2c:39;CMTS-MAC=00:01:5c:92:0a:64;CM-QOS=1.1;CM-VER=3.0;
Apr 30 2018 11:30:033-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:05:b1:f7:2c:39;CMTS-MAC=00:01:5c:92:0a:64;CM-QOS=1.1;CM-VER=3.0;
Apr 30 2018 11:29:333-CriticalR05.0Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:05:b1:f7:2c:39;CMTS-MAC=00:01:5c:92:0a:64;CM-QOS=1.1;CM-VER=3.0;
Apr 30 2018 11:28:564-ErrorC701.0DBC-ACK not received;CM-MAC=10:05:b1:f7:2c:39;CMTS-MAC=00:01:5c:92:0a:64;CM-QOS=1.1;CM-VER=3.0;
Apr 30 2018 11:28:553-CriticalR05.0Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:05:b1:f7:2c:39;CMTS-MAC=00:01:5c:92:0a:64;CM-QOS=1.1;CM-VER=3.0;
Apr 28 2018 20:07:296-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=10:05:b1:f7:2c:39;CMTS-MAC=00:01:5c:92:0a:64;CM-QOS=1.1;CM-VER=3.0;
Apr 28 2018 20:07:295-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=10:05:b1:f7:2c:39;CMTS-MAC=00:01:5c:92:0a:64;CM-QOS=1.1;CM-VER=3.0;

 

Downstream Bonding Channel Value
Channel ID10 11 
Frequency657000000 Hz 633000000 Hz 639000000 Hz 645000000 Hz 651000000 Hz 663000000 Hz 669000000 Hz 675000000 Hz 
Signal to Noise Ratio35 dB 35 dB 35 dB 35 dB 35 dB 36 dB 35 dB 35 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  -9 dBmV  -10 dBmV  -10 dBmV  -10 dBmV  -10 dBmV  -11 dBmV  -11 dBmV  

 

Upstream Bonding Channel Value
Channel ID50 52 51 49 
Frequency24200000 Hz 37000000 Hz 30600000 Hz 19400000 Hz 
Ranging Service ID14333 14333 14333 14333 
Symbol Rate5.120 Msym/sec 5.120 Msym/sec 5.120 Msym/sec 2.560 Msym/sec 
Power Level43 dBmV 44 dBmV 43 dBmV 44 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 ID10 11 
Total Unerrored Codewords2649603433 2649611070 2649606360 2649637222 2649594886 2649595766 2649597640 2649598717 
Total Correctable Codewords364 8581 5022 311 340 324 349 360 
Total Uncorrectable Codewords1565 2451 2551 1402 1459 1619 1543 1452 
1 REPLY 1
Proven Sharer

Re: t4 errors and connection drops.

Your modem reports that the incoming signal level is too low (it should be between -8.0 to +10.0 dBmV) and it may also have excessive noise, indicated by the high number of uncorrectable packet errors on most of the incoming (DS) channels.  You need  a Spectrum home service tech to visit and investigate. 

Typical causes are a drop cable whose protective jacket has worn away where it rubs against a tree branch, or a loose overhead cable connector somewhere along the route.  Or it could be the other classic NO-NO:  A (unneeded) splitter with an unterminated port or a dead-end cable (not connected to a device at the far end).