For the past 6 months, I've been having a sporadic problem with T3 time outs. I've seen a consistent pattern, and have had Comcast out (used my internal Comcast connection to have someone out). I have triple play, so I am stuck with eMTAs
The modem has been swapped out from a UBEE to a DPC-3939. Made no difference. Comcast tech swapped out the connectors on my feed from the pedestal to my house. He also placed an amp as the main splitter. My modem is therefor behind an amp and another 3.5db splitter. The tech also tested the wiring in the house, and all was fine.My levels have generally been excellent (near 0 on DS, and 42-45 US), good SNR,etc., except when the T3 problem occurs, at which point the US goes up to 51, and I get disconnected. A few seconds or a few minutes later, I get reconnected, and the US levels drop to normal
Now, here's the pattern. The T3 problems occur every Sunday morning around 9:30. They may also occur occasionally at other times during the week, usually in the evening. It did happen Saturday morning, but for only 17 seconds (according to the log).
Comcast claims that they checked the node, and everything is green, and that they haven't gotten complaints from anyone else. My retort to that the interruptions are so short, that many people don't notice, or just write it off to "one of those internet things". Note that TV is almost always fine during these occurrences. I did notice a bit of tiling a couple of times during the occurrences, but I'm not sure if that is related- it doesn't happen all the time.
My suspicion is that someone on my node is doing something at these times that is either injecting noise into the line, or causing extremely high traffic.
As a note, I did not notice any problems for the last three Sundays (12/21, 12/28, 1/4). I figure whoever is causing the problem was away on vacation. However, my DPC-3939 was not logging between 1/1 and 1/9. There could have been an unnoticed problem on 1/4.
So, my questions:
1. Is my suspicion valid?
2. If so, what can I get Comcast to do about it (remember, I have an inside contact that can get things done if he knows (I tell him) what needs to be done).
3. If not, what can be done about the problem?
Here is my log for today (now that my DPC-3939 is logging again):
2015/1/11 09:50:35 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:39:11 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:39:10 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:39:10 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:39:10 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:39:09 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:39:09 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:39:08 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:39:07 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:39:07 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:39:07 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:39:06 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:39:06 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:39:06 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:39:05 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:39:05 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:39:05 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:39:04 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:39:04 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:39:04 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:39:02 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:39:02 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:39:02 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:39:01 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:39:01 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:39:01 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:30:24 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:30:24 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:30:22 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:30:22 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:30:21 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:30:21 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:30:20 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:30:20 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:30:19 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:30:19 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:30:18 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:30:18 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:30:16 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:30:16 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:30:15 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:30:15 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:30:14 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:29:20 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:29:18 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:29:17 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:29:15 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:29:14 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:29:13 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:29:12 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:29:11 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:29:09 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:29:08 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:29:07 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:29:06 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:29:04 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:28:39 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:28:39 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:28:12 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:28:12 Critical [Docsis][521]: No Ranging Response received - T3 time-out
2015/1/11 09:28:12 Critical [Docsis][521]: No Ranging Response received - T3 time-out
The US level was up to 51 during this, and came down to normal (around 43) very quickly once it ended.
↧