Expert

Re: Yet another SB6141 related issue?

To the left is where the head end is and that's probably where the ingress is getting in. I don't like the lack of a strain /expansion reliefe right at the amps left side, this may be where the break is.  The amp and messenger cable are being pulled out of line due to the drop that's attached to the messenger that goes to a back house on the next street.

I'd call twc out again, tell them to fix this, It meets no proper outside plant standards....

 

Contributor

Re: Yet another SB6141 related issue?

Sigh, they really need to remove the SB6141 from the approved modems list. Smiley Frustrated

I'm just thinking out loud but perhaps a sticky should be made for SB6141 users logging all issues plaguing that device.

He has no issues with the Ubee and I'm quite sure if he were to lease a company owned modem (DG1670A) then he'd have no issues either.

Expert

Re: Yet another SB6141 related issue?

There's nothing wrong with the 6141, He has a line problem, probably on the left connector of the above pictured amplifier...

IT's broke, there's no strain relief

 

Valued Participant

Re: Yet another SB6141 related issue?

I returned the Ubee DDW36C to TWC yesterday (Tues 3/15/16).  The SB6141 has been running continuously now since Mar 8.  I've lost a couple of Downstream Channels along the way but connectivity has been stable and speeds good thus far.  Maybe the 'Reset All Defaults' mentioned in my previous post help?

 

When I took the DDW36C back, I also gave the lady (Paula) at the counter who helped with the cablemodem return a two page summary with pic of 'suggestions' that @MsRaye has kindly provided to this thread, plus 3 more pages of printouts of @MsRaye specific comments that included pics in this thread and requested of Paula that this summary of issues be forwarded to others at TWC for futher review.  Paula said she would do that.

 

Logs first this time:

TimePriorityCodeMessage

Mar 15 2016 19:36:183-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 12 2016 15:15:145-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 12 2016 15:15:145-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 12 2016 15:15:145-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 12 2016 15:15:145-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 11 2016 01:01:395-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 11 2016 01:01:395-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 11 2016 01:01:146-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;
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;

 

 And current 'Signal':

DownstreamBonding Channel Value
Channel ID10 12 13 14 
Frequency501000000 Hz 531000000 Hz 555000000 Hz 567000000 Hz 573000000 Hz 579000000 Hz 
Signal to Noise Ratio38 dB 39 dB 39 dB 39 dB 39 dB 37 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
7 dBmV  5 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 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 ID10 12 13 14 
Total Unerrored Codewords30049021795 29643439183 29165947936 29379870714 29359561854 28948138591 
Total Correctable Codewords218 556 221 281 263 
Total Uncorrectable Codewords565 7840 13023 7383 7668 32692 

 

 

.

Valued Participant

Re: Yet another SB6141 related issue?

Speed down to 2-3 Mbit/s a little while ago.  Connectivity was starting to get flaky.  Could _not_ browse to the cablemodem (192.168.100.1) at all to check logs, etc.  Had to pull the power cord on the cablemodem to reboot.

 

After reboot see:  'No Ranging Response received - T3 time-out...' error just prior to reboot in the log.

 

TimePriorityCodeMessage

Mar 20 2016 17:54:596-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 20 2016 17:54:585-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 20 2016 17:54: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 20 2016 17:54: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:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Mar 19 2016 22:26:403-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 19 2016 21:56:455-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 19 2016 21:56:455-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 19 2016 21:56:455-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 19 2016 21:56:455-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 18 2016 15:32:285-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 18 2016 15:32:285-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 17 2016 22:00:296-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 17 2016 22:00:285-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 17 2016 22:00:006-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 17 2016 22:00:005-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 17 2016 20:45: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;
Mar 17 2016 20:45:395-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 17 2016 20:45:174-ErrorT06.0RCS Primary DS Failure;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;

 

Yeah i know.  Gotta make another call to TWC.

.

Expert

Re: Yet another SB6141 related issue?

need the signal page

ds partial service is the loss of ds channels due to severe ingress

 

Valued Participant

Re: Yet another SB6141 related issue?

 @MsRaye types:

  need the signal page
ds partial service is the loss of ds channels due to severe ingress

 

 Sorry.  I thought it had to run for a while before the 'Signal' page showed anything relevent.

 

Here's the 'Signal' at current time:

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

 

UpstreamBonding Channel Value
Channel ID
Frequency24200000 Hz 19400000 Hz 30600000 Hz 37000000 Hz 
Ranging Service ID7410 7410 7410 7410 
Symbol Rate5.120 Msym/sec 2.560 Msym/sec 5.120 Msym/sec 2.560 Msym/sec 
Power Level48 dBmV 46 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 Codewords238612670 237715583 237725195 237734261 237710682 237711852 237714254 237734252 
Total Correctable Codewords18 17 47 51 19 
Total Uncorrectable Codewords571 517 474 497 659 681 616 625 

 

 

.

Expert

Re: Yet another SB6141 related issue?

Levels look good for now, I'm not seeing the typical Austin ingress right now

Has TWC been out to fix anything on that amplifier? It might only act up when windy out.

 

Valued Participant

Re: Yet another SB6141 related issue?

@MsRaye types:

>Has TWC been out to fix anything on that amplifier?

 

No TWC activity that I've seen in the area.

 

>It might only act up when windy out.

 

Front came through yesterday.  Temps went from high 80s-90s down into the 50s today.  Frost warnings tonight.  A bit of a breeze this p.m. but nothing special.

 

.

Expert

Re: Yet another SB6141 related issue?

so it looks like the DS partial services occurred when it was windy?

 

Can you get a picture under the amp looking up? it looks like the lines kinked/broken there