Browser

Cable Modem Reboot due to T4 timeout

I've been getting random modem reboots (maybe three a day on average) for the past month or so.  I've had two techs come out.  The first removed the powered splitter that was left over from when I was paying for cable TV (I only have internet service now) and also replaced a cable down at the road that was nicked.  A few hours after he left, I had my next reboot.  Second tech came out yesterday and replaced the ground post at the box on the house, and also replaced every fitting with new fittings.  Again, not long after he left yesterday, I had another reboot and have had multiple since.

 

The second tech suggested replacing my modem (Arris SB6141) which is almost three years old.  The cable from the house to the modem is a straight shot (no splitters).  Both techs checked the signals and said they're good.

 

Should I buy a new modem and see if that helps?

 

TimePriorityCodeMessage

Nov 24 2017 09:43:455-WarningT07.0RCS Partial Service;CM-MAC=d0:39:b3:f8:cf:8e;CMTS-MAC=00:17:10:8b:90:16;CM-QOS=1.1;CM-VER=3.0;
Nov 24 2017 09:43:446-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=d0:39:b3:f8:cf:8e;CMTS-MAC=00:17:10:8b:90:16;CM-QOS=1.1;CM-VER=3.0;
Nov 24 2017 09:43:445-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=d0:39:b3:f8:cf:8e;CMTS-MAC=00:17:10:8b:90:16;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:176-NoticeN/ACable Modem Reboot due to T4 timeout ;CM-MAC=d0:39:b3:f8:cf:8e;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Nov 24 2017 09:42:533-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=d0:39:b3:f8:cf:8e;CMTS-MAC=00:17:10:8b:90:16;CM-QOS=1.1;CM-VER=3.0;
Nov 24 2017 09:42:485-WarningT202.0Lost MDD Timeout;CM-MAC=d0:39:b3:f8:cf:8e;CMTS-MAC=00:17:10:8b:90:16;CM-QOS=1.1;CM-VER=3.0;
Nov 24 2017 09:42:463-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=d0:39:b3:f8:cf:8e;CMTS-MAC=00:17:10:8b:90:16;CM-QOS=1.1;CM-VER=3.0;
Nov 24 2017 09:42:253-CriticalT05.0SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=d0:39:b3:f8:cf:8e;CMTS-MAC=00:17:10:8b:90:16;CM-QOS=1.1;CM-VER=3.0;
Nov 24 2017 09:37:565-WarningT202.0Lost MDD Timeout;CM-MAC=d0:39:b3:f8:cf:8e;CMTS-MAC=00:17:10:8b:90:16;CM-QOS=1.1;CM-VER=3.0;
Nov 24 2017 09:37:565-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=d0:39:b3:f8:cf:8e;CMTS-MAC=00:17:10:8b:90:16;CM-QOS=1.1;CM-VER=3.0;
Nov 24 2017 09:30:426-NoticeN/AMDD Recovery following MDD Loss;CM-MAC=d0:39:b3:f8:cf:8e;CMTS-MAC=00:17:10:8b:90:16;CM-QOS=1.1;CM-VER=3.0;
Nov 24 2017 09:30:395-WarningT202.0Lost MDD Timeout;CM-MAC=d0:39:b3:f8:cf:8e;CMTS-MAC=00:17:10:8b:90:16;CM-QOS=1.1;CM-VER=3.0;
Nov 24 2017 09:30:395-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=d0:39:b3:f8:cf:8e;CMTS-MAC=00:17:10:8b:90:16;CM-QOS=1.1;CM-VER=3.0;
Nov 24 2017 09:30:146-NoticeN/AMDD Recovery following MDD Loss;CM-MAC=d0:39:b3:f8:cf:8e;CMTS-MAC=00:17:10:8b:90:16;CM-QOS=1.1;CM-VER=3.0;
Nov 24 2017 09:30:105-WarningT202.0Lost MDD Timeout;CM-MAC=d0:39:b3:f8:cf:8e;CMTS-MAC=00:17:10:8b:90:16;CM-QOS=1.1;CM-VER=3.0;
Nov 24 2017 09:30:105-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=d0:39:b3:f8:cf:8e;CMTS-MAC=00:17:10:8b:90:16;CM-QOS=1.1;CM-VER=3.0;
Nov 24 2017 09:29:456-NoticeN/AMDD Recovery following MDD Loss;CM-MAC=d0:39:b3:f8:cf:8e;CMTS-MAC=00:17:10:8b:90:16;CM-QOS=1.1;CM-VER=3.0;
Nov 24 2017 09:27:385-WarningT202.0Lost MDD Timeout;CM-MAC=d0:39:b3:f8:cf:8e;CMTS-MAC=00:17:10:8b:90:16;CM-QOS=1.1;CM-VER=3.0;
Nov 24 2017 09:27:385-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=d0:39:b3:f8:cf:8e;CMTS-MAC=00:17:10:8b:90:16;CM-QOS=1.1;CM-VER=3.0;
Nov 24 2017 09:27:136-NoticeN/AMDD Recovery following MDD Loss;CM-MAC=d0:39:b3:f8:cf:8e;CMTS-MAC=00:17:10:8b:90:16;CM-QOS=1.1;CM-VER=3.0;

 

Downstream Bonding Channel Value
Channel ID10 11 12 13 15 16 
Frequency507000000 Hz 513000000 Hz 519000000 Hz 525000000 Hz 531000000 Hz 543000000 Hz 549000000 Hz 
Signal to Noise Ratio38 dB 38 dB 38 dB 36 dB 29 dB 31 dB 35 dB 
Downstream ModulationQAM256 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
3 dBmV  2 dBmV  0 dBmV  -2 dBmV  -7 dBmV  -6 dBmV  -2 dBmV  

 

Upstream Bonding Channel Value
Channel ID
Frequency37000000 Hz 19400000 Hz 30600000 Hz 24200000 Hz 
Ranging Service ID5952 5952 5952 5952 
Symbol Rate2.560 Msym/sec 2.560 Msym/sec 5.120 Msym/sec 5.120 Msym/sec 
Power Level39 dBmV 37 dBmV 38 dBmV 37 dBmV 
Upstream Modulation[3] QPSK
[1] 16QAM
[2] 64QAM
 
[3] QPSK
[2] 16QAM
 
[3] QPSK
[1] 16QAM
[2] 64QAM
 
[3] QPSK
[1] 16QAM
[2] 64QAM
 
Ranging StatusSuccess Success Success Success 

 

Signal Stats (Codewords)Bonding Channel Value
Channel ID10 11 12 13 15 16 
Total Unerrored Codewords50149102 49307744 49321447 49330010 49078303 48975301 49306101 
Total Correctable Codewords27 222684 322856 123 
Total Uncorrectable Codewords1258 1417 1320 1421 4881 3623 947 
17 REPLIES
Browser

Re: Cable Modem Reboot due to T4 timeout

More information about my environment... single family home in Apex, NC.  Paying for only internet (100/10).

 

Modem information:

 

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

Browser

Re: Cable Modem Reboot due to T4 timeout

Already have another reboot :-(  

 

Any help greatly appreciated!  I've read some posts that imply there may be problems with the SB6141 power supply?

 

Nov 24 2017 10:31:575-WarningT07.0RCS Partial Service;CM-MAC=d0:39:b3:f8:cf:8e;CMTS-MAC=00:17:10:8b:90:16;CM-QOS=1.1;CM-VER=3.0;
Nov 24 2017 10:31:556-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=d0:39:b3:f8:cf:8e;CMTS-MAC=00:17:10:8b:90:16;CM-QOS=1.1;CM-VER=3.0;
Nov 24 2017 10:31:555-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=d0:39:b3:f8:cf:8e;CMTS-MAC=00:17:10:8b:90:16;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:176-NoticeN/ACable Modem Reboot due to T4 timeout ;CM-MAC=d0:39:b3:f8:cf:8e;CMTS-MAC=00:17:10:8b:90:16;CM-QOS=1.1;CM-VER=3.0;
Nov 24 2017 10:31:043-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=d0:39:b3:f8:cf:8e;CMTS-MAC=00:17:10:8b:90:16;CM-QOS=1.1;CM-VER=3.0;
Nov 24 2017 10:30:595-WarningT202.0Lost MDD Timeout;CM-MAC=d0:39:b3:f8:cf:8e;CMTS-MAC=00:17:10:8b:90:16;CM-QOS=1.1;CM-VER=3.0;
Nov 24 2017 10:30:563-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=d0:39:b3:f8:cf:8e;CMTS-MAC=00:17:10:8b:90:16;CM-QOS=1.1;CM-VER=3.0;
Nov 24 2017 10:30:363-CriticalT05.0SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=d0:39:b3:f8:cf:8e;CMTS-MAC=00:17:10:8b:90:16;CM-QOS=1.1;CM-VER=3.0;
Nov 24 2017 10:25:585-WarningT202.0Lost MDD Timeout;CM-MAC=d0:39:b3:f8:cf:8e;CMTS-MAC=00:17:10:8b:90:16;CM-QOS=1.1;CM-VER=3.0;
Nov 24 2017 10:25:585-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=d0:39:b3:f8:cf:8e;CMTS-MAC=00:17:10:8b:90:16;CM-QOS=1.1;CM-VER=3.0;
Nov 24 2017 10:25:086-NoticeN/AMDD Recovery following MDD Loss;CM-MAC=d0:39:b3:f8:cf:8e;CMTS-MAC=00:17:10:8b:90:16;CM-QOS=1.1;CM-VER=3.0;
Nov 24 2017 10:24:595-WarningT202.0Lost MDD Timeout;CM-MAC=d0:39:b3:f8:cf:8e;CMTS-MAC=00:17:10:8b:90:16;CM-QOS=1.1;CM-VER=3.0;
Nov 24 2017 10:24:595-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=d0:39:b3:f8:cf:8e;CMTS-MAC=00:17:10:8b:90:16;CM-QOS=1.1;CM-VER=3.0;

 

 

Expert

Re: Cable Modem Reboot due to T4 timeout

Not the modem, you have a bad connection somewhere allowing ingress from local tv channels 24 & 26..., probably 25 as well. 

What's your zip code, need to look it up in Antennaweb.org or tvfool.com...

Is the line overhead and run thru trees? If so it's probably chewed up.

Browser

Re: Cable Modem Reboot due to T4 timeout

Thanks much for the reply!  Zip is 27539.  I'm not sure what local channels 24-26 would be.  I know we have OTA channels 22 and 28 locally.  The line from the road is a pretty long run that goes from the road all the way around the back side of our house to the other side; probably at least 300 feet.  Years ago they replaced the line with one of those really fat cables (maybe 3/4 inch OD?) that terminates at the box, where it's spliced to a "normal" coax cable.  And yes, we're on a very wooded lot and the cable runs through a fair amount of wooded area before it arrives at my back lawn.

 

So it's really not worth trying another modem?  Again, I've had two techs out and they tell me the signal is good, but after they leave I continue to get the same errors showing up on my modem.

 

Thanks again for your support.

Browser

Re: Cable Modem Reboot due to T4 timeout

Hmm... one other thing to note is that AT&T just came through within the last six months and buried fiber lines; they're offering gigabit service in our neighborhood now.  May be an option if this issue can't be resolved!  At any rate, I wonder if they could have nicked something down by the road?  How would that kind of issue get tracked down?

Browser

Re: Cable Modem Reboot due to T4 timeout

Here's the latest stats

 

Channel ID10 11 12 13 14 15 16 
Frequency507000000 Hz 513000000 Hz 519000000 Hz 525000000 Hz 531000000 Hz 537000000 Hz 543000000 Hz 549000000 Hz 
Signal to Noise Ratio38 dB 39 dB 38 dB 38 dB 37 dB 35 dB 32 dB 27 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
4 dBmV  3 dBmV  3 dBmV  2 dBmV  0 dBmV  -1 dBmV  -6 dBmV  -13 dBmV  

 

Upstream Bonding Channel Value
Channel ID
Frequency37000000 Hz 19400000 Hz 30600000 Hz 24200000 Hz 
Ranging Service ID3786 3786 3786 3786 
Symbol Rate2.560 Msym/sec 2.560 Msym/sec 5.120 Msym/sec 5.120 Msym/sec 
Power Level39 dBmV 37 dBmV 38 dBmV 37 dBmV 
Upstream Modulation[3] QPSK
[1] 16QAM
[2] 64QAM
 
[3] QPSK
[2] 16QAM
 
[3] QPSK
[1] 16QAM
[2] 64QAM
 
[3] QPSK
[1] 16QAM
[2] 64QAM
 
Ranging StatusSuccess Success Success Success 

 

 Signal Stats (Codewords)Bonding Channel Value

Channel ID10 11 12 13 14 15 16 
Total Unerrored Codewords869345611 868593566 868574412 868599483 868565439 824654713 461592669 334157003 
Total Correctable Codewords592 1148 1201 462292 1072206 245788768 
Total Uncorrectable Codewords1450 1415 2257 2541 2601 70966 131218 288628719 

 

Nov 24 2017 23:12:406-NoticeN/AMDD Recovery following MDD Loss;CM-MAC=d0:39:b3:f8:cf:8e;CMTS-MAC=00:17:10:8b:90:16;CM-QOS=1.1;CM-VER=3.0;
Nov 24 2017 23:12:235-WarningT202.0Lost MDD Timeout;CM-MAC=d0:39:b3:f8:cf:8e;CMTS-MAC=00:17:10:8b:90:16;CM-QOS=1.1;CM-VER=3.0;
Nov 24 2017 23:12:225-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=d0:39:b3:f8:cf:8e;CMTS-MAC=00:17:10:8b:90:16;CM-QOS=1.1;CM-VER=3.0;
Nov 24 2017 23:08:596-NoticeN/AMDD Recovery following MDD Loss;CM-MAC=d0:39:b3:f8:cf:8e;CMTS-MAC=00:17:10:8b:90:16;CM-QOS=1.1;CM-VER=3.0;
Nov 24 2017 23:08:495-WarningT202.0Lost MDD Timeout;CM-MAC=d0:39:b3:f8:cf:8e;CMTS-MAC=00:17:10:8b:90:16;CM-QOS=1.1;CM-VER=3.0;
Nov 24 2017 23:08:495-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=d0:39:b3:f8:cf:8e;CMTS-MAC=00:17:10:8b:90:16;CM-QOS=1.1;CM-VER=3.0;
Nov 24 2017 23:07:276-NoticeN/AMDD Recovery following MDD Loss;CM-MAC=d0:39:b3:f8:cf:8e;CMTS-MAC=00:17:10:8b:90:16;CM-QOS=1.1;CM-VER=3.0;
Nov 24 2017 23:07:185-WarningT202.0Lost MDD Timeout;CM-MAC=d0:39:b3:f8:cf:8e;CMTS-MAC=00:17:10:8b:90:16;CM-QOS=1.1;CM-VER=3.0;
Nov 24 2017 23:07:185-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=d0:39:b3:f8:cf:8e;CMTS-MAC=00:17:10:8b:90:16;CM-QOS=1.1;CM-VER=3.0;
Nov 24 2017 23:06:316-NoticeN/AMDD Recovery following MDD Loss;CM-MAC=d0:39:b3:f8:cf:8e;CMTS-MAC=00:17:10:8b:90:16;CM-QOS=1.1;CM-VER=3.0;
Nov 24 2017 23:06:315-WarningT202.0Lost MDD Timeout;CM-MAC=d0:39:b3:f8:cf:8e;CMTS-MAC=00:17:10:8b:90:16;CM-QOS=1.1;CM-VER=3.0;
Nov 24 2017 23:06:305-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=d0:39:b3:f8:cf:8e;CMTS-MAC=00:17:10:8b:90:16;CM-QOS=1.1;CM-VER=3.0;
Nov 24 2017 23:06:056-NoticeN/AMDD Recovery following MDD Loss;CM-MAC=d0:39:b3:f8:cf:8e;CMTS-MAC=00:17:10:8b:90:16;CM-QOS=1.1;CM-VER=3.0;
Nov 24 2017 23:05:365-WarningT202.0Lost MDD Timeout;CM-MAC=d0:39:b3:f8:cf:8e;CMTS-MAC=00:17:10:8b:90:16;CM-QOS=1.1;CM-VER=3.0;
Nov 24 2017 23:05:365-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=d0:39:b3:f8:cf:8e;CMTS-MAC=00:17:10:8b:90:16;CM-QOS=1.1;CM-VER=3.0;
Nov 24 2017 23:04:596-NoticeN/AMDD Recovery following MDD Loss;CM-MAC=d0:39:b3:f8:cf:8e;CMTS-MAC=00:17:10:8b:90:16;CM-QOS=1.1;CM-VER=3.0;
Nov 24 2017 23:04:295-WarningT202.0Lost MDD Timeout;CM-MAC=d0:39:b3:f8:cf:8e;CMTS-MAC=00:17:10:8b:90:16;CM-QOS=1.1;CM-VER=3.0;
Nov 24 2017 23:04:295-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=d0:39:b3:f8:cf:8e;CMTS-MAC=00:17:10:8b:90:16;CM-QOS=1.1;CM-VER=3.0;
Nov 24 2017 23:04:046-NoticeN/AMDD Recovery following MDD Loss;CM-MAC=d0:39:b3:f8:cf:8e;CMTS-MAC=00:17:10:8b:90:16;CM-QOS=1.1;CM-VER=3.0;
Nov 24 2017 23:03:385-WarningT202.0Lost MDD Timeout;CM-MAC=d0:39:b3:f8:cf:8e;CMTS-MAC=00:17:10:8b:90:16;CM-QOS=1.1;CM-VER=3.0;
Expert

Re: Cable Modem Reboot due to T4 timeout

 Looks like broken/ loose/ corroded connections 0or chewed up coax:

Your actual channels...:

WTVD-DT 11.1 ABC
RF Channel: 11
13 miles at 103°
Yellow 
WUNC-DT 4.1 PBS
RF Channel: 25
26 miles at 308°
Yellow 
WAUG-LD 8.1 IND
RF Channel: 8
11 miles at 55°
Yellow 
WRAL-DT 5.1 NBC
RF Channel: 48
13 miles at 101°
Yellow 
WRAY-DT 30.1 SAH
RF Channel: 42
36 miles at 82°
Yellow 
WRAZ-DT 50.1 FOX
RF Channel: 49
13 miles at 101°
Yellow 
WRDC-DT 28.1 MNT
RF Channel: 28
13 miles at 101°
Yellow 
WNCN-DT 17.1 CBS
RF Channel: 17
13 miles at 101°
Yellow 
WUVC-DT 40.1 UNI
RF Channel: 38
17 miles at 236°
Yellow 
WLFL-DT 22.1 CW
RF Channel: 27
13 miles at 101°
Yellow 
WACN-LP REL
RF Channel: 34
13 miles at 101°
Green 
WWIW-LD 66.1 REL
RF Channel: 45
9 miles at 55°
Green 
WARZ-CD 34.1 IND
RF Channel: 34
13 miles at 101°
LtGreen 
WRPX-DT 47.1 ION
RF Channel: 15
43 miles at 56°
Red 
WFMY-DT 2.1 CBS
RF Channel: 51
62 miles at 292°
Red 
W46EU-D 46.1 HSN
RF Channel: 46
4 miles at 313°
Red 
W24CP-D 24.1 3ABN
RF Channel: 24
26 miles at 309°
Red 
WZGS-CD 44.1 IND
RF Channel: 44
8 miles at 23°
Red 
WXLV-DT 45.1 ABC
RF Channel: 29
61 miles at 292°
Blue 
WIRP-LD 27.1 IND
RF Channel: 22
26 miles at 309°
Blue 
WTNC-LD 26.1 TFA
RF Channel: 40
28 miles at 347°
Blue 
WGHP-DT 8.1 FOX
RF Channel: 35
61 miles at 288°
Blue 
WMYV-DT 48.1 MNT
RF Channel: 33
61 miles at 292°
Blue 
WITN-DT 7.1 NBC
RF Channel: 32
80 miles at 115°
Violet 
WUNK-DT 25.1 PBS
RF Channel: 23
66 miles at 107°
Violet 
WUNC-LD 4.1 PBS
RF Channel: 30
13 miles at 101°
Violet 
WLXI-DT 43.1 TCT
RF Channel: 43
61 miles at 292°
Violet 

 

Established Sharer

Re: Cable Modem Reboot due to T4 timeout

I think I am also seeing either an old 'no premiums' rolloff filter or effects of an open length of drop line on either the local tap or slightly upstream.  The DS signal level starts to decline quickly above DS12 at 525 MHz.  Definitely is a cable plant issue, not your modem.

Browser

Re: Cable Modem Reboot due to T4 timeout

MsRaye and karlbeckman, thanks for your input.  How do I go about convincing TWC (Spectrum) that I have a cable issue and get the issue resolved?  Two tech trips and so far no results.  Both were very nice guys, but the problem persists.  Do I just keep getting techs out here (squeeky wheel approach) or is there a better way to get the "right" person out to correct the problem?  And what is the fix?  Do they need to bury a new cable run from the street to the house?