Valued Participant

Re: Yet another SB6141 related issue?

FWIW...

 

Last Thursday (3/24/16) I got the promised call back from Arris.  After some initial suggestions that I contact TWC to remove my SB6141 from 'the system' and then provision ONCE AGAIN, the support guy relented to doing an RMA on my current SB6141.  With a payment charged to my credit card of $9.50 I'll get a replacement SB6141 (5-7 day Fedex/SmartPost) and once received, ship back (at my expense also) my current SB6141.

 

Further 'Signal' or 'Logs' at this time will be irrelevant since I've setup a cron job to reboot my current SB6141 daily in an attempt to avoid further connectivity issues.

.

Expert

Re: Yet another SB6141 related issue?

Try another but I think you're throwing modems at a line issue

 

Expert

Re: Yet another SB6141 related issue?

cpboy99 ????? please start a new thread

 

 

Valued Participant

Re: Yet another SB6141 related issue?


@MsRaye wrote:

Try another but I think you're throwing modems at a line issue

 


Once again I agree in principle.  But...  After 60+ replies to and 700+ views of this thread with NOT ONE contribution from a TWC-type, I get it, TWC will not take this issue seriously.  So.  I throw modems at the problem!

 

Anyway here's some details regarding the 'new' SB6141 I received yesterday (Apr 2, 2016) from Arris:

Model Name: SB6141

Vendor Name: Motorola

Firmware Name: SB_KOMODO-1.0.6.14-SCM03-NOSH

Boot Version: PSPU-Boot(25CLK)(W) 1.0.12.18m5

Hardware Version: 8.0

Serial Number: 000000000000000000000000000

Firmware Build Time: Jan 22 2015 14:31:03

 

Yup.  Version 8!

 

Since provisioning by TWC, yesterday, this modem has already automagically rebooted 2 or 3 times thus far without any intervention on my part.  I kind of like that this modem is a able to 'recover' (thus far) rather than just crashing and messing with my Internet connectiviy like the old 'SB6141' was doing which caused the creation of this post in the first place.

 

Yesterday's logs after provisioning:

TimePriorityCodeMessage

Apr 02 2016 18:33:176-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;
Apr 02 2016 18:33:175-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:213-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;
Apr 02 2016 18:32:303-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;
Apr 02 2016 18:32:293-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;
Apr 02 2016 18:32:293-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;
Apr 02 2016 18:32:293-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;
Apr 02 2016 18:32:283-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;
Apr 02 2016 18:32:283-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;
Apr 02 2016 18:32:283-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;
Apr 02 2016 18:32:283-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;
Apr 02 2016 18:32:273-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;
Apr 02 2016 18:32:253-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;
Apr 02 2016 18:32:243-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;
Apr 02 2016 18:32:243-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;
Apr 02 2016 15:48:406-NoticeD106.0DHCP Renew - lease parameters time server-72.183.82.18;tftp file-?BEWGlxUQBbH3EH0KQRA_@CkEQPyV+MX1pfWA0mGx8tMPddoRJ1P33 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;
Apr 02 2016 15:24:596-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;
Apr 02 2016 15:24:595-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;

 

Posting Signal is probably useless information because of the rebooting but here's Signal as of now:

DownstreamBonding Channel Value
Channel ID11 
Frequency501000000 Hz 507000000 Hz 513000000 Hz 525000000 Hz 531000000 Hz 537000000 Hz 549000000 Hz 561000000 Hz 
Signal to Noise Ratio39 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
6 dBmV  6 dBmV  6 dBmV  5 dBmV  5 dBmV  5 dBmV  5 dBmV  5 dBmV  

 

UpstreamBonding Channel Value
Channel ID
Frequency30600000 Hz 24200000 Hz 19400000 Hz 37000000 Hz 
Ranging Service ID3771 3771 3771 3771 
Symbol Rate5.120 Msym/sec 5.120 Msym/sec 2.560 Msym/sec 2.560 Msym/sec 
Power Level47 dBmV 47 dBmV 46 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 ID11 
Total Unerrored Codewords1417444129 1416849265 1416871891 1353269615 1353250122 1353252641 1255470578 1353251158 
Total Correctable Codewords28 15 20 36 28 107 33 
Total Uncorrectable Codewords1387 1383 577 2974 3070 2955 4425 3011 

 

 And also the latest logs:

 

 

TimePriorityCodeMessage

Apr 03 2016 07:24: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;
Apr 03 2016 07:24: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: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;
Apr 03 2016 07:23:533-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;
Apr 03 2016 07:23:533-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;
Apr 03 2016 07:23:533-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;
Apr 03 2016 07:23:533-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;
Apr 03 2016 07:23:523-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;
Apr 03 2016 07:23:523-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;
Apr 03 2016 07:23:523-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;
Apr 03 2016 07:23:523-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;
Apr 03 2016 07:23:523-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;
Apr 03 2016 07:12:596-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;
Apr 03 2016 07:12:595-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;
Apr 03 2016 07:12:173-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;
Apr 03 2016 07:12:163-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;
Apr 03 2016 07:12:163-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;
Apr 03 2016 07:12:163-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;
Apr 03 2016 07:12:163-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;

 

 Hmmmm?  Multiple T3/T4s.  Nothing to see here, TWC.  Move along...

 

LOL

.

Expert

Re: Yet another SB6141 related issue?

Yeah, still looks like intermittent breaks in the outside line.

 Call TWC back out

 

 

 This modem is version 8 hardware, the other was version 7

It also has newer firmware

Neither fix bad or intermittent up/downstream rf

 

Valued Participant

Re: Yet another SB6141 related issue?

As suspected by @MsRaye there has been no improvement in TWC service with the installation of the new SB6141 that came with Hardware Version 8.0 firmware received from Arris on warranty.  In the weeks since my last post I've seen 4 o4 5 days of daily reboots from T4 errors.  When the T4's are not happening I'll see days of DS Partial Service Fallback errors.  As I type the SB6141 is down to five Downstream Channels which means a service disruption is imminent in the next few hours.

 

Current Signal and Logs:

DownstreamBonding Channel Value
Channel ID
Frequency501000000 Hz 513000000 Hz 525000000 Hz 531000000 Hz 549000000 Hz 
Signal to Noise Ratio39 dB 39 dB 39 dB 39 dB 38 dB 
Downstream ModulationQAM256 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  5 dBmV  

 

UpstreamBonding Channel Value
Channel ID
Frequency30600000 Hz 24200000 Hz 19400000 Hz 37000000 Hz 
Ranging Service ID2624 2624 2624 2624 
Symbol Rate5.120 Msym/sec 5.120 Msym/sec 2.560 Msym/sec 2.560 Msym/sec 
Power Level47 dBmV 48 dBmV 47 dBmV 47 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 ID
Total Unerrored Codewords10153990072 10064473230 10064491294 10048529966 10063355256 
Total Correctable Codewords2443 3261 2845 2598 2630 
Total Uncorrectable Codewords11511 11901 12025 12977 13628 

 

 

TimePriorityCodeMessage

Apr 25 2016 17:37:575-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;
Apr 25 2016 17:37:575-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;
Apr 25 2016 17:37:575-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;
Apr 25 2016 17:37:575-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;
Apr 25 2016 11:31:483-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;
Apr 25 2016 06:34:196-NoticeD106.0DHCP Renew - lease parameters tftp file-?BEWGlxUQBbH3EH0KQRA_@CkEQP81BxA3gr_clRkN9kMGuc+gIUf7v 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;
Apr 24 2016 21:04:175-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;
Apr 24 2016 21:04:175-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;
Apr 24 2016 18:52: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;
Apr 23 2016 09:07:456-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;
Apr 23 2016 09:07:455-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:213-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;
Apr 23 2016 09:06:563-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;
Apr 23 2016 09:06:553-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;
Apr 23 2016 09:06:553-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;
Apr 23 2016 09:06:553-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;
Apr 23 2016 09:06:543-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;
Apr 23 2016 09:06:543-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;
Apr 23 2016 09:06:543-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;

 

 

FWIW, I've set up a cron job to reboot the SB6141 every other day.  I figure at some point TWC will have to respond to this issue but until then regular cablemodem reboots will be my workaround.

 

.

Expert

Re: Yet another SB6141 related issue?

You're throwing modems at line issues somewhere on the node. The first place I'd start is with this INCORRECTLY INSTALLED AMPLIFIER IN YOUR BACKYARD...My moneys on broken hardline shielding because of no expansion loop on the left side and the drop behind it anchored to the messenger rather than the pole. SORRY BUT IT"S PLAIN WRONG...  ( ignore the red arrow, that's not the drop that's tugging on the amp)

 

.

 

Valued Participant

Re: Yet another SB6141 related issue?

Recap:

 

Model Name: SB6141
Vendor Name: Motorola
Firmware Name: SB_KOMODO-1.0.6.14-SCM03-NOSH
Boot Version: PSPU-Boot(25CLK)(W) 1.0.12.18m5
Hardware Version: 8.0
Serial Number: xxxxxxxxxxxxxxxxxxxxxxx
Firmware Build Time: Jan 22 2015 14:31:03

 

Zip Code:  78681

 

Out of town for a couple/three weeks in May so this issue was on the back burner for a while.  A couple a weeks ago after my SB6141 rebooted 4 times unasisted in 24 hours I went up to TWC's store to complain.  Again.  That was on a Tuesday, they gave me an appointment for the following Friday.  I keep asking that they send someone who will check signal egress at the hardware on the utility pole.  They never do.

 

Prior to the 4 reboots in one day, the cablemodem had been rebooting on it's own at least once a day without any intervention on my part.  Of course after getting the latest appointment the router never rebooted again!  Friday _two_ TWC techs arrived a head of schedule (not complaining!).  One tech was a 'ride-along' recovering from work related injury.  What was done?  A change out of the grounding block, the connectors on either end of the RG6 running from demarc to wall port in my house, the barrel connector at the wall port, and the patch cord that connects from wall port to the modem.

 

The reason given for replacing the ground block and barrel connector was because 'the colors was wrong'.  I retrieved the original ground block I had purchased from amazon which I had installed to replace an unnecessary splitter after dropping TV, but not the barrel connector that was replaced at the wall port.  After replacing ground block, RG6 cable connectors, barrel connector, tech's hooked up a meter and check signal on various channels with the test meter plugged into the end of the patch cord usually plugged into the cablemodem.  I don't recall which channels they were actually testing?  The proclamation?  'All looks good'.

 

Here's the original ground block:

Wrong color

 

The barrel connector _originally_ installed was identical to the following examples pictured below:

 

Wrong color

 

Anyway.  Replacing all this stuff has made a difference.  The SB6141 has been up for 8 days 4h:54m:2s as I type.  That's the good news.

 

The bad new is DS channels are still being dropped.  And now DS speed is starting to suffer:  Here's the latest 'Signal':

 

DownstreamBonding Channel Value
Channel ID12 
Frequency501000000 Hz 525000000 Hz 543000000 Hz 567000000 Hz 
Signal to Noise Ratio38 dB 39 dB 38 dB 37 dB 
Downstream ModulationQAM256 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  4 dBmV  4 dBmV  5 dBmV  

 

UpstreamBonding Channel Value
Channel ID
Frequency37000000 Hz 24200000 Hz 30600000 Hz 19400000 Hz 
Ranging Service ID1728 1728 1728 1728 
Symbol Rate2.560 Msym/sec 5.120 Msym/sec 5.120 Msym/sec 2.560 Msym/sec 
Power Level46 dBmV 47 dBmV 47 dBmV 47 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 ID12 
Total Unerrored Codewords32224037313 31864840082 31766680318 31731320588 
Total Correctable Codewords123 276 184 160 
Total Uncorrectable Codewords1432 15648 17439 13928 

 

 

And the log:

 

TimePriorityCodeMessage

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;
Jun 15 2016 19:29:595-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 14 2016 23:52:256-NoticeD106.0DHCP Renew - lease parameters time server-72.183.77.48;tftp file-?BEWGlxUQBbH3EH0KQRA_@CkEQP__scIowRwGCl4iWeSUQEN6vQB9z 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 14 2016 21:46:435-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 14 2016 21:46:435-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 12 2016 11:07:076-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 12 2016 11:07:075-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:203-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:166-NoticeN/ACable Modem Reboot due to power reset ;CM-MAC=10:05:b1:f7:10:7d;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;

 

 Oh, and yeah, one of the techs wanted to blame the SB6141 for all my problems.  The other tech, not so much!

 

Higer rez of pics shown above as well as some additional pics of connector types and tools originally used with my RG6 installation from demarc to wall port that I've added (scroll down) to my 'Surfboard SB6141' 'reference' album at the following url:

 

https://goo.gl/photos/bqVq42NhnMhq1t59A

 

FWIW.

.

 

 

Expert

Re: Yet another SB6141 related issue?

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:

 

Expert

Re: Yet another SB6141 related issue?

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.