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

Forum Discussion

pix88's avatar
pix88
Aspirant
Sep 29, 2020
Solved

Intermittent Drops CM500

Hi, working at home and I basically take calls that come in. My modem keeps losing connection, upstream light keeps blinking green. Have already tried things like power cycle, and talking to my ISP, who said the signal is good on their side. This happened all day duing my shift. I use Azure VPN to connection remotely to work. 

I read artical on the Netgear site that you can check the downstream and upstream power? But I'm just having trouble understanding what I'm looking at. Here is chart. 

Downstream Bonded Channels
ChannelLock StatusModulationChannel IDFrequencyPowerSNRCorrectablesUncorrectables
1LockedQAM25637381000000 Hz5.3 dBmV41.4 dB50218
2LockedQAM25633357000000 Hz5.4 dBmV40.8 dB45167
3LockedQAM25634363000000 Hz5.2 dBmV41.2 dB48155
4LockedQAM25635369000000 Hz5 dBmV41.2 dB40103
5LockedQAM25636375000000 Hz5.1 dBmV41.3 dB53162
6LockedQAM25638387000000 Hz5.6 dBmV41.5 dB46153
7LockedQAM25639393000000 Hz5.6 dBmV41.5 dB39153
8LockedQAM25640399000000 Hz5.7 dBmV41.5 dB38116
9LockedQAM25641405000000 Hz5.7 dBmV41.4 dB34121
10LockedQAM25642411000000 Hz5.7 dBmV41.7 dB29119
11LockedQAM25643417000000 Hz5.7 dBmV41.4 dB43244
12LockedQAM25644423000000 Hz5.8 dBmV41.8 dB29147
13LockedQAM25645429000000 Hz6.1 dBmV42 dB43197
14LockedQAM25646435000000 Hz6.3 dBmV42.1 dB37151
15LockedQAM25647441000000 Hz6.5 dBmV42.3 dB39159
16LockedQAM25648447000000 Hz6.7 dBmV42.5 dB38213
 
Upstream Bonded Channels
ChannelLock StatusUS Channel TypeChannel IDSymbol RateFrequencyPower
1LockedATDMA25120 Ksym/sec23900000 Hz42.6 dBmV
2LockedATDMA15120 Ksym/sec17400000 Hz43.9 dBmV
3LockedATDMA35120 Ksym/sec30300000 Hz41.9 dBmV
4LockedATDMA45120 Ksym/sec36700000 Hz41.9 dBmV

 Hope I am not making a duplicate post.  I tried googling the numbers to see if they are good, but didnt really find much.  I'm wondering if I also need to replace coax? Thanks :)

  • plemans's avatar
    plemans
    Sep 30, 2020

    t3/4 errors tend to be line issues. The dynamic range window violations also tend to indicate line isssues as its the power levels going out of limits. 

    I'd contact your isp to check the line. 

4 Replies

  • plemans's avatar
    plemans
    Guru - Experienced User
    Sep 29, 2020

    do you also have your modem logs? 

    The cable connection pages just gives us a snap shot of when you load the page. Its used in conjunction with the logs. 

    If you do have any splitters, amplifiers, attenuators, I'd remove them. 

    • pix88's avatar
      pix88
      Aspirant
      Sep 29, 2020
       
       
       
       
      TimePriorityDescription
      2020-9-29, 21:59:59Warning (5)Dynamic Range Window violation
      2020-9-29, 21:59:28Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:a5:6e:6e:a1:60;CMTS-MAC=70:01:b5:cc:b5:61;CM-QOS=1.1;CM-VER=3.0;
      2020-9-29, 21:58:56Critical (3)Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:a5:6e:6e:a1:60;CMTS-MAC=70:01:b5:cc:b5:61;CM-QOS=1.1;CM-VER=3.0;
      2020-9-29, 21:58:39Warning (5)Dynamic Range Window violation
      2020-9-29, 21:57:48Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:a5:6e:6e:a1:60;CMTS-MAC=70:01:b5:cc:b5:61;CM-QOS=1.1;CM-VER=3.0;
      2020-9-29, 21:57:16Critical (3)Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:a5:6e:6e:a1:60;CMTS-MAC=70:01:b5:cc:b5:61;CM-QOS=1.1;CM-VER=3.0;
      2020-9-29, 21:56:48Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:a5:6e:6e:a1:60;CMTS-MAC=70:01:b5:cc:b5:61;CM-QOS=1.1;CM-VER=3.0;
      2020-9-29, 21:56:16Critical (3)Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:a5:6e:6e:a1:60;CMTS-MAC=70:01:b5:cc:b5:61;CM-QOS=1.1;CM-VER=3.0;
      2020-9-29, 21:55:28Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:a5:6e:6e:a1:60;CMTS-MAC=70:01:b5:cc:b5:61;CM-QOS=1.1;CM-VER=3.0;
      2020-9-29, 21:54:56Critical (3)Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:a5:6e:6e:a1:60;CMTS-MAC=70:01:b5:cc:b5:61;CM-QOS=1.1;CM-VER=3.0;
      2020-9-29, 21:54:29Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:a5:6e:6e:a1:60;CMTS-MAC=70:01:b5:cc:b5:61;CM-QOS=1.1;CM-VER=3.0;
      2020-9-29, 21:53:56Critical (3)Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:a5:6e:6e:a1:60;CMTS-MAC=70:01:b5:cc:b5:61;CM-QOS=1.1;CM-VER=3.0;
      2020-9-29, 21:53:09Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:a5:6e:6e:a1:60;CMTS-MAC=70:01:b5:cc:b5:61;CM-QOS=1.1;CM-VER=3.0;
      2020-9-29, 21:52:36Critical (3)Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:a5:6e:6e:a1:60;CMTS-MAC=70:01:b5:cc:b5:61;CM-QOS=1.1;CM-VER=3.0;
      2020-9-29, 21:52:09Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:a5:6e:6e:a1:60;CMTS-MAC=70:01:b5:cc:b5:61;CM-QOS=1.1;CM-VER=3.0;
      2020-9-29, 21:51:36Critical (3)Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:a5:6e:6e:a1:60;CMTS-MAC=70:01:b5:cc:b5:61;CM-QOS=1.1;CM-VER=3.0;
      2020-9-29, 21:51:21Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:a5:6e:6e:a1:60;CMTS-MAC=70:01:b5:cc:b5:61;CM-QOS=1.1;CM-VER=3.0;
      2020-9-29, 21:50:56Critical (3)Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:a5:6e:6e:a1:60;CMTS-MAC=70:01:b5:cc:b5:61;CM-QOS=1.1;CM-VER=3.0;
      2020-9-29, 21:50:41Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:a5:6e:6e:a1:60;CMTS-MAC=70:01:b5:cc:b5:61;CM-QOS=1.1;CM-VER=3.0;
      2020-9-29, 21:50:09Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:a5:6e:6e:a1:60;CMTS-MAC=70:01:b5:cc:b5:61;CM-QOS=1.1;CM-VER=3.0;
      2020-9-29, 21:49:47Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:a5:6e:6e:a1:60;CMTS-MAC=70:01:b5:cc:b5:61;CM-QOS=1.1;CM-VER=3.0;
      2020-9-29, 21:49:37Critical (3)Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:a5:6e:6e:a1:60;CMTS-MAC=70:01:b5:cc:b5:61;CM-QOS=1.1;CM-VER=3.0;
      2020-9-29, 21:49:09Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:a5:6e:6e:a1:60;CMTS-MAC=70:01:b5:cc:b5:61;CM-QOS=1.1;CM-VER=3.0;
      2020-9-29, 21:48:37Critical (3)Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:a5:6e:6e:a1:60;CMTS-MAC=70:01:b5:cc:b5:61;CM-QOS=1.1;CM-VER=3.0;
      2020-9-29, 21:48:09Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:a5:6e:6e:a1:60;CMTS-MAC=70:01:b5:cc:b5:61;CM-QOS=1.1;CM-VER=3.0;
      2020-9-29, 21:48:03Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:a5:6e:6e:a1:60;CMTS-MAC=70:01:b5:cc:b5:61;CM-QOS=1.1;CM-VER=3.0;
      2020-9-29, 21:47:37Critical (3)Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:a5:6e:6e:a1:60;CMTS-MAC=70:01:b5:cc:b5:61;CM-QOS=1.1;CM-VER=3.0;
      2020-9-29, 21:46:51Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:a5:6e:6e:a1:60;CMTS-MAC=70:01:b5:cc:b5:61;CM-QOS=1.1;CM-VER=3.0;
      2020-9-29, 21:46:19Critical (3)Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:a5:6e:6e:a1:60;CMTS-MAC=70:01:b5:cc:b5:61;CM-QOS=1.1;CM-VER=3.0;
      2020-9-29, 21:45:01Critical (3)16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=44:a5:6e:6e:a1:60;CMTS-MAC=70:01:b5:cc:b5:61;CM-QOS=1.1;CM-VER=3.0;
      2020-9-29, 21:45:01Critical (3)Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=44:a5:6e:6e:a1:60;CMTS-MAC=70:01:b5:cc:b5:61;CM-QOS=1.1;CM-VER=3.0;
      2020-9-29, 21:45:01Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:a5:6e:6e:a1:60;CMTS-MAC=70:01:b5:cc:b5:61;CM-QOS=1.1;CM-VER=3.0;
      2020-9-29, 21:44:01Warning (5)Dynamic Range Window violation
      2020-9-29, 21:43:42Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:a5:6e:6e:a1:60;CMTS-MAC=70:01:b5:cc:b5:61;CM-QOS=1.1;CM-VER=3.0;
      2020-9-29, 21:43:31Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=44:a5:6e:6e:a1:60;CMTS-MAC=70:01:b5:cc:b5:61;CM-QOS=1.1;CM-VER=3.0;
      2020-9-29, 21:43:04Warning (5)Dynamic Range Window violation
      2020-9-29, 21:43:04Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=44:a5:6e:6e:a1:60;CMTS-MAC=70:01:b5:cc:b5:61;CM-QOS=1.1;CM-VER=3.0;
      2020-9-29, 21:43:02Warning (5)Dynamic Range Window violation
      2020-9-29, 21:42:58Critical (3)Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:a5:6e:6e:a1:60;CMTS-MAC=70:01:b5:cc:b5:61;CM-QOS=1.1;CM-VER=3.0;
      2020-9-29, 21:42:52Warning (5)Dynamic Range Window violation
       
       
      Ok I found log from today, it looks bad XD I don't have splitters or any of the kind at least not that I know of. Idk if it could be the high traffic during work hours thats doing it. This modem is new and I recently upgraded my speed.
      • plemans's avatar
        plemans
        Guru - Experienced User
        Sep 30, 2020

        t3/4 errors tend to be line issues. The dynamic range window violations also tend to indicate line isssues as its the power levels going out of limits. 

        I'd contact your isp to check the line.