Expert

Re: Speed drop with 2 different SB6141 modems

these are coaxial issues:

"Lost MDD Timeout" or "DS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode"?

 

this is the proper firmware:

Model Name: SB6141
Vendor Name: Motorola
Firmware Name: SB_KOMODO-1.0.6.14-SCM01-NOSH
Boot Version: PSPU-Boot(25CLK) 1.0.12.18m3
Hardware Version: 7.0
Serial Number: 0001
Firmware Build Time: Mar 6 2014 15:23:55

Rookie

Re: Speed drop with 2 different SB6141 modems

I have been experiencing the exact same issue exacly as described here. They have even installed a new line and I am still experiencing drops to 1-2M Mbs. I noticed my firmware version is different from the one posted above so I'm wondering if I could call TWC and ask to push the correct firmware. This is what I currently have:

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: 39XXXXXX
Firmware Build Time: Jan 22 2015 14:31:03

 

If anyone have any suggestion please help.

 

Adding my logs below:

 

May 14 2016 19:19:553-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=20:3d:66:03:75:29;CMTS-MAC=00:17:10:87:38:4c;CM-QOS=1.1;CM-VER=3.0;
May 14 2016 18:04:596-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=20:3d:66:03:75:29;CMTS-MAC=00:17:10:87:38:4c;CM-QOS=1.1;CM-VER=3.0;
May 14 2016 18:04:595-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=20:3d:66:03:75:29;CMTS-MAC=00:17:10:87:38:4c;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:03:75:29;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
May 14 2016 17:54:526-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=20:3d:66:03:75:29;CMTS-MAC=00:17:10:87:38:4c;CM-QOS=1.1;CM-VER=3.0;
May 14 2016 17:54:525-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=20:3d:66:03:75:29;CMTS-MAC=00:17:10:87:38:4c;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:03:75:29;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
May 14 2016 17:13:403-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=20:3d:66:03:75:29;CMTS-MAC=00:17:10:87:38:4c;CM-QOS=1.1;CM-VER=3.0;
May 14 2016 15:09:205-WarningT202.0Lost MDD Timeout;CM-MAC=20:3d:66:03:75:29;CMTS-MAC=00:17:10:87:38:4c;CM-QOS=1.1;CM-VER=3.0;
May 14 2016 15:09:205-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=20:3d:66:03:75:29;CMTS-MAC=00:17:10:87:38:4c;CM-QOS=1.1;CM-VER=3.0;
May 14 2016 15:09:205-WarningT202.0Lost MDD Timeout;CM-MAC=20:3d:66:03:75:29;CMTS-MAC=00:17:10:87:38:4c;CM-QOS=1.1;CM-VER=3.0;
May 14 2016 15:09:205-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=20:3d:66:03:75:29;CMTS-MAC=00:17:10:87:38:4c;CM-QOS=1.1;CM-VER=3.0;
May 14 2016 12:03:183-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=20:3d:66:03:75:29;CMTS-MAC=00:17:10:87:38:4c;CM-QOS=1.1;CM-VER=3.0;
May 14 2016 08:30:293-CriticalT05.0SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=20:3d:66:03:75:29;CMTS-MAC=00:17:10:87:38:4c;CM-QOS=1.1;CM-VER=3.0;
May 14 2016 08:30:103-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=20:3d:66:03:75:29;CMTS-MAC=00:17:10:87:38:4c;CM-QOS=1.1;CM-VER=3.0;
May 13 2016 19:17:495-WarningT202.0Lost MDD Timeout;CM-MAC=20:3d:66:03:75:29;CMTS-MAC=00:17:10:87:38:4c;CM-QOS=1.1;CM-VER=3.0;
May 13 2016 19:17:495-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=20:3d:66:03:75:29;CMTS-MAC=00:17:10:87:38:4c;CM-QOS=1.1;CM-VER=3.0;
May 13 2016 19:17:266-NoticeN/AMDD Recovery following MDD Loss;CM-MAC=20:3d:66:03:75:29;CMTS-MAC=00:17:10:87:38:4c;CM-QOS=1.1;CM-VER=3.0;
May 13 2016 18:56:013-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=20:3d:66:03:75:29;CMTS-MAC=00:17:10:87:38:4c;CM-QOS=1.1;CM-VER=3.0;
May 11 2016 08:43:566-NoticeD106.0DHCP Renew - lease parameters tftp file-?BEWGlx0gPWYDdSkK+Hvg@Cvh74HrQrNZKEwlo59aetLNayoQ1rP_W modified;CM-MAC=20:3d:66:03:75:29;CMTS-MAC=00:17:10:87:38:4c;CM-QOS=1.1;CM-VER=3.0;

 

 

Expert

Re: Speed drop with 2 different SB6141 modems

you have the new version 8.0 hardware modem... the firmware is probably ok, post the signa;l level page

 

Rookie

Re: Speed drop with 2 different SB6141 modems

Here are my signals

 

DownstreamBonding Channel Value
Channel ID15 
Frequency531000000 Hz 537000000 Hz 543000000 Hz 549000000 Hz 561000000 Hz 567000000 Hz 573000000 Hz 615000000 Hz 
Signal to Noise Ratio38 dB 38 dB 38 dB 38 dB 37 dB 38 dB 38 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
2 dBmV  1 dBmV  1 dBmV  1 dBmV  1 dBmV  1 dBmV  1 dBmV  3 dBmV  

 

UpstreamBonding Channel Value
Channel ID
Frequency37000000 Hz 24200000 Hz 30600000 Hz 19400000 Hz 
Ranging Service ID2082 2082 2082 2082 
Symbol Rate2.560 Msym/sec 5.120 Msym/sec 5.120 Msym/sec 2.560 Msym/sec 
Power Level43 dBmV 44 dBmV 44 dBmV 44 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 ID15 
Total Unerrored Codewords7276423935 7275791385 7275799500 7275782780 7208984544 7208971859 7208964256 7209026172 
Total Correctable Codewords14 23 79 34 35 1535 
Total Uncorrectable Codewords493 1343 1423 1331 2079 2990 3158 3003 
Spectrum Employee

Re: Speed drop with 2 different SB6141 modems


@JFab wrote:

Here are my signals


I'm going to add some info on my own.  I think you might have a legit modem issue and/or return signal issue. 

 

Upstream / Return SNR (signal-to-noise ratio) is bleh... too low...

37.00 MhzATDMA  42.3 dBmv  22.4 dB
24.20 MhzATDMA  44.8 dBmv  15.6 dB
30.60 MhzATDMA  44.3 dBmv  21.9 dB
19.40 MhzTDMA  44.8 dBmv

  25.6 dB

 

 

There is nothing that wrong with your downstream / forward signal.  Those errors that are being accumulated on downstream are, for the most part, thanks to the modem not being bonded/locked when trying to transmit on a reboot.

I'd recommend resetting the counters and then watching to see if they re-accumulate.

 

But here's what's you don't know (but I'm sharing with you!)

 

Your upstream / return / transmit is generating some (if not all) of those T3 and T4 time-outs.
This could present a possible issue with your modem itself, or the return path from your modem back to TWC.  Some factual data:

Spoiler

 

12/4.0/0 (19.4 MHz)Total QuantityRatioThis PollRatio  
Unerrored511,70697.3541%6785.8974%  
Corrected12,4172.3624%1114.1026%  
Uncorrected1,4900.2835%00.0000%  
12/4.1/0 (24.2 MHz)Total445,472    
Unerrored432,41497.0687%4100.0000%  
Corrected7,1391.6026%00.0000%  
Uncorrected5,9191.3287%00.0000%  
12/4.2/0 (30.6 MHz)Total471,906 5  
Unerrored458,51597.1624%5100.0000%  
Corrected6,9601.4749%00.0000%  
Uncorrected6,4311.3628%00.0000%  
12/4.3/0 (37.0 MHz)Total522,616 83  
Unerrored507,98197.1997%7792.7711%  
Corrected13,6162.6054%67.2289%  
Uncorrected1,0190.1950%00.0000%  

 

 

Please check for all signal leaks. Terminate any open coax connections that are active/hot.  If that doesn't improve, I'd probably recommend calling (might need a tech visit on-site)

My postings on this site are my own, off-the-clock, and don’t necessarily represent TWC’s/Charter's strategies or opinions.