Visitor
•
3 Messages
Critical T3 errors - No ranging response received
I've upgraded to gig internet and my US/DS lights won't stop blinking. I'm getting lots of packet loss and late packets now too, and my modem log shows I'm getting a lot of T3 Time-outs. Any advice or solutions would be very much appreciated. Here's my event log if that helps (MAC removed)
Sat Jun 17 14:53:35 2023 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Sat Jun 17 14:53:34 2023 | Critical (3) | 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Sat Jun 17 14:53:34 2023 | Critical (3) | Ranging Request Retries exhausted;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Sat Jun 17 14:52:46 2023 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Sat Jun 17 14:52:44 2023 | Critical (3) | 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Sat Jun 17 14:52:44 2023 | Critical (3) | Ranging Request Retries exhausted;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Sat Jun 17 14:51:23 2023 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Sat Jun 17 14:51:22 2023 | Critical (3) | 16 consecutive T3 timeouts while trying to range on upstream channel 4;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Sat Jun 17 14:51:22 2023 | Critical (3) | Ranging Request Retries exhausted;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Sat Jun 17 14:50:38 2023 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Sat Jun 17 14:50:36 2023 | Critical (3) | 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Sat Jun 17 14:50:36 2023 | Critical (3) | Ranging Request Retries exhausted;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Sat Jun 17 14:49:03 2023 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Sat Jun 17 14:49:02 2023 | Critical (3) | 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Sat Jun 17 14:49:02 2023 | Critical (3) | Ranging Request Retries exhausted;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Sat Jun 17 14:46:17 2023 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Sat Jun 17 14:46:16 2023 | Critical (3) | 16 consecutive T3 timeouts while trying to range on upstream channel 4;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Sat Jun 17 14:46:16 2023 | Critical (3) | Ranging Request Retries exhausted;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Sat Jun 17 14:45:16 2023 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Sat Jun 17 14:45:14 2023 | Critical (3) | 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Sat Jun 17 14:45:14 2023 | Critical (3) | Ranging Request Retries exhausted;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Sat Jun 17 14:44:12 2023 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Sat Jun 17 14:44:10 2023 | Critical (3) | 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Sat Jun 17 14:44:10 2023 | Critical (3) | Ranging Request Retries exhausted;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Sat Jun 17 14:42:17 2023 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Sat Jun 17 14:42:15 2023 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Sat Jun 17 14:42:01 2023 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Sat Jun 17 14:42:00 2023 | Critical (3) | 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Sat Jun 17 14:42:00 2023 | Critical (3) | Ranging Request Retries exhausted;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Sat Jun 17 14:41:47 2023 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Sat Jun 17 14:41:46 2023 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Sat Jun 17 14:41:11 2023 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Sat Jun 17 14:41:08 2023 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Sat Jun 17 14:41:00 2023 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Sat Jun 17 14:40:59 2023 | Critical (3) | 16 consecutive T3 timeouts while trying to range on upstream channel 4;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Sat Jun 17 14:40:59 2023 | Critical (3) | Ranging Request Retries exhausted;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Sat Jun 17 14:40:50 2023 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Sat Jun 17 14:40:47 2023 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Sat Jun 17 14:40:44 2023 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
Sat Jun 17 14:40:42 2023 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; |
somechump
Visitor
•
3 Messages
2 years ago
Status
Profile ID
ID
MER
Number Range
Codewords
Codewords
Codewords
1
0