Participant

Re: Ongoing connectivity issues / T3 timeouts

Signal

 

Channel ID
Frequency507000000 Hz 513000000 Hz 525000000 Hz 543000000 Hz 
Signal to Noise Ratio35 dB 35 dB 35 dB 35 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  5 dBmV  6 dBmV  5 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 47 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 Codewords168141871 167314770 167317140 167308659 
Total Correctable Codewords25885 22996 21035 30969 
Total Uncorrectable Codewords6107 6059 5756 16034 

 

 

Log:

 

Jan 20 2016 16:15:273-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 20 2016 16:11: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 20 2016 16:11:503-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 20 2016 16:11:503-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 20 2016 16:11:503-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 20 2016 16:11:263-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 20 2016 16:05:263-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 20 2016 16:05:263-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 20 2016 16:05:263-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 20 2016 16:05:263-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 20 2016 16:05:023-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 20 2016 15:59:013-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 20 2016 15:59:013-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 20 2016 15:59:013-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 20 2016 15:59:013-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 20 2016 15:58:373-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 20 2016 15:52:373-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 20 2016 15:52:373-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 20 2016 15:52:373-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 20 2016 15:52:373-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;

 

Established Sharer

Re: Ongoing connectivity issues / T3 timeouts

The TWC tech did a poor job... yes, the added splitter reduced the downstream power level, but of course it also increased the upstream power level AND it caused two of your upstream channels to fail due to excessive retries.  I would remove that extra splitter and try to get another tech out -- hopefully you'll get one that understands the basics of dealing with transmission line issues.  The higher upstream power levels will likely increase the frequency of the T3 timeouts, you'd like to see those values in the upper 30s or low 40s.

Expert

Re: Ongoing connectivity issues / T3 timeouts

Ok, It's still skipping over the 2 tv broadcast channels and looks like 543 mHz (tv ch 26) has an issue as well. For a couple hours up time, there's an awfull lot of correcteds/uncorrecteds unless those were when the tech was changing connectors and the filter. It's kind of hard with a 4 ch modem to see what the levels are on the rest of the channels, Your area has at least 8 if not 12 or 16.

See if the problem reoccurs in the morning. If so, see if the neighbor has the same issue.

 

Ingress is from external RF sources, many of which are FCC licensed transmitters and has nothing to do with cable tv channels, if you pay for them or not. Problem was the worst on your first post.

 Another question, how far is your house from the pole tap and roughly how many feet of cable in your house? Are you down in a valley or above surrounding grade? (i'm looking to see where the nearest 26 is...) 115 miles away in Dallas...

SignAffiliateRF ChannelVirtual ChannelBandPowerCityDistance Heading

Total results: 41
KAUZ-TVCBS226.1UHF200.0 kWWichita Falls8.51 mi328.76°
KFDX-TVNBC283.1UHF1000.0 kWWichita Falls8.52 mi319.66°
KJTLFOX1518.1UHF1000.0 kWWichita Falls31.95 mi331.45°
KSWO-TVABC117.1VHF138.0 kWLawton32.56 mi333.05°
KXIICBS1212.1VHF14.37 kWSherman96.82 mi79.79°
KTENNBC2610.1UHF1000.0 kWAda115.78 mi69.80°
KPXDION4268.1UHF1000.0 kWArlington119.93 mi133.64°
WFAA-TVABC88.1VHF21.5 kWDallas119.98 mi133.86°
KDFWFOX354.1UHF1000.0 kWDallas119.98 mi133.86°
KUVN-TVUNIVISION2323.1UHF185.76 kWGarland120.12 mi133.61°
KMPXIND3029.1UHF1000.0 kWDecatur120.22 mi133.58°
KFWDIND952.1VHF6.87 kWFort Worth120.22 mi133.58°
KXAS-TVNBC415.1UHF1000.0 kWFort Worth120.35 mi133.58°
KXTX-TVTELEMUNDO4039.1UHF1000.0 kWDallas120.38 mi133.67°
KTXAINDEPENDENT2921.1UHF1000.0 kWFort Worth121.32 mi133.53°
KTVTCBS1911.1UHF1000.0 kWFort Worth121.32 mi133.53°
KERA-TVPBS1413.1UHF475.0 kWDallas121.32 mi133.53°
KDFIMY NETWORK3627.1UHF1000.0 kWDallas122.81 mi134.45°
KDTX-TVTRINITY BROADCASTING NETWORK4558.1UHF1000.0 kWDallas122.81 mi134.45°

 

 Do you have an outside antenna on your tv and do you get the dallas stations, esp ch 10.1 (on rf ch 26)?

Next, copy and paste a tracert to google.com, that will point to where the head end is and a possible problem there with your node.

 

 

Expert

Re: Ongoing connectivity issues / T3 timeouts


@RickE wrote:

The TWC tech did a poor job... yes, the added splitter reduced the downstream power level, but of course it also increased the upstream power level AND it caused two of your upstream channels to fail due to excessive retries.  I would remove that extra splitter and try to get another tech out -- hopefully you'll get one that understands the basics of dealing with transmission line issues.  The higher upstream power levels will likely increase the frequency of the T3 timeouts, you'd like to see those values in the upper 30s or low 40s.


Rick, Cust Needs to see if that improves or makes the problem worst. 

 

Participant

Re: Ongoing connectivity issues / T3 timeouts

The total length of cabling from the pole tap, to where the wall outlet is, I would have to estimate at 130-140ft. of cabling. From the back of the house where the cable is attached, to the pole itself, is ~100ft.

I should note that the cabling runs outside, along the back wall of the house, is grommeted, and it's not just one cable; there are two lines of coaxial cabling connected via barrel connectors. And everything looked fine and undamaged when the tech inspected it. Only a very small length of cabling actually resides in the walls itself (maybe half of a foot or so).

Lastly, my house sits on grade level and is even with the pole (the pole of course, being taller than the house itself, so the cable from the pole to the house has to descend at a slight angle. Only in the front of the house is where the ground declines.

 

EDIT: If you want, I can take pictures that can describe the environment much better than I can do in words.

Participant

Re: Ongoing connectivity issues / T3 timeouts

 Do you have an outside antenna on your tv and do you get the dallas stations, esp ch 10.1 (on rf ch 26)?
Next, copy and paste a tracert to google.com, that will point to where the head end is and a possible problem there with your node.

 By outside antenna, I'm assuming a rabbit-ears antenna? There is one in-use on the TV in the living room (not in the same room as my modem, but it is closer to the cabling coming to the house than the room that the modem in, if that matters.

I get a 10-1 channel which is OETA-HD, an Oklahoma NBC station; not a Dallas station.

 

Tracert to google: 

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Light>tracert google.com

Tracing route to google.com [216.58.218.174]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    25 ms    22 ms    14 ms  (IP omitted)
  3   190 ms    33 ms    31 ms  tge0-0-15.wcfltxjj02h.texas.rr.com [24.160.24.117]
  4    40 ms    39 ms    38 ms  agg30.hstqtxl301r.texas.rr.com [24.175.63.216]
  5    43 ms    39 ms    46 ms  bu-ether16.hstqtx0209w-bcr00.tbone.rr.com [66.109.6.108]
  6    32 ms    30 ms    30 ms  bu-ether12.dllstx976iw-bcr00.tbone.rr.com [66.109.6.39]
  7    38 ms    30 ms    28 ms  0.ae2.pr1.dfw10.tbone.rr.com [107.14.17.236]
  8    44 ms    39 ms    42 ms  ix-23-0.tcore2.DT8-Dallas.as6453.net [66.110.57.97]
  9    88 ms    78 ms    65 ms  74.125.50.212
 10    30 ms    28 ms    27 ms  66.249.95.16
 11    28 ms    28 ms    27 ms  209.85.246.211
 12    32 ms    30 ms    29 ms  dfw06s46-in-f174.1e100.net [216.58.218.174]

Trace complete.

 

And while we're on the topic of intereference, if it's any use, my cellphone has started completely missing calls altogether recently. When it happens, I get no missed call, just a new voicemail pop-up. My carrier is U.S. Cellular. I keep the phone in the same room as the one the modem is in.

Expert

Re: Ongoing connectivity issues / T3 timeouts


sm-tx wrote:.

Lastly, my house sits on grade level and is even with the pole (the pole of course, being taller than the house itself, so the cable from the pole to the house has to descend at a slight angle. Only in the front of the house is where the ground declines.

 

 


Is your street/ zip code area above surrounding terrain and with more or less a clear shot towards DFW? 

Participant

Re: Ongoing connectivity issues / T3 timeouts

Yes. The house, and the neighboring houses parallel to mine, are all on a large "hill" of sorts.
Minus any trees in the way, it's pretty much a clear line of sight.

Expert

Re: Ongoing connectivity issues / T3 timeouts

OETA is a PBS network with a bunch of translators in OK.

 I can't look up the translators "aliased" channel numbers, the wiki on oeta is a little out of date,  Rabbit ears don't work well on UHF, but I'd expect you to get 4 local channels plus their subchannels .

 

 Anyway, it looks like the head end IP routs to Houston, not DFW, so if there is ingress it's probably in your zip code

 From antenna web, 10.1 is a translator on ch 18...

Stations   Antenna
K20DN-D 20 FMN
RF Channel: 20
8 miles at 329°
507mHz
K24HH-D 24.1 FMN
RF Channel: 24
8 miles at 329°
531mHz
KAUZ-DT 6.1 CBS
RF Channel: 22
8 miles at 338°
519mHz
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
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Expert

Re: Ongoing connectivity issues / T3 timeouts

You could also be getting interference from the AFB, but again, the ingress is due to something loose or corroded between the TWC head end and your house....