Valued Participant

Re: Yet another SB6141 related issue?

TWC was a no show today.  Signal and logs held steady today until tonight.

 

Then tonight all when south...:

 

⟫ speedtest-cli
0.3.4
Retrieving speedtest.net configuration...
Retrieving speedtest.net server list...
Testing from Time Warner Cable (72.179.xxx.zzz)...
Selecting best server based on latency...
Hosted by AT&T (Austin, TX) [31.88 km]: 62.524 ms
Testing download speed........................................
Download: 1.42 Mbit/s
Testing upload speed..................................................
Upload: 8.78 Mbit/s
Tue Feb 23 22:33:49 CST 2016

 

Lost another downstream channel, could not browse to TWC forums...

Signal:

DownstreamBonding Channel Value
Channel ID16 
Frequency501000000 Hz 519000000 Hz 531000000 Hz 537000000 Hz 543000000 Hz 591000000 Hz 
Signal to Noise Ratio38 dB 39 dB 39 dB 39 dB 38 dB 35 dB 
Downstream ModulationQAM256 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
8 dBmV  8 dBmV  7 dBmV  7 dBmV  8 dBmV  0 dBmV  

 

UpstreamBonding Channel Value
Channel ID
Frequency24200000 Hz 19400000 Hz 30600000 Hz 37000000 Hz 
Ranging Service ID3523 3523 3523 3523 
Symbol Rate5.120 Msym/sec 2.560 Msym/sec 5.120 Msym/sec 2.560 Msym/sec 
Power Level48 dBmV 47 dBmV 47 dBmV 46 dBmV 
Upstream Modulation[3] QPSK
[1] 16QAM
[2] 64QAM
 
[3] QPSK
[2] 16QAM
 
[3] QPSK
[1] 16QAM
[2] 64QAM
 
[3] QPSK
[3] 16QAM
 
Ranging StatusSuccess Success Success Success 

 

Signal Stats (Codewords)Bonding Channel Value
Channel ID16 
Total Unerrored Codewords5081171642 4802940415 4794857290 4794833399 4613925596 4493434115 941305545 
Total Correctable Codewords22 74 48 145 554 4594 
Total Uncorrectable Codewords572 1157 1889 2683 2432 44417 272494 

 

Had to reboot the cablemodem to browse again:

 

Logs now:

TimePriorityCodeMessage

Feb 23 2016 22:38:516-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 23 2016 22:38:505-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 23 2016 22:38:246-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 23 2016 22:38:245-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:156-NoticeN/ACable Modem Reboot from GUI/Configuration page ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Feb 23 2016 21:49:295-WarningT202.0Lost MDD Timeout;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 23 2016 21:49:295-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 23 2016 21:49:295-WarningT202.0Lost MDD Timeout;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 23 2016 21:49:295-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 23 2016 21:49:066-NoticeN/AMDD Recovery following MDD Loss;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 22 2016 21:37:535-WarningT202.0Lost MDD Timeout;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 22 2016 21:37:535-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 22 2016 15:30:096-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 22 2016 15:30:085-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 22 2016 15:29:406-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 22 2016 15:29:405-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:156-NoticeN/ACable Modem Reboot due to power reset ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Feb 19 2016 19:48:575-WarningT202.0Lost MDD Timeout;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 19 2016 19:48:575-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 19 2016 19:48:575-WarningT202.0Lost MDD Timeout;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;

 

Signal now after reboot:

 

DownstreamBonding Channel Value
Channel ID
Frequency501000000 Hz 507000000 Hz 513000000 Hz 519000000 Hz 525000000 Hz 531000000 Hz 537000000 Hz 543000000 Hz 
Signal to Noise Ratio39 dB 40 dB 39 dB 39 dB 38 dB 38 dB 39 dB 39 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
8 dBmV  8 dBmV  8 dBmV  8 dBmV  7 dBmV  7 dBmV  7 dBmV  7 dBmV  

 

UpstreamBonding Channel Value
Channel ID
Frequency24200000 Hz 19400000 Hz 30600000 Hz 37000000 Hz 
Ranging Service ID2097 2097 2097 2097 
Symbol Rate5.120 Msym/sec 2.560 Msym/sec 5.120 Msym/sec 2.560 Msym/sec 
Power Level48 dBmV 48 dBmV 48 dBmV 46 dBmV 
Upstream Modulation[3] QPSK
[1] 16QAM
[2] 64QAM
 
[3] QPSK
[2] 16QAM
 
[3] QPSK
[1] 16QAM
[2] 64QAM
 
[3] QPSK
[3] 16QAM
 
Ranging StatusSuccess Success Success Success 

 

Signal Stats (Codewords)Bonding Channel Value
Channel ID
Total Unerrored Codewords25031811 24183141 24192207 24200393 24176816 24175081 24180116 24192196 
Total Correctable Codewords10 120 14 
Total Uncorrectable Codewords476 506 532 530 606 3444 684 678 

 

 

What a mess...

.

 

Valued Participant

Re: Yet another SB6141 related issue?

I feel as though I've enter the TWC Twilight Zone...

 

After having to do another reboot last Wednesday (Feb 24) and since it had been inferred that the issue was my SB6141, I figured replacing the SB6141 with a different cablemodem would either confirm or rule out an issue with my SB6141.  Unfortunately I don't own another 8+ downstream cablemodem to try.

 

The next day (Feb 25) after lunch I took a ride up to TWC's new superstore (what a palace!) to pick up a leased cablemodem.  I told the TWC lady that I needed a cablemodem that _I_could_configure_ to Bridge Mode.  She gave me a Ubee DDW36C1.  Once back at the house I found that configuring the DDW36C1 for Bridge Mode required a phone call to TWC customer service.  Ugh!  .....  So I put the Ubee asside for the moment...

 

An couple of hours later, a knock at my door. I look out the window, there's a TWC van park in front and a TWC guy walking around in my front yard.  I had no scheduled appointment but told the TWC tech I wasn't about to kick him off the property because of blah, blah, blah (see the previous posts in this thread)...

 

Anyway.  TWC guy listens, and then says:  'Well I just here to replace the drop".  Better than nothing I figure and he did.  Also checked the signal on the RG6 from TWC's junction point on the outside of the house to the end of the patch cable that plugs into the cablemodem.  TWC guy says that all is well with the RG6 in house.

 

So since the new drop has been in place it's been wait and see.  For two days the 8 downstream channels held but that didn't last.  Then last night the SB6141 reboot on it's own.  That's never happened before.  There was no power failure here and the SB6141 is on a UPS anyway.  Hmmmm?

 

FWIW, here's the latest 'Signal' and 'Log'.

DownstreamBonding Channel Value
Channel ID13 
Frequency501000000 Hz 507000000 Hz 519000000 Hz 525000000 Hz 531000000 Hz 537000000 Hz 573000000 Hz 
Signal to Noise Ratio39 dB 40 dB 39 dB 39 dB 39 dB 37 dB 40 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
7 dBmV  7 dBmV  6 dBmV  6 dBmV  6 dBmV  6 dBmV  7 dBmV  

 

UpstreamBonding Channel Value
Channel ID
Frequency24200000 Hz 19400000 Hz 30600000 Hz 37000000 Hz 
Ranging Service ID4023 4023 4023 4023 
Symbol Rate5.120 Msym/sec 2.560 Msym/sec 5.120 Msym/sec 2.560 Msym/sec 
Power Level47 dBmV 47 dBmV 47 dBmV 47 dBmV 
Upstream Modulation[3] QPSK
[1] 16QAM
[2] 64QAM
 
[3] QPSK
[2] 16QAM
 
[3] QPSK
[1] 16QAM
[2] 64QAM
 
[3] QPSK
[3] 16QAM
 
Ranging StatusSuccess Success Success Success 

 

Signal Stats (Codewords)Bonding Channel Value
Channel ID13 
Total Unerrored Codewords2604541738 2603587286 2560090924 2560117680 2560073247 2560076009 2086895278 
Total Correctable Codewords45 11 28 92 100 
Total Uncorrectable Codewords532 504 1145 1246 1285 1186 2460 

 

 

TimePriorityCodeMessage

Feb 28 2016 13:38:295-WarningT202.0Lost MDD Timeout;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 28 2016 13:38:295-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 27 2016 22:47:036-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 27 2016 22:47:035-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 27 2016 22:46:336-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 27 2016 22:46:335-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:156-NoticeN/ACable Modem Reboot due to power reset ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Feb 27 2016 17:27:105-WarningT202.0Lost MDD Timeout;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 27 2016 17:27:105-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 27 2016 17:27:105-WarningT202.0Lost MDD Timeout;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 27 2016 17:27:105-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 25 2016 17:59:156-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 25 2016 17:59:145-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 25 2016 17:58:486-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 25 2016 17:58:485-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:156-NoticeN/ACable Modem Reboot due to T4 timeout ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Feb 25 2016 17:34:023-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 25 2016 17:34:015-WarningT202.0Lost MDD Timeout;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 25 2016 17:34:013-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 25 2016 17:34:005-WarningT202.0Lost MDD Timeout;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;

 

 

 

Next up?  I'm going to move to the Ubee DDW36C1 to see if this issue continues... 

 

.

Expert

Re: Yet another SB6141 related issue?

eb 28 2016 13:38:295-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;

 this indicates one or more downstream channels were lost probably due to ingress from broadcast TV

 

 I'll bet the other modem will have the same issue. If everything from the pole to the modem was replaced, it's somewhere down the street.

 

Contributor

Re: Yet another SB6141 related issue?


@martywd wrote:

I feel as though I've enter the TWC Twilight Zone...

 

After having to do another reboot last Wednesday (Feb 24) and since it had been inferred that the issue was my SB6141, I figured replacing the SB6141 with a different cablemodem would either confirm or rule out an issue with my SB6141.  Unfortunately I don't own another 8+ downstream cablemodem to try.

 

The next day (Feb 25) after lunch I took a ride up to TWC's new superstore (what a palace!) to pick up a leased cablemodem.  I told the TWC lady that I needed a cablemodem that _I_could_configure_ to Bridge Mode.  She gave me a Ubee DDW36C1.  Once back at the house I found that configuring the DDW36C1 for Bridge Mode required a phone call to TWC customer service.  Ugh!  .....  So I put the Ubee asside for the moment...

 

An couple of hours later, a knock at my door. I look out the window, there's a TWC van park in front and a TWC guy walking around in my front yard.  I had no scheduled appointment but told the TWC tech I wasn't about to kick him off the property because of blah, blah, blah (see the previous posts in this thread)...

 

Anyway.  TWC guy listens, and then says:  'Well I just here to replace the drop".  Better than nothing I figure and he did.  Also checked the signal on the RG6 from TWC's junction point on the outside of the house to the end of the patch cable that plugs into the cablemodem.  TWC guy says that all is well with the RG6 in house.

 

So since the new drop has been in place it's been wait and see.  For two days the 8 downstream channels held but that didn't last.  Then last night the SB6141 reboot on it's own.  That's never happened before.  There was no power failure here and the SB6141 is on a UPS anyway.  Hmmmm?

 

FWIW, here's the latest 'Signal' and 'Log'.

DownstreamBonding Channel Value
Channel ID13 
Frequency501000000 Hz 507000000 Hz 519000000 Hz 525000000 Hz 531000000 Hz 537000000 Hz 573000000 Hz 
Signal to Noise Ratio39 dB 40 dB 39 dB 39 dB 39 dB 37 dB 40 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
7 dBmV  7 dBmV  6 dBmV  6 dBmV  6 dBmV  6 dBmV  7 dBmV  

 

UpstreamBonding Channel Value
Channel ID
Frequency24200000 Hz 19400000 Hz 30600000 Hz 37000000 Hz 
Ranging Service ID4023 4023 4023 4023 
Symbol Rate5.120 Msym/sec 2.560 Msym/sec 5.120 Msym/sec 2.560 Msym/sec 
Power Level47 dBmV 47 dBmV 47 dBmV 47 dBmV 
Upstream Modulation[3] QPSK
[1] 16QAM
[2] 64QAM
 
[3] QPSK
[2] 16QAM
 
[3] QPSK
[1] 16QAM
[2] 64QAM
 
[3] QPSK
[3] 16QAM
 
Ranging StatusSuccess Success Success Success 

 

Signal Stats (Codewords)Bonding Channel Value
Channel ID13 
Total Unerrored Codewords2604541738 2603587286 2560090924 2560117680 2560073247 2560076009 2086895278 
Total Correctable Codewords45 11 28 92 100 
Total Uncorrectable Codewords532 504 1145 1246 1285 1186 2460 

 

 

TimePriorityCodeMessage

Feb 28 2016 13:38:295-WarningT202.0Lost MDD Timeout;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 28 2016 13:38:295-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 27 2016 22:47:036-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 27 2016 22:47:035-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 27 2016 22:46:336-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 27 2016 22:46:335-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:156-NoticeN/ACable Modem Reboot due to power reset ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Feb 27 2016 17:27:105-WarningT202.0Lost MDD Timeout;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 27 2016 17:27:105-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 27 2016 17:27:105-WarningT202.0Lost MDD Timeout;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 27 2016 17:27:105-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 25 2016 17:59:156-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 25 2016 17:59:145-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 25 2016 17:58:486-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 25 2016 17:58:485-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:156-NoticeN/ACable Modem Reboot due to T4 timeout ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Feb 25 2016 17:34:023-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 25 2016 17:34:015-WarningT202.0Lost MDD Timeout;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 25 2016 17:34:013-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 25 2016 17:34:005-WarningT202.0Lost MDD Timeout;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;

 

 

 

Next up?  I'm going to move to the Ubee DDW36C1 to see if this issue continues... 

 

.


Any update on this, did the Ubee solve any connection issues?

Valued Participant

Re: Yet another SB6141 related issue?

@Jeff_Stephen212 types:  'Any update on this, did the Ubee solve any connection issues?'

 

The Ubee-DDW36C has been up for just over 8 days now with no connectivity or speed issues thus far.

 

The issue with the Ube is, as mentioned in the other thread I created, that there is no logging and little signal info.

 

I'm going to give the Ubee a couple of more days and then call Arris for tech support and hopefully a warranty return.

.

 

 

 

 

Valued Participant

Re: Yet another SB6141 related issue?

I'm back connected via the SB6141 now.

 

Contrary to my previous post where I stated that I'd wait a couple of more days, I instead contacted Arris last Tuesday (3/8/2016) via an email form at their support site.  I explained in detail my SB6141 issues, including a link to this thread.  I explained that I had leased a Ubee DDW36C1 from TWC which had been running for 8+ days on TWC without issues.  I requested warranty return/replacement.

 

Arris was not impressed but replied promptly via email to me with this:

 

Different modems can operate within different signal ranges. It is possible for one model to maintain connectivity while another cannot.

I advise to log into the settings page for the SB6141, and note the signal levels. We would need to verify the Downstream Signal to Noise Ratio, and Downstream and Upstream Power Levels. I'll post a link below with instructions.

Please Click the following link for more Information

http://arris.force.com/consumers/articles/General_FAQs/SB6141-Signal-Level

If the signal levels are well within range and not near the thresholds, please factory reset the unit. This will be done within the same settings page. I will post a link below with instructions.

Please Click the following link for more Information

http://arris.force.com/consumers/articles/General_FAQs/SB6141-Factory-Reset

If you are unable to access the Internet after the reset, please have your cable provider "reprovision" the device. They will send a new configuration file to it. This will help to rule out issues relating to software.

 

Since signal levels have as far as I know always been 'well within range' I decided to try a 'factory reset' of the SB6141.  Again.  I had attempted to do 'factory reset' once before during the call to TWC customer service back on January of this year.  But, at that time clicking the 'Reset All Defaults' button in the SB6141's 'Configuration' page did nothing at all.  I don't know why?  But this last Tuesday after connecting the SB6141, and _before_ calling TWC to get provisioned, I tried clicking the 'Reset All Defaults' it worked!  Signal and logs were reset.  At that point I call TWC and got connected once again with the SB6141...

 

Two days have past and now the 'DS Partial Service Fallback' are starting again.  Connectivity is ok at this time.  Here are the Signal and Logs.  Note that the reboot and other logging on Mar 09 2016 00:52:... happen during a storm which knocked out power in my neighborhood for a couple of minutes (The SB6141 was never off power during that time since it is UPS protected).

 

The 'Mar 10 2016 10:39:02 .... No Ranging Response received - T3 time-out; ....' seems to be something I haven't seen before in previous posting of logs?

 

Log:

TimePriorityCodeMessage

Mar 10 2016 17:28:265-WarningT202.0Lost MDD Timeout;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 10 2016 17:28:265-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 10 2016 10:39:023-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 09 2016 00:53:206-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 09 2016 00:53:195-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 09 2016 00:53:033-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 09 2016 00:52:476-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 09 2016 00:52:475-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:156-NoticeN/ACable Modem Reboot due to T4 timeout ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 09 2016 00:52:053-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 09 2016 00:52:025-WarningT202.0Lost MDD Timeout;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 09 2016 00:51:583-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 09 2016 00:51:383-CriticalT05.0SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 08 2016 19:00:016-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 08 2016 19:00:015-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 08 2016 18:59:316-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 08 2016 18:59:315-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:156-NoticeN/ACable Modem Reboot due to power reset ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 08 2016 18:53:456-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Mar 08 2016 18:53:445-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;

 

 And Signal:

DownstreamBonding Channel Value
Channel ID11 13 
Frequency501000000 Hz 531000000 Hz 537000000 Hz 543000000 Hz 549000000 Hz 561000000 Hz 573000000 Hz 
Signal to Noise Ratio39 dB 39 dB 39 dB 39 dB 39 dB 39 dB 40 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
7 dBmV  6 dBmV  6 dBmV  6 dBmV  7 dBmV  7 dBmV  7 dBmV  

 

UpstreamBonding Channel Value
Channel ID
Frequency24200000 Hz 19400000 Hz 30600000 Hz 37000000 Hz 
Ranging Service ID413 413 413 413 
Symbol Rate5.120 Msym/sec 2.560 Msym/sec 5.120 Msym/sec 2.560 Msym/sec 
Power Level47 dBmV 47 dBmV 47 dBmV 46 dBmV 
Upstream Modulation[3] QPSK
[1] 16QAM
[2] 64QAM
 
[3] QPSK
[2] 16QAM
 
[3] QPSK
[1] 16QAM
[2] 64QAM
 
[3] QPSK
[3] 16QAM
 
Ranging StatusSuccess Success Success Success 

 

Signal Stats (Codewords)Bonding Channel Value
Channel ID11 13 16 
Total Unerrored Codewords7267208947 7174887710 7151498102 7151508348 7101350901 7101340140 7101333525 6474083920 
Total Correctable Codewords36 182 39 125 94 104 2047 
Total Uncorrectable Codewords565 1869 2357 2276 3226 3189 3099 85358 

 

 

 

.

 

Expert

Re: Yet another SB6141 related issue?

You are STILL having broadcast tv ingress from TV ch 34 at 591 mHz and I believe even worst from broadcast ch 33 at 585 mhz Woman Mad

You are throwing modems at a signal level issue is a waste of time... TWC needs to come out and fix the lines.. Something has a broken or corroded shield/ connector!

 585 mHz is a known source of ingress in the Austin area, I show it's 16 miles from you and has extremely high field strength in  zip 78681

 591mHz ch 34 is further and 30 dB weaker.

 get TWC out, have them look at the s/n on all 16 of the modem channels at the modem.

 

Valued Participant

Re: Yet another SB6141 related issue?

@MsRaye types:  ...throwing modems at a signal level issue is a waste of time...

 

Yes, I get that.  Now.

 

...You are STILL having broadcast tv ingress from TV ch 34 at 591 mHz... TWC needs to come out and fix the lines.. Something has a broken or corroded shield/ connector!

 

@MsRaye  I truly appreciate you continued imput regarding this issue.

 

With that typed, any suggestions from a TWC-jane or TWC-joe regarding how to go about getting TWC to come 'out and fix'...

 

Would be greatly appreciated.

 

.

Expert

Re: Yet another SB6141 related issue?

crunching all your data, I'll bet 513,519, 525 and 585 mHz are useless and the 585 is so strong it's splattering into 591

 splattering usually indicates an overloaded amplifier, if you only have a splitter in house and no amplifier, the problem is probably before the amp that feeds your house. Are lines overhead and out on the street or in backyards?

 

 I believe it's an actual physical break in the shield of the aluminum hardline that connects most of the time then breaks open allowing ingress

 

 

Valued Participant

Re: Yet another SB6141 related issue?

@MsRaye types:   splattering usually indicates an overloaded amplifier, if you only have a splitter in house and no amplifier,

 

No amp in the house, no splitters.  Wiring is new drop from pole to TWC's junction box mounted on the side of my house > grounded block > straight run of RG6 > wall port > short patch cord > cablemodem.

 

I mentioned earlier that when the TWC tech was here installing the new drop from the pole, he also checked signal on the RG6 from TWC junction point on the outside of house to end of the patch cord that connects to the cablemodem.  Tech said my RG6 was ok.

 

 @MsRayetypes:  the problem is probably before the amp that feeds your house. Are lines overhead and out on the street or in backyards?

 

Overhead lines in the backyard which it makes it difficult for me to know what other hardware is in the area.

 

BTW, I took 3 additional pics after the new drop was install.  I think the lighting is better to see detail?  (My drop is off to the right in the pics where visible.)

 

https://picasaweb.google.com/martywd/SurfboardSB6141?authkey=Gv1sRgCKzD_q_33cn3jwE&feat=directlink

 

.