Sharer

Re: Bonded downstream channels

TimePriorityCodeMessage

Aug 17 2017 19:07:225-WarningT202.0Lost MDD Timeout;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 17 2017 19:07:225-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 17 2017 19:07:215-WarningT202.0Lost MDD Timeout;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 17 2017 19:07:215-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 17 2017 19:07:215-WarningT202.0Lost MDD Timeout;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 17 2017 19:07:215-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 17 2017 14:09:543-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 14 2017 22:14:576-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 14 2017 22:14:575-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:176-NoticeN/ACable Modem Reboot due to T4 timeout ;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Aug 14 2017 22:14:073-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 14 2017 22:13:373-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 14 2017 21:52:595-WarningT202.0Lost MDD Timeout;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 14 2017 21:52:595-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 14 2017 20:18:136-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 14 2017 20:18:125-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:176-NoticeN/ACable Modem Reboot due to power reset ;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Aug 14 2017 07:30:063-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 13 2017 20:42:046-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
Aug 13 2017 20:42:045-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
Expert

Re: Bonded downstream channels

573 mHz ins local tv broadcast channel 31.... and WXII is on ch 31 looks like severe constant ingress and pushed the s/n into the red at 26 dB...   Of course if you call TWC on the phone, they'll have you reset the modem and unassign that channel, which only masks the problem again....

 

 Tell Billy that it appears Cable ch 82 (573 mHz) has really bad ingress from WXII Broadcast ch 31... That point may be the source of all the issues.

 

If I had access, I'd force all modems on the node to use ch 82 at like 3 am and then querry all for the s/n on ch 82 to see how widespread the issue is to localize it to a street  or maybe even a tapoff.

Then turn it off to deassign it.

Someone really needs to look at the CMTS flop report to see where other dropped/ poor s/n channels are.

 

Expert

Re: Bonded downstream channels

3 other scenarios come to mind:

1- Someone has an outside antenna with saturated amplifiers on it back feeding into the node.

2- Someone has something like a Channel Plus 1,2,3 or 4 channel RF modulator and amp on security cameras and backfeeding into the node.

3- someone has a DirecTv, Dish, or Uverse coax backfeeding into the node. The DirecTv SWM with home theater adapters uses 500-700 mHz as sort of a "MOCA" ethernet adapter. This could also be one or more moca homes with no filters on them, customer installed WHDVR's etc.

HAve you been able to see if there's any not in the tvfool database , Digital ATSC , digital QAM  or NTSC analog channels received?

 

Sharer

Re: Bonded downstream channels

I haven't been able to check anything due to working on some other things for other people the past days and again this coming week.  I will find time this week to test that.

 

I'm still getting the T4 reboots every couple of days.  This afternoon, in addition to a T4 reboot at 2:49pm, I got a  Loss of Sync event at 5:00pm.  I dunno which of the many scenarios has caused this issue.  My neighbor a few houses downstream from me isn't having any issues with her 16-channel leased modem.  I suspect this may never get fixed and I will have to eventually buy a newer 16-channel modem despite the issue being elsewhere.   Robot Mad

Expert

Re: Bonded downstream channels

If not fixed it will get worst if it's indeed a coaxial issue. Most people won't notice temp drops, in video or data, or they think it's normal in other cases... and of course the call center says it's syunspots, the weather, the eclipse....lol.... and are believed.

Last night I had a couple outtages which is unusual for a sat night as twc isn't working then, When I called in I got the "due to excessive calls, wait time is longer than normal" but then the "no outtages are reported in your area"... Only tv went out, data was good, signal levels were good but looking at the cable boxes freq's and levels, a lot had no level, oddball frequencies or poor  s/n of "0dB"It then started working then dropped out a few minutes later. I did not reboot the box, wanted to see if it would reset itself.

It looks like my data and video are on 3 different fiber pairs and one of the pairs for video had issues.  I didn't feel like making the 20 mile round trip to the head end to see if someone was working on them, but from the head end it then goes another 15-20 miles up to Cleveland hts.

 

A different modem might react differently to whatever the outside plant issue is.

 

Sharer

Re: Bonded downstream channels

This is from my neighbor downstream a couple of poles.  She uses a leased 16-channel Arris gateway and suddenly started getting Internet loss while she's trying to work, so contacted me.  She's getting half a dozen T3 Timeouts in a matter of minutes.  Yesterday she got the same plus T4 Timeouts ina period of a couple of hours or less. 
I texted Billy (who's on vacation) and he looked at what he can see from his computer, saw "something popping" on Upstream 24 MHz on the node, was going to call his co-workers and see if they can look at it.

My point here is, as you said, even a 16-channel modem will not help with this new issue of upstream problems causing T4s and T3s.

 

Neighbor's modem:

 

Touchstone Status

Downstream
 DCIDFreqPowerSNRModulationOctetsCorrectedsUncorrectables
Downstream 115543.00 MHz2.00 dBmV40.37 dB256QAM5089149951093
Downstream 210513.00 MHz1.50 dBmV40.37 dB256QAM1819496278978
Downstream 311519.00 MHz1.80 dBmV40.95 dB256QAM1801082111936
Downstream 412525.00 MHz1.70 dBmV40.95 dB256QAM1839705104974
Downstream 513531.00 MHz1.80 dBmV40.95 dB256QAM181090870977
Downstream 614537.00 MHz1.90 dBmV43.38 dB256QAM1831376911076
Downstream 79507.00 MHz0.90 dBmV40.95 dB256QAM1827304160919
Downstream 816549.00 MHz2.10 dBmV40.95 dB256QAM185314286993
Downstream 917555.00 MHz2.10 dBmV40.95 dB256QAM17905171281127
Downstream 1018561.00 MHz1.70 dBmV40.37 dB256QAM1824506721095
Downstream 1119567.00 MHz1.50 dBmV40.95 dB256QAM18343711121055
Downstream 1220573.00 MHz1.80 dBmV40.95 dB256QAM1817067761091
Downstream 1321579.00 MHz1.80 dBmV40.95 dB256QAM1890211106971
Downstream 1422585.00 MHz2.00 dBmV40.95 dB256QAM1842122831171
Downstream 1523591.00 MHz2.20 dBmV40.37 dB256QAM18215511411026
Downstream 1624597.00 MHz2.20 dBmV40.37 dB256QAM18574041643
Reset FEC Counters
Upstream
 UCIDFreqPowerChannel TypeSymbol RateModulation
Upstream 1437.00 MHz40.75 dBmVDOCSIS2.0 (ATDMA)2560 kSym/s16QAM
Upstream 2119.40 MHz37.25 dBmVDOCSIS1.x (TDMA)2560 kSym/s16QAM
Upstream 3330.60 MHz39.00 dBmVDOCSIS2.0 (ATDMA)5120 kSym/s64QAM
Upstream 4224.20 MHz38.00 dBmVDOCSIS2.0 (ATDMA)5120 kSym/s64QAM

 Status
System Uptime:0 d: 19 h: 54 m
Computers Detected:staticCPE(1), dynamicCPE(0)
CM Status:OPERATIONAL
Time and Date:Fri 2017-09-01 15:38:26

 

 

Touchstone Event Log

Date TimeEvent IDEvent LevelDescription
9/1/2017 15:13820002003No Ranging Response received - T3 time-out;CM-MAC=00:ac:e0:9a:90:62;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
9/1/2017 15:13820003003Ranging Request Retries exhausted;CM-MAC=00:ac:e0:9a:90:62;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
9/1/2017 15:13820006003Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:ac:e0:9a:90:62;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
9/1/2017 15:13820002003No Ranging Response received - T3 time-out;CM-MAC=00:ac:e0:9a:90:62;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
9/1/2017 15:13820003003Ranging Request Retries exhausted;CM-MAC=00:ac:e0:9a:90:62;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
9/1/2017 15:13820006003Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:ac:e0:9a:90:62;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
9/1/2017 15:13820003003Ranging Request Retries exhausted;CM-MAC=00:ac:e0:9a:90:62;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
9/1/2017 15:13820006003Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:ac:e0:9a:90:62;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
9/1/2017 15:15820002003No Ranging Response received - T3 time-out;CM-MAC=00:ac:e0:9a:90:62;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
9/1/2017 15:17820003003Ranging Request Retries exhausted;CM-MAC=00:ac:e0:9a:90:62;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
9/1/2017 15:17820006003Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:ac:e0:9a:90:62;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
9/1/2017 15:17820002003No Ranging Response received - T3 time-out;CM-MAC=00:ac:e0:9a:90:62;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
9/1/2017 15:17820003003Ranging Request Retries exhausted;CM-MAC=00:ac:e0:9a:90:62;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
9/1/2017 15:17820006003Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:ac:e0:9a:90:62;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
9/1/2017 15:17820003003Ranging Request Retries exhausted;CM-MAC=00:ac:e0:9a:90:62;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
9/1/2017 15:17820006003Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:ac:e0:9a:90:62;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
9/1/2017 15:17820002003No Ranging Response received - T3 time-out;CM-MAC=00:ac:e0:9a:90:62;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
9/1/2017 15:17820003003Ranging Request Retries exhausted;CM-MAC=00:ac:e0:9a:90:62;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
9/1/2017 15:17820006003Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:ac:e0:9a:90:62;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
9/1/2017 15:17820002003No Ranging Response received - T3 time-out;CM-MAC=00:ac:e0:9a:90:62;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;

 

Expert

Re: Bonded downstream channels

ingress probably between poles, will cause both up and downstream issues