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

Forum Discussion

Bloopbleep's avatar
Bloopbleep
Aspirant
Jun 03, 2022

CM2000 modem unstable internet

Optimum has told me to contact netgear support about my modem. They claim that there is no issue on their end for my internet. But at night and some times randomly during the day my connection becomes very unstable. Which causes horrible ping issues in games and issues streaming. My download speed ends up ranging from 10mbs to 120mbs(I pay for 200). I have my doubts it's the modem, but since I was told to ask here I am.

Cable Connection
Cancel Apply
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 Channel573000000 HzLocked
Connectivity StateOKOperational
Boot StateOKOperational
SecurityEnabledBPI+
 
Downstream Bonded Channels
ChannelLock StatusModulationChannel IDFrequencyPowerSNRCorrectablesUncorrectables
1LockedQAM25614573000000 Hz3.3 dBmV41.2 dB00
2LockedQAM2561489000000 Hz3.3 dBmV41.4 dB00
3LockedQAM2562495000000 Hz3.2 dBmV41.4 dB00
4LockedQAM2563507000000 Hz3.1 dBmV41.3 dB00
5LockedQAM2564513000000 Hz2.9 dBmV41.1 dB00
6LockedQAM2565519000000 Hz2.7 dBmV41.1 dB00
7LockedQAM2566525000000 Hz3.1 dBmV41.3 dB00
8LockedQAM2567531000000 Hz3.2 dBmV41.3 dB00
9LockedQAM2568537000000 Hz2.8 dBmV41.2 dB00
10LockedQAM2569543000000 Hz2.9 dBmV41.1 dB00
11LockedQAM25610549000000 Hz3.1 dBmV41.1 dB00
12LockedQAM25611555000000 Hz3.0 dBmV41.2 dB00
13LockedQAM25612561000000 Hz3.4 dBmV41.3 dB00
14LockedQAM25613567000000 Hz3.6 dBmV41.3 dB00
15LockedQAM25615579000000 Hz3.1 dBmV41.1 dB00
16LockedQAM25616585000000 Hz3.4 dBmV41.2 dB00
17LockedQAM25617591000000 Hz3.6 dBmV41.3 dB00
18LockedQAM25618597000000 Hz3.4 dBmV41.3 dB00
19LockedQAM25619603000000 Hz3.4 dBmV41.2 dB00
20LockedQAM25620609000000 Hz3.3 dBmV41.1 dB00
21LockedQAM25621615000000 Hz3.2 dBmV41.0 dB00
22LockedQAM25622621000000 Hz3.7 dBmV41.1 dB00
23LockedQAM25623627000000 Hz3.8 dBmV41.1 dB00
24LockedQAM25624633000000 Hz3.6 dBmV41.1 dB00
25Not LockedUnknown00 Hz0.0 dBmV0.0 dB00
26Not LockedUnknown00 Hz0.0 dBmV0.0 dB00
27Not LockedUnknown00 Hz0.0 dBmV0.0 dB00
28Not LockedUnknown00 Hz0.0 dBmV0.0 dB00
29Not LockedUnknown00 Hz0.0 dBmV0.0 dB00
30Not LockedUnknown00 Hz0.0 dBmV0.0 dB00
31Not LockedUnknown00 Hz0.0 dBmV0.0 dB00
32Not LockedUnknown00 Hz0.0 dBmV0.0 dB00
 
Upstream Bonded Channels
ChannelLock StatusUS Channel TypeChannel IDSymbol RateFrequencyPower
1LockedATDMA1512030800000 Hz43.8 dBmV
2LockedATDMA2512037500000 Hz45.3 dBmV
3LockedATDMA3512024100000 Hz42.8 dBmV
4LockedATDMA4512017500000 Hz43.3 dBmV
5Not LockedUnknown000 Hz0.0 dBmV
6Not LockedUnknown000 Hz0.0 dBmV
7Not LockedUnknown000 Hz0.0 dBmV
8Not LockedUnknown000 Hz0.0 dBmV
 
Downstream OFDM Channels
ChannelLock
Status
Modulation /
Profile ID
Channel
ID
FrequencyPowerSNR /
MER
Active Subcarrier
Number Range
Unerrored
Codewords
Correctable
Codewords
Uncorrectable
Codewords
1Locked0 ,1 ,2 ,3159717000000 Hz5.0 dBmV41.5 dB1108 ~ 298732611679412336686050
2Not Locked000 Hz0 dBmV0.0 dB0 ~ 4095000
 
Upstream OFDMA Channels
ChannelLock StatusModulation / Profile IDChannel IDFrequencyPower
1Not Locked000 Hz0 dBmV
2Not Locked000 Hz0 dBmV

 

This is what my cable modem shows for my connection. I don't think any thing is out of range, but I could be wrong.

 

Any help would be greater apricated.

4 Replies

  • plemans's avatar
    plemans
    Guru - Experienced User

    A couple things. 

    1. the cable connections page only shows what's going on when you load the page. so next time you're having the issue, reload the page. that'll show us the power levels while the issue is going on. 

    2. the modem event log lets us look at issues longer term. A screen snip of that can help. 

    3. what makes you think its the modem? have you hardwired a computer to the modem and ran it during the period you usually have issues to test it? 

    4. what router is it connected to? Is it connected to a router with a 2.5g port? if so, try connecting it to the 1gig port on the router and use it. I've seen some routers that had issues with their 2.5gig ports. 

    • Bloopbleep's avatar
      Bloopbleep
      Aspirant

      To answer 3: I don't think it's the modem. I've had this issue before this modem, I bought this one to try and fix the issue, which it didn't. Saddly this issue ranges on how annoying it is so I let it slide most days. Today it's been very bad, so I called and they said everything seemed fine and to contact netgear support before sending out a  tech to check in person.

      4: Netgear XR500, I don't see any difference between the ethernet ports.

      The event log:

      Event Log
      Clear Log Refresh
       
      TimePriorityDescription
      Fri Jun 03 16:59:33 2022(Warning (5))Dynamic Range Window violation
      Fri Jun 03 16:59:33 2022(Warning (5))RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=94:a6:7e:fa:30:bc;CMTS-MAC=b0:90:7e:0f:de:b2;CM-QOS=1.1;CM-VER=3.1;
      Fri Jun 03 16:59:30 2022(Warning (5))REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=94:a6:7e:fa:30:bc;CMTS-MAC=b0:90:7e:0f:de:b2;CM-QOS=1.1;CM-VER=3.1;
      Fri Jun 03 16:59:27 2022(Notice (6))DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=94:a6:7e:fa:30:bc;CMTS-MAC=b0:90:7e:0f:de:b2;CM-QOS=1.1;CM-VER=3.1;
      Time Not Established(Warning (5))ToD request sent - No Response received;CM-MAC=94:a6:7e:fa:30:bc;CMTS-MAC=b0:90:7e:0f:de:b2;CM-QOS=1.1;CM-VER=3.1;
      Time Not Established(Warning (5))DHCP WARNING - Non-critical field invalid in response ;CM-MAC=94:a6:7e:fa:30:bc;CMTS-MAC=b0:90:7e:0f:de:b2;CM-QOS=1.1;CM-VER=3.1;
      Time Not Established(Notice (6))Honoring MDD; IP provisioning mode = IPv4
      Time Not Established(Critical (3))SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=94:a6:7e:fa:30:bc;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
      Thu May 26 08:33:04 2022(Notice (6))CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=94:a6:7e:fa:30:bc;CMTS-MAC=b0:90:7e:0f:de:b2;CM-QOS=1.1;CM-VER=3.1;
      Thu May 26 08:32:32 2022(Notice (6))CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=94:a6:7e:fa:30:bc;CMTS-MAC=b0:90:7e:0f:de:b2;CM-QOS=1.1;CM-VER=3.1;
      Wed May 25 15:24:19 2022(Critical (3))Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:a6:7e:fa:30:bc;CMTS-MAC=b0:90:7e:0f:de:b2;CM-QOS=1.1;CM-VER=3.1;
      Wed May 25 13:09:21 2022(Error (4))DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=94:a6:7e:fa:30:bc;CMTS-MAC=b0:90:7e:0f:de:b2;CM-QOS=1.1;CM-VER=3.1;
      Wed May 25 12:21:56 2022(Critical (3))Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:a6:7e:fa:30:bc;CMTS-MAC=b0:90:7e:0f:de:b2;CM-QOS=1.1;CM-VER=3.1;
      Tue May 24 11:45:47 2022(Error (4))DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=94:a6:7e:fa:30:bc;CMTS-MAC=b0:90:7e:0f:de:b2;CM-QOS=1.1;CM-VER=3.1;
      Sun May 22 11:25:51 2022(Warning (5))Dynamic Range Window violation
      Sun May 22 11:25:51 2022(Warning (5))RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=94:a6:7e:fa:30:bc;CMTS-MAC=b0:90:7e:0f:de:b2;CM-QOS=1.1;CM-VER=3.1;
      Sun May 22 11:25:50 2022(Warning (5))Dynamic Range Window violation
      Sun May 22 11:25:50 2022(Warning (5))RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=94:a6:7e:fa:30:bc;CMTS-MAC=b0:90:7e:0f:de:b2;CM-QOS=1.1;CM-VER=3.1;
      Sun May 22 11:25:50 2022(Warning (5))REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=94:a6:7e:fa:30:bc;CMTS-MAC=b0:90:7e:0f:de:b2;CM-QOS=1.1;CM-VER=3.1;
      Sun May 22 11:25:47 2022(Notice (6))DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=94:a6:7e:fa:30:bc;CMTS-MAC=b0:90:7e:0f:de:b2;CM-QOS=1.1;CM-VER=3.1;
      Sun May 22 11:25:39 2022(Warning (5))DHCP WARNING - Non-critical field invalid in response ;CM-MAC=94:a6:7e:fa:30:bc;CMTS-MAC=b0:90:7e:0f:de:b2;CM-QOS=1.1;CM-VER=3.1;
      Time Not Established(Notice (6))Honoring MDD; IP provisioning mode = IPv4
      Time Not Established(Critical (3))SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=94:a6:7e:fa:30:bc;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
      Sun May 22 08:47:43 2022(Critical (3))No Ranging Response received - T3 time-out;CM-MAC=94:a6:7e:fa:30:bc;CMTS-MAC=b0:90:7e:0f:de:b2;CM-QOS=1.1;CM-VER=3.1;
      Sun May 22 08:47:43 2022(Warning (5))Dynamic Range Window violation
      Sun May 22 08:47:43 2022(Warning (5))RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=94:a6:7e:fa:30:bc;CMTS-MAC=b0:90:7e:0f:de:b2;CM-QOS=1.1;CM-VER=3.1;
      Sun May 22 08:47:43 2022(Warning (5))Dynamic Range Window violation
      Sun May 22 08:47:43 2022(Warning (5))RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=94:a6:7e:fa:30:bc;CMTS-MAC=b0:90:7e:0f:de:b2;CM-QOS=1.1;CM-VER=3.1;
      Sun May 22 08:47:42 2022(Warning (5))REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=94:a6:7e:fa:30:bc;CMTS-MAC=b0:90:7e:0f:de:b2;CM-QOS=1.1;CM-VER=3.1;
      Sun May 22 08:47:39 2022(Notice (6))DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=94:a6:7e:fa:30:bc;CMTS-MAC=b0:90:7e:0f:de:b2;CM-QOS=1.1;CM-VER=3.1;
      Sun May 22 08:47:38 2022(Warning (5))DHCP WARNING - Non-critical field invalid in response ;CM-MAC=94:a6:7e:fa:30:bc;CMTS-MAC=b0:90:7e:0f:de:b2;CM-QOS=1.1;CM-VER=3.1;
      Sun May 22 08:47:35 2022(Critical (3))DHCP FAILED - Request sent, No response;CM-MAC=94:a6:7e:fa:30:bc;CMTS-MAC=b0:90:7e:0f:de:b2;CM-QOS=1.1;CM-VER=3.1;
      Sun May 22 08:47:25 2022(Notice (6))Honoring MDD; IP provisioning mode = IPv4
      Sun May 22 08:47:13 2022(Critical (3))Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=94:a6:7e:fa:30:bc;CMTS-MAC=b0:90:7e:0f:de:b2;CM-QOS=1.1;CM-VER=3.1;
      Sun May 22 08:47:11 2022(Notice (6))CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=94:a6:7e:fa:30:bc;CMTS-MAC=b0:90:7e:0f:de:b2;CM-QOS=1.1;CM-VER=3.1;
      Sun May 22 08:47:07 2022(Critical (3))No Ranging Response received - T3 time-out;CM-MAC=94:a6:7e:fa:30:bc;CMTS-MAC=b0:90:7e:0f:de:b2;CM-QOS=1.1;CM-VER=3.1;
      Sun May 22 08:46:59 2022(Critical (3))Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=94:a6:7e:fa:30:bc;CMTS-MAC=b0:90:7e:0f:de:b2;CM-QOS=1.1;CM-VER=3.1;
      Sun May 22 08:46:51 2022(Notice (6))CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=94:a6:7e:fa:30:bc;CMTS-MAC=b0:90:7e:0f:de:b2;CM-QOS=1.1;CM-VER=3.1;
      Sun May 22 08:46:19 2022(Notice (6))CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=94:a6:7e:fa:30:bc;CMTS-MAC=b0:90:7e:0f:de:b2;CM-QOS=1.1;CM-VER=3.1;
      Sun May 22 08:45:12 2022(Critical (3))Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:a6:7e:fa:30:bc;CMTS-MAC=b0:90:7e:0f:de:b2;CM-QOS=1.1;CM-VER=3.1;
      • plemans's avatar
        plemans
        Guru - Experienced User

        You do have line notices/errors but they're not daily. And you have power violations. those usually mean the power has went out of spec and could be causing issues (dynamic range window violation)

        does it happen every day? 

        When it happens, write down the times and compare them to the logs or post them back here with the times it happens and the logs.