Valued Participant

Re: Intermittent downstream speed issues: Lost MDD Timeout...

I think I might have finally understood what MsReye was referring to with 'ingress'.

 

The coax cables and junctions are shielded wires. Loose connections, or breaks in the shielding lets other RF signals into the wire. Broadcast TV is RF, and leaks into the coax cable if there are problems. This can happen in your house, or out in the field.

 

Did I get it?

Sharer

Re: Intermittent downstream speed issues: Lost MDD Timeout...

Sounds about right.  I think of RF signals as acting like water.

Expert

Re: Intermittent downstream speed issues: Lost MDD Timeout...


@glenvee wrote:

Sounds about right.  I think of RF signals as acting like water.


And it's easier to detect ingress points by using egress, leaks, by detecting the cable agc pilot carriers with either a handheld scanner or ham radio portable if you know what the frequencies are.

While many don't exceed FCC limits, they destroy QAM modulation. both by ingress at the same point, Impedance mismatches and noise generation-intermodulation/harmonics.

When RF is passed accross any corrosion or dissimilar metals, noise is generated in both directions, both up and downstream.

 

Valued Participant

Re: Intermittent downstream speed issues: Lost MDD Timeout...

Dang. Just when I think I'm catching up, she goes and drops more jargon on us.

https://www.youtube.com/watch?v=Ac7G7xOG2Ag

Valued Participant

Re: Intermittent downstream speed issues: Lost MDD Timeout...

so far, I've not spotted any speed drop offs of concern.
I'm a participant in the SamKnows broadband monitoring project, and since the replacement of the MoCA amp, addition of terminators and tightening of connections, I see only one server (Off Net (M-Lab) with a speed drop off. That server did come back up to match the other servers used by SamKnows. The modem has been up almost 5 days without rebooting now.
Valued Participant

Re: Intermittent downstream speed issues: Lost MDD Timeout...

OTOH, I should have checked signal levels and logs. I still have a number of MDD timeouts since the 'fix', and I'm sitting at 5 download channels at the moment.
Time to save the pages, and perhaps call TWC

 

Signals:

Channel ID17 22 27 28 29 
Frequency555000000 Hz 585000000 Hz 615000000 Hz 621000000 Hz 627000000 Hz 
Signal to Noise Ratio38 dB 38 dB 39 dB 38 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
6 dBmV  6 dBmV  7 dBmV  7 dBmV  7 dBmV  

 

UpstreamBonding Channel Value
Channel ID
Frequency30600000 Hz 24200000 Hz 19400000 Hz 37000000 Hz 
Ranging Service ID1822 1822 1822 1822 
Symbol Rate5.120 Msym/sec 5.120 Msym/sec 2.560 Msym/sec 2.560 Msym/sec 
Power Level47 dBmV 44 dBmV 44 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 ID17 22 27 28 29 
Total Unerrored Codewords19176674496 18312403175 18255011422 18604387352 18565983035 
Total Correctable Codewords834 1089 1743 1611 2053 
Total Uncorrectable Codewords687 13553 14888 13797 

12926 

 

 

 

 

Logs:

 

Sep 06 2016 02:11:333-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=cc:65:ad:0f:d5:bb;CMTS-MAC=00:17:10:8b:75:03;CM-QOS=1.1;CM-VER=3.0;
Sep 05 2016 13:40:085-WarningT202.0Lost MDD Timeout;CM-MAC=cc:65:ad:0f:d5:bb;CMTS-MAC=00:17:10:8b:75:03;CM-QOS=1.1;CM-VER=3.0;
Sep 05 2016 13:40:085-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=cc:65:ad:0f:d5:bb;CMTS-MAC=00:17:10:8b:75:03;CM-QOS=1.1;CM-VER=3.0;
Sep 05 2016 13:40:085-WarningT202.0Lost MDD Timeout;CM-MAC=cc:65:ad:0f:d5:bb;CMTS-MAC=00:17:10:8b:75:03;CM-QOS=1.1;CM-VER=3.0;
Sep 05 2016 13:40:085-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=cc:65:ad:0f:d5:bb;CMTS-MAC=00:17:10:8b:75:03;CM-QOS=1.1;CM-VER=3.0;
Sep 05 2016 01:07:256-NoticeD106.0DHCP Renew - lease parameters tftp file-?BEWGC1XMZa0P1bsK8agC@CvGoAizJ1Q_WuhdwCNSQN+IHRiBcbu9H modified;CM-MAC=cc:65:ad:0f:d5:bb;CMTS-MAC=00:17:10:8b:75:03;CM-QOS=1.1;CM-VER=3.0;
Sep 05 2016 01:07:254-ErrorD103.0DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=cc:65:ad:0f:d5:bb;CMTS-MAC=00:17:10:8b:75:03;CM-QOS=1.1;CM-VER=3.0;
Sep 04 2016 20:37:215-WarningT202.0Lost MDD Timeout;CM-MAC=cc:65:ad:0f:d5:bb;CMTS-MAC=00:17:10:8b:75:03;CM-QOS=1.1;CM-VER=3.0;
Sep 04 2016 20:37:215-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=cc:65:ad:0f:d5:bb;CMTS-MAC=00:17:10:8b:75:03;CM-QOS=1.1;CM-VER=3.0;
Sep 04 2016 20:37:003-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=cc:65:ad:0f:d5:bb;CMTS-MAC=00:17:10:8b:75:03;CM-QOS=1.1;CM-VER=3.0;
Sep 04 2016 07:02:515-WarningT202.0Lost MDD Timeout;CM-MAC=cc:65:ad:0f:d5:bb;CMTS-MAC=00:17:10:8b:75:03;CM-QOS=1.1;CM-VER=3.0;
Sep 04 2016 07:02:515-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=cc:65:ad:0f:d5:bb;CMTS-MAC=00:17:10:8b:75:03;CM-QOS=1.1;CM-VER=3.0;
Sep 04 2016 07:02:515-WarningT202.0Lost MDD Timeout;CM-MAC=cc:65:ad:0f:d5:bb;CMTS-MAC=00:17:10:8b:75:03;CM-QOS=1.1;CM-VER=3.0;
Sep 04 2016 07:02:515-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=cc:65:ad:0f:d5:bb;CMTS-MAC=00:17:10:8b:75:03;CM-QOS=1.1;CM-VER=3.0;
Sep 04 2016 07:02:286-NoticeN/AMDD Recovery following MDD Loss;CM-MAC=cc:65:ad:0f:d5:bb;CMTS-MAC=00:17:10:8b:75:03;CM-QOS=1.1;CM-VER=3.0;
Sep 04 2016 06:52:343-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=cc:65:ad:0f:d5:bb;CMTS-MAC=00:17:10:8b:75:03;CM-QOS=1.1;CM-VER=3.0;
Sep 02 2016 19:16:155-WarningT202.0Lost MDD Timeout;CM-MAC=cc:65:ad:0f:d5:bb;CMTS-MAC=00:17:10:8b:75:03;CM-QOS=1.1;CM-VER=3.0;
Sep 02 2016 19:16:155-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=cc:65:ad:0f:d5:bb;CMTS-MAC=00:17:10:8b:75:03;CM-QOS=1.1;CM-VER=3.0;
Sep 01 2016 13:33:296-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=cc:65:ad:0f:d5:bb;CMTS-MAC=00:17:10:8b:75:03;CM-QOS=1.1;CM-VER=3.0;
Sep 01 2016 13:33:295-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=cc:65:ad:0f:d5:bb;CMTS-MAC=00:17:10:8b:75:03;CM-QOS=1.1;CM-VER=3.0;
Expert

Re: Intermittent downstream speed issues: Lost MDD Timeout...

That's still bad... severe ingress causing those downstream partial service errors and missing/ skipped over channels.

 

Valued Participant

Re: Intermittent downstream speed issues: Lost MDD Timeout...

Yeah, I'm going to have them out again. I'm collecting logs periodically. It will have to wait until next week, though.