- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
CM500 T3 and T4 Errors
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
CM500 T3 and T4 Errors
Hello,
I am having what appears to be some intermittent connection issues with my cable modem. My ISP is Xfinity and they are telling me everything is fine, so I gather this is probably somewhere on my end. It appears that I do not have any splitters between the coaxial cable coming out of my wall and being plugged into my router. I checked outside and while the cable goes through several extenders/extensions it doesn't seem to go through any splitters. I have the latest firmware for my router and cable modem and have power cycled/reset the modem through the ISP. I checked my event log and it appears the T4 errors are what is causing my internet to go down from what some other posts have described. Any suggestions as to what may be causing this interference?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: CM500 T3 and T4 Errors
Here is my event log
2020-6-9, 12:45:36 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:a5:11:78:af:fc;CMTS-MAC=00:56:2b:77:89:5d;CM-QOS=1.1;CM-VER=3.0; |
2020-6-9, 12:32:58 | Notice (6) | Honoring MDD; IP provisioning mode = IPv6 |
2020-6-9, 12:32:43 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=bc:a5:11:78:af:fc;CMTS-MAC=00:56:2b:77:89:5d;CM-QOS=1.0;CM-VER=3.0; |
2020-6-9, 12:30:31 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:a5:11:78:af:fc;CMTS-MAC=00:56:2b:77:89:5d;CM-QOS=1.1;CM-VER=3.0; |
2020-6-9, 12:30:19 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:a5:11:78:af:fc;CMTS-MAC=00:56:2b:77:89:5d;CM-QOS=1.1;CM-VER=3.0; |
2020-6-9, 12:30:18 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:a5:11:78:af:fc;CMTS-MAC=00:56:2b:77:89:5d;CM-QOS=1.1;CM-VER=3.0; |
2020-6-9, 12:29:59 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:a5:11:78:af:fc;CMTS-MAC=00:56:2b:77:89:5d;CM-QOS=1.1;CM-VER=3.0; |
2020-6-9, 12:29:59 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:a5:11:78:af:fc;CMTS-MAC=00:56:2b:77:89:5d;CM-QOS=1.1;CM-VER=3.0; |
2020-6-9, 12:29:49 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:a5:11:78:af:fc;CMTS-MAC=00:56:2b:77:89:5d;CM-QOS=1.1;CM-VER=3.0; |
2020-6-9, 12:29:45 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=bc:a5:11:78:af:fc;CMTS-MAC=00:56:2b:77:89:5d;CM-QOS=1.1;CM-VER=3.0; |
2020-6-9, 12:29:30 | Warning (5) | Dynamic Range Window violation |
2020-6-9, 12:29:26 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=bc:a5:11:78:af:fc;CMTS-MAC=00:56:2b:77:89:5d;CM-QOS=1.1;CM-VER=3.0; |
2020-6-9, 12:29:11 | Warning (5) | Dynamic Range Window violation |
2020-6-9, 12:29:09 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:a5:11:78:af:fc;CMTS-MAC=00:56:2b:77:89:5d;CM-QOS=1.1;CM-VER=3.0; |
2020-6-9, 12:25:09 | Warning (5) | Dynamic Range Window violation |
2020-6-9, 12:24:58 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:a5:11:78:af:fc;CMTS-MAC=00:56:2b:77:89:5d;CM-QOS=1.1;CM-VER=3.0; |
2020-6-9, 12:24:49 | Warning (5) | Dynamic Range Window violation |
2020-6-9, 12:24:38 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:a5:11:78:af:fc;CMTS-MAC=00:56:2b:77:89:5d;CM-QOS=1.1;CM-VER=3.0; |
2020-6-9, 12:24:26 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=bc:a5:11:78:af:fc;CMTS-MAC=00:56:2b:77:89:5d;CM-QOS=1.1;CM-VER=3.0; |
2020-6-9, 12:24:09 | Warning (5) | Dynamic Range Window violation |
2020-6-9, 12:24:06 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=bc:a5:11:78:af:fc;CMTS-MAC=00:56:2b:77:89:5d;CM-QOS=1.1;CM-VER=3.0; |
2020-6-9, 12:22:29 | Warning (5) | Dynamic Range Window violation |
2020-6-9, 12:21:22 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:a5:11:78:af:fc;CMTS-MAC=00:56:2b:77:89:5d;CM-QOS=1.1;CM-VER=3.0; |
2020-6-9, 12:20:30 | Notice (6) | Honoring MDD; IP provisioning mode = IPv6 |
2020-6-9, 12:20:18 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=bc:a5:11:78:af:fc;CMTS-MAC=00:56:2b:77:89:5d;CM-QOS=1.0;CM-VER=3.0; |
2020-6-9, 12:20:17 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:a5:11:78:af:fc;CMTS-MAC=00:56:2b:77:89:5d;CM-QOS=1.0;CM-VER=3.0; |
2020-6-9, 12:19:29 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:a5:11:78:af:fc;CMTS-MAC=00:56:2b:77:89:5d;CM-QOS=1.0;CM-VER=3.0; |
2020-6-9, 12:19:21 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=bc:a5:11:78:af:fc;CMTS-MAC=00:56:2b:77:89:5d;CM-QOS=1.0;CM-VER=3.0; |
2020-6-9, 12:17:56 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:a5:11:78:af:fc;CMTS-MAC=00:56:2b:77:89:5d;CM-QOS=1.1;CM-VER=3.0; |
2020-6-9, 12:17:23 | Critical (3) | Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=bc:a5:11:78:af:fc;CMTS-MAC=00:56:2b:77:89:5d;CM-QOS=1.1;CM-VER=3.0; |
2020-6-9, 12:17:08 | Warning (5) | Dynamic Range Window violation |
2020-6-9, 12:16:05 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:a5:11:78:af:fc;CMTS-MAC=00:56:2b:77:89:5d;CM-QOS=1.1;CM-VER=3.0; |
2020-6-9, 12:09:47 | Notice (6) | Honoring MDD; IP provisioning mode = IPv6 |
2020-6-9, 12:09:33 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=bc:a5:11:78:af:fc;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
2020-6-9, 12:09:32 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:a5:11:78:af:fc;CMTS-MAC=00:56:2b:77:89:5d;CM-QOS=1.0;CM-VER=3.0; |
2020-6-9, 12:08:44 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:a5:11:78:af:fc;CMTS-MAC=00:56:2b:77:89:5d;CM-QOS=1.0;CM-VER=3.0; |
2020-6-9, 12:08:38 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=bc:a5:11:78:af:fc;CMTS-MAC=00:56:2b:77:89:5d;CM-QOS=1.0;CM-VER=3.0; |
2020-6-9, 12:06:25 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:a5:11:78:af:fc;CMTS-MAC=00:56:2b:77:89:5d;CM-QOS=1.1;CM-VER=3.0; |
2020-6-9, 12:06:12 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:a5:11:78:af:fc;CMTS-MAC=00:56:2b:77:89:5d;CM-QOS=1.1;CM-VER=3.0; |
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: CM500 T3 and T4 Errors
t3 t4 errors tend to be line issues. Do you have a screen snip of the cable connections page? get all the info off the upstream/downstream
• What is the difference between WiFi 6 and WiFi 7?
• Yes! WiFi 7 is backwards compatible with other Wifi devices? Learn more