NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Firmware 5.1.1.8 issues
Ever since the new firmware update, I have been having issues staying connected. I thought it was my ISP but eventually ended up figuring out it was due to the firmware update. Whenever I have conn...
What is having issues saying connected? The CAX80 or a device connected to the CAX80?
Please post a copy and paste of the modems connection status and event log page.
https://kb.netgear.com/30007/How-do-I-obtain-the-cable-connection-information-from-a-NETGEAR-cable-modem-modem-router
https://kb.netgear.com/30008/How-do-I-view-or-clear-the-event-logs-on-my-NETGEAR-cable-modem-or-modem-router
Has a factory reset and setup from scratch been performed since last FW update?
All devices cannot get internet access through the router. The download blinks white and it starts back going though the whole light sequence again starting with the first light. I tried replying twice with the logs but I guess the msgs were too long so it was removed.
Factory reset was initiated every time the issue happened until I realized it was the firmware that was causing the issue. The date this started happening also aligns when the new firmware was released.
This is the event log of when it stops working.
Event Log
Time Priority Description
Fri Nov 22 07:05:50 2024 Notice TLV-11 - unrecognized OID;CM-MAC=80:cc:9c:71:65:90;CMTS-MAC=00:01:5c:6a:44:93;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 22 07:05:40 2024 Notice Honoring MDD; IP provisioning mode = IPv6
Fri Nov 22 07:05:27 2024 Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=80:cc:9c:71:65:90;CMTS-MAC=00:01:5c:6a:44:93;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 22 07:05:09 2024 Critical No Ranging Response received - T3 time-out;CM-MAC=80:cc:9c:71:65:90;CMTS-MAC=00:01:5c:6a:44:93;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 22 07:05:08 2024 Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=80:cc:9c:71:65:90;CMTS-MAC=00:01:5c:6a:44:93;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 22 07:00:25 2024 Critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=80:cc:9c:71:65:90;CMTS-MAC=00:01:5c:6a:44:93;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 22 06:48:18 2024 Notice DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=80:cc:9c:71:65:90;CMTS-MAC=00:01:5c:6a:44:93;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 22 06:48:17 2024 Notice TLV-11 - unrecognized OID;CM-MAC=80:cc:9c:71:65:90;CMTS-MAC=00:01:5c:6a:44:93;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 22 06:48:09 2024 Notice Honoring MDD; IP provisioning mode = IPv6
Fri Nov 22 06:47:57 2024 Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=80:cc:9c:71:65:90;CMTS-MAC=00:01:5c:6a:44:93;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 22 06:47:46 2024 Critical No Ranging Response received - T3 time-out;CM-MAC=80:cc:9c:71:65:90;CMTS-MAC=00:01:5c:6a:44:93;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 22 06:47:45 2024 Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=80:cc:9c:71:65:90;CMTS-MAC=00:01:5c:6a:44:93;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 22 06:47:41 2024 Critical No Ranging Response received - T3 time-out;CM-MAC=80:cc:9c:71:65:90;CMTS-MAC=00:01:5c:6a:44:93;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 22 06:47:40 2024 Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=80:cc:9c:71:65:90;CMTS-MAC=00:01:5c:6a:44:93;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 22 06:46:13 2024 Critical No Ranging Response received - T3 time-out;CM-MAC=80:cc:9c:71:65:90;CMTS-MAC=00:01:5c:6a:44:93;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 22 06:45:50 2024 Notice CM-STATUS message sent. Event Type Code: 7; Chan ID: 1 4; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=80:cc:9c:71:65:90;CMTS-MAC=00:01:5c:6a:44:93;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 22 06:45:21 2024 Critical No Ranging Response received - T3 time-out;CM-MAC=80:cc:9c:71:65:90;CMTS-MAC=00:01:5c:6a:44:93;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 22 06:45:20 2024 Notice CM-STATUS message sent. Event Type Code: 7; Chan ID: 1 4; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=80:cc:9c:71:65:90;CMTS-MAC=00:01:5c:6a:44:93;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 22 06:44:51 2024 Critical No Ranging Response received - T3 time-out;CM-MAC=80:cc:9c:71:65:90;CMTS-MAC=00:01:5c:6a:44:93;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 22 06:44:49 2024 Notice CM-STATUS message sent. Event Type Code: 7; Chan ID: 1 4; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=80:cc:9c:71:65:90;CMTS-MAC=00:01:5c:6a:44:93;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 22 06:44:32 2024 Critical No Ranging Response received - T3 time-out;CM-MAC=80:cc:9c:71:65:90;CMTS-MAC=00:01:5c:6a:44:93;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 22 06:44:19 2024 Notice CM-STATUS message sent. Event Type Code: 7; Chan ID: 1 4; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=80:cc:9c:71:65:90;CMTS-MAC=00:01:5c:6a:44:93;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 22 06:44:06 2024 Critical No Ranging Response received - T3 time-out;CM-MAC=80:cc:9c:71:65:90;CMTS-MAC=00:01:5c:6a:44:93;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 22 06:43:53 2024 Critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=80:cc:9c:71:65:90;CMTS-MAC=00:01:5c:6a:44:93;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 22 06:43:53 2024 Critical No Ranging Response received - T3 time-out;CM-MAC=80:cc:9c:71:65:90;CMTS-MAC=00:01:5c:6a:44:93;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 22 06:43:50 2024 Critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=80:cc:9c:71:65:90;CMTS-MAC=00:01:5c:6a:44:93;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 22 06:43:49 2024 Notice CM-STATUS message sent. Event Type Code: 7; Chan ID: 1 4; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=80:cc:9c:71:65:90;CMTS-MAC=00:01:5c:6a:44:93;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 22 06:43:45 2024 Critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=80:cc:9c:71:65:90;CMTS-MAC=00:01:5c:6a:44:93;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 22 06:43:45 2024 Critical No Ranging Response received - T3 time-out;CM-MAC=80:cc:9c:71:65:90;CMTS-MAC=00:01:5c:6a:44:93;CM-QOS=1.1;CM-VER=3.1;
Please post a copy and paste of the modems connection status page.
Attached is the status info since I can't post it as a reply.
Power is ok.
You have lots of Correctables and Un-correctables that should be mostly zeros.
Any Criticals, Errors or Warnings seen in the event logs needs to be reviewed and resolved by the ISP. Indicates a signal issue on the ISP line up 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
https://kb.netgear.com/24311/Power-level-guidelines-for-a-NETGEAR-cable-modem-router
https://www.duckware.com/tech/solving-intermittent-cable-modem-issues.html
https://highspeed.tips/docsis-events/