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

Forum Discussion

tcq's avatar
tcq
Aspirant
Oct 12, 2017
Solved

Modem CM500: many channels not locked; slow connection (1-2mbps)

See below. Is it normal for many channels not locked? The Internet starts fast, but over one hour or so drops to crawl speed (1mpbs or less). A reboot of the modem often fixes the problem, but it wil...
Troubleshooting
  • vkdelta's avatar
    vkdelta
    Oct 13, 2017

    you have a serious noise issue either in home wiring or ISP's line. that is why most your downstream channels are NOT locked. and whatever is locked have lot of uncorrectable errors. 

     

    what modem did you have before CM500? did it have same problem? or you are moving into a new house/apartment?

tcq's avatar
tcq
Aspirant
Oct 12, 2017

ISP: comcast/xfinity.

tcq's avatar
tcq
Aspirant
Oct 12, 2017

Event Log
       Clear Log                Refresh        
 
 
 
 
TimePriorityDescription
2017-10-11, 21:49:07Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:da:43:fc:c9:48;CMTS-MAC=00:01:5c:63:e0:7b;CM-QOS=1.1;CM-VER=3.0;
2017-10-11, 21:49:28Critical (3)Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=10:da:43:fc:c9:48;CMTS-MAC=00:01:5c:63:e0:7b;CM-QOS=1.1;CM-VER=3.0;
2017-10-11, 21:49:28Critical (3)16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=10:da:43:fc:c9:48;CMTS-MAC=00:01:5c:63:e0:7b;CM-QOS=1.1;CM-VER=3.0;
2017-10-11, 21:49:29Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:da:43:fc:c9:48;CMTS-MAC=00:01:5c:63:e0:7b;CM-QOS=1.1;CM-VER=3.0;
2017-10-11, 21:49:50Critical (3)Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=10:da:43:fc:c9:48;CMTS-MAC=00:01:5c:63:e0:7b;CM-QOS=1.1;CM-VER=3.0;
2017-10-11, 21:49:50Critical (3)16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=10:da:43:fc:c9:48;CMTS-MAC=00:01:5c:63:e0:7b;CM-QOS=1.1;CM-VER=3.0;
2017-10-11, 21:49:52Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:da:43:fc:c9:48;CMTS-MAC=00:01:5c:63:e0:7b;CM-QOS=1.1;CM-VER=3.0;
2017-10-11, 21:50:13Critical (3)Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=10:da:43:fc:c9:48;CMTS-MAC=00:01:5c:63:e0:7b;CM-QOS=1.1;CM-VER=3.0;
2017-10-11, 21:50:13Critical (3)16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=10:da:43:fc:c9:48;CMTS-MAC=00:01:5c:63:e0:7b;CM-QOS=1.1;CM-VER=3.0;
2017-10-11, 21:50:14Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:da:43:fc:c9:48;CMTS-MAC=00:01:5c:63:e0:7b;CM-QOS=1.1;CM-VER=3.0;
2017-10-11, 21:50:35Critical (3)Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=10:da:43:fc:c9:48;CMTS-MAC=00:01:5c:63:e0:7b;CM-QOS=1.1;CM-VER=3.0;
2017-10-11, 21:50:35Critical (3)16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=10:da:43:fc:c9:48;CMTS-MAC=00:01:5c:63:e0:7b;CM-QOS=1.1;CM-VER=3.0;
2017-10-11, 21:50:37Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:da:43:fc:c9:48;CMTS-MAC=00:01:5c:63:e0:7b;CM-QOS=1.1;CM-VER=3.0;
2017-10-11, 21:50:57Critical (3)Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=10:da:43:fc:c9:48;CMTS-MAC=00:01:5c:63:e0:7b;CM-QOS=1.1;CM-VER=3.0;
2017-10-11, 21:50:57Critical (3)16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=10:da:43:fc:c9:48;CMTS-MAC=00:01:5c:63:e0:7b;CM-QOS=1.1;CM-VER=3.0;
2017-10-11, 21:50:59Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:da:43:fc:c9:48;CMTS-MAC=00:01:5c:63:e0:7b;CM-QOS=1.1;CM-VER=3.0;
2017-10-11, 21:51:19Critical (3)Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=10:da:43:fc:c9:48;CMTS-MAC=00:01:5c:63:e0:7b;CM-QOS=1.1;CM-VER=3.0;
2017-10-11, 21:51:19Critical (3)16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=10:da:43:fc:c9:48;CMTS-MAC=00:01:5c:63:e0:7b;CM-QOS=1.1;CM-VER=3.0;
2017-10-11, 21:51:21Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:da:43:fc:c9:48;CMTS-MAC=00:01:5c:63:e0:7b;CM-QOS=1.1;CM-VER=3.0;
2017-10-11, 21:51:42Critical (3)Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=10:da:43:fc:c9:48;CMTS-MAC=00:01:5c:63:e0:7b;CM-QOS=1.1;CM-VER=3.0;
2017-10-11, 21:51:42Critical (3)16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=10:da:43:fc:c9:48;CMTS-MAC=00:01:5c:63:e0:7b;CM-QOS=1.1;CM-VER=3.0;
2017-10-11, 21:51:44Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:da:43:fc:c9:48;CMTS-MAC=00:01:5c:63:e0:7b;CM-QOS=1.1;CM-VER=3.0;
2017-10-11, 21:52:04Critical (3)Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=10:da:43:fc:c9:48;CMTS-MAC=00:01:5c:63:e0:7b;CM-QOS=1.1;CM-VER=3.0;
2017-10-11, 21:52:04Critical (3)16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=10:da:43:fc:c9:48;CMTS-MAC=00:01:5c:63:e0:7b;CM-QOS=1.1;CM-VER=3.0;
2017-10-11, 21:52:05Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:da:43:fc:c9:48;CMTS-MAC=00:01:5c:63:e0:7b;CM-QOS=1.1;CM-VER=3.0;
2017-10-11, 21:52:27Critical (3)Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=10:da:43:fc:c9:48;CMTS-MAC=00:01:5c:63:e0:7b;CM-QOS=1.1;CM-VER=3.0;
2017-10-11, 21:52:27Critical (3)16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=10:da:43:fc:c9:48;CMTS-MAC=00:01:5c:63:e0:7b;CM-QOS=1.1;CM-VER=3.0;
2017-10-11, 21:52:28Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:da:43:fc:c9:48;CMTS-MAC=00:01:5c:63:e0:7b;CM-QOS=1.1;CM-VER=3.0;
2017-10-11, 21:52:49Critical (3)Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=10:da:43:fc:c9:48;CMTS-MAC=00:01:5c:63:e0:7b;CM-QOS=1.1;CM-VER=3.0;
2017-10-11, 21:52:49Critical (3)16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=10:da:43:fc:c9:48;CMTS-MAC=00:01:5c:63:e0:7b;CM-QOS=1.1;CM-VER=3.0;
2017-10-11, 21:52:50Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:da:43:fc:c9:48;CMTS-MAC=00:01:5c:63:e0:7b;CM-QOS=1.1;CM-VER=3.0;
2017-10-11, 21:53:11Critical (3)Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=10:da:43:fc:c9:48;CMTS-MAC=00:01:5c:63:e0:7b;CM-QOS=1.1;CM-VER=3.0;
2017-10-11, 21:53:11Critical (3)16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=10:da:43:fc:c9:48;CMTS-MAC=00:01:5c:63:e0:7b;CM-QOS=1.1;CM-VER=3.0;
2017-10-11, 21:53:12Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:da:43:fc:c9:48;CMTS-MAC=00:01:5c:63:e0:7b;CM-QOS=1.1;CM-VER=3.0;
2017-10-11, 21:53:33Critical (3)Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=10:da:43:fc:c9:48;CMTS-MAC=00:01:5c:63:e0:7b;CM-QOS=1.1;CM-VER=3.0;
2017-10-11, 21:53:33Critical (3)16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=10:da:43:fc:c9:48;CMTS-MAC=00:01:5c:63:e0:7b;CM-QOS=1.1;CM-VER=3.0;
2017-10-11, 21:53:34Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:da:43:fc:c9:48;CMTS-MAC=00:01:5c:63:e0:7b;CM-QOS=1.1;CM-VER=3.0;
2017-10-11, 21:53:55Critical (3)Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=10:da:43:fc:c9:48;CMTS-MAC=00:01:5c:63:e0:7b;CM-QOS=1.1;CM-VER=3.0;
2017-10-11, 21:53:55Critical (3)16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=10:da:43:fc:c9:48;CMTS-MAC=00:01:5c:63:e0:7b;CM-QOS=1.1;CM-VER=3.0;
2017-10-11, 21:53:57Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:da:43:fc:c9:48;CMTS-MAC=00:01:5c:63:e0:7b;CM-QOS=1.1;CM-VER=3.0;
 
Help CenterShow/Hide Help Center
  • tcq's avatar
    tcq
    Aspirant
    Oct 12, 2017

    Cable Connection
     
     
    Apply               Cancel     
    Frequency start Value
    This field below allows you to modify the frequency the cable modem start with its scan during initialization and registration. Enter the new start frequency and restart the cable modem for it to take effect.
    Starting Frequency
     
    Startup Procedure
    ProcedureStatusComment
    Acquire Downstream Channel519000000 HzLocked
    Connectivity StateOKOperational
    Boot StateOKOperational
    SecurityEnabledBPI+
    IP Provisioning ModeHonor MDDhonorMdd(4)
     
    Downstream Bonded Channels (Partial Service)
    ChannelLock StatusModulationChannel IDFrequencyPowerSNRCorrectablesUncorrectables
    1LockedQAM2562519000000 Hz0.2 dBmV40.3 dB00
    2LockedQAM2564531000000 Hz-0.8 dBmV39.9 dB10
    3LockedQAM2566543000000 Hz-2.2 dBmV39.6 dB10
    4Not LockedUnknown7549000000 Hz0.0 dBmV0.0 dB00
    5Not LockedUnknown9561000000 Hz0.0 dBmV0.0 dB00
    6LockedQAM25612579000000 Hz-10.6 dBmV33.9 dB390
    7Not LockedUnknown13585000000 Hz0.0 dBmV0.0 dB00
    8Not LockedUnknown14591000000 Hz0.0 dBmV0.0 dB00
    9Not LockedUnknown17609000000 Hz0.0 dBmV0.0 dB00
    10Not LockedUnknown21633000000 Hz0.0 dBmV0.0 dB00
    11Not LockedUnknown22639000000 Hz0.0 dBmV0.0 dB00
    12Not LockedUnknown23645000000 Hz0.0 dBmV0.0 dB00
    13LockedQAM25624651000000 Hz-3.5 dBmV29.9 dB341075919271
    14LockedQAM25630705000000 Hz1 dBmV39.9 dB20
    15LockedQAM25631717000000 Hz1.7 dBmV39.9 dB10
    16LockedQAM25632723000000 Hz1.2 dBmV39.7 dB10
     
    Upstream Bonded Channels (Partial Service)
    ChannelLock StatusUS Channel TypeChannel IDSymbol RateFrequencyPower
    1LockedATDMA735120 Ksym/sec17300000 Hz47.8 dBmV
    2LockedATDMA745120 Ksym/sec23700000 Hz47.8 dBmV
    3LockedATDMA755120 Ksym/sec30300000 Hz51 dBmV
    4Not LockedUnknown760 Ksym/sec36700000 Hz0.0 dBmV
     
    Current System Time:Wed Oct 11 21:55:14 2017
     
    Help CenterShow/Hide Help Center
    • vkdelta's avatar
      vkdelta
      NETGEAR Employee Retired
      Oct 12, 2017

      please dont copy paste. instead attach them as screenshots. 

       

      from the info you have provided (I could not see Uncorrectables in the power page), it looks like you have US noise issue on comcast and thats why you are seeing lot of T3 timeouts in the event log. But this will cause low performance in US and not in downlink. 

       

      please post screenshot of the power page and not copy-paste them in the reponse as it misses right most columns.

      • tcq's avatar
        tcq
        Aspirant
        Oct 13, 2017

        Thank you for the help and sorry for the inconvience of copy&paste.