Participant

Re: Ongoing connectivity issues / T3 timeouts

So what should my next step be?
Keep an eye on the Corrected/Uncorrected codewords count and see if it continues to steadily increase (as it has been doing, even after the replacement done today)?

EDIT: As of now, only the Corrected codewords has risen. The Uncorrected codewords seems to have leveled-off if not stopped rising completely.


The tech was quite adamant that there was no ingress whatsoever. I even showed him these posts about the RF channels from over-the-air and he said that didn't apply because I don't have TV service. I'm assuming he's ignorant of the fact that other RF signals in the air can cause ingress?

 

The only thing the tech didn't do was replace any existing cabling. I even noted that one of the cables in-use to run the connection along the house was quite old (it's white, not black; that should clearly denote how old it is), yet he found nothing wrong and connected it all back as it was.

Participant

Re: Ongoing connectivity issues / T3 timeouts

Signal levels one more time (I'm contemplating doing another reset on the modem so I can get a clear picture on what the modem does from a fresh state):

 

 

Channel ID
Frequency507000000 Hz 513000000 Hz 525000000 Hz 543000000 Hz 
Signal to Noise Ratio34 dB 34 dB 34 dB 34 dB 
Downstream ModulationQAM256 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
6 dBmV  6 dBmV  6 dBmV  6 dBmV  

 

UpstreamBonding Channel Value
Channel ID
Frequency37000000 Hz 19400000 Hz 24200000 Hz 30600000 Hz 
Ranging Service ID9666 9666 9666 9666 
Symbol Rate2.560 Msym/sec 2.560 Msym/sec 5.120 Msym/sec 5.120 Msym/sec 
Power Level45 dBmV 46 dBmV 46 dBmV 46 dBmV 
Upstream Modulation[3] QPSK
[2] 16QAM
 
[3] QPSK
[2] 16QAM
 
[3] QPSK
[3] 64QAM
 
[3] QPSK
[3] 64QAM
 
Ranging StatusSuccess Success Retries Exceed Retries Exceed 

 

Signal Stats (Codewords)Bonding Channel Value
Channel ID
Total Unerrored Codewords588154116 587359102 587401908 587273240 
Total Correctable Codewords359058 324084 281687 411809 
Total Uncorrectable Codewords6107 6059 5756 16034 
Expert

Re: Ongoing connectivity issues / T3 timeouts

Cat LOLMan LOLRobot LOLSmiley LOLWoman LOL

The tech was quite adamant that there was no ingress whatsoever. I even showed him these posts about the RF channels from over-the-air and he said that didn't apply because I don't have TV service.

 

 

I'm assuming he's ignorant of the fact that other RF signals in the air can cause ingress?  Poor/ no interference training, uhhh, hasn't got a clue...

 Ingress comes in from an external source when it's not supposed to. That causes both downstream and upstream issues, you see the downstream ones in the good vs. corrected/ uncorrecteds and i'd consider 1 in 100,000 good but 1 in 1,000,000 as excellent

 correcteds are a minor nuisance, uncorrecteds can slow you down a lot.

 

upstream ingress is in the 5-45 mHZ reverse path back to the head end, the s/n and errors are only seen by TWC if they ever bother to look at the CMTS flop reports, on the customers side, it's usually causing t3 and T4 errors. T4's are bad as they reset the modem, T3's are an occasional delay. A couple t3's a day might be normal, it's probably someone else on the node with connection issues, T4's are usually upstream ingress

t1,2,5,6 are almost always TWC CMTS hardware failure related but could be a corrupt or misprovisioned modem.

 

 Bottom line is I think you're going to need to rent a TWC modem, Hopefully one that does 8x4 channels and shows up awfull amounts of errors, call twc out again and get them to escallate the issue to the crew that has the bucket trucks andd works on the street amps.

 I'll bet your problem is worst when windy and raining or temp changes suddenly and is a broken shield on hardline enterring an amp tapoff or an amp missing it's cover or shielding on the cover or an incorrect directional coupler.

 I don't like your downstream level being that high with 150' of cable. It points to an amplifier issue.

 

Participant

Re: Ongoing connectivity issues / T3 timeouts

Thank you so much for the help thusfar, MsRaye. After all this is said and done, I think I will have learned a lot more about radio frequencies and interference than I ever wanted to... It's certainly a lot of information to digest in the span of only a couple of days. Thankfully, you've broken it down into more easily understood terms.

 

I'm going to power reset the modem, take a snapshot of the signal levels after it has been up for 5 mins, and then leave it on overnight and check it again tomorrow when I wake up.

I'll report back tomorrow with what I have and will also call TWC again.

 

Have a good night,

sm-tx

Participant

Re: Ongoing connectivity issues / T3 timeouts

Good morning,

 

 

Here is an update on the modem stats.

 

Signal 5mins after the power reset yesterday evening: https://i.gyazo.com/3112396c39300577a371cff5dcb43b1f.png

 

Signal this morning: https://i.gyazo.com/5d3c45b53c1cb1b1c3dc56700229d47c.png

 

Log:

 

Jan 21 2016 07:52:403-CriticalR05.0Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=30:60:23:d4:07:d2;CMTS-MAC=00:01:5c:48:ba:44;CM-QOS=1.1;CM-VER=3.0;
Jan 21 2016 07:46:403-CriticalR06.0Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=30:60:23:d4:07:d2;CMTS-MAC=00:01:5c:48:ba:44;CM-QOS=1.1;CM-VER=3.0;
Jan 21 2016 07:46:403-CriticalR03.0Ranging Request Retries exhausted;CM-MAC=30:60:23:d4:07:d2;CMTS-MAC=00:01:5c:48:ba:44;CM-QOS=1.1;CM-VER=3.0;
Jan 21 2016 07:46:403-CriticalR06.0Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=30:60:23:d4:07:d2;CMTS-MAC=00:01:5c:48:ba:44;CM-QOS=1.1;CM-VER=3.0;
Jan 21 2016 07:46:403-CriticalR03.0Ranging Request Retries exhausted;CM-MAC=30:60:23:d4:07:d2;CMTS-MAC=00:01:5c:48:ba:44;CM-QOS=1.1;CM-VER=3.0;
Jan 21 2016 07:46:403-CriticalR06.0Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=30:60:23:d4:07:d2;CMTS-MAC=00:01:5c:48:ba:44;CM-QOS=1.1;CM-VER=3.0;
Jan 21 2016 07:46:403-CriticalR03.0Ranging Request Retries exhausted;CM-MAC=30:60:23:d4:07:d2;CMTS-MAC=00:01:5c:48:ba:44;CM-QOS=1.1;CM-VER=3.0;
Jan 21 2016 07:46:163-CriticalR05.0Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=30:60:23:d4:07:d2;CMTS-MAC=00:01:5c:48:ba:44;CM-QOS=1.1;CM-VER=3.0;
Jan 21 2016 07:40:163-CriticalR06.0Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=30:60:23:d4:07:d2;CMTS-MAC=00:01:5c:48:ba:44;CM-QOS=1.1;CM-VER=3.0;
Jan 21 2016 07:40:163-CriticalR03.0Ranging Request Retries exhausted;CM-MAC=30:60:23:d4:07:d2;CMTS-MAC=00:01:5c:48:ba:44;CM-QOS=1.1;CM-VER=3.0;
Jan 21 2016 07:40:153-CriticalR06.0Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=30:60:23:d4:07:d2;CMTS-MAC=00:01:5c:48:ba:44;CM-QOS=1.1;CM-VER=3.0;
Jan 21 2016 07:40:153-CriticalR03.0Ranging Request Retries exhausted;CM-MAC=30:60:23:d4:07:d2;CMTS-MAC=00:01:5c:48:ba:44;CM-QOS=1.1;CM-VER=3.0;
Jan 21 2016 07:40:153-CriticalR06.0Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=30:60:23:d4:07:d2;CMTS-MAC=00:01:5c:48:ba:44;CM-QOS=1.1;CM-VER=3.0;
Jan 21 2016 07:40:153-CriticalR03.0Ranging Request Retries exhausted;CM-MAC=30:60:23:d4:07:d2;CMTS-MAC=00:01:5c:48:ba:44;CM-QOS=1.1;CM-VER=3.0;
Jan 21 2016 07:39:513-CriticalR05.0Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=30:60:23:d4:07:d2;CMTS-MAC=00:01:5c:48:ba:44;CM-QOS=1.1;CM-VER=3.0;
Jan 21 2016 07:33:513-CriticalR06.0Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=30:60:23:d4:07:d2;CMTS-MAC=00:01:5c:48:ba:44;CM-QOS=1.1;CM-VER=3.0;
Jan 21 2016 07:33:513-CriticalR03.0Ranging Request Retries exhausted;CM-MAC=30:60:23:d4:07:d2;CMTS-MAC=00:01:5c:48:ba:44;CM-QOS=1.1;CM-VER=3.0;
Jan 21 2016 07:33:513-CriticalR06.0Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=30:60:23:d4:07:d2;CMTS-MAC=00:01:5c:48:ba:44;CM-QOS=1.1;CM-VER=3.0;
Jan 21 2016 07:33:513-CriticalR03.0Ranging Request Retries exhausted;CM-MAC=30:60:23:d4:07:d2;CMTS-MAC=00:01:5c:48:ba:44;CM-QOS=1.1;CM-VER=3.0;
Jan 21 2016 07:33:513-CriticalR06.0

Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=30:60:23:d4:07:d2;CMTS-MAC=00:01:5c:48:ba:44;CM-QOS=1.1;CM-VER=3.0;

 

My main take away from this is that:

1) The T3 timeouts are still happening frequently; more than just a "few a day".

2) I've now lost all but one of my upstream channels; it wasn't like that before the tech put the terminated splitter on the line and changed the filter (or whatever it was) on the pole tap. My guess is that it's because of the terminated splitter.

3) The Corrected codewords continues to rise and shows no signs of leveling off. The Uncorrected codewords, however, seems to have stopped for the time being.

 

Since the tech visit yesterday, I've yet to have any service interruptions.

I have another house visit scheduled for Friday, Jan 22nd. I expressed that no existing cabling was replaced and is several years old. Even if the connectors are good, I still want it all replaced so I can rule that out as a cause. It's the old coaxial cabling that looks like this http://www.tech-faq.com/wp-content/uploads/Coaxial-Cable.jpg (Which I've learned has bad compression, as MsRaye has stated in similar threads).

The good news is that this time, both a tech AND a supervisor are supposed to be coming to reexamine all the lines and double-check everything.

I'll be sure to bring up the topic of RF interference & ingress in relation to the T3 and T4 errors I've had in the past once again, as well as asking about potential bad amplifiers further up the pipeline between me and the head-end. I'll also bring up the notes below as well: 


@MsRaye wrote:

 I'll bet your problem is worst when windy and raining or temp changes suddenly and is a broken shield on hardline enterring an amp tapoff or an amp missing it's cover or shielding on the cover or an incorrect directional coupler.


 

Regards,

sm-tx

Expert

Re: Ongoing connectivity issues / T3 timeouts

Wish you'd paste the levels here... I can't copy them... or compare them easily

..

 

Looks like tech needs to come out in the morning as the s/n is worst.

 

 any possibility that your electric service is sagging in the morning, like from electric heat, especially on the same circuit as the modem?  It's possible that modem has a bad power supply and getting flakey with low line voltage.

It's the only wild guess I have left other than out on the street amps going bad.

 

and yes, the splitter seems to have made it worst.

 

Participant

Re: Ongoing connectivity issues / T3 timeouts

Updated signal:

Channel ID
Frequency513000000 Hz 525000000 Hz 537000000 Hz 543000000 Hz 
Signal to Noise Ratio33 dB 33 dB 33 dB 33 dB 
Downstream ModulationQAM256 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
7 dBmV  7 dBmV  7 dBmV  7 dBmV  

 

UpstreamBonding Channel Value
Channel ID
Frequency37000000 Hz 19400000 Hz 24200000 Hz 30600000 Hz 
Ranging Service ID10080 10080 10080 10080 
Symbol Rate2.560 Msym/sec 2.560 Msym/sec 5.120 Msym/sec 5.120 Msym/sec 
Power Level45 dBmV 45 dBmV 45 dBmV 45 dBmV 
Upstream Modulation[3] QPSK
[2] 16QAM
 
[3] QPSK
[2] 16QAM
 
[3] QPSK
[3] 64QAM
 
[3] QPSK
[3] 64QAM
 
Ranging StatusSuccess Retries Exceed Retries Exceed Retries Exceed 

 

Signal Stats (Codewords)Bonding Channel Value
Channel ID
Total Unerrored Codewords2432088268 2433453339 2431830785 2430134176 
Total Correctable Codewords10448694 9083541 10706129 12402708 
Total Uncorrectable Codewords593 679 651 681 

 

 


MsRaye wrote:

Looks like tech needs to come out in the morning as the s/n is worst.

 

 any possibility that your electric service is sagging in the morning, like from electric heat, especially on the same circuit as the modem?  It's possible that modem has a bad power supply and getting flakey with low line voltage.

It's the only wild guess I have left other than out on the street amps going bad.

 


The electric service has been fine, as-is the wiring in the house; no electricity dips or issues.

Even with that, the computer, my modem, and my router all run on a UPS w/ voltage regulator, so if the voltage was insanely bad, it would be regulated. 

 

Expert

Re: Ongoing connectivity issues / T3 timeouts

This has got to be broadcast tv ingress, the latest channel lineup has skipped over the known area broadcast tv channels

 

 
Frequency513000000 Hz 525000000 Hz 537000000 Hz 543000000 Hz 

 

Stations   Antenna
K20DN-D 20 FMN
RF Channel: 20
8 miles at 329°

507mHz

qam ch 1

K24HH-D 24.1 FMN
RF Channel: 24
8 miles at 329°

531mHz

qam ch 5

KAUZ-DT 6.1 CBS
RF Channel: 22
8 miles at 338°

519mHz

qam ch 3

KFDX-DT 3.1 NBC
RF Channel: 28
8 miles at 329°
555mHz
K44GS-D 13.1 PBS
RF Channel: 44
9 miles at 314°
651mHz
KJBO-LP 35 MNT
RF Channel: 35
8 miles at 336°
597mHz
KJTL-DT 18.1 FOX
RF Channel: 15
32 miles at 334°
477mHz
KSWO-DT 7.1 ABC
RF Channel: 11
32 miles at 335°
199mHz
K18IZ-D 10.1 PBS
RF Channel: 18
32 miles at 334°
495mHz
 
Participant

Re: Ongoing connectivity issues / T3 timeouts

Theoretically, isn't that what it should do, though? To try and prevent interference?

...Unless simply just skipping over them isn't helping the signal quality at all.

Expert

Re: Ongoing connectivity issues / T3 timeouts

yes and no...

 

It appears the ingress is before a line amp and is overloading one or more amps and pushing the s/n down to the marginal level on "good" channels...

What you have is all out of spec and twc needs to send out a tech that will escalate the issue if it's out on the streets somewhere.

 

The tech needs to look at the s/n on ch's 1-3-5,  hopefully a different tech with some interference troubleshooting experience

 

it is horrible at times...