× Introducing the Orbi 970 Series Mesh System with WiFi 7 technology. For more information visit the NETGEAR Press Room.
Orbi WiFi 7 RBE973
Reply

CM500 T3 and T4 Errors

iclimbonthings
Aspirant

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? 

Model: CM500|16x4 DOCSIS 3.0 Cable Modem
Message 1 of 3
iclimbonthings
Aspirant

Re: CM500 T3 and T4 Errors

Here is my event log

 

2020-6-9, 12:45:36Critical (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:58Notice (6)Honoring MDD; IP provisioning mode = IPv6
2020-6-9, 12:32:43Critical (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:31Critical (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:19Critical (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:18Critical (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:59Critical (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:59Critical (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:49Critical (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:45Critical (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:30Warning (5)Dynamic Range Window violation
2020-6-9, 12:29:26Critical (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:11Warning (5)Dynamic Range Window violation
2020-6-9, 12:29:09Critical (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:09Warning (5)Dynamic Range Window violation
2020-6-9, 12:24:58Critical (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:49Warning (5)Dynamic Range Window violation
2020-6-9, 12:24:38Critical (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:26Critical (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:09Warning (5)Dynamic Range Window violation
2020-6-9, 12:24:06Critical (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:29Warning (5)Dynamic Range Window violation
2020-6-9, 12:21:22Critical (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:30Notice (6)Honoring MDD; IP provisioning mode = IPv6
2020-6-9, 12:20:18Critical (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:17Critical (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:29Critical (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:21Critical (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:56Critical (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:23Critical (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:08Warning (5)Dynamic Range Window violation
2020-6-9, 12:16:05Critical (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:47Notice (6)Honoring MDD; IP provisioning mode = IPv6
2020-6-9, 12:09:33Critical (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:32Critical (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:44Critical (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:38Critical (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:25Critical (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:12Critical (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;
Message 2 of 3
plemans
Guru

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 

Message 3 of 3
Discussion stats
  • 2 replies
  • 549 views
  • 0 kudos
  • 2 in conversation
Announcements

Orbi WiFi 7