NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

Ric2L's avatar
Ric2L
Aspirant
Feb 17, 2016
Solved

CM600 Randomly Dropping Internet Connection

Yesterday I replaced my old Motorola Surfboard 6141 modem with a Netgear CM600 modem, and activated it with Comcast.  Ever since I have been getting random drops of my internet connection.  I logged into the modem to check the event log and have 31 critical events.  I'm also using an Asus RT-N66U wireless router, that has been in use for a couple years with no issues with my motorola surfboard 6141 modem.

 

Hardware version: 1.01B

Firmware version:  V1.01.05

 

Hoping someone can help figure this out.

 

Event Log:

2016-02-17, 09:39:56Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:8c:96:b8;CMTS-MAC=00:01:5c:73:b8:5b;CM-QOS=1.1;CM-VER=3.0;
2016-02-17, 03:38:01Notice (6)Honoring MDD; IP provisioning mode = IPv6
2016-02-17, 03:37:58Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:8c:96:b8;CMTS-MAC=00:01:5c:73:b8:5b;CM-QOS=1.0;CM-VER=3.0;
2016-02-17, 03:37:45Critical (3)No Ranging Response received - T3 time-out;CM-MAC=dc:ef:09:8c:96:b8;CMTS-MAC=00:01:5c:73:b8:5b;CM-QOS=1.0;CM-VER=3.0;
2016-02-17, 03:37:21Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=dc:ef:09:8c:96:b8;CMTS-MAC=00:01:5c:73:b8:5b;CM-QOS=1.1;CM-VER=3.0;
2016-02-17, 01:53:36Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:8c:96:b8;CMTS-MAC=00:01:5c:73:b8:5b;CM-QOS=1.1;CM-VER=3.0;
2016-02-16, 20:03:04Notice (6)Honoring MDD; IP provisioning mode = IPv6
2016-02-16, 20:02:54Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=dc:ef:09:8c:96:b8;CMTS-MAC=00:01:5c:73:b8:5b;CM-QOS=1.1;CM-VER=3.0;
2016-02-16, 19:58:33Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:8c:96:b8;CMTS-MAC=00:01:5c:73:b8:5b;CM-QOS=1.1;CM-VER=3.0;
2016-02-16, 19:58:33Critical (3)Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=dc:ef:09:8c:96:b8;CMTS-MAC=00:01:5c:73:b8:5b;CM-QOS=1.1;CM-VER=3.0;
2016-02-16, 19:58:33Critical (3)16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=dc:ef:09:8c:96:b8;CMTS-MAC=00:01:5c:73:b8:5b;CM-QOS=1.1;CM-VER=3.0;
2016-02-16, 19:58:33Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:8c:96:b8;CMTS-MAC=00:01:5c:73:b8:5b;CM-QOS=1.1;CM-VER=3.0;
2016-02-16, 12:07:18Notice (6)Honoring MDD; IP provisioning mode = IPv6
2016-02-16, 12:06:29Critical (3)No Ranging Response received - T3 time-out;CM-MAC=dc:ef:09:8c:96:b8;CMTS-MAC=00:01:5c:73:b8:5b;CM-QOS=1.0;CM-VER=3.0;
2016-02-16, 12:04:30Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=dc:ef:09:8c:96:b8;CMTS-MAC=00:01:5c:73:b8:5b;CM-QOS=1.1;CM-VER=3.0;
2016-02-16, 12:00:10Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:8c:96:b8;CMTS-MAC=00:01:5c:73:b8:5b;CM-QOS=1.1;CM-VER=3.0;
2016-02-16, 11:59:56Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:8c:96:b8;CMTS-MAC=00:01:5c:73:b8:5b;CM-QOS=1.1;CM-VER=3.0;
2016-02-16, 11:59:56Critical (3)Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=dc:ef:09:8c:96:b8;CMTS-MAC=00:01:5c:73:b8:5b;CM-QOS=1.1;CM-VER=3.0;
2016-02-16, 11:59:56Critical (3)16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=dc:ef:09:8c:96:b8;CMTS-MAC=00:01:5c:73:b8:5b;CM-QOS=1.1;CM-VER=3.0;
2016-02-16, 09:41:56Notice (6)Honoring MDD; IP provisioning mode = IPv6
2016-02-16, 09:41:37Critical (3)No Ranging Response received - T3 time-out;CM-MAC=dc:ef:09:8c:96:b8;CMTS-MAC=00:01:5c:73:b8:5b;CM-QOS=1.0;CM-VER=3.0;
2016-02-16, 09:39:38Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=dc:ef:09:8c:96:b8;CMTS-MAC=00:01:5c:73:b8:5b;CM-QOS=1.1;CM-VER=3.0;
2016-02-16, 09:35:18Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:8c:96:b8;CMTS-MAC=00:01:5c:73:b8:5b;CM-QOS=1.1;CM-VER=3.0;
2016-02-16, 09:35:03Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:8c:96:b8;CMTS-MAC=00:01:5c:73:b8:5b;CM-QOS=1.1;CM-VER=3.0;
2016-02-16, 09:35:03Critical (3)Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=dc:ef:09:8c:96:b8;CMTS-MAC=00:01:5c:73:b8:5b;CM-QOS=1.1;CM-VER=3.0;
2016-02-16, 09:35:03Critical (3)16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=dc:ef:09:8c:96:b8;CMTS-MAC=00:01:5c:73:b8:5b;CM-QOS=1.1;CM-VER=3.0;
2016-02-16, 08:00:44Notice (6)Honoring MDD; IP provisioning mode = IPv6
2016-02-16, 08:00:14Critical (3)No Ranging Response received - T3 time-out;CM-MAC=dc:ef:09:8c:96:b8;CMTS-MAC=00:01:5c:73:b8:5b;CM-QOS=1.0;CM-VER=3.0;
2016-02-16, 07:59:47Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=dc:ef:09:8c:96:b8;CMTS-MAC=00:01:5c:73:b8:5b;CM-QOS=1.1;CM-VER=3.0;
2016-02-16, 07:55:27Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:8c:96:b8;CMTS-MAC=00:01:5c:73:b8:5b;CM-QOS=1.1;CM-VER=3.0;
2016-02-16, 05:48:05Notice (6)Honoring MDD; IP provisioning mode = IPv6
2016-02-16, 05:47:50Critical (3)No Ranging Response received - T3 time-out;CM-MAC=dc:ef:09:8c:96:b8;CMTS-MAC=00:01:5c:73:b8:5b;CM-QOS=1.0;CM-VER=3.0;
2016-02-16, 05:44:58Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=dc:ef:09:8c:96:b8;CMTS-MAC=00:01:5c:73:b8:5b;CM-QOS=1.1;CM-VER=3.0;
2016-02-16, 05:40:38Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:8c:96:b8;CMTS-MAC=00:01:5c:73:b8:5b;CM-QOS=1.1;CM-VER=3.0;
2016-02-15, 22:52:06Critical (3)No Ranging Response received - T3 time-out;CM-MAC=dc:ef:09:8c:96:b8;CMTS-MAC=00:01:5c:73:b8:5b;CM-QOS=1.0;CM-VER=3.0;
2016-02-15, 22:51:46Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=dc:ef:09:8c:96:b8;CMTS-MAC=00:01:5c:73:b8:5b;CM-QOS=1.1;CM-VER=3.0;
2016-02-15, 22:47:26Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=dc:ef:09:8c:96:b8;CMTS-MAC=00:01:5c:73:b8:5b;CM-QOS=1.1;CM-VER=3.0;
2016-02-15, 21:41:33Critical (3)No Ranging Response received - T3 time-out;CM-MAC=dc:ef:09:8c:96:b8;CMTS-MAC=00:01:5c:73:b8:5b;CM-QOS=1.0;CM-VER=3.0;
2016-02-15, 21:38:38Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=dc:ef:09:8c:96:b8;CMTS-MAC=00:01:5c:73:b8:5b;CM-QOS=1.1;CM-VER=3.0;
Time Not EstablishedNotice (6)Honoring MDD; IP provisioning mode = IPv6
Troubleshooting
  • Ric2L's avatar
    Ric2L
    Feb 21, 2016

    Comcast tech found a bad splitter and cable, replaced them and all is good.

3 Replies

    • Ric2L's avatar
      Ric2L
      Aspirant
      Feb 19, 2016

      Thanks for the reply Darren

       

      I contacted comcast, they checked out everything they could over the phone and are sending out a tech tomorrow morning.  Hopefully he can solve the issues.  I will update with his findings tomorrow afternoon.

       

      Rick

      • Ric2L's avatar
        Ric2L
        Aspirant
        Feb 21, 2016

        Comcast tech found a bad splitter and cable, replaced them and all is good.