NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
CM1200 V1.02.01 On Spectrum - Keeps Crashing - is it mys ervice or device?
I have a personal modem CM1200 V1.02.01 connected to a R900 V1.0.5.28 on Spectrum internet in San Antonio Texas. I am tracking that I cannot update the firmware, but hoping that someone on here can let me know if these settings show something outside of all the critical priorities. I am thinking my disconnects are due to he old firmware, but not sure. I am about to go buy a different modem as this is happening almost daily now.
| Procedure | Status | Comment |
| Acquire Downstream Channel | 399000000 Hz | Locked |
| Connectivity State | OK | Operational |
| Boot State | OK | Operational |
| Security | Enabled | BPI+ |
| IP Provisioning Mode | Honor MDD | honorMdd(4) |
7 Replies
Time Priority Description Mon Mar 08 17:04:52 2021 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=28:80:88:b3:8d:e0;CMTS-MAC=00:17:10:8d:d2:05;CM-QOS=1.1;CM-VER=3.1; Mon Mar 08 17:02:56 2021 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:b3:8d:e0;CMTS-MAC=00:17:10:8d:d2:05;CM-QOS=1.1;CM-VER=3.1; Mon Mar 08 17:02:51 2021 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=28:80:88:b3:8d:e0;CMTS-MAC=00:17:10:8d:d2:05;CM-QOS=1.1;CM-VER=3.1; Mon Mar 08 16:59:56 2021 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:b3:8d:e0;CMTS-MAC=00:17:10:8d:d2:05;CM-QOS=1.1;CM-VER=3.1; Mon Mar 08 16:59:51 2021 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=28:80:88:b3:8d:e0;CMTS-MAC=00:17:10:8d:d2:05;CM-QOS=1.1;CM-VER=3.1; Mon Mar 08 16:59:35 2021 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:b3:8d:e0;CMTS-MAC=00:17:10:8d:d2:05;CM-QOS=1.1;CM-VER=3.1; Mon Mar 08 16:59:21 2021 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=28:80:88:b3:8d:e0;CMTS-MAC=00:17:10:8d:d2:05;CM-QOS=1.1;CM-VER=3.1; Mon Mar 08 16:51:26 2021 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:b3:8d:e0;CMTS-MAC=00:17:10:8d:d2:05;CM-QOS=1.1;CM-VER=3.1; Mon Mar 08 16:51:17 2021 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=28:80:88:b3:8d:e0;CMTS-MAC=00:17:10:8d:d2:05;CM-QOS=1.1;CM-VER=3.1; Mon Mar 08 16:40:36 2021 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:b3:8d:e0;CMTS-MAC=00:17:10:8d:d2:05;CM-QOS=1.1;CM-VER=3.1; Mon Mar 08 16:40:13 2021 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=28:80:88:b3:8d:e0;CMTS-MAC=00:17:10:8d:d2:05;CM-QOS=1.1;CM-VER=3.1; Mon Mar 08 16:28:17 2021 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:b3:8d:e0;CMTS-MAC=00:17:10:8d:d2:05;CM-QOS=1.1;CM-VER=3.1; Mon Mar 08 16:28:08 2021 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=28:80:88:b3:8d:e0;CMTS-MAC=00:17:10:8d:d2:05;CM-QOS=1.1;CM-VER=3.1; Mon Mar 08 16:17:37 2021 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:b3:8d:e0;CMTS-MAC=00:17:10:8d:d2:05;CM-QOS=1.1;CM-VER=3.1; Mon Mar 08 16:17:34 2021 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=28:80:88:b3:8d:e0;CMTS-MAC=00:17:10:8d:d2:05;CM-QOS=1.1;CM-VER=3.1; Mon Mar 08 15:58:01 2021 Notice (6) CM-STATUS message sent. Event Type Code: 6; Chan ID: 10; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=28:80:88:b3:8d:e0;CMTS-MAC=00:17:10:8d:d2:05;CM-QOS=1.1;CM-VER=3.1; Mon Mar 08 15:57:59 2021 Notice (6) CM-STATUS message sent. Event Type Code: 7; Chan ID: 10; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=28:80:88:b3:8d:e0;CMTS-MAC=00:17:10:8d:d2:05;CM-QOS=1.1;CM-VER=3.1; Mon Mar 08 15:57:38 2021 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=28:80:88:b3:8d:e0;CMTS-MAC=00:17:10:8d:d2:05;CM-QOS=1.1;CM-VER=3.1; Mon Mar 08 15:57:08 2021 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:b3:8d:e0;CMTS-MAC=00:17:10:8d:d2:05;CM-QOS=1.1;CM-VER=3.1; Mon Mar 08 15:57:06 2021 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 8;CM-MAC=28:80:88:b3:8d:e0;CMTS-MAC=00:17:10:8d:d2:05;CM-QOS=1.1;CM-VER=3.1; Mon Mar 08 15:57:06 2021 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=28:80:88:b3:8d:e0;CMTS-MAC=00:17:10:8d:d2:05;CM-QOS=1.1;CM-VER=3.1; Mon Mar 08 15:57:06 2021 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:b3:8d:e0;CMTS-MAC=00:17:10:8d:d2:05;CM-QOS=1.1;CM-VER=3.1; Mon Mar 08 15:56:48 2021 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 8;CM-MAC=28:80:88:b3:8d:e0;CMTS-MAC=00:17:10:8d:d2:05;CM-QOS=1.1;CM-VER=3.1; Mon Mar 08 15:56:48 2021 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=28:80:88:b3:8d:e0;CMTS-MAC=00:17:10:8d:d2:05;CM-QOS=1.1;CM-VER=3.1; Mon Mar 08 15:56:48 2021 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:b3:8d:e0;CMTS-MAC=00:17:10:8d:d2:05;CM-QOS=1.1;CM-VER=3.1; Mon Mar 08 15:56:27 2021 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=28:80:88:b3:8d:e0;CMTS-MAC=00:17:10:8d:d2:05;CM-QOS=1.1;CM-VER=3.1; Mon Mar 08 15:56:27 2021 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:b3:8d:e0;CMTS-MAC=00:17:10:8d:d2:05;CM-QOS=1.1;CM-VER=3.1; Mon Mar 08 15:56:09 2021 Warning (5) REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=28:80:88:b3:8d:e0;CMTS-MAC=00:17:10:8d:d2:05;CM-QOS=1.1;CM-VER=3.1; Mon Mar 08 15:56:03 2021 Notice (6) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2.;CM-MAC=28:80:88:b3:8d:e0;CMTS-MAC=00:17:10:8d:d2:05;CM-QOS=1.1;CM-VER=3.1; Mon Mar 08 15:56:02 2021 Notice (6) TLV-11 - unrecognized OID;CM-MAC=28:80:88:b3:8d:e0;CMTS-MAC=00:17:10:8d:d2:05;CM-QOS=1.1;CM-VER=3.1; Mon Mar 08 15:56:02 2021 Error (4) Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=28:80:88:b3:8d:e0;CMTS-MAC=00:17:10:8d:d2:05;CM-QOS=1.1;CM-VER=3.1; Mon Mar 08 15:56:02 2021 Error (4) Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=28:80:88:b3:8d:e0;CMTS-MAC=00:17:10:8d:d2:05;CM-QOS=1.1;CM-VER=3.1; Mon Mar 08 15:56:02 2021 Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=28:80:88:b3:8d:e0;CMTS-MAC=00:17:10:8d:d2:05;CM-QOS=1.1;CM-VER=3.1; Mon Mar 08 15:55:59 2021 Notice (6) Honoring MDD; IP provisioning mode = IPv4 Mon Mar 08 15:55:57 2021 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=28:80:88:b3:8d:e0;CMTS-MAC=00:17:10:8d:d2:05;CM-QOS=1.1;CM-VER=3.1; Mon Mar 08 15:55:57 2021 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:b3:8d:e0;CMTS-MAC=00:17:10:8d:d2:05;CM-QOS=1.1;CM-VER=3.1; Mon Mar 08 15:55:43 2021 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=28:80:88:b3:8d:e0;CMTS-MAC=00:17:10:8d:d2:05;CM-QOS=1.1;CM-VER=3.1; Mon Mar 08 15:55:13 2021 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:b3:8d:e0;CMTS-MAC=00:17:10:8d:d2:05;CM-QOS=1.1;CM-VER=3.1; Mon Mar 08 15:55:06 2021 Warning (5) DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=28:80:88:b3:8d:e0;CMTS-MAC=00:17:10:8d:d2:05;CM-QOS=1.1;CM-VER=3.1; Mon Mar 08 15:55:00 2021 Warning (5) MDD message timeout;CM-MAC=28:80:88:b3:8d:e0;CMTS-MAC=00:17:10:8d:d2:05;CM-QOS=1.1;CM-VER=3.1; Please post a copy and paste of the modems connection status page.
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.
https://community.netgear.com/t5/Cable-Modems-Routers/General-info-and-Troubleshooting-for-Cable-Modems/m-p/1530376#M12853Does the modem crash if not connected with the R9000 router online?
Connect a wired PC to the CM modem and reboot it and check.
Users can not FW update CM series modems. ISP can only do this.
Mines on V2.02.03. Ask escalated ISP support if they can update the modems FW.
I had major issues with the r9000 before, but finally got stable firmware and has been solid for a while. I will be calling Spectrum tomorrow to see what they say, but I am really curious about all those critical and warning messages in the log. Is that normal?
I have not tried bypassing the R9000, but can try...just did not want to leave network down until it crashes again.
Good Luck with Spectrum. Heard they are ones that are hard to deal with.
Ya you should not be seeing those messages that much. The ISP needs to help address this.
