NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
XR1000 the cable modem is scanning for a downstream channel.
All, A new issue has come up. I noticed last night that the internet was getting bogged down. Went and looked at the Netgear cable modem and the downstream light was blinking. I tried to reboot...
Lost IPV6 again. Speed seems to be good. I cannot login into modem. I can get to the CM2000 page but every time I put the password in nothing happens.
un Dec 11 21:13:27 2022 (Warning (5)) Dynamic Range Window violation
Sun Dec 11 21:13:27 2022 (Warning (5)) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM- =1.1;CM-VER=3.1;
Sun Dec 11 21:13:27 2022 (Warning (5)) Dynamic Range Window violation
Sun Dec 11 21:13:27 2022 (Warning (5)) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC= -QOS=1.1;CM-VER=3.1;
Sun Dec 11 20:50:47 2022 (Notice (6)) CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM- CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Sun Dec 11 20:50:07 2022 (Notice (6)) CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MACxxxxxxxxxxxx;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Sun Dec 11 20:20:11 2022 (Notice (6)) CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MACxxxxxxxxxxxx;CMTS-MAC=bCM-QOS=1.1;CM-VER=3.1;
Sun Dec 11 20:19:43 2022 (Notice (6)) CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MACxxxxxxxxxxxx;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Sun Dec 11 20:16:58 2022 (Notice (6)) CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MACxxxxxxxxxxxx;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Sun Dec 11 20:15:12 2022 (Notice (6)) CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MACxxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
Sun Dec 11 20:12:47 2022 (Notice (6)) CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MACxxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
Sun Dec 11 20:12:26 2022 (Notice (6)) CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MACxxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
Sun Dec 11 20:12:13 2022 (Warning (5)) Dynamic Range Window violation
Sun Dec 11 20:12:13 2022 (Warning (5)) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MACxxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
Sun Dec 11 20:12:12 2022 (Warning (5)) Dynamic Range Window violation
Sun Dec 11 20:12:12 2022 (Warning (5)) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MACxxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
Sun Dec 11 19:59:06 2022 (Notice (6)) CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MACxxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
Sun Dec 11 19:58:38 2022 (Notice (6)) CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MACxxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
Sun Dec 11 19:41:04 2022 (Notice (6)) CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MACxxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
Sun Dec 11 19:40:22 2022 (Notice (6)) CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MACxxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
Sun Dec 11 19:10:58 2022 (Warning (5)) Dynamic Range Window violation
Sun Dec 11 19:10:58 2022 (Warning (5)) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MACxxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
Sun Dec 11 19:10:58 2022 (Warning (5)) Dynamic Range Window violation
Sun Dec 11 19:10:58 2022 (Warning (5)) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MACxxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
Sun Dec 11 19:04:49 2022 (Notice (6)) CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MACxxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
Sun Dec 11 19:03:45 2022 (Notice (6)) CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MACxxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
Sun Dec 11 18:59:18 2022 (Notice (6)) CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MACxxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
Sun Dec 11 18:58:53 2022 (Notice (6)) CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MACxxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
Sun Dec 11 18:42:51 2022 (Notice (6)) CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MACxxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
Sun Dec 11 18:42:22 2022 (Notice (6)) CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MACxxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
Sun Dec 11 18:35:10 2022 (Notice (6)) CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MACxxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
Sun Dec 11 18:34:30 2022 (Notice (6)) CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MACxxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
Sun Dec 11 18:32:32 2022 (Notice (6)) CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MACxxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
Sun Dec 11 18:32:06 2022 (Notice (6)) CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MACxxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
Sun Dec 11 18:25:21 2022 (Notice (6)) CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MACxxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
Sun Dec 11 18:24:56 2022 (Notice (6)) CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MACxxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
Sun Dec 11 18:22:58 2022 (Notice (6)) CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MACxxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
Sun Dec 11 18:22:07 2022 (Notice (6)) CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MACxxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
Sun Dec 11 18:09:44 2022 (Warning (5)) Dynamic Range Window violation
Sun Dec 11 18:09:44 2022 (Warning (5)) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MACxxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
Everytime I try to upload the other info. Netgear keeps saying I am flodding msg board.
I hooked up the XR500 to see what happens over night with IPV6 as well as the modem dowload blinking.
The previous time you lost IPv6, was that without the XR500 connected? Let us know how you get on with it connected again if so.
Can you capture the cable connections page from the CM modem now?
Copy and paste that in to a PDF or picture file then select Choose File on your post to attached it to the post instead of trying to put it in the post window.
Event log looks ok...Thought I see some Warnings that maybe the ISP should take a look at.
Never lost IPV6 on XR500.
Your power levels are mostly all over the place and also too high for some channels:
https://kb.netgear.com/24311/Power-level-guidelines-for-a-NETGEAR-cable-modem-router
I'd get the ISP to look at the power levels and bring them down a bit and also get ALL the channels on or near same power levels for each other.
Have the ISP check the signal and line quality UP to the modem. Be sure the ISP provisions the modem correctly. Might ask for a on site visit to be sure.
Be sure there are no coax cable line splitters in the between the modem and ISP service box.
Be sure your using good quality RG6 coax cable up to the modem.
Start with removing any amplifiers, signal attenuators, or splitters from the coax.
From there check the line for kinks, damage, moisture in the line.
Check the connectors for improperly made ends, foil touching the copper coax line, loose connections, bad/old/cheap connectors, or corroded connections. Replace them if you do.
https://community.netgear.com/t5/Cable-Modems-Routers/General-info-and-Troubleshooting-for-Cable-Modems/m-p/1530376#M12853Had the XR500 hooked up all last night and unti 1200 EST. As soon as I plugged the XR1000 in the downstream blinked and I lost IPV6. Would like and try and figure this out but at the same time this is taking serious time.
Be sure there are no coax cable line splitters in the between the modem and ISP service box. Done
Be sure your using good quality RG6 coax cable up to the modem. I guess I need to buy one
Start with removing any amplifiers, signal attenuators, or splitters from the coax. Done
From there check the line for kinks, damage, moisture in the line. None
Check the connectors for improperly made ends, foil touching the copper coax line, loose connections, bad/old/cheap connectors, or corroded connections. Replace them if you do. Did not see anything. Also the XR500 is not having that issue on the same line with the same hook up.Still have the ISP review the event logs page and power levels. Power is too high.
- Try setting the XR1000 to use the same MAC address as the XR500 - some ISPs get weird when introducing a new router, if that is the case then the MAC change can prevent that
Noticed there's not been an update in a few months. Did you manage to get your XR1000 issue sorted with IPv6?
