Forum Discussion

rjpeterson's avatar
rjpeterson
New Contributor

Arris SBG6580-2 Router briefly but frequently drops internet connection, wifi signal stays strong throughout

I recently set up a new Arris SBG6580-2 router/modem combo.  At least once every couple minutes it will drop the internet connection for 5-10 seconds and then reconnect. The wifi signal stays strong even while the internet connection has dropped out. I have tested my devices on other wifi networks and this only happens when connected to my router. My router's event log shows these errors repeatedly:

Thu Sep 28 23:55:29 2017 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:64:4b:9a:da:7d;CMTS-MAC=a4:4c:11:8a:dc:79;CM-QOS=1.1;CM-VER=3.0;
Thu Sep 28 23:49:44 2017 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:64:4b:9a:da:7d;CMTS-MAC=a4:4c:11:8a:dc:79;CM-QOS=1.1;CM-VER=3.0;
Thu Sep 28 23:49:02 2017 Notice (6) TLV-11 - unrecognized OID;CM-MAC=bc:64:4b:9a:da:7d;CMTS-MAC=a4:4c:11:8a:dc:79;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=bc:64:4b:9a:da:7d;CMTS-MAC=a4:4c:11:8a:dc:79;CM-QOS=1.0;CM-VER=3.0;

I have tried several different channels.

My current shows "acceptable" interference levels.

My security is set to WPA2-PSK (AES).

I have disabled WPS.

I have had Cox technicians come out several times. They have supposedly replaced the cable lines running to the house, but I have seen no change in the problem.

Thanks for your help.

8 Replies

Sort By
Most LikedOldestNewest
Replies have been turned off for this discussion
  • d3x0r's avatar
    d3x0r
    New Contributor

    I confirm that I have the same issues.  They are unable to identify that there is an issue because it's intermittent.  I had same behavior on Motorola modem before, but it didn't show any meaningful error messages in its log.

    I've been collecting these for some time now... since the log only goes back a few days.

    9-28-2017, 6:1:46 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    9-28-2017, 6:1:37 Warning(5) "MDD message timeout;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    9-28-2017, 6:1:37 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    9-28-2017, 6:1:31 Warning(5) "MDD message timeout;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    9-28-2017, 6:1:31 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    9-27-2017, 12:3:48 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    9-27-2017, 9:27:35 Warning(5) "Dynamic Range Window violation"
    9-27-2017, 8:49:52 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    9-26-2017, 21:34:30 Warning(5) "Dynamic Range Window violation"
    9-26-2017, 18:55:5 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    9-26-2017, 18:46:52 Warning(5) "Dynamic Range Window violation"
    9-26-2017, 18:37:8 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    9-26-2017, 5:28:38 Notice(6) "TLV-11 - unrecognized OID;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    9-21-2017, 19:34:6 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    9-21-2017, 18:57:11 Critical(3) "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    9-21-2017, 18:57:8 Critical(3) "No Ranging Response received - T3 time-out;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    9-21-2017, 18:56:56 Critical(3) "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    9-21-2017, 18:56:56 Critical(3) "No Ranging Response received - T3 time-out;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    9-21-2017, 18:56:50 Critical(3) "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    9-21-2017, 18:55:11 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    9-21-2017, 18:29:26 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    9-21-2017, 8:44:17 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    9-19-2017, 22:46:13 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    9-19-2017, 19:1:28 Critical(3) "SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"

    9-19-2017, 17:54:28 Critical(3) "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    9-19-2017, 17:54:26 Critical(3) "No Ranging Response received - T3 time-out;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    9-19-2017, 17:54:22 Critical(3) "Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    9-19-2017, 17:54:22 Critical(3) "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    9-19-2017, 17:52:28 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    9-19-2017, 17:48:24 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    9-19-2017, 17:18:31 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    9-18-2017, 8:58:40 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    9-18-2017, 8:45:14 Critical(3) "16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    9-18-2017, 8:45:14 Critical(3) "Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    9-18-2017, 8:45:14 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=5c:e3:0e:73:b
    9-12-2017, 18:7:30 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"

    Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    9-8-2017, 18:12:26 Critical(3) "Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    9-8-2017, 18:12:25 Critical(3) "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    9-8-2017, 18:12:16 Critical(3) "Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    9-8-2017, 18:12:16 Critical(3) "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    9-8-2017, 18:10:30 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    9-8-2017, 17:42:51 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    9-8-2017, 15:57:10 Critical(3) "SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    1-1-1970, 0:0:33 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
    1-1-1970, 0:0:39 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    1-1-1970, 0:0:33 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
    9-8-2017, 14:14:9 Critical(3) "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    9-8-2017, 14:14:9 Critical(3) "No Ranging Response received - T3 time-out;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    9-8-2017, 14:14:8 Critical(3) "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    9-8-2017, 14:13:53 Critical(3) "Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    9-8-2017, 14:13:53 Critical(3) "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    9-8-2017, 14:13:48 Critical(3) "Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    9-8-2017, 14:13:48 Critical(3) "Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    9-8-2017, 14:12:9 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"


    8-26-2017, 17:38:57 Warning(5) "Dynamic Range Window violation"
    8-26-2017, 17:38:55 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"

    8-25-2017, 17:54:50 Critical(3) "SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    8-25-2017, 17:53:39 Notice(6) "TLV-11 - unrecognized OID;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    1-1-1970, 0:0:49 Warning(5) "DHCP WARNING - Non-critical field invalid in response ;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    1-1-1970, 0:0:47 Notice(6) "Honoring MDD; IP provisioning mode = IPv4"
    1-1-1970, 0:0:39 Critical(3) "No Ranging Response received - T3 time-out;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    1-1-1970, 0:0:33 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
    8-25-2017, 17:52:29 Critical(3) "Resetting the cable modem due to docsDevResetNow"
    8-25-2017, 17:51:45 Critical(3) "SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    1-1-1970, 0:0:33 Critical(3) "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"

    8-25-2017 ticket numbr 5120273

    8-23-2017, 0:26:41 Error(4) "DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    8-18-2017, 17:53:3 Warning(5) "Dynamic Range Window violation"
    8-18-2017, 17:51:35 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    8-17-2017, 17:57:6 Warning(5) "Dynamic Range Window violation"
    8-16-2017, 0:26:41 Error(4) "DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    8-5-2017, 19:3:23 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    8-5-2017, 19:3:23 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    8-5-2017, 19:3:22 Warning(5) "MDD message timeout;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    8-5-2017, 19:3:14 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    8-5-2017, 19:3:12 Warning(5) "MDD message timeout;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    8-5-2017, 19:3:6 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    8-5-2017, 19:3:2 Warning(5) "MDD message timeout;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"
    8-5-2017, 19:2:55 Warning(5) "Dynamic Range Window violation"
    8-5-2017, 19:2:54 Critical(3) "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=5c:e3:0e:73:b5:e9;CMTS-MAC=50:57:a8:89:27:c4;CM-QOS=1.1;CM-VER=3.1;"

  • d3x0r's avatar
    d3x0r
    New Contributor

    Oh oops, my model isn't that ... it's the SB8200; still have the same intermittent issues.  

  • DannyS's avatar
    DannyS
    Moderator

    The purpose of the Cox Internet Forum is to allow customers to discuss technical topics related to residential Cox Cable, Telephone and High Speed Internet services with other customers. This appears as if you may need for someone to look into your account personally.  We can definitely be able to assist you with this.  Please reach us on Twitter at @CoxHelp, visit us on Facebook, or email by at cox.help@cox.com. Provide us the name on the account with the full service address with a link to this thread so we can get started.

  • Skyguy's avatar
    Skyguy
    New Contributor

    Im having these same issues! Ive had 5 techs out here and they keep giving me the run around. This is my log. 

    10/3/2017 8:54 84000700 5 RCS Partial Service;CM-MAC=78:23:ae:21:a6:9d;CMTS-MAC=00:38:df:9a:5a:41;CM-QOS=1.1;CM-VER=3.0;
    10/3/2017 8:54 84000500 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=78:23:ae:21:a6:9d;CMTS-MAC=00:38:df:9a:5a:41;CM-QOS=1.1;CM-VER=3.0;
    10/3/2017 8:54 84020200 5 Lost MDD Timeout;CM-MAC=78:23:ae:21:a6:9d;CMTS-MAC=00:38:df:9a:5a:41;CM-QOS=1.1;CM-VER=3.0;
    10/3/2017 8:54 84000700 5 RCS Partial Service;CM-MAC=78:23:ae:21:a6:9d;CMTS-MAC=00:38:df:9a:5a:41;CM-QOS=1.1;CM-VER=3.0;
    10/3/2017 8:56 84000500 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=78:23:ae:21:a6:9d;CMTS-MAC=00:38:df:9a:5a:41;CM-QOS=1.1;CM-VER=3.0;
    10/3/2017 8:56 84000700 5 RCS Partial Service;CM-MAC=78:23:ae:21:a6:9d;CMTS-MAC=00:38:df:9a:5a:41;CM-QOS=1.1;CM-VER=3.0;
    10/3/2017 8:56 84000500 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=78:23:ae:21:a6:9d;CMTS-MAC=00:38:df:9a:5a:41;CM-QOS=1.1;CM-VER=3.0;
    10/3/2017 8:56 84020200 5 Lost MDD Timeout;CM-MAC=78:23:ae:21:a6:9d;CMTS-MAC=00:38:df:9a:5a:41;CM-QOS=1.1;CM-VER=3.0;
    10/3/2017 8:57 82000400 3 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=78:23:ae:21:a6:9d;CMTS-MAC=00:38:df:9a:5a:41;CM-QOS=1.1;CM-VER=3.0;
    10/3/2017 9:06 73040100 6 TLV-11 - unrecognized OID;CM-MAC=78:23:ae:21:a6:9d;CMTS-MAC=00:38:df:9a:5a:41;CM-QOS=1.1;CM-VER=3.0;
    10/3/2017 9:08 84000700 5 RCS Partial Service;CM-MAC=78:23:ae:21:a6:9d;CMTS-MAC=00:38:df:9a:5a:41;CM-QOS=1.1;CM-VER=3.0;
    10/3/2017 9:08 84000500 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=78:23:ae:21:a6:9d;CMTS-MAC=00:38:df:9a:5a:41;CM-QOS=1.1;CM-VER=3.0;
    10/3/2017 9:08 84000700 5 RCS Partial Service;CM-MAC=78:23:ae:21:a6:9d;CMTS-MAC=00:38:df:9a:5a:41;CM-QOS=1.1;CM-VER=3.0;
    10/3/2017 9:08 84000500 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=78:23:ae:21:a6:9d;CMTS-MAC=00:38:df:9a:5a:41;CM-QOS=1.1;CM-VER=3.0;
    10/3/2017 9:08 84020200 5 Lost MDD Timeout;CM-MAC=78:23:ae:21:a6:9d;CMTS-MAC=00:38:df:9a:5a:41;CM-QOS=1.1;CM-VER=3.0;
    10/3/2017 9:26 73040100 6 TLV-11 - unrecognized OID;CM-MAC=78:23:ae:21:a6:9d;CMTS-MAC=00:38:df:9a:5a:41;CM-QOS=1.1;CM-VER=3.0;
    1/1/1970 0:01 82000200 3 No Ranging Response received - T3 time-out;CM-MAC=78:23:ae:21:a6:9d;CMTS-MAC=00:38:df:9a:5a:41;CM-QOS=1.1;CM-VER=3.0;
    10/3/2017 9:55 73040100 6 TLV-11 - unrecognized OID;CM-MAC=78:23:ae:21:a6:9d;CMTS-MAC=00:38:df:9a:5a:41;CM-QOS=1.1;CM-VER=3.0;
    10/3/2017 11:16 82000200 3 No Ranging Response received - T3 time-out;CM-MAC=78:23:ae:21:a6:9d;CMTS-MAC=00:38:df:9a:5a:41;CM-QOS=1.1;CM-VER=3.0;
    10/3/2017 23:51 73040100 6 TLV-11 - unrecognized OID;CM-MAC=78:23:ae:21:a6:9d;CMTS-MAC=00:38:df:9a:5a:41;CM-QOS=1.1;CM-VER=3.0;

  • Skyguy's avatar
    Skyguy
    New Contributor

    If anyone gets this fixed please tell me so i can show the techs next time they come. Also to any moderators please help me. 

  • Skyguy's avatar
    Skyguy
    New Contributor

    Ive had this same issue. What should I do? Ive had 5 techs out at my house and no believes me that this is happening. please help me. 

  • bryan9's avatar
    bryan9
    New Contributor

    I had exactly the same problem with my Arris SBG6900-AC -- T3 and T4 errors, and in my case, requiring a modem reset before I could access the Internet.  The techs came out, to no avail. I finally decided to get a new modem -- a Netgear CM700 -- and lo and behold, all the problems disappeared.