Orbi - unstable connection, no event logs

[przemek3d]

My Orbi system is unstable, the wifi disconnects often. I am getting many unstable connection notifications while having video calls.

As a side note, I do not see any event logs. I saw them after I recreated my mesh from scratch, but they stopped showing after few days. Not sure if both issues are related.

I would be very grateful for help.

[FURRYe38]

What Orbi model do you have?

What Firmware version is currently loaded?
What is the Mfr and model# of the Internet Service Providers modem/ONT the NG router is connected too?
Be sure your using a good quality LAN cable between the modem and router. CAT6 is recommended.

What is the size of your home? Sq Ft?
What is the distance between the router and 📡 satellite(s)? 30 feet or more is recommended in between RBR and RBS📡 to begin with depending upon building materials when wirelessly connected.
https://kb.netgear.com/31029/Where-should-I-place-my-Orbi-satellite 📡

What channels are you using? Auto? Try Auto and 48 on 5Ghz. Or try setting manual channel 1, 6 or 11 on 2.4Ghz and 40 to 48 channel on 5Ghz.
Any Wifi Neighbors near by? If so, how many?

[przemek3d]

Hi FURRYe38, thanks for your help:

What Orbi model do you have? CBR750

What Firmware version is currently loaded? V4.6.5.8_2.0.54

What is the size of your home? Sq Ft? 3500

What is the distance between the router and satellite(s)? 30 feet or more, might be less than 30 feet in a straight line, but they are on separate floors, separated by walls - I can move it further

What channels are you using? Auto and 48 on 5Ghz

I did not answer the question about the modem router connection as this is one device. After I restarted the main router I saw the event logs for a day. Then they stopped appearing. There are also issues with NTP Settings. As I mentioned, the wifi connection becomes unstable - I need to manually switch between the primary and guest network, as one of them becomes unusable. Not sure if all of the above issues are related.

[FURRYe38]

Please post a copy and paste of the modems connection status and event log page. Use a different browser if needed.

https://kb.netgear.com/30007/How-do-I-obtain-the-cable-connection-information-from-a-NETGEAR-cable-m...
https://kb.netgear.com/30008/How-do-I-view-or-clear-the-event-logs-on-my-NETGEAR-cable-modem-or-mode...

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. 
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-Mod...
https://kb.netgear.com/24311/Power-level-guidelines-for-a-NETGEAR-cable-modem-router?article=24311
https://www.duckware.com/tech/solving-intermittent-cable-modem-issues.html

Try using channels 1 and 40. 

Try setting the transmit power to 50% on the CBR. Under Advanced Tab/Advanced Settings/Wireless Settings

[przemek3d]

Thanks for the help. I changed the channels to 1 and 40 and reduced the power to 50%. After reading the article, I noticed that one of the upstream channels might be problematic:

6

Locked

ATDMA

6

2560 Ksym/sec

40400000 Hz

49.8 dBmV

I also noticed quite often the following critical event.

Sep 16 2022 22:08:07

Critical (3)

No Ranging Response received - T3 time-out

I hope this is not an issue with my home wirings, as that would be hard to detect. There were multiple Comcast technicians checking my wirings and signal coming to the modem. They said it was ok.

I'm attaching the cable connection (sorry for the format, it is hard to attach something readable here) to the post and pasting event logs below (they were usually missing):

Time Priority Description
Sep 16 2022 12:53:14 Notice (6) CM-STATUS message sent. Event Type Code: 5
Sep 16 2022 12:53:14 Notice (6) CM-STATUS message sent. Event Type Code: 5
Sep 16 2022 12:53:14 Notice (6) CM-STATUS message sent. Event Type Code: 5
Sep 16 2022 12:53:14 Notice (6) CM-STATUS message sent. Event Type Code: 5
Sep 16 2022 12:53:14 Notice (6) CM-STATUS message sent. Event Type Code: 5
Sep 16 2022 12:53:14 Notice (6) CM-STATUS message sent. Event Type Code: 5
Sep 16 2022 12:53:14 Notice (6) CM-STATUS message sent. Event Type Code: 5
Sep 16 2022 12:53:14 Notice (6) CM-STATUS message sent. Event Type Code: 5
Sep 16 2022 12:53:14 Notice (6) CM-STATUS message sent. Event Type Code: 5
Sep 16 2022 13:06:58 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW
Sep 16 2022 13:06:59 Notice (6) CM-STATUS message sent. Event Type Code: 5
Sep 16 2022 13:26:56 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW
Sep 16 2022 13:27:01 Notice (6) CM-STATUS message sent. Event Type Code: 5
Sep 16 2022 13:32:56 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW
Sep 16 2022 13:33:18 Notice (6) CM-STATUS message sent. Event Type Code: 5
Sep 16 2022 13:38:55 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW
Sep 16 2022 13:38:58 Notice (6) CM-STATUS message sent. Event Type Code: 5
Sep 16 2022 13:48:54 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW
Sep 16 2022 13:48:55 Notice (6) CM-STATUS message sent. Event Type Code: 5
Sep 16 2022 22:08:07 Critical (3) No Ranging Response received - T3 time-out
Sep 16 2022 22:46:25 Notice (6) CM-STATUS message sent. Event Type Code: 5
Sep 17 2022 00:07:42 Alert (2) CM Certificate Error
Sep 17 2022 00:10:23 Notice (6) CM-STATUS message sent. Event Type Code: 5
Sep 17 2022 11:39:08 Critical (3) No Ranging Response received - T3 time-out
Sep 17 2022 11:41:16 Notice (6) CM-STATUS message sent. Event Type Code: 5
Sep 17 2022 13:23:18 Critical (3) No Ranging Response received - T3 time-out
Sep 17 2022 13:35:56 Notice (6) CM-STATUS message sent. Event Type Code: 5
Sep 17 2022 22:03:28 Critical (3) No Ranging Response received - T3 time-out
Sep 17 2022 22:11:48 Notice (6) CM-STATUS message sent. Event Type Code: 5
Sep 18 2022 00:07:41 Alert (2) CM Certificate Error
Sep 18 2022 00:08:17 Notice (6) CM-STATUS message sent. Event Type Code: 5
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Sep 18 2022 07:48:37 Warning (5) MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Sep 18 2022 07:48:37 Notice (6) TLV-11 - unrecognized OID
Sep 18 2022 07:48:37 Critical (3) Config File Rejected due to Invalid or Unexpected TLV 11
Sep 18 2022 07:48:42 Warning (5) REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value
Sep 18 2022 07:48:42 Warning (5) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW
Sep 18 2022 07:48:42 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW
Sep 18 2022 07:48:53 Alert (2) CM Certificate Error
Sep 18 2022 09:07:40 Notice (6) CM-STATUS message sent. Event Type Code: 5
Sep 18 2022 14:27:41 Warning (5) MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Sep 18 2022 14:27:41 Notice (6) TLV-11 - unrecognized OID
Sep 18 2022 14:27:41 Critical (3) Config File Rejected due to Invalid or Unexpected TLV 11
Sep 18 2022 14:27:45 Warning (5) REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value
Sep 18 2022 14:27:45 Warning (5) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW
Sep 18 2022 14:27:46 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW
Sep 18 2022 14:27:56 Alert (2) CM Certificate Error
Sep 18 2022 14:37:46 Notice (6) CM-STATUS message sent. Event Type Code: 5

[FURRYe38]

What the Correct and Un-Correctables look like on the cable connection status page? 

You have Criticals and Warnings that the ISP needs to look into.

If there are lots of numbers seen in the Correct and Un-correctables, this needs to be resolved as well as these should be mostly zeros seen here. 

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. Check all fittings and connections. 

Power levels are with in spec however could come up just a bit if the ISP can do that. 

https://kb.netgear.com/24311/Power-level-guidelines-for-a-NETGEAR-cable-modem-router?article=24311

[przemek3d]

The posts keep disappearing...

Startup Procedure

Procedure Status Comment Acquire Downstream Channel 423000000 Hz Locked Connectivity State Ok Operational Boot State Ok Operational Security Enabled BPI+ IP Provisioning Mode Honor MDD honorMdd(4)

Downstream Bonded Channels

Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectable 1 Locked QAM 256 1 423000000 Hz 0.0 dBmV 40.9 dB 81 85 2 Locked QAM 256 2 429000000 Hz -0.2 dBmV 40.9 dB 103 62 3 Locked QAM 256 3 435000000 Hz -0.5 dBmV 40.3 dB 114 55 4 Locked QAM 256 4 441000000 Hz -0.9 dBmV 40.9 dB 147 36 5 Locked QAM 256 5 447000000 Hz -0.7 dBmV 40.9 dB 108 64 6 Locked QAM 256 6 453000000 Hz -0.2 dBmV 40.3 dB 92 58 7 Locked QAM 256 7 459000000 Hz -0.5 dBmV 40.9 dB 1717 1470 8 Locked QAM 256 8 465000000 Hz -1.2 dBmV 40.9 dB 3285 4930 9 Locked QAM 256 9 471000000 Hz -2.9 dBmV 38.9 dB 20741 14793 10 Locked QAM 256 10 477000000 Hz -9.2 dBmV 34.3 dB 31909 73557 11 Locked QAM 256 11 483000000 Hz -8.5 dBmV 34.3 dB 55906 90530 12 Locked QAM 256 12 489000000 Hz -3.2 dBmV 38.9 dB 76213 46393 13 Locked QAM 256 13 495000000 Hz -1.5 dBmV 40.3 dB 30812 17514 14 Locked QAM 256 14 507000000 Hz -0.5 dBmV 40.9 dB 110 24 15 Locked QAM 256 15 513000000 Hz -0.2 dBmV 40.3 dB 52 0 16 Locked QAM 256 16 519000000 Hz -0.2 dBmV 40.9 dB 31 0 17 Locked QAM 256 17 525000000 Hz 0.0 dBmV 40.3 dB 21 11 18 Locked QAM 256 18 531000000 Hz 0.0 dBmV 40.3 dB 38 0 19 Locked QAM 256 19 543000000 Hz 0.2 dBmV 40.3 dB 27 0 20 Locked QAM 256 20 549000000 Hz 0.2 dBmV 40.3 dB 31 0 21 Locked QAM 256 21 555000000 Hz 0.2 dBmV 40.9 dB 28 4 22 Locked QAM 256 22 561000000 Hz 0.0 dBmV 40.3 dB 27 5 23 Locked QAM 256 23 567000000 Hz 0.0 dBmV 38.6 dB 26 0 24 Locked QAM 256 24 573000000 Hz 0.0 dBmV 38.9 dB 33 0 25 Locked QAM 256 25 579000000 Hz 0.0 dBmV 40.9 dB 29 0 26 Locked QAM 256 26 585000000 Hz 0.0 dBmV 40.3 dB 41 0 27 Locked QAM 256 27 591000000 Hz 0.2 dBmV 40.9 dB 42 0 28 Locked QAM 256 28 597000000 Hz 0.2 dBmV 40.3 dB 6 28 29 Locked QAM 256 29 603000000 Hz 0.0 dBmV 40.3 dB 38 0 30 Locked QAM 256 30 609000000 Hz 0.0 dBmV 40.3 dB 49 6 31 Locked QAM 256 31 615000000 Hz 0.0 dBmV 40.9 dB 6 28 32 Locked QAM 256 32 621000000 Hz 0.0 dBmV 40.9 dB 31 2

Upstream Bonded Channels

Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 1 2560 Ksym/sec 10400000 Hz 46.5 dBmV 2 Locked ATDMA 2 5120 Ksym/sec 16400000 Hz 43.8 dBmV 3 Locked ATDMA 3 5120 Ksym/sec 22800000 Hz 43.3 dBmV 4 Locked ATDMA 4 5120 Ksym/sec 29200000 Hz 43.8 dBmV 5 Locked ATDMA 5 5120 Ksym/sec 35600000 Hz 45.3 dBmV 6 Locked ATDMA 6 2560 Ksym/sec 40400000 Hz 48.8 dBmV 7 Not Locked N/A Unknown 0 Ksym/sec 0 Hz 0.0 dBmV 8 Not Locked N/A Unknown 0 Ksym/sec 0 Hz 0.0 dBmV

Downstream OFDM Channels

Channel Lock Status Modulation/Profile ID Channel ID Frequency Power SNR/MER Active Subcarrier Number Range Unerrored Codewords Correctable Codewords Uncorrectable Codewords 1 Locked 3 159 722000000 Hz -1.9 dBmV 40.9 dB 1246~2849 0 0 0 2 Not Locked 0 0 0 Hz 0.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.0 dBmV 2 Not Locked 0 0 0 Hz 0.0 dBmV

[FURRYe38]

Power levels are ok but there are too many correctables and un-correctables. These need to be zeros. Something the ISP should help resolve. Check the fittings and for splitters. Suggestions mentioned to help on this.