Expert

Re: Bonded downstream channels

look for something like this which is located about 3/4 of a mile from my house and there's 3 amlifiers between it and me... It feeds 5 different streets and at least 100 houses. there are several directional couplers on the left that feed in 3 different directions.

Any intermittents and DS ingress is probably between that amp and your house. Upstream can be anywhere

 

ah5SErL

 

Expert

Re: Bonded downstream channels

If the big green boxes behind the fence look like this, they're battery backuped inverter supplies that take the 37.5 vdc from 3 huge batteries on the bottom and converts to 90 VAC to feed down coax for amps and fiber converters. guLoqaa

Expert

Re: Bonded downstream channels

here's one of the 60vac ones, was like this for a year after a car hit it., no Idea how they powered amps, it got replaced last fall so it was necesssary, lol

btw, the power wires coming up from the conduit were hot....

 

7Zv13Mj

 

Sharer

Re: Bonded downstream channels

It all just went to crap again at 10:45 pm.  Dropped 3 DS channels at once, and lost all download speed.  Normally I get better than 60 Mbps down, and after the three  service fallbacks, I'm now getting only one-third of a Mbps.  this is what was happening a year ago when I started this thread.  Nothing fixed after a year!  Amazingly bad.

 

Ah, and now the modem just rebooted due to T4 Timeout as I was typing this.

 

TimePriorityCodeMessage

Jul 26 2017 21:58:406-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;
Jul 26 2017 21:58:405-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;
Jul 26 2017 21:57:525-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;
Jul 26 2017 21:57:523-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;
Jul 26 2017 21:57:515-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;
Jul 26 2017 21:57:493-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;
Jul 26 2017 21:57:293-CriticalT05.0SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
Jul 26 2017 21:37:275-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;
Jul 26 2017 21:37:275-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;
Jul 26 2017 21:37:275-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;
Jul 26 2017 21:37:275-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;
Jul 26 2017 21:37:275-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;
Jul 26 2017 21:37:275-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;
Jul 24 2017 21:06:426-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;
Jul 24 2017 21:06:425-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;
Jul 24 2017 21:05:513-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;
Jul 24 2017 21:05:495-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;
Jul 24 2017 21:05:483-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;

 

 

Sharer

Re: Bonded downstream channels

None of the pictures you posted are visible, just boxes with a triangle, so I can't see what you are showing me.

Sharer

Re: Bonded downstream channels

...and then this morning, another T3 Timeout followed by Loss Of Sync.  My cable Starter TV pixelated, stalled, and then showed a black screen with "Interruption of Service",  at the same time as the Loss of Sync in the modem log.

TimePriorityCodeMessage

Jul 27 2017 07:05:173-CriticalT05.0SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
Jul 27 2017 06:50:363-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;
Jul 26 2017 21:58:406-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;
Jul 26 2017 21:58:405-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;
Jul 26 2017 21:57:525-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;
Jul 26 2017 21:57:523-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;
Jul 26 2017 21:57:515-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;
Jul 26 2017 21:57:493-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;
Jul 26 2017 21:57:293-CriticalT05.0SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=30:60:23:cc:fe:fc;CMTS-MAC=00:17:10:8b:e2:8e;CM-QOS=1.1;CM-VER=3.0;
Jul 26 2017 21:37:275-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;
Jul 26 2017 21:37:275-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;
Jul 26 2017 21:37:275-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;
Jul 26 2017 21:37:275-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;
Jul 26 2017 21:37:275-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;
Jul 26 2017 21:37:275-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;
Jul 24 2017 21:06:426-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;
Jul 24 2017 21:06:425-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;
Jul 24 2017 21:05:513-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;
Sharer

Re: Bonded downstream channels

Signal page this morning..... nothing to use here as it rebooted from T4s late last night.

Downstream Bonding 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 Ratio38 dB 38 dB 37 dB 37 dB 37 dB 37 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
-2 dBmV  -2 dBmV  -2 dBmV  -2 dBmV  -1 dBmV  -1 dBmV  -1 dBmV  -1 dBmV  

 

Upstream Bonding Channel Value
Channel ID
Frequency24200000 Hz 37000000 Hz 30600000 Hz 19400000 Hz 
Ranging Service ID5077 5077 5077 5077 
Symbol Rate5.120 Msym/sec 2.560 Msym/sec 5.120 Msym/sec 2.560 Msym/sec 
Power Level46 dBmV 48 dBmV 47 dBmV 45 dBmV 
Upstream Modulation[3] QPSK
[1] 16QAM
[2] 64QAM
 
[3] QPSK
[3] 16QAM
 
[3] QPSK
[1] 16QAM
[2] 64QAM
 
[3] QPSK
[2] 16QAM
 
Ranging StatusSuccess Success Success Success 

 

Signal Stats (Codewords)Bonding Channel Value
Channel ID10 11 12 13 14 15 16 
Total Unerrored Codewords1607227927 1606430679 1606438145 1606445840 1606420889 1606419820 1606423383 1606425267 
Total Correctable Codewords2333 2861 2094 1857 2180 2345 1991 1923 
Total Uncorrectable Codewords15929 15023 4915 6099 15491 15749 15021 16012 
Sharer

Re: Bonded downstream channels

This box with an electric meter feeding it, is a couple of blocks from me, on Old Chapman St.    It says "Lectro" on the front.  What is it?

https://techshots.shutterfly.com/pictures/42

Lead Moderator

Re: Bonded downstream channels

I am sorry to see you are still experiencing issues. I have taken a look at the connection 

and would like it if you would DM us at your convenience. 

 

Forums_Help

 

Thanks!


Julia R.
Spectrum-Social Media Customer Care
Lead Moderator-Community Forums

Expert

Re: Bonded downstream channels

That is the power supply for your node with an amp above it that I mentioned earlier. Canyou get a closeup photo of the amp? I need to see about a foot around it to see if it has a fiber going into it. If so it has the HFC converter in it and is where the transition occurs. There is fiber tied onto the hardline at the next street Chapman runs into but it's pretty poor resolution to see more.

Mine here looks like this:  All our hardline is 40year old bare aluminum and fiber is black jacketted and smaller with no omega loops like the hardline has at amps and tapoffs. The fiber also has large radius bends and wagon wheels on it to allow it to be dropped to the ground for splicing

 

http://imgur.com/ah5SErL

 

If that is the HFC, then the ingress has to be between it and your house . It appears to be cracked aluminum hardline at a tap off, directional coupler or an amplifier( my photo has everything listed in it.

 The T4 reset realligned to consecutive channels again, we know that won't last though.

I've not gotten responses to any ham radio operators in your area, will try again....