|Acquire Downstream Channel||Locked|
|DOCSIS Network Access Enabled||Allowed|
|Channel||Lock Status||Modulation||Channel ID||Frequency||Power||SNR||Corrected||Uncorrectables|
|1||Locked||256QAM||15||585.00 MHz||3.60 dBmV||40.95 dB||0||0|
|2||Locked||256QAM||2||507.00 MHz||5.00 dBmV||40.95 dB||11||0|
|3||Locked||256QAM||3||513.00 MHz||4.40 dBmV||40.95 dB||15||0|
|4||Locked||256QAM||4||519.00 MHz||4.70 dBmV||40.37 dB||9||0|
|5||Locked||256QAM||5||525.00 MHz||4.40 dBmV||40.37 dB||17||0|
|6||Locked||256QAM||6||531.00 MHz||4.30 dBmV||40.95 dB||17||0|
|7||Locked||256QAM||7||537.00 MHz||4.50 dBmV||40.95 dB||15||0|
|8||Locked||256QAM||8||543.00 MHz||3.90 dBmV||40.37 dB||29||0|
|9||Locked||256QAM||9||549.00 MHz||4.40 dBmV||40.95 dB||9||0|
|10||Locked||256QAM||10||555.00 MHz||3.90 dBmV||40.37 dB||0||0|
|11||Locked||256QAM||11||561.00 MHz||4.10 dBmV||40.37 dB||0||0|
|12||Locked||256QAM||12||567.00 MHz||4.00 dBmV||40.37 dB||0||0|
|13||Locked||256QAM||13||573.00 MHz||3.80 dBmV||40.95 dB||1||0|
|14||Locked||256QAM||14||579.00 MHz||3.90 dBmV||40.37 dB||0||0|
|15||Locked||256QAM||1||501.00 MHz||4.80 dBmV||40.95 dB||32||10441|
|16||Locked||256QAM||16||591.00 MHz||3.60 dBmV||40.37 dB||45||0|
|Channel||Lock Status||US Channel Type||Channel ID||Symbol Rate||Frequency||Power|
|1||Locked||ATDMA||6||5120 kSym/s||24.20 MHz||42.50 dBmV|
|2||Locked||ATDMA||8||2560 kSym/s||37.00 MHz||42.50 dBmV|
|3||Locked||ATDMA||7||5120 kSym/s||30.60 MHz||42.50 dBmV|
|4||Locked||TDMA||5||2560 kSym/s||19.40 MHz||42.25 dBmV|
I have spoken to Tier 3 phones (advanced repair) and supervisors for onsite techs. Can anyone tell me what they think is going on based off the information provided? I do not have a filter between me and the splitter at the drop; at least I didn't the last time I saw the contents of the box with the supervisor.
bad or loose connection allowing ingress from your local TV ch 19 on 501 mHz for a start.
What's your zip code ?
Ch 19 is weaker than 21,22,23 which are the usual Austin culprits, but the levels assume an even pattern and can easily vary 20 dB
513,519, 525 are ch's 21,22,23
here's the printout, it's possible ch 19 changed it's profile and not caught in the may 2016 updates...
at least the s/n is linear on all channels indicating that it's not a continuous problem and there aren't errors on 585 which is the "home" channel
Unless your service degrades, TWC's not going to address this
What I see is increasing packetloss. I work in networking, so I know 1-2% packet loss isn't a huge hit, but it appears to be a sign of soemthing else.
It tends to affect my online gaming alot, which i know is like arguing first world problems; but essentially leads to weird timeouts and it can affect my ability to work from home over VPN;
I see in ym log (i clear it regularly):
|Sat Jun 11 06:43:10 2016||3||No Ranging Response received - T3 time-out;CM-MAC=<redacted MAC address>;CMTS-MAC=<redacted MAC address>;CM-QOS=1.1;CM-VER=3.0;|
Is this fairly normal?
T3's are "common" not "normal" especially painfull when they exceed 3 seconds and become a T4 that resets the modem
These are due to multiple bad in house and outside plant shielding and grounding issues that TWC is lax at locating and repairing.
Those are usually a 5-45 mHz upstream issue and don't affect downstream individual channels in the 54-1002 mHz range
Dont mean to hijack, but i have been following this thread as i have been chasing some similar issues.
MsRaye, would you comment further re: "Those are usually a 5-45mHz upstream issue"
Is it the "ranging response" T3 time out that leads you there? (this is the only error i get in my logs). While all may be ingress issues, those frequencies are a different animal than the higher VHF and UHF sources.
In any case, just looking to narrow in on the problem. I am running out of the easy solutions on my end of the plant. I will open a seperate thread if needed on my specifics
Thanks, and good hunting IrishMan...
We, on the CM side can't see the error, s/n and correction on the upstream channels as those are on the CMTS boxes customers don't have access to
So it takes looking at the levels and logs to try to determine where's the issue. Phone support doesn't do that.
resetting modems clears out the logs making troubleshooting intermittents impossible
|Thu Jan 01 00:02:19 1970||3||No Ranging Response received - T3 time-out;CM-MAC=d<redacted MAC address>;CMTS-MAC=<redacted MAC address>;CM-QOS=1.1;CM-VER=3.0;|
|Thu Jun 16 12:17:03 2016||5||TCS Partial Service;CM-MAC=<redacted MAC address>;CMTS-MAC=<redacted MAC address>;CM-QOS=1.1;CM-VER=3.0;|
|Thu Jun 16 12:18:05 2016||3||No Ranging Response received - T3 time-out;CM-MAC=<redacted MAC address>;CMTS-MAC=<redacted MAC address>;CM-QOS=1.1;CM-VER=3.0;|
Recent log entries
don't reset the modem, paste the signal page... something took out a channel or channels to cause partial service, need to see which one(s)