Orbi WiFi 7 RBE973
Reply

New CAX80 has poor cable connection issues.

Harunkingcool
Aspirant

New CAX80 has poor cable connection issues.

Hello, I very recently moved into a new place where I decided to buy my own modem router instead of renting one. I picked up a brand new CAX80 from Best Buy and went home to set it up. I plugged the nighthawk straight into the wall with both the coaxial cable and power supply. The people before me left there modem router which was a "Arris TG1682G" and so I unplugged there's to plug in mine in the same spot. I went through the rest of the steps and downloaded the nighthawk app on my phone. I next went to go check it on routerlogin.com and I see that under "Cable Connection" it says that the status is "Poor", I click on it and it comes up with some cable diagnostics; now I'm not that good at reading them but I do see that the "Internet Access:" is green and the "Downstream Status:" is green but the "Upstream Status:" is yellow. I believe it not to be a problem with the power level but I do not know. Next I go and do a couple of speed tests on the app and I end up getting around 250-350 Mbps for download and only 10-15 Mbps for upload, now it says that this is "extremely fast!" but I strongly think both of these are much lower than what I should be getting because my internet service provider (ISP) is Xfinity and I am paying for the 1.2 Gbps plan (1200 Mbps), now I did some research and I see that you don't actually get that high of a number but I expect it to be at least be in the 700's for download and 250's for upload. The other thing I noticed is that on the nighthawk it self all the lights that are usually on are white (which is fine) but the upstream and downstream are blinking and not solid which may tell you something. I tried rebooting it once with the app and also unplugging it from the wall which didn't seem to do much. I really hope to get this working but if I can't I will have to return it and find something else.

 

My Firmware Version is: V2.1.5.2

My ISP and plan is: Xfinity and the 1.2 Gbps plan

My modem router is plugged straight into the wall

 

\/ My cable diagnostics \/

 

Cable Diagnostic

Status: Poor

Action:
[Partial Service]
If the Partial Service mode does not go away within a few hours (Click the Refresh button after each step):
1) Make sure the coaxial cable is tightly connected.
2) Remove any unnecessary splitters.
3) Replace any required ones.
4) Contact your service provider for troubleshooting help.

Internet Access: Good

Downstream Status: Good

Downstream Power Level: Good

Downstream SNR: Good

Upstream Status: Poor

Partial Service: Poor
Cable modem is in partial service mode. Your service provider might be under maintenance. Most of the time it won't affect your traffic and will automatically clear when work is complete.

Upstream Power Level: Good


Current time: Mon Aug 07 15:59:28 2023

Startup Procedure
Acquire Downstream Channel: 507 MHz Locked
Connectivity State: OK Operational
Boot State: OK Operational
Security: Enabled BPI+


Downstream Bonded Channels
Channel LockedStatus Modulation ChannelID Frequency Power SNR Correctables Uncorrectables
1 Locked 256 QAM 13 507000000 Hz -7.7 dBmV 38.6 dB 6862 2225
2 Locked 256 QAM 1 423000000 Hz -6.5 dBmV 39.5 dB 5293 1270
3 Locked 256 QAM 2 429000000 Hz -6.4 dBmV 39.5 dB 5095 1319
4 Locked 256 QAM 3 435000000 Hz -6.7 dBmV 39.3 dB 5286 1345
5 Locked 256 QAM 4 441000000 Hz -6.3 dBmV 39.3 dB 5200 1384
6 Locked 256 QAM 5 453000000 Hz -6.1 dBmV 39.4 dB 5116 1297
7 Locked 256 QAM 6 459000000 Hz -6.3 dBmV 39.3 dB 4919 1293
8 Locked 256 QAM 7 465000000 Hz -6.8 dBmV 39.2 dB 5062 1441
9 Locked 256 QAM 8 471000000 Hz -7 dBmV 39.1 dB 5334 1467
10 Locked 256 QAM 9 477000000 Hz -6.8 dBmV 39.1 dB 5256 1434
11 Locked 256 QAM 10 483000000 Hz -6.6 dBmV 39.1 dB 5342 1333
12 Locked 256 QAM 11 489000000 Hz -6.7 dBmV 39.1 dB 5266 1364
13 Locked 256 QAM 12 495000000 Hz -7 dBmV 38.9 dB 5189 1307
14 Locked 256 QAM 14 513000000 Hz -7.6 dBmV 38.7 dB 5289 1410
15 Locked 256 QAM 15 519000000 Hz -7.3 dBmV 38.2 dB 424 625
16 Locked 256 QAM 16 525000000 Hz -7.3 dBmV 38.7 dB 3723 9727
17 Locked 256 QAM 17 531000000 Hz -7.6 dBmV 38.6 dB 1897 5875
18 Locked 256 QAM 18 537000000 Hz -8 dBmV 38.4 dB 6957 1657
19 Locked 256 QAM 19 543000000 Hz -7.8 dBmV 38.5 dB 4682 1058
20 Locked 256 QAM 20 549000000 Hz -7.9 dBmV 38.5 dB 4721 1134
21 Locked 256 QAM 21 555000000 Hz -7.9 dBmV 38.6 dB 4720 1045
22 Locked 256 QAM 22 561000000 Hz -7.8 dBmV 38.5 dB 4620 1111
23 Locked 256 QAM 23 567000000 Hz -8.1 dBmV 38.4 dB 4791 1249
24 Locked 256 QAM 24 573000000 Hz -7.6 dBmV 38.5 dB 4864 1314
25 Locked 256 QAM 25 579000000 Hz -8.1 dBmV 38.3 dB 5018 1371
26 Locked 256 QAM 26 585000000 Hz -7.8 dBmV 38.4 dB 5568 1526
27 Locked 256 QAM 27 591000000 Hz -8 dBmV 38.3 dB 7407 2129
28 Locked 256 QAM 42 399000000 Hz -7.1 dBmV 39.3 dB 6063 1824
29 Locked 256 QAM 43 405000000 Hz -7.2 dBmV 39.3 dB 6009 1699
30 Locked 256 QAM 44 411000000 Hz -6.5 dBmV 39.5 dB 5543 1457
31 Locked 256 QAM 45 417000000 Hz -6.3 dBmV 39.6 dB 5329 1447
32 Not Locked Unknown 0 0 Hz 0.0 0.0 0 0


Upstream Bonded Channels
Channel LockedStatus ChannelType ChannelID SymbolRate Frequency Power
1 Locked ATDMA 10 1280 Ksym/sec 39600000 Hz 46.8 dBmV
2 Locked ATDMA 5 5120 Ksym/sec 35600000 Hz 43.3 dBmV
3 Locked ATDMA 6 5120 Ksym/sec 29200000 Hz 45.3 dBmV
4 Locked ATDMA 7 5120 Ksym/sec 22800000 Hz 43.8 dBmV
5 Locked ATDMA 8 5120 Ksym/sec 16400000 Hz 45.3 dBmV
6 Not Locked Unknown 0 0 0 0.0
7 Not Locked Unknown 0 0 0 0.0
8 Not Locked Unknown 0 0 0 0.0


Downstream OFDM Channels
Channel LockedStatus ProfileID ChannelID Frequency Power SNR/MER ActiveSubcarrier Unerror Correctable Uncorrectable
1 Locked 0 ,1 ,2 ,3 41 722000000 Hz -12.72 dBmV 33.3 dB 1108 ~ 2987 217097297 198477746 17110009
2 Not Locked 0 0 0 Hz 0 dBmV 0 dB 0 ~ 4095 0 0 0


Upstream OFDMA Channels
Channel LockedStatus ProfileID ChannelID Frequency Power
1 Not Locked 0 0 0 Hz 0 dBmV
2 Not Locked 0 0 0 Hz 0 dBmV


Event Log
Time Priority Description
Mon Aug 7 16:00:56 2023 Critical No Ranging Response received - T3 time-out;CM-MAC=94:18:65:a4:a5:3b;CMTS-MAC=00:01:5c:79:b8:46;CM-QOS=1.1;CM-VER=3.1;
Mon Aug 7 16:00:55 2023 Critical 16 consecutive T3 timeouts while trying to range on upstream channel 4;CM-MAC=94:18:65:a4:a5:3b;CMTS-MAC=00:01:5c:79:b8:46;CM-QOS=1.1;CM-VER=3.1;
Mon Aug 7 16:00:55 2023 Critical Ranging Request Retries exhausted;CM-MAC=94:18:65:a4:a5:3b;CMTS-MAC=00:01:5c:79:b8:46;CM-QOS=1.1;CM-VER=3.1;
Mon Aug 7 15:55:48 2023 Critical No Ranging Response received - T3 time-out;CM-MAC=94:18:65:a4:a5:3b;CMTS-MAC=00:01:5c:79:b8:46;CM-QOS=1.1;CM-VER=3.1;
Mon Aug 7 15:55:47 2023 Critical 16 consecutive T3 timeouts while trying to range on upstream channel 4;CM-MAC=94:18:65:a4:a5:3b;CMTS-MAC=00:01:5c:79:b8:46;CM-QOS=1.1;CM-VER=3.1;
Mon Aug 7 15:55:47 2023 Critical Ranging Request Retries exhausted;CM-MAC=94:18:65:a4:a5:3b;CMTS-MAC=00:01:5c:79:b8:46;CM-QOS=1.1;CM-VER=3.1;
Mon Aug 7 15:55:19 2023 Critical No Ranging Response received - T3 time-out;CM-MAC=94:18:65:a4:a5:3b;CMTS-MAC=00:01:5c:79:b8:46;CM-QOS=1.1;CM-VER=3.1;
Mon Aug 7 15:55:18 2023 Critical 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=94:18:65:a4:a5:3b;CMTS-MAC=00:01:5c:79:b8:46;CM-QOS=1.1;CM-VER=3.1;
Mon Aug 7 15:55:18 2023 Critical Ranging Request Retries exhausted;CM-MAC=94:18:65:a4:a5:3b;CMTS-MAC=00:01:5c:79:b8:46;CM-QOS=1.1;CM-VER=3.1;
Mon Aug 7 15:54:27 2023 Critical No Ranging Response received - T3 time-out;CM-MAC=94:18:65:a4:a5:3b;CMTS-MAC=00:01:5c:79:b8:46;CM-QOS=1.1;CM-VER=3.1;
Mon Aug 7 15:54:25 2023 Critical 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=94:18:65:a4:a5:3b;CMTS-MAC=00:01:5c:79:b8:46;CM-QOS=1.1;CM-VER=3.1;
Mon Aug 7 15:54:25 2023 Critical Ranging Request Retries exhausted;CM-MAC=94:18:65:a4:a5:3b;CMTS-MAC=00:01:5c:79:b8:46;CM-QOS=1.1;CM-VER=3.1;
Mon Aug 7 15:50:18 2023 Critical No Ranging Response received - T3 time-out;CM-MAC=94:18:65:a4:a5:3b;CMTS-MAC=00:01:5c:79:b8:46;CM-QOS=1.1;CM-VER=3.1;
Mon Aug 7 15:50:18 2023 Critical 16 consecutive T3 timeouts while trying to range on upstream channel 4;CM-MAC=94:18:65:a4:a5:3b;CMTS-MAC=00:01:5c:79:b8:46;CM-QOS=1.1;CM-VER=3.1;
Mon Aug 7 15:50:18 2023 Critical Ranging Request Retries exhausted;CM-MAC=94:18:65:a4:a5:3b;CMTS-MAC=00:01:5c:79:b8:46;CM-QOS=1.1;CM-VER=3.1;
Mon Aug 7 15:50:17 2023 Critical No Ranging Response received - T3 time-out;CM-MAC=94:18:65:a4:a5:3b;CMTS-MAC=00:01:5c:79:b8:46;CM-QOS=1.1;CM-VER=3.1;
Mon Aug 7 15:50:17 2023 Critical 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=94:18:65:a4:a5:3b;CMTS-MAC=00:01:5c:79:b8:46;CM-QOS=1.1;CM-VER=3.1;
Mon Aug 7 15:50:17 2023 Critical Ranging Request Retries exhausted;CM-MAC=94:18:65:a4:a5:3b;CMTS-MAC=00:01:5c:79:b8:46;CM-QOS=1.1;CM-VER=3.1;
Mon Aug 7 15:50:03 2023 Critical No Ranging Response received - T3 time-out;CM-MAC=94:18:65:a4:a5:3b;CMTS-MAC=00:01:5c:79:b8:46;CM-QOS=1.1;CM-VER=3.1;
Mon Aug 7 15:49:55 2023 Notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2.;CM-MAC=94:18:65:a4:a5:3b;CMTS-MAC=00:01:5c:79:b8:46;CM-QOS=1.1;CM-VER=3.1;
Mon Aug 7 15:49:27 2023 Critical No Ranging Response received - T3 time-out;CM-MAC=94:18:65:a4:a5:3b;CMTS-MAC=00:01:5c:79:b8:46;CM-QOS=1.1;CM-VER=3.1;
Mon Aug 7 15:49:26 2023 Notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 3.;CM-MAC=94:18:65:a4:a5:3b;CMTS-MAC=00:01:5c:79:b8:46;CM-QOS=1.1;CM-VER=3.1;
Mon Aug 7 15:49:12 2023 Critical No Ranging Response received - T3 time-out;CM-MAC=94:18:65:a4:a5:3b;CMTS-MAC=00:01:5c:79:b8:46;CM-QOS=1.1;CM-VER=3.1;
Mon Aug 7 15:49:11 2023 Notice CM-STATUS message sent. Event Type Code: 22; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=94:18:65:a4:a5:3b;CMTS-MAC=00:01:5c:79:b8:46;CM-QOS=1.1;CM-VER=3.1;
Mon Aug 7 15:49:11 2023 Critical No Ranging Response received - T3 time-out;CM-MAC=94:18:65:a4:a5:3b;CMTS-MAC=00:01:5c:79:b8:46;CM-QOS=1.1;CM-VER=3.1;
Mon Aug 7 15:49:09 2023 Notice CM-STATUS message sent. Event Type Code: 22; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=94:18:65:a4:a5:3b;CMTS-MAC=00:01:5c:79:b8:46;CM-QOS=1.1;CM-VER=3.1;
Mon Aug 7 15:48:31 2023 Critical No Ranging Response received - T3 time-out;CM-MAC=94:18:65:a4:a5:3b;CMTS-MAC=00:01:5c:79:b8:46;CM-QOS=1.1;CM-VER=3.1;
Mon Aug 7 15:48:31 2023 Notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2.;CM-MAC=94:18:65:a4:a5:3b;CMTS-MAC=00:01:5c:79:b8:46;CM-QOS=1.1;CM-VER=3.1;
Mon Aug 7 15:48:26 2023 Critical No Ranging Response received - T3 time-out;CM-MAC=94:18:65:a4:a5:3b;CMTS-MAC=00:01:5c:79:b8:46;CM-QOS=1.1;CM-VER=3.1;
Mon Aug 7 15:48:23 2023 Notice CM-STATUS message sent. Event Type Code: 20; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=94:18:65:a4:a5:3b;CMTS-MAC=00:01:5c:79:b8:46;CM-QOS=1.1;CM-VER=3.1;
Mon Aug 7 15:48:14 2023 Critical No Ranging Response received - T3 time-out;CM-MAC=94:18:65:a4:a5:3b;CMTS-MAC=00:01:5c:79:b8:46;CM-QOS=1.1;CM-VER=3.1;
Mon Aug 7 15:48:14 2023 Critical 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=94:18:65:a4:a5:3b;CMTS-MAC=00:01:5c:79:b8:46;CM-QOS=1.1;CM-VER=3.1;
Mon Aug 7 15:48:14 2023 Critical Ranging Request Retries exhausted;CM-MAC=94:18:65:a4:a5:3b;CMTS-MAC=00:01:5c:79:b8:46;CM-QOS=1.1;CM-VER=3.1;
Mon Aug 7 15:48:07 2023 Critical No Ranging Response received - T3 time-out;CM-MAC=94:18:65:a4:a5:3b;CMTS-MAC=00:01:5c:79:b8:46;CM-QOS=1.1;CM-VER=3.1;
Mon Aug 7 15:46:55 2023 Critical No Ranging Response received - T3 time-out;CM-MAC=94:18:65:a4:a5:3b;CMTS-MAC=00:01:5c:79:b8:46;CM-QOS=1.1;CM-VER=3.1;
Mon Aug 7 15:46:53 2023 Critical 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=94:18:65:a4:a5:3b;CMTS-MAC=00:01:5c:79:b8:46;CM-QOS=1.1;CM-VER=3.1;
Mon Aug 7 15:46:53 2023 Critical Ranging Request Retries exhausted;CM-MAC=94:18:65:a4:a5:3b;CMTS-MAC=00:01:5c:79:b8:46;CM-QOS=1.1;CM-VER=3.1;
Mon Aug 7 15:45:42 2023 Critical No Ranging Response received - T3 time-out;CM-MAC=94:18:65:a4:a5:3b;CMTS-MAC=00:01:5c:79:b8:46;CM-QOS=1.1;CM-VER=3.1;
Mon Aug 7 15:45:08 2023 Notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=94:18:65:a4:a5:3b;CMTS-MAC=00:01:5c:79:b8:46;CM-QOS=1.1;CM-VER=3.1;
Mon Aug 7 15:43:31 2023 Critical No Ranging Response received - T3 time-out;CM-MAC=94:18:65:a4:a5:3b;CMTS-MAC=00:01:5c:79:b8:46;CM-QOS=1.1;CM-VER=3.1;

Message 1 of 7
Kitsap
Master

Re: New CAX80 has poor cable connection issues.

Have you activated your CAX80 on your Xfinity account at your new location?

 

 

Message 2 of 7
Harunkingcool
Aspirant

Re: New CAX80 has poor cable connection issues.

I believe I have.

Message 3 of 7
FURRYe38
Guru

Re: New CAX80 has poor cable connection issues.

Power levels are mostly low or too low:

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

 

Any Criticals, Errors or Warnings seen in the event logs needs to be reviewed and resolved by the ISP. Indicates a signal issue on the ISP line up to the modem.

You have a ton of correctables and un-correctables that should all be mostly zeros.

 

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

https://www.duckware.com/tech/solving-intermittent-cable-modem-issues.html

Message 4 of 7
Harunkingcool
Aspirant

Re: New CAX80 has poor cable connection issues.

The power levels seem to be sufficient, but is there anything else I can do before I call my internet service provider?

Message 5 of 7
Kitsap
Master

Re: New CAX80 has poor cable connection issues.


@Harunkingcool wrote:

The power levels seem to be sufficient, but is there anything else I can do before I call my internet service provider?


Disagree.  Ideal is between 0 and +1 dBmV.

 

 

Message 6 of 7
plemans
Guru

Re: New CAX80 has poor cable connection issues.

Your power levels are low and you have errors in your line. All indicate line problems. 

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.
If you can, simply connect the modem right where the coax comes into the home. This prevents wiring in the home from being the issue. And some ISP’s charge if the wiring issue is in the home. So this helps prevent this.

 

If that doesn't help, the ISP needs to check it. 

Message 7 of 7
Top Contributors
Discussion stats
  • 6 replies
  • 1056 views
  • 0 kudos
  • 4 in conversation
Announcements

Orbi WiFi 7