Highlighted
Rookie

Re: Excessive Data Packet Loss, 96744

Here are today’s readings:
Startup Procedure
Procedure Status Comment
Acquire Downstream Channel 777000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Security Enabled BPI+
IP Provisioning Mode Honor MDD honorMdd(4)

Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 2 777000000 Hz 10.3 dBmV 42.2 dB 3753 3707
2 Locked QAM256 1 771000000 Hz 10.1 dBmV 43.2 dB 154 679
3 Locked QAM256 23 903000000 Hz 7.2 dBmV 41.1 dB 4352 4003
4 Locked QAM256 4 789000000 Hz 9.5 dBmV 42.1 dB 143 650
5 Locked QAM256 5 795000000 Hz 8.8 dBmV 41.4 dB 146 663
6 Locked QAM256 6 801000000 Hz 8.5 dBmV 42.3 dB 217 707
7 Locked QAM256 7 807000000 Hz 8.6 dBmV 42.1 dB 356 700
8 Locked QAM256 8 813000000 Hz 8.7 dBmV 41.9 dB 675 792
9 Locked QAM256 9 819000000 Hz 8.4 dBmV 41.5 dB 215 687
10 Locked QAM256 10 825000000 Hz 8.3 dBmV 41.4 dB 304 771
11 Locked QAM256 11 831000000 Hz 8.1 dBmV 40.5 dB 505 903
12 Locked QAM256 12 837000000 Hz 7.9 dBmV 40.2 dB 262 743
13 Locked QAM256 13 843000000 Hz 8 dBmV 40 dB 174 712
14 Locked QAM256 14 849000000 Hz 8 dBmV 40.9 dB 317 686
15 Locked QAM256 15 855000000 Hz 7.9 dBmV 41.4 dB 319 754
16 Locked QAM256 24 909000000 Hz 7 dBmV 40.1 dB 235 730

Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 50 5120 Ksym/sec 24200000 Hz 51 dBmV
2 Locked TDMA 49 2560 Ksym/sec 19400000 Hz 51 dBmV
3 Locked ATDMA 51 5120 Ksym/sec 30600000 Hz 51.3 dBmV
4 Locked ATDMA 52 5120 Ksym/sec 37000000 Hz 51 dBmV

Current System Time:Fri Oct 13 03:36:12 2017
Expert

Re: Excessive Data Packet Loss, 96744

This is unacceptable... Are you internet only or is there a splitter between the outside line and the modem? what's marked on it?

Your US is too high for no or a 2 way splitter and an issue anything near +52 dBmv will be unreliable, s/b below +50 dBmv

 

Your DS correctables have increased so there is still ingress from primarily Verizon 4G and TWC/Spectrum needs to fix the corrosion issues between pole amps/tapoffs. Is street wiring overhead or underground?

 

 

Rookie

Re: Excessive Data Packet Loss, 96744

[ Edited ]
Outside line to powered amp, out to a splitter (one for modem, one for tv-20 channels El Cheapo package, spectrum tech installed). Wiring is above ground, old neighborhood, old hardware is my guess.
Rookie

Re: Excessive Data Packet Loss, 96744

24hrs later: tartup Procedure
Procedure Status Comment
Acquire Downstream Channel 777000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Security Enabled BPI+
IP Provisioning Mode Honor MDD honorMdd(4)

Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 2 777000000 Hz 10.5 dBmV 42.2 dB 0 0
2 Locked QAM256 1 771000000 Hz 10.3 dBmV 43.1 dB 0 0
3 Locked QAM256 21 891000000 Hz 7.4 dBmV 40.5 dB 0 0
4 Locked QAM256 4 789000000 Hz 9.6 dBmV 42 dB 0 0
5 Locked QAM256 5 795000000 Hz 8.9 dBmV 41.1 dB 0 0
6 Locked QAM256 6 801000000 Hz 8.6 dBmV 42.2 dB 0 0
7 Locked QAM256 7 807000000 Hz 8.7 dBmV 42 dB 476 298
8 Locked QAM256 8 813000000 Hz 8.8 dBmV 41.6 dB 75 64
9 Locked QAM256 22 897000000 Hz 7.4 dBmV 39.8 dB 8 0
10 Locked QAM256 10 825000000 Hz 8.4 dBmV 41.2 dB 348 41
11 Locked QAM256 23 903000000 Hz 7.4 dBmV 41 dB 0 0
12 Locked QAM256 24 909000000 Hz 7 dBmV 39.8 dB 0 0
13 Locked QAM256 13 843000000 Hz 8.1 dBmV 39.8 dB 0 0
14 Locked QAM256 18 873000000 Hz 7.5 dBmV 40.4 dB 0 0
15 Locked QAM256 19 879000000 Hz 7.7 dBmV 41.1 dB 0 0
16 Locked QAM256 20 885000000 Hz 7.6 dBmV 40.7 dB 0 0

Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 50 5120 Ksym/sec 24200000 Hz 51 dBmV
2 Locked TDMA 49 2560 Ksym/sec 19400000 Hz 51 dBmV
3 Locked ATDMA 51 5120 Ksym/sec 30600000 Hz 51.3 dBmV
4 Locked ATDMA 52 5120 Ksym/sec 37000000 Hz 51 dBmV

Current System TimeSmiley Frustratedat Oct 14 01:04:00 2017
Rookie

Re: Excessive Data Packet Loss, 96744

24hrs later: 2017-10-6, 20:13:11 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a0:04:60:f4:56:90;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-10-6, 20:13:12 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=a0:04:60:f4:56:90;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-10-6, 20:13:14 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a0:04:60:f4:56:90;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-10-6, 20:13:16 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=a0:04:60:f4:56:90;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-10-6, 20:13:17 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a0:04:60:f4:56:90;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-10-6, 20:13:18 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=a0:04:60:f4:56:90;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-10-6, 20:13:19 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a0:04:60:f4:56:90;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-10-6, 20:13:20 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=a0:04:60:f4:56:90;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-10-6, 20:13:21 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a0:04:60:f4:56:90;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-10-6, 20:13:22 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=a0:04:60:f4:56:90;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-10-7, 02:43:33 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a0:04:60:f4:56:90;CMTS-MAC=00:01:6c:6b:84:70;CM-QOS=1.1;CM-VER=3.0;
1970-1-1, 00:00:22 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a0:04:60:f4:56:90;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:27 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=a0:04:60:f4:56:90;CMTS-MAC=00:01:6c:6b:84:70;CM-QOS=1.0;CM-VER=3.0;
2017-10-8, 09:35:11 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a0:04:60:f4:56:90;CMTS-MAC=00:01:6c:6b:84:70
Established Sharer

Re: Excessive Data Packet Loss, 96744

[ Edited ]

Recommend that the first thing you do is get rid of the in-line amplifier.  It should not be needed at all if Spectrum's signal levels on the street tap are set properly.  Chances are that it is an older version not built for the proper frequency range, since your local franchise is using internet channels above 900 MHz.

Instead, connect the splitter feeding your modem and basic TV directly to the incoming drop cable, unplug the amplifier, then let it run for a day and post the new signal levels page.  None of the upstream levels should exceed +50 dBmv, while the downstream channel levels should all be between -8 and +10 dBmv. 

The uncorrected error counts on every DS channel should be less than about 2000 after two days, but no more than the corrected errors.  Uncorrected errors more than 2 x corrected errors suggest ingress leakage from licensed TV or 4G LTE cell phones, usually from loose cable connectors, old RG-59 cabling, or unused "dead-end" cables that don't have 75 ohm terminations on the ends.

You will soon be notified by Spectrum that you will have to rent a set-top box even for economy local channel service.  All programming channels are changing to digital encryption, so there will be no more direct coaxial cable connections for either newer digital TV sets or ancient analog sets.

Expert

Re: Excessive Data Packet Loss, 96744

[ Edited ]

Is the amplifier a single out port and marked FWD gain 10 dB and REV- unity or 0dB?

If so, it's not wanted. But even with it out, I'll bet the US level won't drop below +50 dBmv

 

What model is the amplifier?

Does power go in thru a seperate connector on it?

 

Spectrum Employee

Re: Excessive Data Packet Loss, 96744

[ Edited ]

The field tech's comment about that being all he could so isn't so as "unacceptable" (as MsRaye put it), but it does seem like there's a need for maintenance to check the upstream/return/Tx at the tap.  It's possible that there field tech can't get it lower due to footage and other configurations.  An amplifier is good if it's a unity gain amp, if it's a forward gain and return loss then that's no good.  Entirely depends on what was used...

 

This is why  I don't like plant designs that leave such little headroom tolerance on the return/Tx.  I mean if it's 45 dBmV at the tap, that only gives you a headroom a 5 dB to work with for both footage an splitters.  (for example, ay if you have 1.5 dB from footage/distance and 3.5 dB from a 2-way splitter.  45 + 1.5 + 3.5 = 50).

 

From here I can only guess though... I don't know what kind of amp, don't know what exact footage, don't know what the Tx/return/upstream level at the utility tap is or what "value" that tap is (different taps have different expected Tx outputs), if there's splitters in the feeder or trunk hardlines in the outside plant before it gets to your tap (i.e.: a 10value 8-port tap with a DC-9-Split that would be +9 to any expected Tx level,  maybe that 39 dBmV would be normal & expected even though it's a 10v tap).

 

tl;dr (too long, didn't read) for you @Yzf0304

If 50 to 51 dBmV on your usptream/return/Tx is working ok, then cool.

If not then unfortuantely we'd need to know if this like that from the tap, or with the local house design. 

1. Determine what kind of "in-line amplifier" that is, it ideally should be a no-loss-no-gain (aka. unity gain) amp, they are more expensive but they don't take a hit on adding to that that upstream/return/Tx from your modem's end. 

2.  If you don't know what the upstream level at the tap is, then maybe the tech had dispatch leave notes on the account as to what it was?  If not, we might have to come out and check the tap.

3. Sounds like a lot of good repair work a was done, would hate to have the guy who helped do all that get a repeat, but if you do keep having issues just need to know if it's in range or not.

4.  Perfect lab-condition zero packet loss is unrealistic. There will always be some, but it depends on what's "customer impacting" or not.  If it affects applications and hampers your usuage of services, then yeah.  If it's only a measurment and you can't tell (i.e.: a +15 dBmV on forward/receive/Rx) then it's non-impacting and adjustments won't matter.  My concern is a 51 dBmV is uncomfortable close to the edge of the cliff.  But to declare it's "unacceptable" is far too strongly worded, IMHO.  So have things improved notably?

My postings on this site are my own, off-the-clock, and don’t necessarily represent TWC’s/Charter's strategies or opinions.
Expert

Re: Excessive Data Packet Loss, 96744

[ Edited ]

51 is unacceptable as there's no longer 3 dB of headroom on most modems and they're going to try to reset and relevel if theirs any level change between your modem and the cable head end miles away.

Out here we only have return or upstream amps in only one of every 3 street amps that boost DS or forward levels. So every 6 tapoffs, those customers  have issues if any more than a 2 way splitter is used for the cable modem. My levels here vary 2 dB over outside temperature changes