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

Forum Discussion

raymondjtoth's avatar
raymondjtoth
Guide
Mar 07, 2022

CM500-100NAS help thanks

hi i have

CM500-100NAS help thanks and fixed the lines last i posted not the modem is radiomly losing channle bonding on down  stream here 192.168.100.1 info you need

Cable Connection
 
 
 
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
Procedure Status Comment
Acquire Downstream Channel561000000 HzLocked
Connectivity StateOKOperational
Boot StateOKOperational
SecurityEnabledBPI+
IP Provisioning ModeHonor MDDhonorMdd(4)
 
Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1LockedQAM2561561000000 Hz-1.5 dBmV40.7 dB40
2LockedQAM2562567000000 Hz0.7 dBmV41.5 dB30
3LockedQAM2563573000000 Hz-1.2 dBmV40.1 dB40
4LockedQAM2564579000000 Hz-2.9 dBmV40 dB110
5LockedQAM2565585000000 Hz-1.7 dBmV38.9 dB60
6LockedQAM2566591000000 Hz-3.2 dBmV35.3 dB220
7LockedQAM2568603000000 Hz-2.1 dBmV38.7 dB40
8LockedQAM2569609000000 Hz-1.4 dBmV40.7 dB80
9LockedQAM25610615000000 Hz-1.2 dBmV40.7 dB80
10LockedQAM25611621000000 Hz-3.1 dBmV39.7 dB77361
11LockedQAM25612627000000 Hz-4.1 dBmV36.9 dB12680043157342
12LockedQAM25613633000000 Hz-1.8 dBmV40.2 dB268659916848
13LockedQAM25615645000000 Hz-1 dBmV29.7 dB10885773539
14LockedQAM25616651000000 Hz-0.3 dBmV41.3 dB20
15LockedQAM25623699000000 Hz-1 dBmV41.2 dB150
16LockedQAM25626717000000 Hz-2.3 dBmV40.2 dB160
 
Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1LockedATDMA25120 Ksym/sec24600000 Hz43 dBmV
2LockedATDMA12560 Ksym/sec18000000 Hz42.8 dBmV
3LockedATDMA35120 Ksym/sec31000000 Hz43.5 dBmV
4LockedATDMA45120 Ksym/sec37400000 Hz43.8 dBmV
 
Extended Upstream Transmit Power
Enable Extended Upstream Transmit Power
 
Current System Time:Tue Mar 08 07:25:13 2022
System Up Time:00:23:39

 

 

37 Replies

  • raymondjtoth's avatar
    raymondjtoth
    Guide
    Mar 07, 2022
    Cable Connection
     
     
     
    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
    Procedure Status Comment
    Acquire Downstream Channel561000000 HzLocked
    Connectivity StateOKOperational
    Boot StateOKOperational
    SecurityEnabledBPI+
    IP Provisioning ModeHonor MDDhonorMdd(4)
     
    Downstream Bonded Channels
    Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
    1LockedQAM2561561000000 Hz-1.4 dBmV40.7 dB40
    2LockedQAM2562567000000 Hz0.7 dBmV41.6 dB30
    3LockedQAM2563573000000 Hz-1.2 dBmV40.1 dB40
    4LockedQAM2564579000000 Hz-2.8 dBmV40 dB110
    5LockedQAM2565585000000 Hz-1.7 dBmV38.9 dB60
    6LockedQAM2566591000000 Hz-3.1 dBmV35.1 dB220
    7LockedQAM2568603000000 Hz-2.1 dBmV38.5 dB40
    8LockedQAM2569609000000 Hz-1.4 dBmV40.7 dB80
    9LockedQAM25610615000000 Hz-1.2 dBmV40.6 dB80
    10LockedQAM25611621000000 Hz-3.1 dBmV38.7 dB77571
    11LockedQAM25612627000000 Hz-4 dBmV31.3 dB13416373364790
    12LockedQAM25613633000000 Hz-1.8 dBmV35.4 dB276093936455
    13Not LockedUnknown00 Hz0.0 dBmV0.0 dB00
    14LockedQAM25616651000000 Hz-0.3 dBmV41.3 dB20
    15LockedQAM25623699000000 Hz-1 dBmV41.2 dB150
    16LockedQAM25626717000000 Hz-2.2 dBmV40.2 dB160
     
    Upstream Bonded Channels
    Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
    1LockedATDMA25120 Ksym/sec24600000 Hz43 dBmV
    2LockedATDMA12560 Ksym/sec18000000 Hz42.8 dBmV
    3LockedATDMA35120 Ksym/sec31000000 Hz43.5 dBmV
    4LockedATDMA45120 Ksym/sec37400000 Hz43.8 dBmV
     
    Extended Upstream Transmit Power
    Enable Extended Upstream Transmit Power
     
    Current System Time:Tue Mar 08 07:26:05 2022
    System Up Time:00:24:31

     

     
    • raymondjtoth's avatar
      raymondjtoth
      Guide
      Mar 07, 2022
      Event Log
         

            

        
       
       
       
       
      Time Priority Description
      2022-3-8, 07:03:02Warning (5)MDD message timeout;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.1;CM-VER=3.0;
      2022-3-8, 07:02:08Notice (6)TLV-11 - unrecognized OID;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.1;CM-VER=3.0;
      1970-1-1, 00:00:30Notice (6)Honoring MDD; IP provisioning mode = IPv4
      1970-1-1, 00:00:27Critical (3)No Ranging Response received - T3 time-out;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.0;CM-VER=3.0;
      1970-1-1, 00:00:22Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
      1970-1-1, 00:00:27Critical (3)No Ranging Response received - T3 time-out;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.0;CM-VER=3.0;
      1970-1-1, 00:00:21Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
      1970-1-1, 00:00:27Critical (3)No Ranging Response received - T3 time-out;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.0;CM-VER=3.0;
      1970-1-1, 00:00:22Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
      2022-3-8, 01:53:14Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.1;CM-VER=3.0;
      2022-3-8, 00:33:29Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.1;CM-VER=3.0;
      2022-3-7, 23:30:26Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.1;CM-VER=3.0;
      2022-3-7, 22:54:21Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.1;CM-VER=3.0;
      2022-3-7, 22:39:09Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.1;CM-VER=3.0;
      2022-3-7, 22:04:05Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.1;CM-VER=3.0;
      2022-3-7, 16:48:38Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.1;CM-VER=3.0;
      2022-3-7, 15:32:38Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.1;CM-VER=3.0;
      2022-3-7, 15:26:56Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.1;CM-VER=3.0;
      2022-3-7, 15:05:09Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.1;CM-VER=3.0;
      2022-3-7, 14:12:08Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.1;CM-VER=3.0;
      2022-3-7, 13:39:42Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.1;CM-VER=3.0;
      2022-3-7, 13:11:32Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.1;CM-VER=3.0;
      2022-3-7, 12:08:53Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.1;CM-VER=3.0;
      2022-3-7, 08:49:24Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.1;CM-VER=3.0;
      2022-3-7, 05:55:22Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.1;CM-VER=3.0;
      2022-3-7, 05:55:16Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.1;CM-VER=3.0;
      2022-3-7, 05:11:45Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.1;CM-VER=3.0;
      2022-3-7, 02:26:11Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.1;CM-VER=3.0;
      1970-1-1, 00:00:27Critical (3)No Ranging Response received - T3 time-out;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.0;CM-VER=3.0;
      1970-1-1, 00:00:21Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
      2022-3-6, 13:27:37Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.1;CM-VER=3.0;
      1970-1-1, 00:00:27Critical (3)No Ranging Response received - T3 time-out;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.0;CM-VER=3.0;
      1970-1-1, 00:00:22Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
      1970-1-1, 00:00:28Critical (3)No Ranging Response received - T3 time-out;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.0;CM-VER=3.0;
      1970-1-1, 00:00:21Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
      2022-2-28, 12:10:16Critical (3)Resetting the cable modem due to docsDevResetNow
      1970-1-1, 00:00:28Critical (3)No Ranging Response received - T3 time-out;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:01:5c:69:fc:4d;CM-QOS=1.0;CM-VER=3.0;
      1970-1-1, 00:00:22Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=94:a6:7e:bb:f7:04;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
      2022-2-28, 04:24:17Critical (3)Resetting the cable modem due to docsDevResetNow
      • raymondjtoth's avatar
        raymondjtoth
        Guide
        Mar 07, 2022

        whats going on and what i tell wowway tech support when i chat or call them on phone there running me around want the right thing tell me cant get into modem to config it need to call netgear them netgear tell me call isp since there end what goin on so can tell them what need to be done will tell them talked to netgear and sed thsi is problem once i get what going on from here thansk ray