Community Forums

Yet another SB6141 related issue?

Reply

Yet another SB6141 related issue?

martywd
Valued Participant
‎06-22-2016 06:34 PM
‎06-22-2016 06:34 PM

Re: Yet another SB6141 related issue?

@MsRaye wrote:

The 3 connectors look corroded and the terminator even worst, It also looks like there might not be a stainless screw in the bottom hole and a lot of corrosion, if so it needs to be replaced as well.

 I took a 'close up' pic today from my side of the fence.

 

Connections

 

Looks like the bottom screw is there.  But some of the other stuff doesn't look so great.  My tap is top right.

 

Again and FWIW, for a high rez zoomable of this pic go to my google photos link and scroll down:

 

https://goo.gl/photos/bqVq42NhnMhq1t59A

 

Modem up ~10+ days last time I was able to connect to the SB6141's embedded webserver this a.m.  Further browsing to the SB6141 started failing early afternoon today so 'Signal' and/or 'Log' collection no longer possible at this time, thus not added to this post.  DS speed still ok at the moment.  No change of the LED display on the modem thus far so I'm just going to let this SB6141 run and see what happens next!

.

 

0 Enjoys
MsRaye
Expert
‎06-22-2016 07:26 PM
‎06-22-2016 07:26 PM

Re: Yet another SB6141 related issue?

Connectors don't look awfull, the terminator looks terrible, unknown what shape the internal, non floting actual terminating resistor looks like

, I'd suspect the connection on the other side of the amp, but it should affect everyone on your tapoff and to the right of it

 

 

0 Enjoys
martywd
Valued Participant
‎06-30-2016 03:00 PM
‎06-30-2016 03:00 PM

Re: Yet another SB6141 related issue?

The SB6141 ran uninterrupted for ~17 days.

 

Had to reboot the SB6141 yesterday.  LEDs look 'normal', (solid blue Receive (DS), solid blue Send (US), solid green Online, flashing blue Link.  No hint from the LED display that there was trouble.  As is usually the case I didn't lose Internet, but browsing slowed way down.  Did a couple of speedtests, speedtest.net showed 0.55 Mbps down, 11.71 Mbps up, dslreport's speedtest:  3.28 Mbps down, 3.73 Mbps up.  (Speeds when all is well are normally in the range of 100+ Mbps down / 10+ Mbps up).  I was able to login to my TWC account to troubleshoot the cablemodem which indicated that the cablemodem was not connected (red dot).

 

Anyway.  Like I just typed, rebooted.  It's been up 24 hours now so I'll post Signal and Logs.  Times are off by an hour, times shown are CST.

 

Cable Modem OperationValue

Current Time and DateJun 30 2016 15:52:48
System Up Time1 days 1h:13m:24s

 

Signal:

DownstreamBonding Channel Value
Channel ID1 2 3 4 5 6 9 13 
Frequency501000000 Hz 507000000 Hz 513000000 Hz 519000000 Hz 525000000 Hz 531000000 Hz 549000000 Hz 573000000 Hz 
Signal to Noise Ratio38 dB 39 dB 39 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
4 dBmV  4 dBmV  4 dBmV  4 dBmV  4 dBmV  4 dBmV  4 dBmV  4 dBmV  
UpstreamBonding Channel Value
Channel ID4 2 3 1 
Frequency37000000 Hz 24200000 Hz 30600000 Hz 19400000 Hz 
Ranging Service ID4932 4932 4932 4932 
Symbol Rate2.560 Msym/sec 5.120 Msym/sec 5.120 Msym/sec 2.560 Msym/sec 
Power Level46 dBmV 47 dBmV 46 dBmV 46 dBmV 
Upstream Modulation[3] QPSK
[3] 16QAM
 		[3] QPSK
[1] 16QAM
[2] 64QAM
 		[3] QPSK
[1] 16QAM
[2] 64QAM
 		[3] QPSK
[2] 16QAM
 
Ranging StatusSuccess Success Success Success 
Signal Stats (Codewords)Bonding Channel Value
Channel ID1 2 3 4 5 6 9 13 
Total Unerrored Codewords4129648080 4128933162 4128941319 4128951540 4128924561 4128925552 4125415869 4031048929 
Total Correctable Codewords4 277 306 118 45 18 30 56 
Total Uncorrectable Codewords1260 1483 1483 534 1410 1509 2985 4582 

 

Log:

TimePriorityCodeMessage

Jun 30 2016 13:51:463-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=10:05:b1:f7:10:7d;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Jun 29 2016 15:09:516-NoticeD106.0DHCP Renew - lease parameters tftp file-?BEWGlxUQBbH3EH0KQRA_@CkEQPxb60XuvfpiuPvh3XNCvCar_xPt9 modified;CM-MAC=10:05:b1:f7:10:7d;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Jun 29 2016 14:39:546-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=10:05:b1:f7:10:7d;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Jun 29 2016 14:39:545-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=10:05:b1:f7:10:7d;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=10:05:b1:f7:10:7d;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jun 29 2016 13:05:026-NoticeN/AMDD Recovery following MDD Loss;CM-MAC=10:05:b1:f7:10:7d;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Jun 28 2016 08:54:333-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=10:05:b1:f7:10:7d;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Jun 21 2016 23:41:213-CriticalT05.0SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=10:05:b1:f7:10:7d;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Jun 19 2016 16:16:165-WarningT202.0Lost MDD Timeout;CM-MAC=10:05:b1:f7:10:7d;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Jun 19 2016 16:16:165-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=10:05:b1:f7:10:7d;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Jun 19 2016 16:16:165-WarningT202.0Lost MDD Timeout;CM-MAC=10:05:b1:f7:10:7d;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Jun 19 2016 16:16:165-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=10:05:b1:f7:10:7d;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Jun 18 2016 11:52:366-NoticeD106.0DHCP Renew - lease parameters tftp file-?BEWGlxUQBbH3EH0KQRA_@CkEQP_cOmIOzLPRkmeEoayMVD5Fcd3Vn modified;CM-MAC=10:05:b1:f7:10:7d;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Jun 17 2016 20:22:535-WarningT202.0Lost MDD Timeout;CM-MAC=10:05:b1:f7:10:7d;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Jun 17 2016 20:22:535-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=10:05:b1:f7:10:7d;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Jun 17 2016 20:22:535-WarningT202.0Lost MDD Timeout;CM-MAC=10:05:b1:f7:10:7d;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Jun 17 2016 20:22:535-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=10:05:b1:f7:10:7d;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Jun 17 2016 20:22:535-WarningT202.0Lost MDD Timeout;CM-MAC=10:05:b1:f7:10:7d;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Jun 17 2016 20:22:535-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=10:05:b1:f7:10:7d;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Jun 15 2016 19:29:595-WarningT202.0Lost MDD Timeout;CM-MAC=10:05:b1:f7:10:7d;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;

 

 

 

.

 

0 Enjoys
martywd
Valued Participant
‎07-14-2016 07:04 PM
‎07-14-2016 07:04 PM

Re: Yet another SB6141 related issue?

This issue continues...  Cablemodem rebooted on it's own earlier this a.m. and again this afternoon (Tuesday, 07/14/16).  This afternoon was when I notice loss of Internet connectivity but didn't check the log until a few minutes ago.   Signal and Logs follow.  Logs are CST.

 

Cable Modem OperationValue

Current Time and DateJul 14 2016 19:54:28
System Up Time0 days 18h:5m:20s

 

 

DownstreamBonding Channel Value
Channel ID7 8 9 10 1 3 5 6 
Frequency501000000 Hz 507000000 Hz 513000000 Hz 519000000 Hz 465000000 Hz 477000000 Hz 489000000 Hz 495000000 Hz 
Signal to Noise Ratio39 dB 39 dB 39 dB 39 dB 39 dB 40 dB 40 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
4 dBmV  4 dBmV  4 dBmV  4 dBmV  4 dBmV  4 dBmV  4 dBmV  5 dBmV  
UpstreamBonding Channel Value
Channel ID3 2 1 4 
Frequency30600000 Hz 24200000 Hz 19400000 Hz 37000000 Hz 
Ranging Service ID1490 1490 1490 1490 
Symbol Rate5.120 Msym/sec 5.120 Msym/sec 2.560 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
[1] 16QAM
[2] 64QAM
 		[3] QPSK
[2] 16QAM
 		[3] QPSK
[3] 16QAM
 
Ranging StatusSuccess Success Success Success 
Signal Stats (Codewords)Bonding Channel Value
Channel ID7 8 9 10 1 3 5 6 
Total Unerrored Codewords2889163450 2863523868 2863555920 2758233368 2863438781 2863419293 2863459679 2863505943 
Total Correctable Codewords34 47 67 31 75 45 58 62 
Total Uncorrectable Codewords3731 4260 4381 6064 3660 4481 3979 3594 

 

 

TimePriorityCodeMessage

Jul 14 2016 01:58:346-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=10:05:b1:f7:10:7d;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Jul 14 2016 01:58:345-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=10:05:b1:f7:10:7d;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:09:163-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=10:05:b1:f7:10:7d;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:06:065-WarningR09.0B-INIT-RNG Failure - Retries exceeded;CM-MAC=10:05:b1:f7:10:7d;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:05:453-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=10:05:b1:f7:10:7d;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=10:05:b1:f7:10:7d;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jul 14 2016 01:48:513-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:05:b1:f7:10:7d;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Jul 14 2016 01:23:096-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=10:05:b1:f7:10:7d;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Jul 14 2016 01:23:095-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=10:05:b1:f7:10:7d;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=10:05:b1:f7:10:7d;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Jul 14 2016 01:22:183-CriticalR06.0Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=10:05:b1:f7:10:7d;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Jul 14 2016 01:22:183-CriticalR03.0Ranging Request Retries exhausted;CM-MAC=10:05:b1:f7:10:7d;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Jul 14 2016 01:22:173-CriticalR06.0Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=10:05:b1:f7:10:7d;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Jul 14 2016 01:22:173-CriticalR03.0Ranging Request Retries exhausted;CM-MAC=10:05:b1:f7:10:7d;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Jul 14 2016 01:22:173-CriticalR06.0Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=10:05:b1:f7:10:7d;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Jul 14 2016 01:22:173-CriticalR03.0Ranging Request Retries exhausted;CM-MAC=10:05:b1:f7:10:7d;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Jul 14 2016 01:22:153-CriticalR06.0Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=10:05:b1:f7:10:7d;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Jul 14 2016 01:22:153-CriticalR03.0Ranging Request Retries exhausted;CM-MAC=10:05:b1:f7:10:7d;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Jul 14 2016 01:22:083-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=10:05:b1:f7:10:7d;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Jul 14 2016 01:20:305-WarningT202.0Lost MDD Timeout;CM-MAC=10:05:b1:f7:10:7d;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;

 

 

 

 

 

.

 

 

0 Enjoys
MsRaye
Expert
‎07-14-2016 07:26 PM
‎07-14-2016 07:26 PM

Re: Yet another SB6141 related issue?

@MsRaye wrote:

You still have DS partial service gropped channels on those shared with local broadcast TV channels?

Did they change the connector up on the pole tap off block? Actually they should change all 4Robot Sad

 

 Partial DS=  still have ingress, my gut feeling is it's this connecter, the aluminum hardline is broken under the glue filled shrink thanks to no strain relief doglegs and the neighbors drop tugging on the messenger in the wind.

This takes the bucket truck guys to fix, eventually the center wire will break taking out service completely.

The iside stuff has reduced the problem, not eliminated it

 

 

Modems don't have ingress issues, especially the 6121,41,83,92, it's a coax issueWoman Sad

  If all connectors in the house are new and tight, it's outside somewhere. nothing you pulled and pictured looks bad! BTW, when you do compression F's, you leave the foil intackt, but fan out the braid back over the black insulation so the the connecors inner ferrule slides between the braid and the foil

The white dielectric foam will then come up to the inside of the threaded nut.

 

Probably this:

 

STILL SAY THIS CONNECTION NEEDS TO BE REDONE, I FEEL THE ALUMINUM IS BROKEN, INTERMITTENT. IT'S INSTALLED WRONG WITH THAT DROP BEHIND IT ADDING STRESS TO THE MESSENGER.

 

0 Enjoys