NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
CBR750 having issued with Cox after move
I had the system I have now with cox at a different address and never had any issues with it. Now I have moved and it is terrible and none of the techs can figure out why.
Possible new location has some ISP signal and line issues.
Did the CBR work ok at the prior location?
What Firmware version is currently loaded?
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
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
This setup was working well before the move. I have left the diag and the event log below. V4.6.14.4_2.3.12 is the firmware version. Cox checked the lines running to the house with no clear conclusion on whether the lines were good. The tech said there was some noise but it probably will work fine then left his number. Thank you for any help you can provide
Cable Diagnostic
Status: Good
Action: Your setup looks fine. If you are still experience an internet issue, the Netgear Cable Knowledge Base can provide additional troubleshooting info.
Internet Access: Good
Downstream Status: Good
Downstream Power Level: Good
Downstream SNR: Good
Upstream Status: Good
Upstream Power Level: Good
Current time: Mon Feb 20 13:50:15 2023
Startup Procedure
Acquire Downstream Channel: 381000000 Hz Locked
Connectivity State: Ok Operational
Boot State: Ok Operational
Security: Enabled BPI+
IP Provisioning Mode: Honor MDD honorMdd(4)
Downstream Bonded Channels
Channel LockedStatus Modulation ChannelID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM 256 33 357000000 Hz 1.9 40.3 0 0
2 Locked QAM 256 34 363000000 Hz 1.9 40.3 0 0
3 Locked QAM 256 35 369000000 Hz 2.0 40.3 0 0
4 Locked QAM 256 36 375000000 Hz 2.0 38.9 0 0
5 Locked QAM 256 37 381000000 Hz 2.0 38.9 0 0
6 Locked QAM 256 38 387000000 Hz 2.2 38.9 0 0
7 Locked QAM 256 39 393000000 Hz 2.2 38.9 0 0
8 Locked QAM 256 40 399000000 Hz 2.5 40.3 0 0
9 Locked QAM 256 41 405000000 Hz 2.7 40.9 0 0
10 Locked QAM 256 42 411000000 Hz 2.5 40.3 0 0
11 Locked QAM 256 43 417000000 Hz 2.5 38.9 0 0
12 Locked QAM 256 44 423000000 Hz 2.5 38.9 0 0
13 Locked QAM 256 45 429000000 Hz 2.5 38.9 0 0
14 Locked QAM 256 46 435000000 Hz 2.7 38.9 0 0
15 Locked QAM 256 47 441000000 Hz 3.0 40.3 0 0
16 Locked QAM 256 48 447000000 Hz 3.2 38.9 0 0
17 Locked QAM 256 1 783000000 Hz -0.4 36.3 5 0
18 Locked QAM 256 2 789000000 Hz -0.4 36.3 0 0
19 Locked QAM 256 3 795000000 Hz -0.7 36.3 0 0
20 Locked QAM 256 4 801000000 Hz -1.0 36.3 0 0
21 Locked QAM 256 5 807000000 Hz -1.4 36.6 7 0
22 Locked QAM 256 6 813000000 Hz -1.5 36.3 6 0
23 Locked QAM 256 7 819000000 Hz -1.7 36.3 4 0
24 Locked QAM 256 8 825000000 Hz -2.0 35.7 4 0
25 Locked QAM 256 9 831000000 Hz -2.2 36.3 0 0
26 Locked QAM 256 10 837000000 Hz -2.0 35.7 0 0
27 Locked QAM 256 11 843000000 Hz -2.0 36.3 0 0
28 Locked QAM 256 12 849000000 Hz -1.5 35.7 0 0
29 Locked QAM 256 13 855000000 Hz -1.2 35.7 0 0
30 Locked QAM 256 14 861000000 Hz -1.2 35.7 0 0
31 Locked QAM 256 15 867000000 Hz -1.5 35.7 0 0
32 Locked QAM 256 16 873000000 Hz -1.7 35.5 0 0
Upstream Bonded Channels
Channel LockedStatus ChannelType ChannelID SymbolRate Frequency Power
1 Locked ATDMA 1 5120 17400000 Hz 38.5
2 Locked ATDMA 2 5120 23900000 Hz 39.0
3 Locked ATDMA 3 5120 30300000 Hz 39.0
4 Locked ATDMA 4 5120 36700000 Hz 39.5
5 Not Locked N/A 0 0 0 Hz 0.0
6 Not Locked N/A 0 0 0 Hz 0.0
7 Not Locked N/A 0 0 0 Hz 0.0
8 Not Locked N/A 0 0 0 Hz 0.0
Downstream OFDM Channels
Channel LockedStatus ProfileID ChannelID Frequency Power SNR/MER ActiveSubcarrier Unerror Correctable Uncorrectable
1 Locked 3 159 300000000 Hz 1.5 dBmV 42.5 dB 2216~5975 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 LockedStatus ProfileID ChannelID Frequency Power
1 Locked 0 6 36800000 Hz 36.5 dBmV
2 Not Locked 0 0 0 Hz 0.0 dBmV
Event Log
Time Priority Description
Feb 20 2023 10:17:15 Critical Config File Rejected due to Invalid or Unexpected TLV 11
Feb 20 2023 10:17:15 Critical Config File Rejected due to Invalid or Unexpected TLV 11
Feb 20 2023 10:17:15 Critical Config File Rejected due to Invalid or Unexpected TLV 11
Feb 20 2023 10:17:15 Critical Config File Rejected due to Invalid or Unexpected TLV 11
Feb 20 2023 10:17:15 Critical Config File Rejected due to Invalid or Unexpected TLV 11
Feb 20 2023 10:17:15 Critical Config File Rejected due to Invalid or Unexpected TLV 11
Feb 20 2023 10:17:15 Critical Config File Rejected due to Invalid or Unexpected TLV 11
Feb 20 2023 10:17:15 Critical Config File Rejected due to Invalid or Unexpected TLV 11
Feb 20 2023 10:17:15 Critical Config File Rejected due to Invalid or Unexpected TLV 11
Feb 20 2023 10:17:15 Critical Config File Rejected due to Invalid or Unexpected TLV 11
Feb 20 2023 10:17:15 Critical Config File Rejected due to Invalid or Unexpected TLV 11
Feb 20 2023 10:17:15 Critical Config File Rejected due to Invalid or Unexpected TLV 11
Feb 20 2023 10:17:15 Critical Config File Rejected due to Invalid or Unexpected TLV 11
Feb 20 2023 10:17:15 Critical Config File Rejected due to Invalid or Unexpected TLV 11
Feb 20 2023 10:17:15 Critical Config File Rejected due to Invalid or Unexpected TLV 11
Feb 20 2023 10:17:15 Critical Config File Rejected due to Invalid or Unexpected TLV 11
Feb 20 2023 10:17:15 Critical Config File Rejected due to Invalid or Unexpected TLV 11
Feb 20 2023 10:17:15 Critical Config File Rejected due to Invalid or Unexpected TLV 11
Feb 20 2023 10:17:15 Critical Config File Rejected due to Invalid or Unexpected TLV 11
Feb 20 2023 10:17:19 Warning REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value
Feb 20 2023 10:17:19 Warning RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW
Feb 20 2023 10:17:19 Warning RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW
Feb 20 2023 10:17:29 Alert CM Certificate Error
Feb 20 2023 10:17:32 Warning DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value
Feb 20 2023 10:17:32 Warning RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW
Feb 20 2023 10:17:32 Notice US profile assignment change. US Chan ID: 6
Feb 20 2023 10:17:40 Notice CM-STATUS message sent. Event Type Code: 3
Feb 20 2023 10:19:10 Notice US profile assignment change. US Chan ID: 6
Feb 20 2023 10:20:03 Warning RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW
Feb 20 2023 10:22:31 Notice US profile assignment change. US Chan ID: 6
Feb 20 2023 10:30:02 Warning RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW
Feb 20 2023 10:30:17 Warning DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value
Feb 20 2023 10:30:17 Warning RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW
Feb 20 2023 10:30:17 Notice US profile assignment change. US Chan ID: 6
Feb 20 2023 10:30:17 Warning RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW
Feb 20 2023 10:30:21 Critical Unicast Ranging Received Abort Response - initializing MAC
Feb 20 2023 10:30:21 Critical No Ranging Response received - T3 time-out
Feb 20 2023 10:32:18 Critical Unicast Ranging Received Abort Response - initializing MAC
Feb 20 2023 10:32:18 Critical No Ranging Response received - T3 time-out
Feb 20 2023 10:33:42 Warning RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW
Feb 20 2023 10:35:11 Warning MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Feb 20 2023 10:35:11 Notice TLV-11 - unrecognized OID
Feb 20 2023 10:35:11 Critical Config File Rejected due to Invalid or Unexpected TLV 11
Feb 20 2023 10:35:15 Warning REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value
Feb 20 2023 10:35:15 Warning RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW
Feb 20 2023 10:35:15 Warning RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW
Feb 20 2023 10:35:15 Critical No Ranging Response received - T3 time-out
Feb 20 2023 10:35:16 Warning RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW
Feb 20 2023 10:35:16 Critical No Ranging Response received - T3 time-out
Feb 20 2023 10:35:17 Warning RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW
Feb 20 2023 10:35:26 Alert CM Certificate Error
Feb 20 2023 10:35:29 Warning DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value
Feb 20 2023 10:35:29 Warning RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW
Feb 20 2023 10:35:29 Notice US profile assignment change. US Chan ID: 6
Feb 20 2023 10:38:06 Warning RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW
Feb 20 2023 10:38:48 Notice US profile assignment change. US Chan ID: 6
Feb 20 2023 10:58:24 Critical No Ranging Response received - T3 time-out
Feb 20 2023 10:59:11 Notice US profile assignment change. US Chan ID: 6
Feb 20 2023 10:17:15 Critical (3) Config File Rejected due to Invalid or Unexpected TLV 11
Feb 20 2023 10:17:15 Critical (3) Config File Rejected due to Invalid or Unexpected TLV 11
Feb 20 2023 10:17:15 Critical (3) Config File Rejected due to Invalid or Unexpected TLV 11
Feb 20 2023 10:17:15 Critical (3) Config File Rejected due to Invalid or Unexpected TLV 11
Feb 20 2023 10:17:15 Critical (3) Config File Rejected due to Invalid or Unexpected TLV 11
Feb 20 2023 10:17:15 Critical (3) Config File Rejected due to Invalid or Unexpected TLV 11
Feb 20 2023 10:17:15 Critical (3) Config File Rejected due to Invalid or Unexpected TLV 11
Feb 20 2023 10:17:15 Critical (3) Config File Rejected due to Invalid or Unexpected TLV 11
Feb 20 2023 10:17:15 Critical (3) Config File Rejected due to Invalid or Unexpected TLV 11
Feb 20 2023 10:17:15 Critical (3) Config File Rejected due to Invalid or Unexpected TLV 11
Feb 20 2023 10:17:15 Critical (3) Config File Rejected due to Invalid or Unexpected TLV 11
Feb 20 2023 10:17:15 Critical (3) Config File Rejected due to Invalid or Unexpected TLV 11
Feb 20 2023 10:17:15 Critical (3) Config File Rejected due to Invalid or Unexpected TLV 11
Feb 20 2023 10:17:15 Critical (3) Config File Rejected due to Invalid or Unexpected TLV 11
Feb 20 2023 10:17:15 Critical (3) Config File Rejected due to Invalid or Unexpected TLV 11
Feb 20 2023 10:17:15 Critical (3) Config File Rejected due to Invalid or Unexpected TLV 11
Feb 20 2023 10:17:15 Critical (3) Config File Rejected due to Invalid or Unexpected TLV 11
Feb 20 2023 10:17:15 Critical (3) Config File Rejected due to Invalid or Unexpected TLV 11
Feb 20 2023 10:17:15 Critical (3) Config File Rejected due to Invalid or Unexpected TLV 11
Feb 20 2023 10:17:19 Warning (5) REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value
Feb 20 2023 10:17:19 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW
Feb 20 2023 10:17:19 Warning (5) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW
Feb 20 2023 10:17:29 Alert (2) CM Certificate Error
Feb 20 2023 10:17:32 Warning (5) DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value
Feb 20 2023 10:17:32 Warning (5) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW
Feb 20 2023 10:17:32 Notice (6) US profile assignment change. US Chan ID: 6
Feb 20 2023 10:17:40 Notice (6) CM-STATUS message sent. Event Type Code: 3
Feb 20 2023 10:19:10 Notice (6) US profile assignment change. US Chan ID: 6
Feb 20 2023 10:20:03 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW
Feb 20 2023 10:22:31 Notice (6) US profile assignment change. US Chan ID: 6
Feb 20 2023 10:30:02 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW
Feb 20 2023 10:30:17 Warning (5) DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value
Feb 20 2023 10:30:17 Warning (5) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW
Feb 20 2023 10:30:17 Notice (6) US profile assignment change. US Chan ID: 6
Feb 20 2023 10:30:17 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW
Feb 20 2023 10:30:21 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
Feb 20 2023 10:30:21 Critical (3) No Ranging Response received - T3 time-out
Feb 20 2023 10:32:18 Critical (3) Unicast Ranging Received Abort Response - initializing MAC
Feb 20 2023 10:32:18 Critical (3) No Ranging Response received - T3 time-out
Feb 20 2023 10:33:42 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW
Feb 20 2023 10:35:11 Warning (5) MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Feb 20 2023 10:35:11 Notice (6) TLV-11 - unrecognized OID
Feb 20 2023 10:35:11 Critical (3) Config File Rejected due to Invalid or Unexpected TLV 11
Feb 20 2023 10:35:15 Warning (5) REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value
Feb 20 2023 10:35:15 Warning (5) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW
Feb 20 2023 10:35:15 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW
Feb 20 2023 10:35:15 Critical (3) No Ranging Response received - T3 time-out
Feb 20 2023 10:35:16 Warning (5) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW
Feb 20 2023 10:35:16 Critical (3) No Ranging Response received - T3 time-out
Feb 20 2023 10:35:17 Warning (5) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW
Feb 20 2023 10:35:26 Alert (2) CM Certificate Error
Feb 20 2023 10:35:29 Warning (5) DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value
Feb 20 2023 10:35:29 Warning (5) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW
Feb 20 2023 10:35:29 Notice (6) US profile assignment change. US Chan ID: 6
Feb 20 2023 10:38:06 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW
Feb 20 2023 10:38:48 Notice (6) US profile assignment change. US Chan ID: 6
Feb 20 2023 10:58:24 Critical (3) No Ranging Response received - T3 time-out
Feb 20 2023 10:59:11 Notice (6) US profile assignment change. US Chan ID: 6
Cable Connections page looks ok.
However the events logs, you have lots of Criticals, Alerts and Warnings that the ISP needs to review and resolve.
Is there anything specific I can ask them to address. They have been to my house 6 times now and they've done little more than swap the modem. I had hoped they would TDR the line or something more than a network analyzer that tells the same information about data transfer that the modem does. I do not understand what the information the notice, warning, and critical flags are trying to convey.
The ISP should know what the event logs means are:
https://highspeed.tips/docsis-events
They need to review and resolve them. That's on there side.