Newcomer

Yet another T4 timeout issue on SB6141

Title says it all. Modem will randomly restart. It typically happens a few times a week, especially when I am working from home. At first glace, I did not see anything crazy with the configuration numbers. I had a level 3 out to my home and re-wire the pole-to-house line (it was overbound). I believe there may be splitters somewhere in the source location, but my home is older and I am not familiar with how the original coax configuration was setup. The level 3 tech also mentioned I have coax runs going all over, but none of them are used. He said it might cause crosstalk and degrade the signal.

 

Here are my stats:

Time

Priority

Code

Message

Feb 11 2018 16:58:22

6-Notice

I401.0

TLV-11 - unrecognized OID;CM-MAC=20:3d:66:03:a9:fe;CMTS-MAC=00:17:10:8b:37:11;CM-QOS=1.1;CM-VER=3.0;

Feb 11 2018 16:58:22

5-Warning

Z00.0

MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=20:3d:66:03:a9:fe;CMTS-MAC=00:17:10:8b:37:11;CM-QOS=1.1;CM-VER=3.0;

Jan 01 1970 00:00:17

6-Notice

N/A

Cable Modem Reboot due to power reset ;CM-MAC=20:3d:66:03:a9:fe;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

Feb 11 2018 16:19:34

6-Notice

I401.0

TLV-11 - unrecognized OID;CM-MAC=20:3d:66:03:a9:fe;CMTS-MAC=00:17:10:8b:37:11;CM-QOS=1.1;CM-VER=3.0;

Feb 11 2018 16:19:34

5-Warning

Z00.0

MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=20:3d:66:03:a9:fe;CMTS-MAC=00:17:10:8b:37:11;CM-QOS=1.1;CM-VER=3.0;

Jan 01 1970 00:00:17

6-Notice

N/A

Cable Modem Reboot due to T4 timeout ;CM-MAC=20:3d:66:03:a9:fe;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

Feb 11 2018 16:18:26

3-Critical

R04.0

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=20:3d:66:03:a9:fe;CMTS-MAC=00:17:10:8b:37:11;CM-QOS=1.1;CM-VER=3.0;

Feb 11 2018 16:18:23

5-Warning

T202.0

Lost MDD Timeout;CM-MAC=20:3d:66:03:a9:fe;CMTS-MAC=00:17:10:8b:37:11;CM-QOS=1.1;CM-VER=3.0;

Feb 11 2018 16:17:58

3-Critical

T05.0

SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=20:3d:66:03:a9:fe;CMTS-MAC=00:17:10:8b:37:11;CM-QOS=1.1;CM-VER=3.0;

Feb 11 2018 13:24:31

5-Warning

T202.0

Lost MDD Timeout;CM-MAC=20:3d:66:03:a9:fe;CMTS-MAC=00:17:10:8b:37:11;CM-QOS=1.1;CM-VER=3.0;

Feb 11 2018 13:24:31

5-Warning

N/A

DS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=20:3d:66:03:a9:fe;CMTS-MAC=00:17:10:8b:37:11;CM-QOS=1.1;CM-VER=3.0;

Feb 11 2018 11:22:29

5-Warning

T202.0

Lost MDD Timeout;CM-MAC=20:3d:66:03:a9:fe;CMTS-MAC=00:17:10:8b:37:11;CM-QOS=1.1;CM-VER=3.0;

Feb 11 2018 11:22:28

5-Warning

N/A

DS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=20:3d:66:03:a9:fe;CMTS-MAC=00:17:10:8b:37:11;CM-QOS=1.1;CM-VER=3.0;

Feb 05 2018 15:00:01

6-Notice

I401.0

TLV-11 - unrecognized OID;CM-MAC=20:3d:66:03:a9:fe;CMTS-MAC=00:17:10:8b:37:11;CM-QOS=1.1;CM-VER=3.0;

Feb 05 2018 15:00:01

5-Warning

Z00.0

MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=20:3d:66:03:a9:fe;CMTS-MAC=00:17:10:8b:37:11;CM-QOS=1.1;CM-VER=3.0;

Jan 01 1970 00:10:51

3-Critical

R02.0

No Ranging Response received - T3 time-out;CM-MAC=20:3d:66:03:a9:fe;CMTS-MAC=00:17:10:8b:37:11;CM-QOS=1.1;CM-VER=3.0;

Jan 01 1970 00:00:17

6-Notice

N/A

Cable Modem Reboot due to T4 timeout ;CM-MAC=20:3d:66:03:a9:fe;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

Feb 05 2018 14:48:37

3-Critical

R04.0

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=20:3d:66:03:a9:fe;CMTS-MAC=00:17:10:8b:37:11;CM-QOS=1.1;CM-VER=3.0;

Feb 05 2018 14:48:33

5-Warning

T202.0

Lost MDD Timeout;CM-MAC=20:3d:66:03:a9:fe;CMTS-MAC=00:17:10:8b:37:11;CM-QOS=1.1;CM-VER=3.0;

Feb 05 2018 14:48:30

3-Critical

R04.0

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=20:3d:66:03:a9:fe;CMTS-MAC=00:17:10:8b:37:11;CM-QOS=1.1;CM-VER=3.0;

 

Downstream

Bonding Channel Value

Channel ID

10 

11 

12 

13 

14 

15 

16 

Frequency

507000000 Hz 

513000000 Hz 

519000000 Hz 

525000000 Hz 

531000000 Hz 

537000000 Hz 

543000000 Hz 

549000000 Hz 

Signal to Noise Ratio

39 dB 

39 dB 

39 dB 

39 dB 

37 dB 

39 dB 

39 dB 

38 dB 

Downstream Modulation

QAM256 

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

5 dBmV  

5 dBmV  

5 dBmV  

4 dBmV  

4 dBmV  

4 dBmV  

4 dBmV  

4 dBmV  

 

Upstream

Bonding Channel Value

Channel ID

Frequency

24000000 Hz 

36800000 Hz 

30400000 Hz 

19200000 Hz 

Ranging Service ID

1628 

1628 

1628 

1628 

Symbol Rate

5.120 Msym/sec 

5.120 Msym/sec 

5.120 Msym/sec 

2.560 Msym/sec 

Power Level

34 dBmV 

36 dBmV 

36 dBmV 

34 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 Status

Success 

Success 

Success 

Success 

 

Signal Stats (Codewords)

Bonding Channel Value

Channel ID

10 

11 

12 

13 

14 

15 

16 

Total Unerrored Codewords

6049696 

5167147 

5158876 

5175774 

5155802 

5184413 

5186762 

5186325 

Total Correctable Codewords

12 

10 

15 

17 

Total Uncorrectable Codewords

520 

512 

608 

531 

674 

681 

627 

620 

 

3 REPLIES
Established Sharer

Re: Yet another T4 timeout issue on SB6141

Your signal levels look good in both directions, but there is something interfering with DS13 at 531 MHz  (notice the lower SNR signal-to-noise ratio).  Recommend you  have the tech return to disconnect every unused cable and put terminations on the splitter ports.  If the interference remains it is coming in from their outdoor cable plant; they will need to chase it down and repair, which can take days or weeks.  That step will improve both TV and internet signals for the entire neighborhood.

Newcomer

Re: Yet another T4 timeout issue on SB6141

It looks like the downstream table was truncated. Channels 14, 15 and 16 are at 537Mhz, 543Mhz, and 549Mhz, respectively. I guess that adds weight to the arguement?

Highlighted
Expert

Re: Yet another T4 timeout issue on SB6141

copy and paste the signal page again.. DON"T RESET THE MODEM, need to see real history, You have some sort of ingress causing the DS partial service errors