Browser

Another Lost MDD Timeout...

Good morning.

 

Getting the dreaded "Lost MDD Timeout". This has been happening to me more and more over the last week. Any insights?

 

I'm using:

Model Name: SB6141
Vendor Name: Motorola
Firmware Name: SB_KOMODO-1.0.6.16-SCM00-NOSH
Boot Version: PSPU-Boot(25CLK) 1.0.12.18m3
Hardware Version: 7.0
Serial Number: 359781315023429209030011
Firmware Build Time: Feb 16 2016 11:28:04

 

Signal when bad (excuses for bad layout) :

DownstreamBonding Channel ValueChannel ID

9 15 19 24 26 30 

Frequency

507000000 Hz 543000000 Hz 567000000 Hz 597000000 Hz 609000000 Hz 633000000 Hz 

Signal to Noise Ratio

37 dB 37 dB 37 dB 35 dB 36 dB 34 dB 

Downstream Modulation

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  -9 dBmV  -9 dBmV  -10 dBmV  0 dBmV  

Upstream Bonding Channel Value

Channel ID5 6 7 8 

Frequency19400000 Hz 24200000 Hz 30600000 Hz 37000000 Hz 

Ranging Service ID7504 7504 7504 7504 

Symbol Rate2.560 Msym/sec 5.120 Msym/sec 5.120 Msym/sec 2.560 Msym/sec 

Power Level54 dBmV 54 dBmV 54 dBmV 54 dBmV 

Upstream Modulation[3] QPSK
[2] 16QAM
 [3] QPSK
[1] 16QAM
[2] 64QAM
 [3] QPSK
[1] 16QAM
[2] 64QAM
 [3] QPSK
[3] 16QAM
 Ranging Status Success Success Success Success 

Signal Stats (Codewords) Bonding Channel Value

Channel ID9 15 19 24 26 30 

Total Unerrored Codewords 10463250709 10154468120 9955504990 9721396571 9742323282 3218754968 

Total Correctable Codewords 1012 742 1529 3234 1571 3168 

Total Uncorrectable Codewords 5958 11559 14817 19102 16357 2096544 

 

 Signal when all good:

DownstreamBonding Channel Value
Channel ID10 11 13 14 15 16 18 
Frequency507000000 Hz 513000000 Hz 519000000 Hz 531000000 Hz 537000000 Hz 543000000 Hz 549000000 Hz 561000000 Hz 
Signal to Noise Ratio37 dB 37 dB 37 dB 36 dB 36 dB 36 dB 37 dB 37 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  -8 dBmV  -8 dBmV  -8 dBmV  -9 dBmV  

 

UpstreamBonding Channel Value
Channel ID
Frequency19400000 Hz 24200000 Hz 30600000 Hz 37000000 Hz 
Ranging Service ID552 552 552 552 
Symbol Rate2.560 Msym/sec 5.120 Msym/sec 5.120 Msym/sec 2.560 Msym/sec 
Power Level54 dBmV 54 dBmV 54 dBmV 54 dBmV 
Upstream Modulation[3] QPSK
[2] 16QAM
 
[3] QPSK
[1] 16QAM
[2] 64QAM
 
[3] QPSK
[1] 16QAM
[2] 64QAM
 
[3] QPSK
[3] 16QAM
 
Ranging StatusSuccess Success Success Success 

 

Signal Stats (Codewords)Bonding Channel Value
Channel ID10 11 13 14 15 16 18 
Total Unerrored Codewords211011287 210014246 210006067 184348811 184330374 184332372 184335232 184335629 
Total Correctable Codewords44 38 29 75 29 
Total Uncorrectable Codewords593 529 537 1287 1280 1358 1308 1438 

Log:

TimePriorityCodeMessage

Jul 13 2017 07:08:176-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=b8:16:19:2e:cf:71;CMTS-MAC=00:17:10:88:b2:43;CM-QOS=1.1;CM-VER=3.0;
Jul 13 2017 07:08:175-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=b8:16:19:2e:cf:71;CMTS-MAC=00:17:10:88:b2:43;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:156-NoticeN/ACable Modem Reboot due to power reset ;CM-MAC=b8:16:19:2e:cf:71;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jul 12 2017 21:31:445-WarningT202.0Lost MDD Timeout;CM-MAC=b8:16:19:2e:cf:71;CMTS-MAC=00:17:10:88:b2:43;CM-QOS=1.1;CM-VER=3.0;
Jul 12 2017 21:31:445-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=b8:16:19:2e:cf:71;CMTS-MAC=00:17:10:88:b2:43;CM-QOS=1.1;CM-VER=3.0;
Jul 12 2017 21:31:445-WarningT202.0Lost MDD Timeout;CM-MAC=b8:16:19:2e:cf:71;CMTS-MAC=00:17:10:88:b2:43;CM-QOS=1.1;CM-VER=3.0;
Jul 12 2017 21:31:445-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=b8:16:19:2e:cf:71;CMTS-MAC=00:17:10:88:b2:43;CM-QOS=1.1;CM-VER=3.0;
Jul 12 2017 13:30:025-WarningT202.0Lost MDD Timeout;CM-MAC=b8:16:19:2e:cf:71;CMTS-MAC=00:17:10:88:b2:43;CM-QOS=1.1;CM-VER=3.0;
Jul 12 2017 13:30:025-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=b8:16:19:2e:cf:71;CMTS-MAC=00:17:10:88:b2:43;CM-QOS=1.1;CM-VER=3.0;
Jul 12 2017 09:25:235-WarningT202.0Lost MDD Timeout;CM-MAC=b8:16:19:2e:cf:71;CMTS-MAC=00:17:10:88:b2:43;CM-QOS=1.1;CM-VER=3.0;
Jul 12 2017 09:25:235-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=b8:16:19:2e:cf:71;CMTS-MAC=00:17:10:88:b2:43;CM-QOS=1.1;CM-VER=3.0;
Jul 11 2017 21:28:545-WarningT202.0Lost MDD Timeout;CM-MAC=b8:16:19:2e:cf:71;CMTS-MAC=00:17:10:88:b2:43;CM-QOS=1.1;CM-VER=3.0;
Jul 11 2017 21:28:545-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=b8:16:19:2e:cf:71;CMTS-MAC=00:17:10:88:b2:43;CM-QOS=1.1;CM-VER=3.0;
Jul 11 2017 17:00:195-WarningT202.0Lost MDD Timeout;CM-MAC=b8:16:19:2e:cf:71;CMTS-MAC=00:17:10:88:b2:43;CM-QOS=1.1;CM-VER=3.0;
Jul 11 2017 17:00:195-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=b8:16:19:2e:cf:71;CMTS-MAC=00:17:10:88:b2:43;CM-QOS=1.1;CM-VER=3.0;
Jul 11 2017 16:59:556-NoticeN/AMDD Recovery following MDD Loss;CM-MAC=b8:16:19:2e:cf:71;CMTS-MAC=00:17:10:88:b2:43;CM-QOS=1.1;CM-VER=3.0;
Jul 11 2017 12:30:045-WarningT202.0Lost MDD Timeout;CM-MAC=b8:16:19:2e:cf:71;CMTS-MAC=00:17:10:88:b2:43;CM-QOS=1.1;CM-VER=3.0;
Jul 11 2017 12:30:045-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=b8:16:19:2e:cf:71;CMTS-MAC=00:17:10:88:b2:43;CM-QOS=1.1;CM-VER=3.0;
Jul 11 2017 01:35:333-CriticalT05.0SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=b8:16:19:2e:cf:71;CMTS-MAC=00:17:10:88:b2:43;CM-QOS=1.1;CM-VER=3.0;
Jul 10 2017 21:17:165-WarningT202.0Lost MDD Timeout;CM-MAC=b8:16:19:2e:cf:71;CMTS-MAC=00:17:10:88:b2:43;CM-QOS=1.1;CM-VER=3.0;

 

Regards, Jan

 

21 REPLIES
Established Sharer

Re: Another Lost MDD Timeout...

If I'm not mistaken, it looks like you've got some serious signal issues. Too many splitters, loose connection, chewed up wire, water in the line...something like that. Others here will respond that have more technical expertise on reading the logs, but downstream is barely within range and upstream is way out of range.

Browser

Re: Another Lost MDD Timeout...

It is a 3 year old home, so fairly new I'd think. What I was wondering about after browing some other threads, when cable was installed I had cable-outlets added in I think five rooms, just in case I'd want cableTV there. So that means the main TWC box would have a 5 way splitter. Could that be a problem?

Established Sharer

Re: Another Lost MDD Timeout...


jvanmo5 wrote:

It is a 3 year old home, so fairly new I'd think. What I was wondering about after browing some other threads, when cable was installed I had cable-outlets added in I think five rooms, just in case I'd want cableTV there. So that means the main TWC box would have a 5 way splitter. Could that be a problem?


Yes...one the main incoming line to the house attach a grounded two-way splitter. Then have one dedicated line going to the modem and one line to your splitter for the tv outlets. Most cable boxes can operate just fine being split like that but modems can't.

Expert

Re: Another Lost MDD Timeout...

It is iomproperly installed, Remove the splitter, bet it's an 8 way and connect the modem line to the grounding block. Next issue is that TWC/ Spectrum is sending you channels outside the modemns 96 mHz acceptance window and refuses to correct their improper CMTS programming.

 With the coax disconnected, do a factory reset. Unpower the modem , reconnect the coax, power it back up and see if you can get sequential channels that are no further than 90 mHz apart.

This cannot be fixed over the phone.  

 

You may also have broadcast tv ingress from bad outside line causing the skipped channels, it too must be physicly repaired and can't be fixed over the phone.

 

Browser

Re: Another Lost MDD Timeout...

reds91185, MsRaye, thank you for your replies, much appreciated!

I'll see if I can do something with the splitter...

Expert

Re: Another Lost MDD Timeout...

Horrible Verizon issues here, wasted another 8 hours with them, sorry for the late reply.

 

If you have no cable TV, bypass the entire splitter mess and repost levels.

If you have 1 cable box, there should be a two way splitter with one port to the modem and the other port feeding the cable box/dvr or a splitter with 4 ports feeding those 4 out of 5 empty outlets. If those outlets are indeed connected to the splitter,they MUST HAVE 75 ohm terminating resistors on them.

Either of the above should work fine.

If there is an 8 way splitter only, it won't and can't work and appears  that way due to your levels which are out of spec and it's a typical response by the phone support to reset the modem which does nothing but maybe gets the modem sort of woirking(intermittently)

 

Level on the US path must be all 4 channels lower than +52 dBmv with a +30 to +49 being optimum as long as the DS level is in a -8 to + 8 range and s/n at like 35 dB or higher on the older modems and acceptance bandwidth less than 96 mHz( 90 mHz between lowest and highest freq DS channels.

 

Any more than 3 devices needs the proper gain bidirectional amplifierand that needs TWC/Spectrum techs to first verify the outside connection is good and inside lines are good.

 Amplifiers must not be used to "fix" coaxial issues....

If lines and splitters were installed 5 years ago, I'll bet all the connectors are crimped not compression and maybe the coax has been crushed by stapling. This includes connectors on the backside of wall plates.

 

Browser

Re: Another Lost MDD Timeout...

Yes, you both are so right! See pics, it goes into an eight-way splitter. Since I only use my cable modem, I will just bypass the whole splitter block and connect my modem line straight to that input on top to which the splitter now connects. Looks like that part is grounded by that green line. Correct?

 

Thanks again!

 

Pics... 

https://photos.app.goo.gl/ynqLo0vKPAq2zCBB3

 

Established Sharer

Re: Another Lost MDD Timeout...

If you're an internet only subscriber, bypass the splitter and go straight to the modem. If you add tv service later you can always loop the splitter back in at that time. Yes the green wire is the ground.

 

Out of curiousity what are the blue wires?

Browser

Re: Another Lost MDD Timeout...

>> Out of curiousity what are the blue wires?

They are cat5e cables.

 

Changed the wiring, new readings are:

 

DownstreamBonding Channel Value
Channel ID10 11 12 13 14 15 16 
Frequency507000000 Hz 513000000 Hz 519000000 Hz 525000000 Hz 531000000 Hz 537000000 Hz 543000000 Hz 549000000 Hz 
Signal to Noise Ratio39 dB 38 dB 38 dB 38 dB 38 dB 39 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
1 dBmV  1 dBmV  1 dBmV  1 dBmV  1 dBmV  1 dBmV  1 dBmV  1 dBmV  

 

UpstreamBonding Channel Value
Channel ID
Frequency19400000 Hz 24200000 Hz 30600000 Hz 37000000 Hz 
Ranging Service ID499 499 499 499 
Symbol Rate2.560 Msym/sec 5.120 Msym/sec 5.120 Msym/sec 2.560 Msym/sec 
Power Level44 dBmV 44 dBmV 45 dBmV 45 dBmV 
Upstream Modulation[3] QPSK
[2] 16QAM
 
[3] QPSK
[1] 16QAM
[2] 64QAM
 
[3] QPSK
[1] 16QAM
[2] 64QAM
 
[3] QPSK
[3] 16QAM
 
Ranging StatusSuccess Success Success Success 

 

Signal Stats (Codewords)Bonding Channel Value
Channel ID10 11 12 13 14 15 16 
Total Unerrored Codewords21036497 19895142 19877900 19886082 19868173 19871278 19870084 19871198 
Total Correctable Codewords23 20 44 47 
Total Uncorrectable Codewords485 543 485 528 679 660 593 577 

 

 

TimePriorityCodeMessage

Jul 14 2017 14:11:566-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=b8:16:19:2e:cf:71;CMTS-MAC=00:17:10:88:b2:43;CM-QOS=1.1;CM-VER=3.0;
Jul 14 2017 14:11:565-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=b8:16:19:2e:cf:71;CMTS-MAC=00:17:10:88:b2:43;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:156-NoticeN/ACable Modem Reboot due to power reset ;CM-MAC=b8:16:19:2e:cf:71;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;