Participant

Re: Yet another SB6141 issue thread (slow DL speeds)

DownstreamBonding Channel Value
Channel ID17 21 25 27 28 
Frequency555000000 Hz 579000000 Hz 603000000 Hz 615000000 Hz 621000000 Hz 
Signal to Noise Ratio37 dB 37 dB 37 dB 36 dB 36 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
8 dBmV  8 dBmV  7 dBmV  6 dBmV  6 dBmV  

 

UpstreamBonding Channel Value
Channel ID
Frequency30600000 Hz 24200000 Hz 19400000 Hz 37000000 Hz 
Ranging Service ID6147 6147 6147 6147 
Symbol Rate5.120 Msym/sec 5.120 Msym/sec 2.560 Msym/sec 2.560 Msym/sec 
Power Level41 dBmV 39 dBmV 36 dBmV 39 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 ID17 21 25 27 28 
Total Unerrored Codewords21442091356 21099038885 20776194841 20726488447 20496336395 
Total Correctable Codewords47040 44520 18967 10637 11336 
Total Uncorrectable Codewords344384 189156 67564 14864 15622 

 

This is as of today. And the error log:

 

Sep 07 2016 19:47:595-WarningT202.0Lost MDD Timeout;CM-MAC=20:3d:66:0b:fc:5e;CMTS-MAC=00:17:10:86:ab:cb;CM-QOS=1.1;CM-VER=3.0;
Sep 07 2016 19:47:595-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=20:3d:66:0b:fc:5e;CMTS-MAC=00:17:10:86:ab:cb;CM-QOS=1.1;CM-VER=3.0;
Sep 07 2016 19:47:595-WarningT202.0Lost MDD Timeout;CM-MAC=20:3d:66:0b:fc:5e;CMTS-MAC=00:17:10:86:ab:cb;CM-QOS=1.1;CM-VER=3.0;
Sep 07 2016 19:47:595-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=20:3d:66:0b:fc:5e;CMTS-MAC=00:17:10:86:ab:cb;CM-QOS=1.1;CM-VER=3.0;
Sep 07 2016 19:47:595-WarningT202.0Lost MDD Timeout;CM-MAC=20:3d:66:0b:fc:5e;CMTS-MAC=00:17:10:86:ab:cb;CM-QOS=1.1;CM-VER=3.0;
Sep 07 2016 19:47:595-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=20:3d:66:0b:fc:5e;CMTS-MAC=00:17:10:86:ab:cb;CM-QOS=1.1;CM-VER=3.0;
Sep 05 2016 07:22:066-NoticeD106.0DHCP Renew - lease parameters time server-24.25.19.70;tftp file-?BEWGC1UgPWYL_F4K8R6b@CvEem2alicCF9zDCFw3GdAef4afY5fr3 modified;CM-MAC=20:3d:66:0b:fc:5e;CMTS-MAC=00:17:10:86:ab:cb;CM-QOS=1.1;CM-VER=3.0;
Sep 05 2016 07:22:064-ErrorD103.0DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=20:3d:66:0b:fc:5e;CMTS-MAC=00:17:10:86:ab:cb;CM-QOS=1.1;CM-VER=3.0;
Sep 04 2016 23:47:205-WarningT202.0Lost MDD Timeout;CM-MAC=20:3d:66:0b:fc:5e;CMTS-MAC=00:17:10:86:ab:cb;CM-QOS=1.1;CM-VER=3.0;
Sep 04 2016 23:47:205-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=20:3d:66:0b:fc:5e;CMTS-MAC=00:17:10:86:ab:cb;CM-QOS=1.1;CM-VER=3.0;
Sep 04 2016 23:47:205-WarningT202.0Lost MDD Timeout;CM-MAC=20:3d:66:0b:fc:5e;CMTS-MAC=00:17:10:86:ab:cb;CM-QOS=1.1;CM-VER=3.0;
Sep 04 2016 23:47:205-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=20:3d:66:0b:fc:5e;CMTS-MAC=00:17:10:86:ab:cb;CM-QOS=1.1;CM-VER=3.0;
Sep 04 2016 23:47:205-WarningT202.0Lost MDD Timeout;CM-MAC=20:3d:66:0b:fc:5e;CMTS-MAC=00:17:10:86:ab:cb;CM-QOS=1.1;CM-VER=3.0;
Sep 04 2016 23:47:205-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=20:3d:66:0b:fc:5e;CMTS-MAC=00:17:10:86:ab:cb;CM-QOS=1.1;CM-VER=3.0;
Sep 04 2016 20:30:405-WarningT202.0Lost MDD Timeout;CM-MAC=20:3d:66:0b:fc:5e;CMTS-MAC=00:17:10:86:ab:cb;CM-QOS=1.1;CM-VER=3.0;
Sep 04 2016 20:30:405-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=20:3d:66:0b:fc:5e;CMTS-MAC=00:17:10:86:ab:cb;CM-QOS=1.1;CM-VER=3.0;
Sep 04 2016 20:30:405-WarningT202.0Lost MDD Timeout;CM-MAC=20:3d:66:0b:fc:5e;CMTS-MAC=00:17:10:86:ab:cb;CM-QOS=1.1;CM-VER=3.0;
Sep 04 2016 20:30:405-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=20:3d:66:0b:fc:5e;CMTS-MAC=00:17:10:86:ab:cb;CM-QOS=1.1;CM-VER=3.0;
Sep 04 2016 20:30:405-WarningT202.0Lost MDD Timeout;CM-MAC=20:3d:66:0b:fc:5e;CMTS-MAC=00:17:10:86:ab:cb;CM-QOS=1.1;CM-VER=3.0;
Sep 04 2016 20:30:395-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=20:3d:66:0b:fc:5e;CMTS-MAC=00:17:10:86:ab:cb;CM-QOS=1.1;CM-VER=3.0;

 

Ive given it a couple of days to see how it performs, but still having consistent signal ingress on anything 600+ and still dropping channels. 

Expert

Re: Yet another SB6141 issue thread (slow DL speeds)

They need to be called back out, you had 2  total failures yesterday.

 

Participant

Re: Yet another SB6141 issue thread (slow DL speeds)

So, Im guessing they were out and shot the modem with a reset signal last night at some point. The "power reset" entry is definitely not right because the modem is on a UPS along with two servers and router, and neither of those have recorded downtime. One of the servers would have emailed me if it switch to battery backup, but I digress.

 

This is as of this morning:

DownstreamBonding Channel Value
Channel ID17 18 19 20 21 22 23 24 
Frequency555000000 Hz 561000000 Hz 567000000 Hz 573000000 Hz 579000000 Hz 585000000 Hz 591000000 Hz 597000000 Hz 
Signal to Noise Ratio38 dB 38 dB 38 dB 37 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
9 dBmV  9 dBmV  9 dBmV  9 dBmV  9 dBmV  9 dBmV  9 dBmV  8 dBmV  

 

UpstreamBonding Channel Value
Channel ID
Frequency30600000 Hz 24200000 Hz 19400000 Hz 37000000 Hz 
Ranging Service ID606 606 606 606 
Symbol Rate5.120 Msym/sec 5.120 Msym/sec 2.560 Msym/sec 2.560 Msym/sec 
Power Level39 dBmV 38 dBmV 37 dBmV 39 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 ID17 18 19 20 21 22 23 24 
Total Unerrored Codewords1904906518 1904312544 1904316358 1844251437 1844225575 1844214240 1844209509 1844199361 
Total Correctable Codewords29 3411 31 70 2769 28 1047 
Total Uncorrectable Codewords542 561 1539 1309 2055 1332 1239 1301 

 

TimePriorityCodeMessage
Sep 08 2016 19:32:316-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=20:3d:66:0b:fc:5e;CMTS-MAC=00:17:10:86:ab:cb;CM-QOS=1.1;CM-VER=3.0;
Sep 08 2016 19:32:315-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=20:3d:66:0b:fc:5e;CMTS-MAC=00:17:10:86:ab:cb;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:156-NoticeN/ACable Modem Reboot due to power reset ;CM-MAC=20:3d:66:0b:fc:5e;CMTS-MAC=00:17:10:86:ab:cb;CM-QOS=1.1;CM-VER=3.0;
Sep 08 2016 19:22:166-NoticeD106.0DHCP Renew - lease parameters time server-24.25.19.80;tftp file-?BEWGC1UgPWYL_F4K8R6b@CvEem6uIvVffmSLv4UYtZ7fZx8KZEVtv modified;CM-MAC=20:3d:66:0b:fc:5e;CMTS-MAC=00:17:10:86:ab:cb;CM-QOS=1.1;CM-VER=3.0;
Sep 08 2016 19:22:164-ErrorD103.0DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=20:3d:66:0b:fc:5e;CMTS-MAC=00:17:10:86:ab:cb;CM-QOS=1.1;CM-VER=3.0;
Sep 08 2016 14:37:033-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=20:3d:66:0b:fc:5e;CMTS-MAC=00:17:10:86:ab:cb;CM-QOS=1.1;CM-VER=3.0;
Sep 07 2016 19:47:595-WarningT202.0Lost MDD Timeout;CM-MAC=20:3d:66:0b:fc:5e;CMTS-MAC=00:17:10:86:ab:cb;CM-QOS=1.1;CM-VER=3.0;
Sep 07 2016 19:47:595-WarningN/A

DS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=20:3d:66:0b:fc:5e;CMTS-MAC=00:17:10:86:ab:cb;CM-QOS=1.1;CM-VER=3.0;

 

The lost MDD timeout at the bottom is the end of the previous log, so the T3 timeout and the DHCP renew warnings are new.

Expert

Re: Yet another SB6141 issue thread (slow DL speeds)

If you're on a UPS and got the power reset warning, either the modems supply is going bad or the modem itself.

 There's been an issue with one version of the 12 vdc 750 ma supplies, replace it with a 1 or 1.5 amp 12vdc center pin + regulated supply to eliminate that possibility.

 

You can't remotely cause a power reset error. It is a power failureof some sort.