Forum Discussion

CanoePaddler's avatar
CanoePaddler
New Contributor
7 years ago

T3/T4 Timeout

Long story short, we have been having Internet issues this past week. Looked into it, and looks like T3 and T4 timeouts. I called customer support and they are sending a tech (contractor) out this Tuesday. I've been reading on this forum how this issue wasn't fixed until after multiple tech visits. Now, I'm not saying this will happen, but can't help but think that. I am wondering what I need to tell the tech when they come out? I've already tried a new modem. We don't use splitters. We've had no issues in the 6 years we've have Cox. My wife works from home remotely and Internet is pretty much a necessity.

Pasting the log from the modem. This isn't happening just a few times a day, it is multiple times an hour. Any help is appreciated! Thanks in advance!

 Log  
  
 Time   Priority   Description 
 Sun Jul 01 17:54:27 2018    Critical (3)   Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:40:36:50:30:05;CMTS-MAC=00:42:5a:1d:4d:cf;CM-QOS=1.1;CM-VER=3.0; 
 Sun Jul 01 17:54:27 2018    Critical (3)   16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=00:40:36:50:30:05;CMTS-MAC=00:42:5a:1d:4d:cf;CM-QOS=1.1;CM-VER=3.0; 
 Sun Jul 01 17:56:37 2018    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:50:30:05;CMTS-MAC=00:42:5a:1d:4d:cf;CM-QOS=1.1;CM-VER=3.0; 
 Sun Jul 01 17:59:03 2018    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:50:30:05;CMTS-MAC=00:42:5a:1d:4d:cf;CM-QOS=1.1;CM-VER=3.0; 
 Sun Jul 01 18:01:13 2018    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:50:30:05;CMTS-MAC=00:42:5a:1d:4d:cf;CM-QOS=1.1;CM-VER=3.0; 
 Sun Jul 01 18:07:57 2018    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:50:30:05;CMTS-MAC=00:42:5a:1d:4d:cf;CM-QOS=1.1;CM-VER=3.0; 
 Sun Jul 01 18:12:17 2018    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:50:30:05;CMTS-MAC=00:42:5a:1d:4d:cf;CM-QOS=1.1;CM-VER=3.0; 
 Sun Jul 01 18:13:08 2018    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:50:30:05;CMTS-MAC=00:42:5a:1d:4d:cf;CM-QOS=1.1;CM-VER=3.0; 
 Sun Jul 01 18:15:18 2018    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:50:30:05;CMTS-MAC=00:42:5a:1d:4d:cf;CM-QOS=1.1;CM-VER=3.0; 
 Sun Jul 01 18:16:29 2018    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:50:30:05;CMTS-MAC=00:42:5a:1d:4d:cf;CM-QOS=1.1;CM-VER=3.0; 
 Sun Jul 01 18:29:29 2018    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:50:30:05;CMTS-MAC=00:42:5a:1d:4d:cf;CM-QOS=1.1;CM-VER=3.0; 
 Sun Jul 01 18:30:34 2018    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:50:30:05;CMTS-MAC=00:42:5a:1d:4d:cf;CM-QOS=1.1;CM-VER=3.0; 
 Sun Jul 01 18:32:44 2018    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:50:30:05;CMTS-MAC=00:42:5a:1d:4d:cf;CM-QOS=1.1;CM-VER=3.0; 
 Sun Jul 01 18:34:03 2018    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:50:30:05;CMTS-MAC=00:42:5a:1d:4d:cf;CM-QOS=1.1;CM-VER=3.0; 
 Sun Jul 01 18:36:13 2018    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:50:30:05;CMTS-MAC=00:42:5a:1d:4d:cf;CM-QOS=1.1;CM-VER=3.0; 
 Sun Jul 01 18:37:09 2018    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:50:30:05;CMTS-MAC=00:42:5a:1d:4d:cf;CM-QOS=1.1;CM-VER=3.0; 
 Sun Jul 01 18:39:19 2018    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:50:30:05;CMTS-MAC=00:42:5a:1d:4d:cf;CM-QOS=1.1;CM-VER=3.0; 
 Sun Jul 01 18:43:19 2018    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:50:30:05;CMTS-MAC=00:42:5a:1d:4d:cf;CM-QOS=1.1;CM-VER=3.0; 
 Sun Jul 01 18:43:19 2018    Critical (3)   Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:40:36:50:30:05;CMTS-MAC=00:42:5a:1d:4d:cf;CM-QOS=1.1;CM-VER=3.0; 
 Sun Jul 01 18:43:19 2018    Critical (3)   16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=00:40:36:50:30:05;CMTS-MAC=00:42:5a:1d:4d:cf;CM-QOS=1.1;CM-VER=3.0; 
 Sun Jul 01 18:45:12 2018    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:50:30:05;CMTS-MAC=00:42:5a:1d:4d:cf;CM-QOS=1.1;CM-VER=3.0; 
 Sun Jul 01 18:49:32 2018    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:50:30:05;CMTS-MAC=00:42:5a:1d:4d:cf;CM-QOS=1.1;CM-VER=3.0; 
 Sun Jul 01 18:49:46 2018    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:50:30:05;CMTS-MAC=00:42:5a:1d:4d:cf;CM-QOS=1.1;CM-VER=3.0; 
 Sun Jul 01 18:50:51 2018    Critical (3)   Resetting the cable modem due to docsDevResetNow 
 Time Not Established   Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40:36:50:30:05;CMTS-MAC=00:42:5a:1d:4d:cf;CM-QOS=1.0;CM-VER=3.0; 
 Time Not Established   Notice (6)   Honoring MDD; IP provisioning mode = IPv4 
 Sun Jul 01 21:51:34 2018    Warning (5)   DHCP WARNING - Non-critical field invalid in response ;CM-MAC=00:40:36:50:30:05;CMTS-MAC=00:42:5a:1d:4d:cf;CM-QOS=1.1;CM-VER=3.0; 
 Sun Jul 01 21:51:34 2018    Notice (6)   TLV-11 - unrecognized OID;CM-MAC=00:40:36:50:30:05;CMTS-MAC=00:42:5a:1d:4d:cf;CM-QOS=1.1;CM-VER=3.0; 
 Sun Jul 01 21:52:30 2018    Warning (5)   Unicast DSID PSN startup error 
 Sun Jul 01 22:09:52 2018    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:50:30:05;CMTS-MAC=00:42:5a:1d:4d:cf;CM-QOS=1.1;CM-VER=3.0; 
 Sun Jul 01 22:10:34 2018    Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:50:30:05;CMTS-MAC=00:42:5a:1d:4d:cf;CM-QOS=1.1;CM-VER=3.0; 
 Sun Jul 01 22:22:37 2018    Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:50:30:05;CMTS-MAC=00:42:5a:1d:4d:cf;CM-QOS=1.1;CM-VER=3.0; 
  • Hi CanoePaddler,

    I am sorry to learn of your chronic service issues. I am glad that we have scheduled a technician to investigate your issue. Please send us your service address to cox.help@cox.com so that I can check the work order to ensure this information is added.

    Latitia

    Cox Support Forums Moderator
  • The tech came out, checked around for basic stuff, went in our garage and then outside to look around. Basically, we had an outdated splitter in the garage that he replaced and everything is as good as new! Just wanted to let you both know. Also, thank you for the responses and also adding it to the work order LatitiaS. That was one of the first things he mentioned was the modem errors. 

    • JonathanJ's avatar
      JonathanJ
      Former Moderator
      @CanoePaddler

      Glad it's been resolved please let us know if you have further issues.

      Cox support moderator