Expert

Re: Bonded downstream channels

Your upstream is slowly creaping up. I wonder if it's spiking out to max at times. Yet the DS seems stable.

 

All you can do is call TWC back about the intermittents.

 

Sharer

Re: Bonded downstream channels

Downstream is good till it drops a channel or two.  It's already switched to some higher channels tonight.  The Upstream issue is new.  I'm considering taking the  attenuator off the modem cable in the box outside, to drop the upstream power by 6, and putting an extra length of coax on instead to keep the downstream power from rising too much as a result of removing the attenuator.

Sharer

Re: Bonded downstream channels

Haven't removed the attenuator yet, as things seem to stabilize for a couple of days except for a daily T3 Timeout.  Now tonight, another set of Lost MDD's and then Loss of Sync, followed by a T4 Timeout auto-reboot.  Sheessh.....

TimePriorityCodeMessage

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;
Jul 24 2017 21:05:243-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 24 2017 20:48:365-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 20:48:365-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 20:48:365-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 20:48:365-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 23 2017 21:02: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;
Jul 21 2017 11:36:056-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 21 2017 11:36:055-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 21 2017 11:35:173-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 21 2017 11:35:115-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 21 2017 11:35:113-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 21 2017 11:35:105-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 21 2017 11:35:093-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 after reboot....

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 39 dB 39 dB 38 dB 39 dB 39 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
0 dBmV  0 dBmV  0 dBmV  0 dBmV  0 dBmV  0 dBmV  0 dBmV  0 dBmV  

 

Upstream Bonding Channel Value
Channel ID
Frequency24200000 Hz 37000000 Hz 30600000 Hz 19400000 Hz 
Ranging Service ID4028 4028 4028 4028 
Symbol Rate5.120 Msym/sec 2.560 Msym/sec 5.120 Msym/sec 2.560 Msym/sec 
Power Level47 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 Codewords285529917 284635665 284644026 284626867 284623617 284627055 284652687 284621628 
Total Correctable Codewords16 53 12 120 
Total Uncorrectable Codewords536 583 506 1292 1445 595 1520 1474 
Highlighted
Expert

Re: Bonded downstream channels

Need to see the signal level page again after 8-24 hours to see which channels are dropped  or have high corrected/uncorrected counts.

Right now you have 8 adjacent channels DS, a RCS partial service error indicates one or more got trashed by ingress, then the channel get's dropped and a new one added.

the T3-4 errors are often an upstream ingress issue. a TCS partial service is a serious problem.

 

Expert

Re: Bonded downstream channels

The attenuator will only affect ingress if the ingress is between the attenuator and the modem,

 In your case, it's out on the street somewhere, the only way to find it is to go sniffing for egress and having TWC bucket truck guys fix it. Most likely spot is other neighbors on the same tapoff block as you for DS ingress, but for US ingress, it can be anywhere on the node and probably from multiple bad drops, and usually right at the tap offs on the hardline

.

 

Expert

Re: Bonded downstream channels

TWC uses rather useless leak detectors that operate in the area of 135 mHzand can only detect hardline leaks as many customers are now internet only and everything from 50-500mHz is trapped out by a "internet only" filter screwed into their drop on the tap off block. However it allows egesss and ingress in the US 5-45 mHz band as well as the DS 500-1000mHz band.

In most areas the filters are being replaced with ones that go down to 450 mHz and if TWC has a 445.250 mHz agc pilot, that should be receivable thru the filter whereas the 135 mHz "leak detector" signal won't be radiated.

The only way they can find US 5-45 mHz ingress is for a bucket truck guy to start at the fiber converter and work down each amp to see where the ingress disappears, then look at the tap offs to each customer between the 2.

 TWC/ Spectrum is simply unwilling to do any of the above.

other than "fix' obvious 135 mHz leaks as that area affects aircraft comms...

So they shoot themselves in both feet.

The overhead streets here have horrible egress with probably 1 in 5-10 houses with measureable egress and the new underground ones having 1 in 10-20. Old underground can be a lot worst if the pedestals are near the street and get winter salt spray and lawn pesticides in the connections and amps.

Overhead lines next to/ under raised freeways and bridges are horrible

 

Sharer

Re: Bonded downstream channels

July 26, just after midnight:

Downstream Bonding Channel Value
Channel ID11 12 13 14 15 22 25 
Frequency507000000 Hz 519000000 Hz 525000000 Hz 531000000 Hz 537000000 Hz 543000000 Hz 585000000 Hz 603000000 Hz 
Signal to Noise Ratio37 dB 38 dB 38 dB 38 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
0 dBmV  0 dBmV  0 dBmV  0 dBmV  0 dBmV  0 dBmV  1 dBmV  2 dBmV  

 

Upstream Bonding Channel Value
Channel ID
Frequency24200000 Hz 37000000 Hz 30600000 Hz 19400000 Hz 
Ranging Service ID4028 4028 4028 4028 
Symbol Rate5.120 Msym/sec 2.560 Msym/sec 5.120 Msym/sec 2.560 Msym/sec 
Power Level47 dBmV 49 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 ID11 12 13 14 15 22 25 
Total Unerrored Codewords4339412294 4273762235 4273755935 4273770494 4273720085 4273719354 4269330813 4273727519 
Total Correctable Codewords27 23 33 49 81 95 77 147 
Total Uncorrectable Codewords536 2094 1120 2009 2070 2064 3683 2986 
Expert

Re: Bonded downstream channels

broadcastTV ch's 21 & ch 27...killed 10&16 for a start...  I think the head end is at 1811 Spring Garden st. no tv broadcast towers along the way there.

 

 

Expert

Re: Bonded downstream channels

The fiber to coax converters are usually overhead and located where the smaller black fiber goes in one side and in your area, larger bare aluminum line comes out. It will only service 100-200 homes. I see there's a power supply, hanging on a pole (with an electric meter on it, dead giveaway) between you and there as the fiber has no power on it, that's backfed via coax.

 Problem is ingress somewhere on the coax or possibly really bad levels on lower channels causing noise on the qam data channels. None of the towers along the route are broadcast, they're all cellular and trunked radio.

Fiber is immune to radio ingress.

And ummm yes, all that bare aluminum hardline is an issue, it only has a life of 20-30 years and connectors if not glue filled shrink will fail quickly when pulled on by vines and tree branches in the wind. That results in intermittently brokes outer coaxial shielding and both ingres and egress.

Since all the outside plant is old, it has to use a single AGC pilot frequency to adjust downstream levels. Some of the really new stuff uses thermal controls and no pilot. Here it's on 445.250 mHz and easily receivable with any 70cm ham radio

the next issue is that the 4G cell companies are actively targetting the cable co's for leaks in the 699-869 mHz range. So I'll bet there's no leaks in the half mile radius around the cell towers

I also see fiber for your local telco's neighborhood SLICK's, it's above the twc bundle and may also feed verizon& ATt neighborhood 4G poletop sites.