Visitor
•
2 Messages
Identical outages three days in a row
Hi,
We turned our connection up at the end of April. After a honeymoon period where everything worked great, we started to experience intermittent outages. For the most part they're usually pretty short, but we have had a tech out once after one of the longer ones. They couldn't find any obvious issues, but did replace a connector on our tap at the pole just to be thorough, though that didn't seem to have any effect. My computer is connected via ethernet to a switch which connects to my router and then into my Arris SB8200 modem. There is no wifi involved and my router is working 100% fine. It appears to be that the modem is losing sync during these outages.
The connection had been solid for the past week and a half or so with zero issues, but then we started having intermittent outages again. I wouldn't get too excited about it, except that the connection has gone down at almost exactly the same time, in exactly the same way, three days in a row:
07/28/2021 20:40
07/29/2021 20:46
07/30/2021 21:14
The software that Comcast is pushing out to SB8200s appears to have a pretty egregious and unfortunate bug where often when you load the event log on the modem web interface it causes the web server in the modem to crash and become unresponsive until you restart the modem. For that reason I wasn't able to get any information from the logs the first two days, but was able to grab the information from todays outage. The other unfortunate bug is that either the SB8200 or the CMTS doesn't seem to know/care about daylight saving time, so the time in the logs is off by an hour. MAC addresses have been sanitized to protect the innocent:
Date Time Event ID Event Level Description
07/30/2021 20:17 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=ec:a9:40:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"
07/30/2021 20:16 74010100 6 "CM-STATUS message sent. Event Type Code: 7; Chan ID: 1 2 4; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=ec:a9:40:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"
07/30/2021 20:16 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=ec:a9:40:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"
07/30/2021 20:16 74010100 6 "CM-STATUS message sent. Event Type Code: 7; Chan ID: 1 2 4; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=ec:a9:40:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"
07/30/2021 20:15 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=ec:a9:40:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"
07/30/2021 20:15 74010100 6 "CM-STATUS message sent. Event Type Code: 7; Chan ID: 1 2 4; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=ec:a9:40:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"
07/30/2021 20:15 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=ec:a9:40:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"
07/30/2021 20:14 74010100 6 "CM-STATUS message sent. Event Type Code: 7; Chan ID: 1 2 4; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=ec:a9:40:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"
07/30/2021 20:14 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=ec:a9:40:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"
07/30/2021 20:14 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=ec:a9:40:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"
07/30/2021 20:14 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=ec:a9:40:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"
07/30/2021 20:14 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=ec:a9:40:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"
07/30/2021 20:14 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=ec:a9:40:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"
07/30/2021 20:14 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=ec:a9:40:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"
07/30/2021 20:14 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=ec:a9:40:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"
07/30/2021 20:14 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=ec:a9:40:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"
07/30/2021 20:14 74010100 6 "CM-STATUS message sent. Event Type Code: 7; Chan ID: 1 2 4; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=ec:a9:40:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"
07/30/2021 20:14 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=ec:a9:40:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"
07/30/2021 20:14 82000800 3 "16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=ec:a9:40:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"
07/30/2021 20:14 82000600 3 "Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=ec:a9:40:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"
07/30/2021 20:14 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=ec:a9:40:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"
07/30/2021 20:14 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=ec:a9:40:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"
07/30/2021 20:14 82000800 3 "16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=ec:a9:40:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"
07/30/2021 20:14 82000600 3 "Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=ec:a9:40:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"
07/30/2021 20:14 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=ec:a9:40:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"
07/30/2021 20:14 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=ec:a9:40:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"
07/30/2021 20:14 82000800 3 "16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=ec:a9:40:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"
07/30/2021 20:14 82000600 3 "Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=ec:a9:40:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"
07/30/2021 20:14 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=ec:a9:40:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"
07/30/2021 20:08 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=ec:a9:40:xx:xx:xx;CMTS-MAC=00:01:5c:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;"
I can't imagine any sort of wiring issue that would cause problems like clockwork three days in a row, so I don't know how much use rolling a tech out would be. Though I know that my signal levels aren't perfect, the connection is 100% solid with zero packet loss in the times between the intermittent outages. Is there anything that support can look at to see if this is part of a larger issue in my area/node?
EG
Expert
•
111.5K Messages
4 years ago
An FYI. Modems do not do daylight savings time. It doesn't have any bearing on performance. Only the timestamps of the error log entries are affected.
That said. Please also post the *Downstream Power Level*, the *Upstream Power Level*, and the *SNR* (Signal to Noise Ratio) numbers.
1
0
user_48baac
Visitor
•
2 Messages
4 years ago
@EG Yeah, I wasn't implying the time zone thing had anything to do with the connection quality, it's just an annoyance when troubleshooting. If they're going to set a time zone but ignore DST, they should just use UTC instead. But I guess that's a complaint for Arris not Comcast.
As I mentioned, the signal levels aren't great, but these are the current levels and the connection works perfectly right now and does so most of the time. Zero packet loss at these signal levels currently. And again, I'm not aware of any kind of wiring issue that can repeat itself three days in a row almost like clockwork.
1