Orbi WiFi 7 RBE973
Reply

Re: CM2000/Obi/Xfinity constantly dropping connection

helpplease2021
Aspirant

CM2000/Orbi/Xfinity constantly dropping connection

(The Model question did not list CM2000, but I have a CM2000 and not the CM1200).

 

It's been over a year now with the Internet disconnecting dozens of times, day and night. Xfinity says it's my equipment, and NetGear says it's Xfinity!

 

Any help making sense of the event log would be greatly appreciated as I've tried everything I can think of.

 

I bought a Neatgear Nighthawk CM2000 and Orbi RBR850 with 2 RBS850's in an attempt to ensure that my issues should have nothing to do with too many devices or not good enough coverage for my house size. I also upgraded to GIG speed with Xfinity hoping that would help, but it's done nothing whatsoever.

 

There is pretty much zero craziness going on at the house (kids watch YouTube on a TV and play a game on Xbox while wife sometimes listens to music or watches YouTube on a tablet and I'm simply viewing "normal" websites like Google during the day). However, we do have a Ring video doorbell and 2 furnaces that are connected to wifi. There's also a couple wifi outlet plugs and alexa devices. Also 2 cell phones. That's why I bought "the best I could find" on modem/router and upgraded to Gig speed as I assume there has to be some way this stuff can work and the devices I bought should be able to handle it.

 

The Coax cable from the cabel box is brand new. There are zero splitters or connectors, I even cancelled TV to help figure this out. My modem/router are all in the middle of the room. The ethernet cord is brand new, etc.

 

I'm not sure what this stuff means, but the info I've gathered I'm hoping someone can make sense of:

 

8.8.8.8 ping statistics ---

823 packets transmitted, 690 packets received, 16.2% packet loss

round-trip min/avg/max/stddev = 11.101/21.427/1024.748/43.836 ms

 

The above caught one of the disconnects. The Internet worked again within 2 minutes without me having to do anything (which is usually the case, 30 seconds - 7 minutes showing not connected using a different connectivity monitor app that checks Google.com every 30 seconds and then it reconnects by itself somehow).

 

I factory reset the modem/router/satellites as well.

 

Earlier today modem log starting from when I factory reset around 8AM and showing 11:23 where it disconnected for literally less than a minute (which is exactly what just happened now at 1:20PM (another 30-60 second not connected and then okay).

 

 

Time

Priority

Description

Mon Feb 22 11:23:21 2021

(Critical (3))

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;

Mon Feb 22 11:23:21 2021

(Warning (5))

Dynamic Range Window violation

Mon Feb 22 11:23:21 2021

(Warning (5))

RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;

Mon Feb 22 11:23:20 2021

(Critical (3))

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;

Mon Feb 22 11:23:17 2021

(Warning (5))

Dynamic Range Window violation

Mon Feb 22 11:23:17 2021

(Warning (5))

RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;

Mon Feb 22 11:23:17 2021

(Warning (5))

Dynamic Range Window violation

Mon Feb 22 11:23:17 2021

(Warning (5))

RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;

Mon Feb 22 11:23:17 2021

(Warning (5))

Dynamic Range Window violation

Mon Feb 22 11:23:17 2021

(Warning (5))

RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;

Mon Feb 22 11:23:16 2021

(Critical (3))

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;

Mon Feb 22 08:10:16 2021

(Warning (5))

Dynamic Range Window violation

Mon Feb 22 08:10:16 2021

(Warning (5))

RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;

Mon Feb 22 08:10:10 2021

(Critical (3))

SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;

Mon Feb 22 08:10:10 2021

(Notice (6))

DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;

Mon Feb 22 08:10:09 2021

(Notice (6))

TLV-11 - unrecognized OID;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;

Mon Feb 22 08:09:59 2021

(Notice (6))

Honoring MDD; IP provisioning mode = IPv6

Mon Feb 22 08:09:51 2021

(Critical (3))

No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;

Mon Feb 22 08:09:43 2021

(Warning (5))

Lost MDD Timeout;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

Mon Feb 22 08:09:36 2021

(Critical (3))

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

Mon Feb 22 08:09:35 2021

(Warning (5))

Lost MDD Timeout;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

Mon Feb 22 08:09:22 2021

(Critical (3))

SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;

Mon Feb 22 08:09:22 2021

(Notice (6))

DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;

Mon Feb 22 08:09:21 2021

(Critical (3))

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;

Mon Feb 22 08:09:15 2021

(Notice (6))

TLV-11 - unrecognized OID;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;

Time Not Established

(Notice (6))

Honoring MDD; IP provisioning mode = IPv6

Time Not Established

(Critical (3))

No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;

Time Not Established

(Critical (3))

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

Time Not Established

(Warning (5))

Lost MDD Timeout;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

Time Not Established

(Critical (3))

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

 

Model: CM1200|Nighthawk Multi-Gig Speed Cable Modem
Message 1 of 4
helpplease2021
Aspirant

Re: CM2000/Obi/Xfinity constantly dropping connection

 

12:45 happened again and then fixed itself within 2 minutes. Event log showed:

 

Mon Feb 22 12:45:48 2021

(Critical (3))

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;

 

 

Mon Feb 22 12:46:52 2021

(Notice (6))

CM-STATUS message sent. Event Type Code: 7; Chan ID: 4; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;

Mon Feb 22 12:46:52 2021

(Critical (3))

No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;

Mon Feb 22 12:46:49 2021

(Critical (3))

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;

Mon Feb 22 12:46:48 2021

(Critical (3))

No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;

Mon Feb 22 12:46:38 2021

(Critical (3))

16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;

Mon Feb 22 12:46:38 2021

(Critical (3))

Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;

Mon Feb 22 12:46:38 2021

(Critical (3))

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;

 

Time

Priority

Description

Mon Feb 22 12:48:00 2021

(Notice (6))

CM-STATUS message sent. Event Type Code: 8; Chan ID: 2 4; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;

Mon Feb 22 12:47:25 2021

(Critical (3))

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;

Mon Feb 22 12:47:25 2021

(Warning (5))

Dynamic Range Window violation

Mon Feb 22 12:47:25 2021

(Warning (5))

RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;

Mon Feb 22 12:47:24 2021

(Critical (3))

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;

Mon Feb 22 12:47:23 2021

(Notice (6))

CM-STATUS message sent. Event Type Code: 7; Chan ID: 2 4; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;

Mon Feb 22 12:47:23 2021

(Warning (5))

Dynamic Range Window violation

Mon Feb 22 12:47:23 2021

(Warning (5))

RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;

Mon Feb 22 12:47:23 2021

(Warning (5))

Dynamic Range Window violation

Mon Feb 22 12:47:23 2021

(Warning (5))

RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;

Mon Feb 22 12:47:23 2021

(Warning (5))

Dynamic Range Window violation

Mon Feb 22 12:47:23 2021

(Warning (5))

RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;

Mon Feb 22 12:47:23 2021

(Warning (5))

Dynamic Range Window violation

Mon Feb 22 12:47:23 2021

(Warning (5))

RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;

Mon Feb 22 12:47:21 2021

(Critical (3))

No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;

Mon Feb 22 12:47:13 2021

(Critical (3))

16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;

Mon Feb 22 12:47:13 2021

(Critical (3))

Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;

Mon Feb 22 12:47:13 2021

(Critical (3))

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;

Mon Feb 22 12:47:02 2021

(Critical (3))

No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;

 

 

Mon Feb 22 13:19:40 2021(Critical (3))Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;
Mon Feb 22 13:12:18 2021(Notice (6))CM-STATUS message sent. Event Type Code: 8; Chan ID: 2 4; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;
Mon Feb 22 13:11:44 2021(Notice (6))CM-STATUS message sent. Event Type Code: 7; Chan ID: 4; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;
Mon Feb 22 13:11:28 2021(Critical (3))Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;
Mon Feb 22 13:11:26 2021(Critical (3))No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;
Mon Feb 22 13:11:26 2021(Critical (3))Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;
Mon Feb 22 13:11:26 2021(Warning (5))Dynamic Range Window violation
Mon Feb 22 13:11:26 2021(Warning (5))RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;
Mon Feb 22 13:11:26 2021(Critical (3))Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;
Mon Feb 22 13:11:14 2021(Notice (6))CM-STATUS message sent. Event Type Code: 7; Chan ID: 4; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;
Mon Feb 22 13:11:12 2021(Critical (3))No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;
Mon Feb 22 13:10:58 2021(Critical (3))16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;
Mon Feb 22 13:10:58 2021(Critical (3))Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;
Mon Feb 22 13:10:58 2021(Critical (3))Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;
Mon Feb 22 12:48:00 2021(Notice (6))CM-STATUS message sent. Event Type Code: 8; Chan ID: 2 4; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;
Mon Feb 22 12:47:25 2021(Critical (3))Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;
Mon Feb 22 12:47:25 2021(Warning (5))Dynamic Range Window violation
Mon Feb 22 12:47:25 2021(Warning (5))RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;
Mon Feb 22 12:47:24 2021(Critical (3))Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;
Mon Feb 22 12:47:23 2021(Notice (6))CM-STATUS message sent. Event Type Code: 7; Chan ID: 2 4; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;
Mon Feb 22 12:47:23 2021(Warning (5))Dynamic Range Window violation
Mon Feb 22 12:47:23 2021(Warning (5))RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;
Mon Feb 22 12:47:23 2021(Warning (5))Dynamic Range Window violation
Mon Feb 22 12:47:23 2021(Warning (5))RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;
Mon Feb 22 12:47:23 2021(Warning (5))Dynamic Range Window violation
Mon Feb 22 12:47:23 2021(Warning (5))RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;
Mon Feb 22 12:47:23 2021(Warning (5))Dynamic Range Window violation
Mon Feb 22 12:47:23 2021(Warning (5))RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;
Mon Feb 22 12:47:21 2021(Critical (3))No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;
Mon Feb 22 12:47:13 2021(Critical (3))16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;
Mon Feb 22 12:47:13 2021(Critical (3))Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;
Mon Feb 22 12:47:13 2021(Critical (3))Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;
Mon Feb 22 12:47:02 2021(Critical (3))No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:9f:5f:58;CMTS-MAC=00:01:5c:6a:ac:48;CM-QOS=1.1;CM-VER=3.1;

 

 

And yet again another 30 second disconnect. It's just the basic 1 ring video doorbell + 2 furnaces / nest thermostats + 2 cell phones not being used at the time + couple alexa devices also not being used and a couple wifi plugs. Other than the ring video doorbell I don't think any of our devices would be causing excessive use that's a problem for the equipment we have but maybe I'm wrong? 

 

Thank you SO MUCH for any help!

Message 2 of 4
plemans
Guru

Re: CM2000/Obi/Xfinity constantly dropping connection

Your modem is indicating line issues. Those dynamic range window violations indicate your power levels going out of spec by a ways. 

 

Message 3 of 4
Bloat
Aspirant

Re: CM2000/Orbi/Xfinity constantly dropping connection

Hi

I have a Netgear CM1200 modem Firmware 2.02.03

 

At the bottom of your log file there is a check box "Extended Upstream Transmit Power"  that may or may not be available to you...it depends on the ISP. Make sure it is checked and reboot modem, router, it worked for me. Best of Luck.

Model: CM1200|Nighthawk Multi-Gig Speed Cable Modem
Message 4 of 4
Top Contributors
Discussion stats
  • 3 replies
  • 1296 views
  • 0 kudos
  • 3 in conversation
Announcements

Orbi WiFi 7