Regular Visitor
•
3 Messages
Multiple drops in Service - Lots of T3 and T4 Timeouts
I am pretty much at my wits end here.
Our internet drops at least several times DAILY. These internet drops always come with some sort of t3 or t4 error in the event log. Signals looks fine, we have had techs out in the past that have said everything is fine, ran new cables, but the problem has been persistent for so long now.
Date Time | Event ID | Event Level | Description |
6/8/2020 9:22 | 82000200 | 3 | No Ranging Response received - T3 time-out;CM-MAC=14:c0:3e:1d:c7:0c;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
6/8/2020 9:23 | 82000300 | 3 | Ranging Request Retries exhausted;CM-MAC=14:c0:3e:1d:c7:0c;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
6/8/2020 9:23 | 82000600 | 3 | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=14:c0:3e:1d:c7:0c;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
6/8/2020 9:23 | 82000200 | 3 | No Ranging Response received - T3 time-out;CM-MAC=14:c0:3e:1d:c7:0c;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
6/8/2020 9:23 | 84020200 | 5 | Lost MDD Timeout;CM-MAC=14:c0:3e:1d:c7:0c;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
6/8/2020 9:24 | 82000200 | 3 | No Ranging Response received - T3 time-out;CM-MAC=14:c0:3e:1d:c7:0c;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
6/8/2020 9:42 | 82000300 | 3 | Ranging Request Retries exhausted;CM-MAC=14:c0:3e:1d:c7:0c;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
6/8/2020 9:42 | 82000600 | 3 | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=14:c0:3e:1d:c7:0c;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
6/8/2020 10:24 | 82000200 | 3 | No Ranging Response received - T3 time-out;CM-MAC=14:c0:3e:1d:c7:0c;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
6/8/2020 16:50 | 84000500 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=14:c0:3e:1d:c7:0c;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
12/31/1969 18:01 | 82000200 | 3 | No Ranging Response received - T3 time-out;CM-MAC=14:c0:3e:1d:c7:0c;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
6/8/2020 19:34 | 90000000 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=14:c0:3e:1d:c7:0c;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
6/8/2020 22:37 | 82000200 | 3 | No Ranging Response received - T3 time-out;CM-MAC=14:c0:3e:1d:c7:0c;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
6/8/2020 23:18 | 82001200 | 5 | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=14:c0:3e:1d:c7:0c;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
6/9/2020 13:15 | 82000200 | 3 | No Ranging Response received - T3 time-out;CM-MAC=14:c0:3e:1d:c7:0c;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
6/9/2020 16:28 | 82000300 | 3 | Ranging Request Retries exhausted;CM-MAC=14:c0:3e:1d:c7:0c;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
6/9/2020 16:28 | 82000600 | 3 | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=14:c0:3e:1d:c7:0c;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
6/9/2020 16:29 | 82000300 | 3 | Ranging Request Retries exhausted;CM-MAC=14:c0:3e:1d:c7:0c;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
6/9/2020 16:29 | 82000600 | 3 | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=14:c0:3e:1d:c7:0c;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
6/9/2020 16:29 | 82000300 | 3 | Ranging Request Retries exhausted;CM-MAC=14:c0:3e:1d:c7:0c;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
6/9/2020 16:29 | 82000600 | 3 | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=14:c0:3e:1d:c7:0c;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
6/9/2020 16:29 | 82000200 | 3 | No Ranging Response received - T3 time-out;CM-MAC=14:c0:3e:1d:c7:0c;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
6/9/2020 16:37 | 82000400 | 3 | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=14:c0:3e:1d:c7:0c;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
6/9/2020 16:37 | 82001100 | 5 | RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=14:c0:3e:1d:c7:0c;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
6/9/2020 16:38 | 90000000 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=14:c0:3e:1d:c7:0c;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
6/9/2020 18:33 | 82000200 | 3 | No Ranging Response received - T3 time-out;CM-MAC=14:c0:3e:1d:c7:0c;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
6/9/2020 18:33 | 82001200 | 5 | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=14:c0:3e:1d:c7:0c;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
6/9/2020 20:00 | 82000200 | 3 | No Ranging Response received - T3 time-out;CM-MAC=14:c0:3e:1d:c7:0c;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
6/9/2020 21:01 | 82000300 | 3 | Ranging Request Retries exhausted;CM-MAC=14:c0:3e:1d:c7:0c;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
6/9/2020 21:01 | 82000600 | 3 | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=14:c0:3e:1d:c7:0c;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
6/10/2020 9:15 | 82000200 | 3 | No Ranging Response received - T3 time-out;CM-MAC=14:c0:3e:1d:c7:0c;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
6/10/2020 9:15 | 84000500 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=14:c0:3e:1d:c7:0c;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
6/10/2020 9:15 | 82000200 | 3 | No Ranging Response received - T3 time-out;CM-MAC=14:c0:3e:1d:c7:0c;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
6/10/2020 9:15 | 82000300 | 3 | Ranging Request Retries exhausted;CM-MAC=14:c0:3e:1d:c7:0c;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
6/10/2020 9:15 | 82000600 | 3 | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=14:c0:3e:1d:c7:0c;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
6/10/2020 9:15 | 82000200 | 3 | No Ranging Response received - T3 time-out;CM-MAC=14:c0:3e:1d:c7:0c;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
6/10/2020 9:19 | 82000400 | 3 | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=14:c0:3e:1d:c7:0c;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
6/10/2020 9:20 | 90000000 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=14:c0:3e:1d:c7:0c;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
6/10/2020 9:43 | 82000200 | 3 | No Ranging Response received - T3 time-out;CM-MAC=14:c0:3e:1d:c7:0c;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
6/10/2020 11:28 | 84000500 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=14:c0:3e:1d:c7:0c;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
6/10/2020 13:14 | 82000200 | 3 | No Ranging Response received - T3 time-out;CM-MAC=14:c0:3e:1d:c7:0c;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
6/10/2020 13:15 | 82000300 | 3 | Ranging Request Retries exhausted;CM-MAC=14:c0:3e:1d:c7:0c;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
6/10/2020 13:15 | 82000600 | 3 | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=14:c0:3e:1d:c7:0c;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
6/10/2020 13:15 | 82000200 | 3 | No Ranging Response received - T3 time-out;CM-MAC=14:c0:3e:1d:c7:0c;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
6/10/2020 13:15 | 82000300 | 3 | Ranging Request Retries exhausted;CM-MAC=14:c0:3e:1d:c7:0c;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
6/10/2020 13:15 | 82000600 | 3 | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=14:c0:3e:1d:c7:0c;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
6/10/2020 13:15 | 82000200 | 3 | No Ranging Response received - T3 time-out;CM-MAC=14:c0:3e:1d:c7:0c;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
6/10/2020 13:19 | 82000400 | 3 | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=14:c0:3e:1d:c7:0c;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
6/10/2020 13:20 | 90000000 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=14:c0:3e:1d:c7:0c;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
6/10/2020 13:44 | 82000200 | 3 | No Ranging Response received - T3 time-out;CM-MAC=14:c0:3e:1d:c7:0c;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
EG
Expert
•
111.6K Messages
5 years ago
We need to see the signal status numbers as well. Please also post the *Downstream Power Level*, the *Upstream Power Level*, and the *SNR* (Signal to Noise Ratio) numbers as well.
0
0
gclubhouse
Regular Visitor
•
3 Messages
5 years ago
0
0
EG
Expert
•
111.6K Messages
5 years ago
The signal stats are good but the error log entries indicate that something is going on. Perhaps there is noise ingress into the line(s) somewhere.
There are other signal stat figures that can't be read by the modem. They are the "Upstream Rx Power" (Upstream Receive Power Level), the "Upstream SNR Ch." (Upstream Signal To Noise Ratio), and the "Upstream ICFR" (In Channel Frequency Response). These are as equally important in diagnosing connectivity issues as are the modem's stats.
I'm going to escalate your issue to the Comcast corporate employees that are available to these boards. They will be able to poll the CMTS to see whether or not everything is in the green zone, see your node / cable plant and modem health, and also see a history plot for the modem. You should get a reply here in your topic. Good luck !
0
gclubhouse
Regular Visitor
•
3 Messages
5 years ago
Awesome - Thank you
0
0
XfinityMichaelC
Administrator
•
4.4K Messages
5 years ago
Greetings, @gclubhouse! I appreciate you taking the time to reach out to us here on the forums. I hope you are having an amazing day! I apologize to hear of the issues you are having with your internet dropping out. I work from home myself and certainly understand the need for a reliable connection. I would like to have a closer look at this and see what we can do to get this resolved for you. Can you please send me a PM with your first and last name so I may further assist you?
To send a private message, please click my name "ComcastMichael" then select "Send a Message" on the right side.
0
caseyblue93
Visitor
•
2 Messages
4 years ago
Hello,
Just stumbled upon this post and have this identical issue. Had techs come out multiple times, re-ran wires, and everything tested "Perfect" yet I'm unable to get above 250 MBPS in most cases and it fluctuates wildly all day. Can you help me Xfinity? Here are my logs. I feel like I'm getting ripped off paying for Gigbit when it can't barely get above 250 and then divebombs down to the 60s-70s (SOMETIMES TO KBPS!!!). Please help! Brand new Motorola MB8611 modem and TP-Link Deco M9 Mesh network. Thank you!
Sun Jul 4 2021
Sun Jul 4 2021
Sun Jul 4 2021
Sun Jul 4 2021
Sun Jul 4 2021
Sun Jul 4 2021
Tue Jul 13 2021
Mon Jul 19 2021
Mon Jul 19 2021
(edited)
2
0