Expert

Re: Bonded downstream channels

somewhere between your modem and the CMTS server, the coax/fiber went dead.

Are there now different DS channels listed.

 

Sharer

Re: Bonded downstream channels

The channels didn't change, the modem didn't reboot from the timeouts.  However this morning, 30 minutes ago, the modem rebooted and got 8 consecutive channels, after a T4 Timeout.  I suspect it's all due to someone working on lines somewhere.  There was a Spectrum van in the neighborhood the day of the T6 Timeout, with a worker on a ladder on a pole. 

 

This morning when i got the T4 Timeout and reboot, this was the log:

 

TimePriorityCodeMessage

May 30 2017 08:10:523-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
May 30 2017 08:10:516-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
May 30 2017 08:10:515-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:156-NoticeN/ACable Modem Reboot due to T4 timeout ;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
May 30 2017 08:10:013-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
May 30 2017 08:10:005-WarningT202.0Lost MDD Timeout;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
May 30 2017 08:09:563-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
May 30 2017 08:09:353-CriticalT05.0SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
May 28 2017 20:44:166-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
May 28 2017 20:44:165-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
May 28 2017 20:43:503-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
May 28 2017 20:43:343-CriticalI02.0REG RSP not received;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
May 28 2017 20:43:344-ErrorI271.0T6 Timeout and retries exceeded;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
May 28 2017 20:43:226-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
May 28 2017 20:43:225-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
May 28 2017 20:42:593-CriticalT05.0SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
May 28 2017 15:29:533-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
May 28 2017 08:18:506-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
May 28 2017 08:18:505-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:156-NoticeN/ACable Modem Reboot due to power reset ;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Expert

Re: Bonded downstream channels

Post the signal level page... I doubt a guy on a ladder did any hardline work, that's reserved for the bucket truck guys.

 

Sharer

Re: Bonded downstream channels

Signal page was fine all day after that, consecutive channels starting at 507 MHz, SNR and power levels all quite good.  Some time in the evening, a couple of DS channels switched to higher ones, but still looking otherwise decent tonight.

 

Downstream Bonding Channel Value
Channel ID10 11 12 15 16 25 26 
Frequency507000000 Hz 513000000 Hz 519000000 Hz 525000000 Hz 543000000 Hz 549000000 Hz 603000000 Hz 609000000 Hz 
Signal to Noise Ratio39 dB 39 dB 39 dB 39 dB 39 dB 39 dB 39 dB 40 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
0 dBmV  0 dBmV  0 dBmV  0 dBmV  0 dBmV  0 dBmV  2 dBmV  2 dBmV  

 

Upstream Bonding Channel Value
Channel ID
Frequency19400000 Hz 24200000 Hz 30600000 Hz 37000000 Hz 
Ranging Service ID461 461 461 461 
Symbol Rate2.560 Msym/sec 5.120 Msym/sec 5.120 Msym/sec 2.560 Msym/sec 
Power Level46 dBmV 46 dBmV 47 dBmV 48 dBmV 
Upstream Modulation[3] QPSK
[2] 16QAM
 
[3] QPSK
[1] 16QAM
[2] 64QAM
 
[3] QPSK
[1] 16QAM
[2] 64QAM
 
[3] QPSK
[3] 16QAM
 
Ranging StatusSuccess Success Success Success 

 

Signal Stats (Codewords)Bonding Channel Value
Channel ID10 11 12 15 16 25 26 
Total Unerrored Codewords2362273545 2361310215 2361328344 2361318665 2136650512 2136644548 2136635960 2136647420 
Total Correctable Codewords79 42 620 994 
Total Uncorrectable Codewords578 1373 507 1542 3601 2897 5551 2900
Expert

Re: Bonded downstream channels

[ Edited ]

Modem is now exceeding channel acceptance bandwidth by 18 mHz

due to severe ingress on the skipped channels.. Problem is still not fixed.

max acceptance is 96 mHz and that's provided there's not any serious ingress on the skipped channels.

 Was it windy when the change occurred? It still appears to be a hardline break between your tapoff and the fiber optic converter

 

 

Sharer

Re: Bonded downstream channels

[ Edited ]

Yes, I'm aware of the acceptance range of the modem, have mentioned it myself in previous posts.  It wasn't windy and often the weather is beautiful when the channels get switched, or when channels drop altogether.

 

Considering some of the things the bucket truck tech has already found and fixed, like a wrong filter where a cable simulator should be, and dirty fiber optic at the converter at the hub, I suspect the entire infrastructure in my neighborhood is old and has numerous failing points.  The bucket truck guys are basically playing whack-a-mole trying to find it all.

 

Whack-a-mole:
https://www.youtube.com/watch?v=D0n8N98mpes

Expert

Re: Bonded downstream channels

Only solution is to find the break yourself and tell them where it is... probably in the ivy overgrown lines... poison ivy? yuk.  Is any of the line bare aluminum or is it newer black plastic jacketed?

 

Will your guy tell you what frequency the ALC pilot is on?

We have 445.250 here

 

Sharer

Re: Bonded downstream channels

Sorry for the delay replying.... had a hamstring tear and a couple of funerals take up my time.  The vines growing on the lines a couple of poles after mine were taken care of by a neighbor a few months ago, when none of the utility companies would do anything about it.  It was Virginia Creeper not poison ivy.

 

The lines in my neighborhood are black jacketed, but I'm not sure about a few blocks away, between me and the fiber optic conversion hub.  I'll try to look soon. 

 

I'll try asking my tech what frequency the ALC pilot is on here, but it may be a while, since he's been off due to family illness.

Sharer

Re: Bonded downstream channels

Well, this thread and the issues have been ongoing for a year now, and seem to have gotten worse instead of better.  The firmware of the SB6141 was updated on July 10 and now shows as an Arris instead of a Motorola.  It didn't fix any issues though.   Starting on July 11, the logs started showing multiple T4 Timeouts leading to modem reboots, multiple T3 Timeouts, dropped DS channels nearly every day,  B-INIT-RNG-FAILURE, dropped two of the four Upstream Channels on Sunday, Upstream power levels have been too wide and sometimes too high .  I had to reboot the modem again late last night shortly after a reboot, due to lack of Internet connectivity. 

Here's the current signal page after last night's reboot (upstream spread between 45 and 50 dBmV). 

Downstream Bonding Channel Value
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 Ratio37 dB 38 dB 38 dB 38 dB 38 dB 38 dB 38 dB 38 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
-1 dBmV  -1 dBmV  -1 dBmV  -1 dBmV  0 dBmV  0 dBmV  0 dBmV  0 dBmV  

 

Upstream Bonding Channel Value
Channel ID
Frequency24200000 Hz 37000000 Hz 30600000 Hz 19400000 Hz 
Ranging Service ID2668 2668 2668 2668 
Symbol Rate5.120 Msym/sec 2.560 Msym/sec 5.120 Msym/sec 2.560 Msym/sec 
Power Level47 dBmV 50 dBmV 48 dBmV 45 dBmV 
Upstream Modulation[3] QPSK
[1] 16QAM
[2] 64QAM
 
[3] QPSK
[3] 16QAM
 
[3] QPSK
[1] 16QAM
[2] 64QAM
 
[3] QPSK
[2] 16QAM
 
Ranging StatusSuccess Success Success Success 

 

Signal Stats (Codewords)Bonding Channel Value
Channel ID10 11 12 13 14 15 16 
Total Unerrored Codewords2323432636 2322570592 2322592059 2322583001 2322568134 2322569198 2322563236 2322570632 
Total Correctable Codewords20 19 12 46 
Total Uncorrectable Codewords593 571 468 1351 706 644 1421 

650 

 

 

Sharer

Re: Bonded downstream channels

...and here's the modem log, showing only some of what has been going on for days.

 

TimePriorityCodeMessage

Jul 17 2017 00:08:093-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
Jul 16 2017 22:27:146-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
Jul 16 2017 22:27:145-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:176-NoticeN/ACable Modem Reboot due to power reset ;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jul 16 2017 22:03:536-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
Jul 16 2017 22:03:535-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:223-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:176-NoticeN/ACable Modem Reboot due to T4 timeout ;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
Jul 16 2017 22:02:593-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
Jul 16 2017 22:02:555-WarningT202.0Lost MDD Timeout;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
Jul 16 2017 22:02:543-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
Jul 16 2017 22:02:545-WarningT202.0Lost MDD Timeout;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
Jul 16 2017 22:02:533-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
Jul 16 2017 22:02:313-CriticalT05.0SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
Jul 16 2017 21:48:225-WarningT202.0Lost MDD Timeout;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
Jul 16 2017 21:48:225-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
Jul 16 2017 21:26:345-WarningT202.0Lost MDD Timeout;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
Jul 16 2017 21:26:345-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
Jul 16 2017 18:10:566-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
Jul 16 2017 18:10:565-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;