Orbi WiFi 7 RBE973
Reply

CM1200 V1.02.01 On Spectrum - Keeps Crashing - is it mys ervice or device?

sh0rty
Tutor

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 Channel399000000 HzLocked
Connectivity StateOKOperational
Boot StateOKOperational
SecurityEnabledBPI+
IP Provisioning ModeHonor MDDhonorMdd(4)

 

 

 

Model: CM1200|Nighthawk Multi-Gig Speed Cable Modem
Message 1 of 8
sh0rty
Tutor

Re: CM1200 V1.02.01 On Spectrum - Keeps Crashing - is it mys ervice or device?

Time Priority Description
Mon Mar 08 17:04:52 2021Critical (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 2021Critical (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 2021Critical (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 2021Critical (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 2021Critical (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 2021Critical (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 2021Critical (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 2021Critical (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 2021Critical (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 2021Critical (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 2021Critical (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 2021Critical (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 2021Critical (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 2021Critical (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 2021Critical (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 2021Notice (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 2021Notice (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 2021Critical (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 2021Critical (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 2021Critical (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 2021Critical (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 2021Critical (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 2021Critical (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 2021Critical (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 2021Critical (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 2021Critical (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 2021Critical (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 2021Warning (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 2021Notice (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 2021Notice (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 2021Error (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 2021Error (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 2021Warning (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 2021Notice (6)Honoring MDD; IP provisioning mode = IPv4
Mon Mar 08 15:55:57 2021Critical (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 2021Critical (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 2021Critical (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 2021Critical (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 2021Warning (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 2021Warning (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;
Message 2 of 8
FURRYe38
Guru

Re: CM1200 V1.02.01 On Spectrum - Keeps Crashing - is it mys ervice or device?

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-Mod...

 

Does 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. 

My Setup ISP SparkLight | Internet Cable 1000↓/50↑ CAX80 Modem Mode  | Wifi Router RAXE500 and RBKE963; Router mode | Switches NG GS105/8, GS308v3, GS110MX and XS505M | Additional NG HW: C7800/CAX30/CAX80/CM1100/CM1200/CM2000, Orbi: CBK40, CBK752, RBK50, RBK853, RBK752, RBK953, SXK30 | NightHawk: MK63, R7000, R7800, R7960P, R8000, RAXE500, RAX120v2, RAX50v2, XR450/500/700/1000, EX7500/EX7700

Message 3 of 8
sh0rty
Tutor

Re: CM1200 V1.02.01 On Spectrum - Keeps Crashing - is it mys ervice or device?

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.

Message 4 of 8
FURRYe38
Guru

Re: CM1200 V1.02.01 On Spectrum - Keeps Crashing - is it mys ervice or device?

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. 

My Setup ISP SparkLight | Internet Cable 1000↓/50↑ CAX80 Modem Mode  | Wifi Router RAXE500 and RBKE963; Router mode | Switches NG GS105/8, GS308v3, GS110MX and XS505M | Additional NG HW: C7800/CAX30/CAX80/CM1100/CM1200/CM2000, Orbi: CBK40, CBK752, RBK50, RBK853, RBK752, RBK953, SXK30 | NightHawk: MK63, R7000, R7800, R7960P, R8000, RAXE500, RAX120v2, RAX50v2, XR450/500/700/1000, EX7500/EX7700

Message 5 of 8
sh0rty
Tutor

Re: CM1200 V1.02.01 On Spectrum - Keeps Crashing - is it mys ervice or device?

For whatever reason it keeps blocking me from posting modem status. I will try again later.

 

Message 6 of 8
sh0rty
Tutor

Re: CM1200 V1.02.01 On Spectrum - Keeps Crashing - is it mys ervice or device?

So, I got nowhere with getting resolution using spectrum so bit the bullet and bought a new modem. I went with an Arris S33 and after 2 days it has been rock solid with zero drops. I have been using netgear modems and routers for years, but now having to go back and forth previously with my R9000 and now this CM1200 I think I am moving on.

 

Message 7 of 8
FURRYe38
Guru

Re: CM1200 V1.02.01 On Spectrum - Keeps Crashing - is it mys ervice or device?

Shame Spectrum won't do anything for user owned modems. There one ISP that seems to avoid user own modems. Find someone on a different ISP service that you could sell the CM1200 too if you feel. 


Good Luck. 

My Setup ISP SparkLight | Internet Cable 1000↓/50↑ CAX80 Modem Mode  | Wifi Router RAXE500 and RBKE963; Router mode | Switches NG GS105/8, GS308v3, GS110MX and XS505M | Additional NG HW: C7800/CAX30/CAX80/CM1100/CM1200/CM2000, Orbi: CBK40, CBK752, RBK50, RBK853, RBK752, RBK953, SXK30 | NightHawk: MK63, R7000, R7800, R7960P, R8000, RAXE500, RAX120v2, RAX50v2, XR450/500/700/1000, EX7500/EX7700

Message 8 of 8
Top Contributors
Discussion stats
  • 7 replies
  • 832 views
  • 0 kudos
  • 2 in conversation
Announcements

Orbi WiFi 7