Re: Model CAX80 router upstream LED blinking.

Gbol · ‎2023-11-11

I have a Model CAX80 router and have been having problems streaming at certain times of day due to the signal dropping out. I had Xfinity out and the tech put in a MOCA filter to isolate our system from others in the neighborhood. The tech said he was concerned about the blinking upstream LED and said that the modem may be failing. I reset the network, and the LED was solid, but overnight, it began blinking again. We are still having drop out when streaming, but I do not think it is the modem. Is this blinking LED a problem?

microchip8 · ‎2023-11-11

Why don't you consult the manual about what the LED status means? Go to NETGEAR's site, punch in your model and grab the manual!

FURRYe38 · ‎2023-11-11

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-m...
https://kb.netgear.com/30008/How-do-I-view-or-clear-the-event-logs-on-my-NETGEAR-cable-modem-or-mode...

Gbol · ‎2023-11-11

Had it wrong, it is the upstream LED, and I did check the manual. No help there.

Gbol · ‎2023-11-11

Firmware is 2.5.1.2, and it is actually the downstream LED that is blinking. I reset the network and it was solid white, but after a while, it starts blinking again. Not sure what that means and the manual is no help.

Gbol · ‎2023-11-11

The site keeps asking me to reset my password, which I do, but then it will not let me in and asks me again to reset the password, so I am unable to get any further info. Absolutely horrible site.

michaelkenward · ‎2023-11-12

@Gbol wrote:

The site keeps asking me to reset my password....

What "site" is that?

Do you mean the graphical user interface (GUI) as seen in a web browser?

That's not so much a "site" as a way into your modem/router's controls.

Gbol · ‎2023-11-12

Yes. Thank you. I can open the app on my iPad fine, but the browser access keeps asking me to reset my password. I do, then when it asks me to log in, I get the reset password message again. I am beginning to think maybe I need to replace the modem. I did a reboot last night and the download stream LED was solid, but this morning it is blinking again.

Gbol · ‎2023-11-12

Not using the app, as it really does not have any real options to fix anything, other than a reboot. I have tried accessing the GUI in both Firefox and Safari, and get the same results.

Between 3:00 to 5:00 PM the screen on the TV goes black, and there is a no signal message on the screen. It will do this for a period of time, cutting in and out and then be fine. Occasionally it does happen later. The tech from Xfinity was concerned about the blinking download stream LED, and said the modem could be failing.

The coax cable from outside goes into the modem/router. The Apple TV we are streaming from is connected directly to the router via an ethernet cable. The Apple TV is connected to the TV via an HDMI cable, so all the connections are wired.

A factory reset would be my last resort, and I have done it in the past. There was a Netgear update that really messed things up a while back and that was the only way to get it working again.

Gbol · ‎2023-11-12

Was able to get into the browser GUI today. Weird. I will send the logs requested.

Gbol · ‎2023-11-12

Event Log

Time	Priority	Description
Sun Nov 12 09:25:50 2023	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:9f:2d:f8;CMTS-MAC=00:90:f0:76:05:00;CM-QOS=1.1;CM-VER=3.1;
Sun Nov 12 08:22:57 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=08:36:c9:9f:2d:f8;CMTS-MAC=00:90:f0:76:05:00;CM-QOS=1.1;CM-VER=3.1;
Sun Nov 12 08:22:57 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 22; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:9f:2d:f8;CMTS-MAC=00:90:f0:76:05:00;CM-QOS=1.1;CM-VER=3.1;
Sun Nov 12 08:15:57 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=08:36:c9:9f:2d:f8;CMTS-MAC=00:90:f0:76:05:00;CM-QOS=1.1;CM-VER=3.1;
Sun Nov 12 08:15:57 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 20; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:9f:2d:f8;CMTS-MAC=00:90:f0:76:05:00;CM-QOS=1.1;CM-VER=3.1;
Sat Nov 11 21:57:08 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=08:36:c9:9f:2d:f8;CMTS-MAC=00:90:f0:76:05:00;CM-QOS=1.1;CM-VER=3.1;
Sat Nov 11 21:57:08 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 22; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:9f:2d:f8;CMTS-MAC=00:90:f0:76:05:00;CM-QOS=1.1;CM-VER=3.1;
Sat Nov 11 21:52:19 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 20; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:9f:2d:f8;CMTS-MAC=00:90:f0:76:05:00;CM-QOS=1.1;CM-VER=3.1;
Sat Nov 11 21:52:15 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=08:36:c9:9f:2d:f8;CMTS-MAC=00:90:f0:76:05:00;CM-QOS=1.1;CM-VER=3.1;
Sat Nov 11 21:01:43 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 22; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:9f:2d:f8;CMTS-MAC=00:90:f0:76:05:00;CM-QOS=1.1;CM-VER=3.1;
Sat Nov 11 21:00:14 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 20; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:9f:2d:f8;CMTS-MAC=00:90:f0:76:05:00;CM-QOS=1.1;CM-VER=3.1;
Sat Nov 11 20:54:04 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=08:36:c9:9f:2d:f8;CMTS-MAC=00:90:f0:76:05:00;CM-QOS=1.1;CM-VER=3.1;
Sat Nov 11 20:51:15 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=08:36:c9:9f:2d:f8;CMTS-MAC=00:90:f0:76:05:00;CM-QOS=1.1;CM-VER=3.1;
Sat Nov 11 20:22:23 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 22; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:9f:2d:f8;CMTS-MAC=00:90:f0:76:05:00;CM-QOS=1.1;CM-VER=3.1;
Sat Nov 11 20:22:09 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=08:36:c9:9f:2d:f8;CMTS-MAC=00:90:f0:76:05:00;CM-QOS=1.1;CM-VER=3.1;
Sat Nov 11 20:17:16 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 20; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:9f:2d:f8;CMTS-MAC=00:90:f0:76:05:00;CM-QOS=1.1;CM-VER=3.1;
Sat Nov 11 20:17:16 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=08:36:c9:9f:2d:f8;CMTS-MAC=00:90:f0:76:05:00;CM-QOS=1.1;CM-VER=3.1;
Sat Nov 11 20:17:07 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=08:36:c9:9f:2d:f8;CMTS-MAC=00:90:f0:76:05:00;CM-QOS=1.1;CM-VER=3.1;
Sat Nov 11 20:17:07 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 22; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:9f:2d:f8;CMTS-MAC=00:90:f0:76:05:00;CM-QOS=1.1;CM-VER=3.1;
Sat Nov 11 20:16:33 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=08:36:c9:9f:2d:f8;CMTS-MAC=00:90:f0:76:05:00;CM-QOS=1.1;CM-VER=3.1;
Sat Nov 11 20:16:33 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 20; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:9f:2d:f8;CMTS-MAC=00:90:f0:76:05:00;CM-QOS=1.1;CM-VER=3.1;
Sat Nov 11 20:01:36 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 22; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:9f:2d:f8;CMTS-MAC=00:90:f0:76:05:00;CM-QOS=1.1;CM-VER=3.1;
Sat Nov 11 19:58:25 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 20; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:9f:2d:f8;CMTS-MAC=00:90:f0:76:05:00;CM-QOS=1.1;CM-VER=3.1;
Sat Nov 11 19:17:21 2023	Notice (6)	DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=08:36:c9:9f:2d:f8;CMTS-MAC=00:90:f0:76:05:00;CM-QOS=1.1;CM-VER=3.1;
Sat Nov 11 19:16:55 2023	Notice (6)	TLV-11 - unrecognized OID;CM-MAC=08:36:c9:9f:2d:f8;CMTS-MAC=00:90:f0:76:05:00;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:00:51 1970	Notice (6)	Honoring MDD; IP provisioning mode = IPv6
Thu Jan 1 00:00:43 1970	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:9f:2d:f8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Thu Nov 9 14:41:37 2023	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:9f:2d:f8;CMTS-MAC=00:90:f0:76:05:00;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:00:43 1970	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:9f:2d:f8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Tue Nov 7 09:17:59 2023	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:9f:2d:f8;CMTS-MAC=00:90:f0:76:05:00;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:00:43 1970	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:9f:2d:f8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Tue Nov 7 09:13:06 2023	Critical (3)	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=08:36:c9:9f:2d:f8;CMTS-MAC=00:90:f0:76:05:00;CM-QOS=1.1;CM-VER=3.1;
Tue Nov 7 09:12:44 2023	Critical (3)	TFTP Request Retries exceeded, CM unable to register
Tue Nov 7 09:12:21 2023	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:9f:2d:f8;CMTS-MAC=00:90:f0:76:05:00;CM-QOS=1.1;CM-VER=3.1;
Tue Nov 7 09:11:40 2023	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:9f:2d:f8;CMTS-MAC=00:90:f0:76:05:00;CM-QOS=1.1;CM-VER=3.1;
Tue Nov 7 09:11:34 2023	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:9f:2d:f8;CMTS-MAC=00:90:f0:76:05:00;CM-QOS=1.1;CM-VER=3.1;
Tue Nov 7 09:11:30 2023	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:9f:2d:f8;CMTS-MAC=00:90:f0:76:05:00;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:00:43 1970	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:9f:2d:f8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Fri Oct 20 11:10:33 2023	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:9f:2d:f8;CMTS-MAC=00:90:f0:76:05:00;CM-QOS=1.1;CM-VER=3.1;
Fri Oct 20 11:08:42 2023	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:9f:2d:f8;CMTS-MAC=00:90:f0:76:05:00;CM-QOS=1.1;CM-VER=3.1;

Gbol · ‎2023-11-12

Cable Connection

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:

Downstream Status:

Upstream Status:

Advanced Information

Frequency Start Value

This field below allows you to modify the frequency the cable modem start with its scan during initialization and registration. Enter the new start frequency and restart the cable modem for it to take effect.

Starting Frequency

Startup Procedure

Procedure	Status	Comment
Acquire Downstream Channel	435 MHz	Locked
Connectivity State	OK	Operational
Boot State	OK	Operational
Security	Enabled	BPI+

Downstream Bonded Channels

Channel	Lock Status	Modulation	Channel ID	Frequency	Power	SNR	Correctables	Uncorrectables
1	Locked	256 QAM	4	435000000 Hz	3.8 dBmV	42.8 dB	0	0
2	Locked	256 QAM	1	417000000 Hz	3.7 dBmV	42.9 dB	0	0
3	Locked	256 QAM	2	423000000 Hz	3.7 dBmV	42.8 dB	0	0
4	Locked	256 QAM	3	429000000 Hz	3.8 dBmV	42.8 dB	0	0
5	Locked	256 QAM	5	441000000 Hz	3.8 dBmV	42.8 dB	0	0
6	Locked	256 QAM	6	447000000 Hz	3.9 dBmV	42.8 dB	0	0
7	Locked	256 QAM	7	453000000 Hz	4.0 dBmV	42.7 dB	0	0
8	Locked	256 QAM	8	459000000 Hz	3.9 dBmV	42.7 dB	0	0
9	Locked	256 QAM	9	465000000 Hz	3.9 dBmV	42.6 dB	0	0
10	Locked	256 QAM	10	471000000 Hz	3.9 dBmV	42.6 dB	0	0
11	Locked	256 QAM	11	477000000 Hz	3.8 dBmV	42.5 dB	0	0
12	Locked	256 QAM	12	483000000 Hz	3.7 dBmV	42.4 dB	0	0
13	Locked	256 QAM	13	489000000 Hz	3.7 dBmV	42.3 dB	0	0
14	Locked	256 QAM	14	495000000 Hz	3.7 dBmV	42.3 dB	0	0
15	Locked	256 QAM	15	501000000 Hz	3.9 dBmV	42.3 dB	0	0
16	Locked	256 QAM	16	507000000 Hz	4.1 dBmV	42.4 dB	0	0
17	Locked	256 QAM	17	513000000 Hz	4.2 dBmV	42.4 dB	0	0
18	Locked	256 QAM	18	519000000 Hz	4.4 dBmV	42.4 dB	0	0
19	Locked	256 QAM	19	525000000 Hz	4.4 dBmV	42.4 dB	0	0
20	Locked	256 QAM	20	531000000 Hz	4.5 dBmV	42.3 dB	0	0
21	Locked	256 QAM	21	537000000 Hz	4.5 dBmV	42.2 dB	0	0
22	Locked	256 QAM	22	543000000 Hz	4.4 dBmV	42.1 dB	0	0
23	Locked	256 QAM	23	555000000 Hz	4.5 dBmV	42.1 dB	0	0
24	Locked	256 QAM	24	561000000 Hz	4.6 dBmV	42.1 dB	0	0
25	Locked	256 QAM	25	567000000 Hz	4.7 dBmV	42.2 dB	0	0
26	Locked	256 QAM	26	573000000 Hz	4.8 dBmV	42.2 dB	0	0
27	Locked	256 QAM	27	579000000 Hz	4.8 dBmV	42.3 dB	0	0
28	Locked	256 QAM	28	585000000 Hz	4.8 dBmV	42.3 dB	0	0
29	Locked	256 QAM	29	591000000 Hz	4.9 dBmV	42.3 dB	0	0
30	Locked	256 QAM	30	597000000 Hz	5.0 dBmV	42.3 dB	0	0
31	Locked	256 QAM	31	603000000 Hz	5.1 dBmV	42.3 dB	0	0
32	Locked	256 QAM	32	609000000 Hz	5.0 dBmV	42.2 dB	0	0

Upstream Bonded Channels

Channel	Lock Status	US Channel Type	Channel ID	Symbol Rate	Frequency	Power
1	Locked	ATDMA	5	2560 Ksym/sec	40400000 Hz	42.3 dBmV
2	Locked	ATDMA	2	5120 Ksym/sec	22800000 Hz	40.3 dBmV
3	Locked	ATDMA	3	5120 Ksym/sec	29200000 Hz	39.8 dBmV
4	Locked	ATDMA	4	5120 Ksym/sec	35600000 Hz	39.0 dBmV
5	Locked	ATDMA	1	5120 Ksym/sec	16400000 Hz	40.3 dBmV
6	Locked	ATDMA	6	2560 Ksym/sec	10400000 Hz	44.0 dBmV
7	Not Locked	Unknown	0	0	0	0.0 dBmV
8	Not Locked	Unknown	0	0	0	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	0 ,1 ,2 ,3	193	805000000 Hz	5.88 dBmV	42.3 dB	1108 ~ 2987	661618867	173420212	2
2	Not Locked	0	0	0 Hz	0 dBmV	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 dBmV
2	Not Locked	0	0	0 Hz	0 dBmV

Extended Upstream Transmit Power

Current System Time:Sun Nov 12 09:38:28 2023

System Up Time:14:22:32

Help Center

Show/Hide Help Center

FURRYe38 · ‎2023-11-12

Power levels are good and no correctables or un-correctables.

However lots of Criticals. 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.

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

Gbol · ‎2023-11-13

Thanks`. A lot to process. The ISP provider was out and claimed that everything is fine on their end. He blamed the problems on a possibly failing modem. Xfinity here in Arizona is pretty bad, especially when it comes to service. Thanks to everyone who tried to help here. It is much appreciated.

FURRYe38 · ‎2023-11-13

Might try the modem at a different location to see if problem follows or not. Would be telling.
Ya, ISPs and some techs are not willing to take a deep dive and quick to blame NG. 🙄