Participant

Re: Cable Modem Reboot due to T4 timeout

Any suggestions on the best way to get action on this issue?

Expert

Re: Cable Modem Reboot due to T4 timeout

Did they replace the connectors and grounding block? Is the pedestal open, can you get a photo of what's inside it?

Have you verified there's nothing else in line from the grounding block to the modem?

 

Participant

Re: Cable Modem Reboot due to T4 timeout

I don't have pictures, but the second tech told me that he replaced everything in the box attached to the house, including the grounding block and all connectors.  I believe there are three connections in the box, but all connectors are new.  I'll see if I can't post a picture if I can get into the box.

 

The line from that runs to the modem is (to my knowledge) a direct connection, albeit a fairly long run (probably over 50 feet).

Participant

Re: Cable Modem Reboot due to T4 timeout

Ok, here's the picture of the inside of the box.  As you can see, everything looks shiny new!  Would this seem to imply the issue is down at the road?

 

You should be able to view the picture at http://tinypic.com/r/33nzxc9/9

Expert

Re: Cable Modem Reboot due to T4 timeout

Yeah that's all new... good luck, problem is probably one or more houses on the node with bad connectors.

 

Participant

Re: Cable Modem Reboot due to T4 timeout

So there's really nothing I can do to address this with Spectrum?  It's really frustrating having my connection drop multiple times a day.  Could it be an issue on the line from the road to the house?

 

How may houses would normally be on a "node"?  Should I request that Spectrum examine connections to nearby homes?

 

Thanks for your advice.

Expert

Re: Cable Modem Reboot due to T4 timeout

It could be that cable or the connector/ jumper out at the street pedestal, but I assume they replaced them when they did the box on the house.

 

Participant

Re: Cable Modem Reboot due to T4 timeout

The first tech told me he'd replaced a jumper at the street that had a nick in it.  Other than that, I don't know what they've done at the street.  On a chat with support now, and they're saying

 

"I'll arrange a technician along with a supervisor to address the issue and examine the lines from pole to the house and if needed from node point to ensure a fix."

 

Guess we'll see!

Participant

Re: Cable Modem Reboot due to T4 timeout

Ok, status update time!  I'm working with a Spectrum supervisor now who's troubleshooting with me.  He brought in an ubee DVW32CB (16 channels) and hooked it up to a splitter along with my modem, so he could see if the ubee rebooted like my SB6141 (8 channels) does.  My SB6141 continues to error and reboot, but the ubee is not.  However, the ubee is showing a number of uncorrectables, especially on the lower frequency channels that are used by my SB6141.  Here's the connection info from the ubee:

 

Startup ProcedureProcedure Status Comment

Acquire Downstream Channel555000000 HzLocked
Connectivity StateOKOperational
Boot State  
Configuration FileOK 
SecurityEnabledBPI+



Downstream Bonded ChannelsChannel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables

1 QAM256 555000000 Hz-6.3 dBmV35.6 dB19979
2 QAM256 513000000 Hz-1.4 dBmV39.5 dB4777763452799
3 unknown 519000000 Hz-5.5 dBmV48.6 dB26077484409850
4 QAM256 525000000 Hz-4.7 dBmV37.0 dB5403968028489154
5 QAM256 531000000 Hz-9.0 dBmV33.2 dB3203108313387440
6 unknown 537000000 Hz-16.9 dBmV0.0 dB223844692967420
7 QAM256 543000000 Hz-14.6 dBmV27.5 dB512815864190902370
8 QAM256 549000000 Hz-9.0 dBmV33.4 dB42027712772142734
9 unknown 507000000 Hz-2.8 dBmV30.5 dB36833882676795
10 QAM256 561000000 Hz-4.9 dBmV37.0 dB410
11 QAM256 567000000 Hz-4.3 dBmV37.3 dB480
12 QAM256 573000000 Hz-3.3 dBmV38.1 dB626
13 QAM256 579000000 Hz-3.0 dBmV38.3 dB623
14 QAM256 585000000 Hz-2.3 dBmV38.8 dB590
15 QAM256 591000000 Hz-2.4 dBmV38.7 dB240
16 QAM256 597000000 Hz-2.3 dBmV38.7 dB545

 

Total Correctables Total Uncorrectables

1052619469315428585



Upstream Bonded ChannelsChannel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power

1 ATDMA 2560 Ksym/sec37000000 Hz42.8 dBmV
2 ATDMA 5120 Ksym/sec24200000 Hz41.3 dBmV
3 ATDMA 5120 Ksym/sec30600000 Hz41.8 dBmV
4 TDMA 2560 Ksym/sec19400000 Hz39.8 dBmV

 

Currently, my modem and the ubee are inside the house.  To rule out my inside coax, I think the next step is to connect the ubee directly to the outside tap (at the house) and see if the uncorrectables continue on the ubee.  If they do, is it safe to assume the issue is on the line between the road and the house?  If the uncorrectables stop, then it's likely the coax running inside the house?

 

Also, just because the ubee isn't rebooting (like the SB6141 is) doesn't imply that I should replace my modem with a 16 channel modem correct to "bypass" the problem?

Participant

Re: Cable Modem Reboot due to T4 timeout

And for good measure, here's the current log from my SB6141:

 

Dec 15 2017 17:45:505-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;
Dec 15 2017 17:45:486-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;
Dec 15 2017 17:45:485-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;
Dec 15 2017 17:44:583-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;
Dec 15 2017 17:44:535-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;
Dec 15 2017 17:44:503-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;
Dec 15 2017 17:44:293-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;
Dec 15 2017 16:29: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;
Dec 15 2017 16:29:485-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;
Dec 15 2017 16:29:236-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;
Dec 15 2017 16:29:075-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;
Dec 15 2017 16:29:075-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;
Dec 15 2017 16:28: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;
Dec 15 2017 16:28:335-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;
Dec 15 2017 16:28:335-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;
Dec 15 2017 14:50:005-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;
Dec 15 2017 14:49:586-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;
Dec 15 2017 14:49:585-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 IP loss ;CM-MAC=d0:39:b3:f8:cf:8e;CMTS-MAC=00:00:00:00:00:00;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 39 dB 38 dB 37 dB 33 dB 27 dB 33 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
0 dBmV  0 dBmV  -1 dBmV  -3 dBmV  -7 dBmV  -14 dBmV  -8 dBmV  

 

Upstream Bonding Channel Value
Channel ID
Frequency37000000 Hz 19400000 Hz 30600000 Hz 24200000 Hz 
Ranging Service ID1226 1226 1226 1226 
Symbol Rate2.560 Msym/sec 2.560 Msym/sec 5.120 Msym/sec 5.120 Msym/sec 
Power Level42 dBmV 40 dBmV 42 dBmV 40 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 Codewords63993573 63186092 63192476 63177030 63165457 41600755 63165255 
Total Correctable Codewords657 66 21095109 12 
Total Uncorrectable Codewords1431 1375 2528 1345 1523 412286 1532