NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
CM2050V - Internet keeps dropping. ISP has no clue.
At my wits end. Internet keeps dropping at cabel modem level (not just wi-fi/router). ISP came out and said it was the ISP provided modem that had issues with the "flaps" and offered to replace it with my CM2050V that I had used at my old house whrn I had Xfinity Gig. After the activation with my current ISP, it worked great for about a week. Now, the issues started 7 days after service call. Looking for advice on what the issue could be when there were no issues for past 7 days, and now again same intermittant dropping issue keeps happening. I find it hard to believe 2 modems would be the issue and would need a 3rd? Connection stats screenshot attached, event log below:
Event log:
Time Priority Description
Fri Jan 06 15:37:40 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 16; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 15:37:34 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 24; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 15:35:23 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 16; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 15:35:16 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 24; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 15:26:10 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 16; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 15:26:05 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 24; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 15:09:56 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 16; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 15:09:46 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 24; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 15:02:11 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 16; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 15:02:04 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 24; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 14:52:06 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 16; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 14:52:01 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 24; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 14:47:31 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 16; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 14:47:27 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 16; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 14:47:25 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 5; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 14:47:16 2023 (Notice (6)) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 14:47:15 2023 (Warning (5)) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 14:47:10 2023 (Critical (3)) DHCP FAILED - Discover sent, no offer received;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 14:46:55 2023 (Critical (3)) DHCP FAILED - Critical field invalid in response ;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 14:46:54 2023 (Critical (3)) DHCP FAILED - Discover sent, no offer received;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 14:46:47 2023 (Critical (3)) DHCP FAILED - Critical field invalid in response ;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 14:46:46 2023 (Critical (3)) DHCP FAILED - Discover sent, no offer received;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 14:46:43 2023 (Critical (3)) DHCP FAILED - Critical field invalid in response ;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 14:46:43 2023 (Notice (6)) Honoring MDD; IP provisioning mode = IPv4
Fri Jan 06 14:46:36 2023 (Critical (3)) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 14:46:33 2023 (Critical (3)) No Ranging Response received - T3 time-out;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 14:46:22 2023 (Critical (3)) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 14:46:21 2023 (Critical (3)) No Ranging Response received - T3 time-out;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 14:46:20 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 6; Chan ID: 2; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 14:46:20 2023 (Critical (3)) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 14:46:20 2023 (Critical (3)) No Ranging Response received - T3 time-out;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 14:46:18 2023 (Critical (3)) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 14:46:17 2023 (Critical (3)) No Ranging Response received - T3 time-out;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 14:46:16 2023 (Critical (3)) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 14:45:52 2023 (Critical (3)) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 14:45:15 2023 (Warning (5)) Dynamic Range Window violation
Fri Jan 06 14:45:15 2023 (Warning (5)) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 14:30:42 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 16; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 14:30:34 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 16; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 14:30:33 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 5; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Event log:
Time Priority Description
Fri Jan 06 15:37:40 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 16; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 15:37:34 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 24; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 15:35:23 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 16; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 15:35:16 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 24; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 15:26:10 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 16; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 15:26:05 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 24; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 15:09:56 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 16; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 15:09:46 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 24; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 15:02:11 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 16; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 15:02:04 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 24; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 14:52:06 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 16; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 14:52:01 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 24; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 14:47:31 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 16; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 14:47:27 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 16; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 14:47:25 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 5; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 14:47:16 2023 (Notice (6)) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 14:47:15 2023 (Warning (5)) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 14:47:10 2023 (Critical (3)) DHCP FAILED - Discover sent, no offer received;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 14:46:55 2023 (Critical (3)) DHCP FAILED - Critical field invalid in response ;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 14:46:54 2023 (Critical (3)) DHCP FAILED - Discover sent, no offer received;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 14:46:47 2023 (Critical (3)) DHCP FAILED - Critical field invalid in response ;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 14:46:46 2023 (Critical (3)) DHCP FAILED - Discover sent, no offer received;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 14:46:43 2023 (Critical (3)) DHCP FAILED - Critical field invalid in response ;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 14:46:43 2023 (Notice (6)) Honoring MDD; IP provisioning mode = IPv4
Fri Jan 06 14:46:36 2023 (Critical (3)) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 14:46:33 2023 (Critical (3)) No Ranging Response received - T3 time-out;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 14:46:22 2023 (Critical (3)) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 14:46:21 2023 (Critical (3)) No Ranging Response received - T3 time-out;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 14:46:20 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 6; Chan ID: 2; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 14:46:20 2023 (Critical (3)) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 14:46:20 2023 (Critical (3)) No Ranging Response received - T3 time-out;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 14:46:18 2023 (Critical (3)) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 14:46:17 2023 (Critical (3)) No Ranging Response received - T3 time-out;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 14:46:16 2023 (Critical (3)) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 14:45:52 2023 (Critical (3)) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 14:45:15 2023 (Warning (5)) Dynamic Range Window violation
Fri Jan 06 14:45:15 2023 (Warning (5)) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 14:30:42 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 16; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 14:30:34 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 16; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
Fri Jan 06 14:30:33 2023 (Notice (6)) CM-STATUS message sent. Event Type Code: 5; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=28:80:88:d5:59:28;CMTS-MAC=00:17:10:90:ca:1c;CM-QOS=1.1;CM-VER=3.1;
7 Replies
You have Criticals that the ISP needs to review and resolve.
Power levels on some channels is way to high and power levels are all over the place:
https://kb.netgear.com/24311/Power-level-guidelines-for-a-NETGEAR-cable-modem-router
Be sure your using a good quality LAN cable between the modem and router. CAT6A STP is recommended.
What is the brand and model of the host wifi router connected to the modem?Have the ISP check the signal and line quality UP to the modem. Be sure the ISP provisions the modem correctly.
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.
Be sure to power OFF the modem for 1 minute then back ON.
https://community.netgear.com/t5/Cable-Modems-Routers/General-info-and-Troubleshooting-for-Cable-Modems/m-p/1530376#M12853- Thanks! Yes, I noticed the big variance in power and boarderline concerning varience in SNR across the 32 downstream bonded channels. Now more and more channels are showing correctible and uncorrectible codes as time goes on, until I end up doing a power cycle or reboot.
LAN cable from modem to main gateway router cable is unlabled, so cannot verify that it is CAT6A STP, but I assume it is as it is the one that came with the router system. Router being used is eero 6 Pro mesh (1 as wired gateway with 2 others as wirelesh mesh extenders).
When ISP techvwas out here last week, he checked the wiring and said it all looked good, and when we swapped out the old modem for this model, everything was great and all stats were within range. If other writing issues, would it take 7 days to show up without dropping issues? Just want to know what to do or advocate/ask for when the tech comes back out.
Also, dropping issues occur within an hour or so even after unplugging/power cycling and/or rebooting modem and router.
Thanks in advance.Good afternoon,
Update: I decided to test at the site where the internet enters the home. Had modem plugged in now for about an hour, and so far, no uncorrectable errors on the downstream boned channels (so.. I guess that's a good sign? but it's only been an hour thus far...). Power still seems to be highly variant across the 32 channels ranging from a low of 7.7 to a high of 19.1. SNR, again, seems to have less, but still some borderline worrisome variance with a range of a low at 35.8 and a high of 38.7. Only thing I see on the upstream bonded channels is that the power for the 4th channel is not quite getting up to the desired minimum of 35.0. Now... for the Downstream OFDM channel, I'm getting a LOT of uncorrectable codewords that keep climbing and climbing and climbing by the minute. As of now though, no critical errors in the event log.. just recurring "notices" every few mins (CM-STATUS message sent. Event Type Code: 16 and 24).
My worry is now with no evidence of uncorrectable errors on the bonded downstream channels, that the ISP will again attempt to tell me it's a hardware issue on my end. Based on what I'm reading, the variance in power and SNR, and lack of getting consistent upstream power on all channels, there still looks to be an issue on the ISP side, no? I don't even have a clue about why the downstream OFCM is coughing up that many uncorrectables though? ISP is supposed to come tomorrow, and just want to make sure I'm armed with best info to finally get the issue resolved without further issues of recurrence.
Thanks to anybody who can give me pointers. Current Connection stats below (based on plugging modem in at site ISP cable enters home (i.e. bypassing ALL wiring in home). Also.. stats are based on just CAT 6A STP cable from modem to laptop without any other connections).
----
Cable ConnectionCancel ApplyFrequency 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 Channel 651000000 Hz Locked Connectivity State OK Operational Boot State OK Operational Security Disabled Disabled Downstream Bonded Channels Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables 1 Locked QAM256 32 651000000 Hz 11.5 dBmV 36.4 dB 0 0 2 Locked QAM256 1 465000000 Hz 10.8 dBmV 37.6 dB 0 0 3 Locked QAM256 2 471000000 Hz 10.2 dBmV 37.4 dB 0 0 4 Locked QAM256 4 483000000 Hz 11.8 dBmV 37.6 dB 0 0 5 Locked QAM256 5 489000000 Hz 14.2 dBmV 38.3 dB 0 0 6 Locked QAM256 8 507000000 Hz 16.4 dBmV 38.5 dB 0 0 7 Locked QAM256 13 537000000 Hz 14.3 dBmV 38.5 dB 0 0 8 Locked QAM256 14 543000000 Hz 15.6 dBmV 38.7 dB 0 0 9 Locked QAM256 15 549000000 Hz 16.0 dBmV 38.6 dB 0 0 10 Locked QAM256 17 561000000 Hz 14.5 dBmV 37.8 dB 0 0 11 Locked QAM256 18 567000000 Hz 12.4 dBmV 37.2 dB 0 0 12 Locked QAM256 19 573000000 Hz 10.9 dBmV 37.2 dB 0 0 13 Locked QAM256 21 585000000 Hz 10.0 dBmV 37.8 dB 0 0 14 Locked QAM256 22 591000000 Hz 9.9 dBmV 37.7 dB 0 0 15 Locked QAM256 23 597000000 Hz 10.4 dBmV 37.2 dB 0 0 16 Locked QAM256 24 603000000 Hz 11.6 dBmV 37.2 dB 0 0 17 Locked QAM256 26 615000000 Hz 15.4 dBmV 37.4 dB 0 0 18 Locked QAM256 27 621000000 Hz 15.9 dBmV 37.5 dB 0 0 19 Locked QAM256 28 627000000 Hz 15.5 dBmV 37.7 dB 0 0 20 Locked QAM256 29 633000000 Hz 14.6 dBmV 37.7 dB 0 0 21 Locked QAM256 30 639000000 Hz 13.5 dBmV 37.4 dB 0 0 22 Locked QAM256 34 663000000 Hz 12.2 dBmV 36.8 dB 0 0 23 Locked QAM256 35 669000000 Hz 13.1 dBmV 37.0 dB 0 0 24 Locked QAM256 36 675000000 Hz 14.1 dBmV 37.3 dB 0 0 25 Locked QAM256 37 681000000 Hz 13.4 dBmV 37.5 dB 0 0 26 Locked QAM256 38 687000000 Hz 11.2 dBmV 37.0 dB 0 0 27 Locked QAM256 40 699000000 Hz 8.2 dBmV 35.9 dB 0 0 28 Locked QAM256 41 705000000 Hz 7.7 dBmV 35.8 dB 0 0 29 Locked QAM256 42 711000000 Hz 9.5 dBmV 36.0 dB 0 0 30 Locked QAM256 43 717000000 Hz 12.7 dBmV 37.2 dB 0 0 31 Locked QAM256 44 723000000 Hz 15.3 dBmV 37.7 dB 0 0 32 Locked QAM256 47 741000000 Hz 19.1 dBmV 37.2 dB 0 0 Upstream Bonded Channels Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 1 5120 16600000 Hz 35.0 dBmV 2 Locked ATDMA 2 5120 23000000 Hz 35.0 dBmV 3 Locked ATDMA 3 5120 29400000 Hz 35.0 dBmV 4 Locked ATDMA 4 5120 35800000 Hz 33.8 dBmV 5 Not Locked Unknown 0 0 0 Hz 0.0 dBmV 6 Not Locked Unknown 0 0 0 Hz 0.0 dBmV 7 Not Locked Unknown 0 0 0 Hz 0.0 dBmV 8 Not Locked Unknown 0 0 0 Hz 0.0 dBmV Downstream OFDM Channels Channel Lock Status Profile ID Channel ID Frequency Power SNR / MER Active Subcarrier
Number RangeUnerrored
CodewordsCorrectable
CodewordsUncorrectable
Codewords1 Locked 0 ,1 ,2 ,3 49 212000000 Hz 12.2 dBmV 36.1 dB 1088 ~ 3007 68802730 51443103 4429109 2 Not Locked 0 0 0 Hz 0 dBmV 0.0 dB 0 ~ 4095 0 0 0 Upstream OFDMA Channels Channel Lock Status Modulation / Profile ID Channel ID Frequency Power 1 Not Locked 0 0 0 Hz 0 dBmV 2 Not Locked 0 0 0 Hz 0 dBmV Current System Time:Tue Jan 10 13:10:02 2023 System Up Time:01:20:44
