CAX80 Not Getting Plan Speed

[AndrewD0318]

I bought a CAX80 yesterday, with the hopes that the wi-fi in it would be better than the XF XB7 with the 2 GB plan. After activating the CAX80 on XF, it's falling real short of what I was getting with the XF gateway.

I have it routed through a 5-port 2.5GB switch (standard fare), then to the PC (2.5GB PCIE card, onboard couldn't handle it).

Speedtest (online/app) Fast, and internal tests (XF app, and both Netgear App/logged into modem), all come up in the range of 500-600MB down, 5Mb (yes, Mega) up.

On the XB7 I got from Xfinity, I was getting 2.2G/240M, religiously.

Wifi (using my S22U to test, in the same room), has similar results, 500-600D/5M up.

I've tried to read/step through every article I could on this, but there seems to be no change.

Looking at anything to try, at this point.

[FURRYe38]

So you could not speed test effectively on the ethernet connected 2.5Gb PC? 

One should see near this thru the PC, Switch connected to the 2.5Gb multi gig port on the CAX80. 

What is the Mfr and model# of the ethernet switch in the configuration?

I get over 900Mpbs with my ethernet connected PC on my 1Gb ISP Plan here. 

Be sure your using a good quality LAN cable between the modem and router. CAT6A STP is recommended for connection speeds 2.5Gb and higher.

You'll not see any near this on WiFi. AX mode and 5Ghz and design of the wifi mobile devices are limited and mostly 2x2 MIMO antenna supporting. So I would presume at best, you might see 700-800Mpbs. 

I get around just over 800Mpbs with my Samsung Galaxy Tab S7 FW on my 1Gb ISP plan here thru the CAX80. 

If you have a 4x4 MIMO supporting device then you should see 900Mpbs or over however, still depending if the device can support 160Mhz and can connect at 2.5Gb or beyond which the CAX80 supports 4800Mpbs on 5Ghz however thats mostly in close proximity with the CAX80 and near perfect condtions. I've never seen 4800Mpbs with my CAX80 and a RAXE500 in wirelss bridge mode. 

Link Rate
2722.2 Mbps

What Firmware version is currently loaded?

[AndrewD0318]

Hi, the switch is a TrendNet  TEG-S350, but looping that out, there is no change. CAX80 straight to PC is still 500-600. All cables are CAT8. Exact cables/switch/setup as with the Xfin XB7 gateway, it's just 1/3 the speed.

The wifi performance isn't bothering me as much for the moment as the LAN. Speedtest within the netgear app shows 2300D/240U. (as well as the "2.5" lit up on the front of the modem.

Actual speed tests result in 500-600 and less than 10M up.

Firmware is V2.1.5.2

[FURRYe38]

So you were able to see to spec speeds with same PC connected to the ISP modem? 

CAT8 STP should be used.

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

[AndrewD0318]

To answer your question, yes, I get the 2.2G on the xfinity gateway, direct to PC and through switch.

Connection info:

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

Channel	Lock Status	Modulation	Channel ID	Frequency	Power	SNR	Correctables	Uncorrectables
1	Locked	256 QAM	4	447000000 Hz	0.9 dBmV	45.1 dB	0	0
2	Locked	256 QAM	1	429000000 Hz	0.9 dBmV	45.1 dB	0	0
3	Locked	256 QAM	2	435000000 Hz	0.7 dBmV	45.0 dB	0	0
4	Locked	256 QAM	3	441000000 Hz	0.8 dBmV	45.1 dB	0	0
5	Locked	256 QAM	5	453000000 Hz	1.2 dBmV	45.2 dB	0	0
6	Locked	256 QAM	6	459000000 Hz	1.2 dBmV	45.3 dB	0	0
7	Locked	256 QAM	7	465000000 Hz	1.1 dBmV	45.1 dB	0	0
8	Locked	256 QAM	8	471000000 Hz	1.1 dBmV	44.7 dB	0	0
9	Locked	256 QAM	9	477000000 Hz	1.1 dBmV	44.6 dB	0	0
10	Locked	256 QAM	10	483000000 Hz	1.3 dBmV	45.1 dB	0	0
11	Locked	256 QAM	11	489000000 Hz	1.3 dBmV	44.9 dB	0	0
12	Locked	256 QAM	12	495000000 Hz	1.5 dBmV	37.7 dB	0	0
13	Locked	256 QAM	13	501000000 Hz	1.3 dBmV	40.9 dB	0	0
14	Locked	256 QAM	14	507000000 Hz	1.5 dBmV	35.9 dB	0	0
15	Locked	256 QAM	15	513000000 Hz	1.4 dBmV	38.7 dB	0	0
16	Locked	256 QAM	16	519000000 Hz	1.6 dBmV	44.8 dB	0	0
17	Locked	256 QAM	17	525000000 Hz	1.5 dBmV	45.0 dB	0	0
18	Locked	256 QAM	18	531000000 Hz	1.8 dBmV	45.1 dB	0	0
19	Locked	256 QAM	19	537000000 Hz	1.5 dBmV	44.9 dB	0	0
20	Locked	256 QAM	20	543000000 Hz	1.6 dBmV	45.0 dB	0	0
21	Locked	256 QAM	21	549000000 Hz	1.3 dBmV	44.8 dB	0	0
22	Locked	256 QAM	22	555000000 Hz	1.2 dBmV	44.7 dB	0	0
23	Locked	256 QAM	23	561000000 Hz	1.3 dBmV	44.7 dB	0	0
24	Locked	256 QAM	24	567000000 Hz	1.4 dBmV	44.6 dB	0	0
25	Locked	256 QAM	25	573000000 Hz	1.6 dBmV	44.9 dB	0	0
26	Locked	256 QAM	26	579000000 Hz	1.7 dBmV	44.9 dB	0	0
27	Locked	256 QAM	27	585000000 Hz	1.8 dBmV	44.9 dB	0	0
28	Locked	256 QAM	28	591000000 Hz	1.8 dBmV	44.8 dB	0	0
29	Locked	256 QAM	29	597000000 Hz	1.8 dBmV	44.7 dB	0	0
30	Locked	256 QAM	30	603000000 Hz	1.6 dBmV	44.6 dB	0	0
31	Locked	256 QAM	31	609000000 Hz	1.9 dBmV	44.7 dB	0	0
32	Locked	256 QAM	32	615000000 Hz	1.5 dBmV	44.5 dB	0	0

[AndrewD0318]

Ok, now I guess I need help on how to post the rest of the logs, I get this error: "Your post has been changed because invalid HTML was found in the message body. The invalid HTML has been removed. Please review the message and submit the message when you are satisfied."

[FURRYe38]

Just press POST when you see that message. 

Cable Connections page looks good. Power and such is with specs. Zero Correctables is good. 

Post the Event Logs page.

What is the connection rate speed seen on the CAX80s WEB page under Advanced tab/Internet Port section/Show Stats/LAN port 5?

[AndrewD0318]

Ok, it just kept giving me the error repeatedly.

Event Log: (seeing all the "critical", makes me wonder if this is "it"

Time	Priority	Description
Sun Jul 2 15:25:46 2023	Critical (3)	UCD invalid or channel unusable;CM-MAC=94:18:65:a4:8d:b3;CMTS-MAC=00:90:f0:31:0b:00;CM-QOS=1.1;CM-VER=3.1;
Sun Jul 2 15:25:46 2023	Notice (6)	DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=94:18:65:a4:8d:b3;CMTS-MAC=00:90:f0:31:0b:00;CM-QOS=1.1;CM-VER=3.1;
Sun Jul 2 15:25:20 2023	Notice (6)	TLV-11 - unrecognized OID;CM-MAC=94:18:65:a4:8d:b3;CMTS-MAC=00:90:f0:31:0b:00;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:00:50 1970	Notice (6)	Honoring MDD; IP provisioning mode = IPv6
Thu Jan 1 00:00:44 1970	Critical (3)	UCD invalid or channel unusable;CM-MAC=94:18:65:a4:8d:b3;CMTS-MAC=00:90:f0:31:0b: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=94:18:65:a4:8d:b3;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Sat Jul 1 16:40:55 2023	Critical (3)	UCD invalid or channel unusable;CM-MAC=94:18:65:a4:8d:b3;CMTS-MAC=00:90:f0:31:0b:00;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:00:44 1970	Critical (3)	UCD invalid or channel unusable;CM-MAC=94:18:65:a4:8d:b3;CMTS-MAC=00:90:f0:31:0b: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=94:18:65:a4:8d:b3;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Sat Jul 1 16:38:29 2023	Critical (3)	UCD invalid or channel unusable;CM-MAC=94:18:65:a4:8d:b3;CMTS-MAC=00:90:f0:31:0b:00;CM-QOS=1.1;CM-VER=3.1;
Sat Jul 1 16:38:27 2023	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=94:18:65:a4:8d:b3;CMTS-MAC=00:90:f0:31:0b:00;CM-QOS=1.1;CM-VER=3.1;
Sat Jul 1 16:38:22 2023	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=94:18:65:a4:8d:b3;CMTS-MAC=00:90:f0:31:0b:00;CM-QOS=1.1;CM-VER=3.1;
Sat Jul 1 16:38:19 2023	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=94:18:65:a4:8d:b3;CMTS-MAC=00:90:f0:31:0b:00;CM-QOS=1.1;CM-VER=3.1;
Sat Jul 1 16:38:17 2023	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:18:65:a4:8d:b3;CMTS-MAC=00:90:f0:31:0b:00;CM-QOS=1.1;CM-VER=3.1;
Sat Jul 1 16:38:14 2023	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:18:65:a4:8d:b3;CMTS-MAC=00:90:f0:31:0b:00;CM-QOS=1.1;CM-VER=3.1;
Sat Jul 1 16:38:12 2023	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:18:65:a4:8d:b3;CMTS-MAC=00:90:f0:31:0b:00;CM-QOS=1.1;CM-VER=3.1;
Sat Jul 1 16:38:10 2023	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:18:65:a4:8d:b3;CMTS-MAC=00:90:f0:31:0b:00;CM-QOS=1.1;CM-VER=3.1;
Sat Jul 1 16:38:08 2023	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:18:65:a4:8d:b3;CMTS-MAC=00:90:f0:31:0b:00;CM-QOS=1.1;CM-VER=3.1;
Sat Jul 1 16:38:06 2023	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:18:65:a4:8d:b3;CMTS-MAC=00:90:f0:31:0b:00;CM-QOS=1.1;CM-VER=3.1;
Sat Jul 1 15:46:51 2023	Critical (3)	UCD invalid or channel unusable;CM-MAC=94:18:65:a4:8d:b3;CMTS-MAC=00:90:f0:31:0b:00;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:00:45 1970	Critical (3)	UCD invalid or channel unusable;CM-MAC=94:18:65:a4:8d:b3;CMTS-MAC=00:90:f0:31:0b:00;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:00:44 1970	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=94:18:65:a4:8d:b3;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Sat Jul 1 14:46:29 2023	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=94:18:65:a4:8d:b3;CMTS-MAC=00:90:f0:31:0b:00;CM-QOS=1.1;CM-VER=3.1;
Sat Jul 1 14:45:54 2023	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=94:18:65:a4:8d:b3;CMTS-MAC=00:90:f0:31:0b:00;CM-QOS=1.1;CM-VER=3.1;
Sat Jul 1 14:45:47 2023	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=94:18:65:a4:8d:b3;CMTS-MAC=00:90:f0:31:0b:00;CM-QOS=1.1;CM-VER=3.1;
Sat Jul 1 14:45:45 2023	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=94:18:65:a4:8d:b3;CMTS-MAC=00:90:f0:31:0b:00;CM-QOS=1.1;CM-VER=3.1;
Sat Jul 1 14:02:21 2023	Critical (3)	UCD invalid or channel unusable;CM-MAC=94:18:65:a4:8d:b3;CMTS-MAC=00:90:f0:31:0b:00;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:00:44 1970	Critical (3)	UCD invalid or channel unusable;CM-MAC=94:18:65:a4:8d:b3;CMTS-MAC=00:90:f0:31:0b: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=94:18:65:a4:8d:b3;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Sat Jul 1 13:41:35 2023	Critical (3)	UCD invalid or channel unusable;CM-MAC=94:18:65:a4:8d:b3;CMTS-MAC=00:90:f0:31:0b:00;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:00:45 1970	Critical (3)	UCD invalid or channel unusable;CM-MAC=94:18:65:a4:8d:b3;CMTS-MAC=00:90:f0:31:0b: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=94:18:65:a4:8d:b3;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Sat Jul 1 13:14:34 2023	Critical (3)	UCD invalid or channel unusable;CM-MAC=94:18:65:a4:8d:b3;CMTS-MAC=00:90:f0:31:0b:00;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:00:46 1970	Critical (3)	UCD invalid or channel unusable;CM-MAC=94:18:65:a4:8d:b3;CMTS-MAC=00:90:f0:31:0b: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=94:18:65:a4:8d:b3;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Sat Jul 1 13:12:19 2023	Critical (3)	Resetting the cable modem due to docsDevResetNow
Sat Jul 1 13:07:01 2023	Critical (3)	UCD invalid or channel unusable;CM-MAC=94:18:65:a4:8d:b3;CMTS-MAC=00:90:f0:31:0b:00;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:00:44 1970	Critical (3)	UCD invalid or channel unusable;CM-MAC=94:18:65:a4:8d:b3;CMTS-MAC=00:90:f0:31:0b: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=94:18:65:a4:8d:b3;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Sat Jul 1 13:04:03 2023	Critical (3)	UCD invalid or channel unusable;CM-MAC=94:18:65:a4:8d:b3;CMTS-MAC=00:90:f0:31:0b:00;CM-QOS=1.1;CM-VER=3.1;

Others from connection:

Upstream Bonded Channels
Channel	Lock Status	US Channel Type	Channel ID	Symbol Rate	Frequency	Power
1	Locked	ATDMA	3	5120 Ksym/sec	29200000 Hz	36.3 dBmV
2	Locked	ATDMA	2	5120 Ksym/sec	22800000 Hz	36.5 dBmV
3	Locked	ATDMA	1	5120 Ksym/sec	16400000 Hz	36.5 dBmV
4	Locked	ATDMA	4	5120 Ksym/sec	35600000 Hz	36.3 dBmV
5	Not Locked	Unknown	0	0	0	0.0 dBmV
6	Not Locked	Unknown	0	0	0	0.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	Modulation /	Channel	Frequency	Power	SNR /	Active Subcarrier	Unerrored	Correctable	Uncorrectable
Status	Profile ID	ID	MER	Number Range	Codewords	Codewords	Codewords
1	Locked	0 ,1 ,2 ,3	193	957000000 Hz	2.08 dBmV	43.8 dB	148 ~ 3947	12372970	1811590	0
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

Stats:

System Up Time 02:34:04

Port	Status	TxPkts	RxPkts	Collisions	Tx B/s	Rx B/s	Up Time
WAN	Link Up	1071927	5103859	0	18450	784450	02:31:54
LAN1	Link Down	--	--	--	--	--	--
LAN2	Link Down	--	--	--	--	--	--
LAN3	Link Down	--	--	--	--	--	--
LAN4	Link Down	--	--	--	--	--	--
LAN5	2.5G/Full	210243	79301	0	23789	2289	02:32:35
2.4G WLAN b/g/n/ax	1200M	1804883	365441	6	276670	6165	02:32:44
5G WLAN a/n/ac/ax	4800M	734550	249475	0	347562	7332	02:32:43

[FURRYe38]

I see your connecting at 2.5Gb on the multi gig port. Thats good. 

I see lots of Criticals.

Was the modem rebooted recently before taking the Event log capture? 

Criticals, Errors or Warnings seen in the Event logs indicate a signal problem on the ISP and modem side. The ISP needs to review this and resolve them. 

[AndrewD0318]

It's been rebooted several times. I will reach out to XF. Thank you.

[FURRYe38]

Should be getting higher speeds thru the Multigig port with a ethernet connected PC. Even with connecting to the 1Gb ports in back, you should see over 900Mpbs. 

Try a different PC to compare. 

Let us know how it goes. 

[AndrewD0318]

It's definitely on the XF side. Speed test within NG app is only showing 370/5 D/U

[FURRYe38]

Keep on them. 

[AndrewD0318]

They ran a test on their side and saw something, a tech is going to be here this afternoon.

[FURRYe38]

👍

[AndrewD0318]

Yesterday was a journey. Three calls with their "special" tech support, what they said it was, the netgear modem doesn't have a phone jack, as I had one of those "bundled" packages with a phone, it was erroring out on things because it was looking for the phone hardware... ok.....

So they reset my service (removing the phone part), THEN, dropped the "oh, you can only have the 2 gigabit service on a retail modem" on me (after 90 minutes on the call). So I reluctantly went back to the 1.2 (which should be 1.5 actual) as that was the highest they DO support on an owned modem.

End result? Still at 600/5 U/D. Tech is supposed to be here this afternoon, although I'm not real sure what they'll be able to do here, as this is 100% switch side on their part. Maybe they have a magic wand, or they're a which doctor. I guess we'll see.

This has been a hell of a week.

[FURRYe38]

Ya the modem doesn't support a phone jack. LOL

Ok, have them check the logs while they are there so they can see. 

Hopefully they can get it working. 

Keep us posted.

[AndrewD0318]

I am now (at least) getting 1.3 down, and 40 up (the up is a little short) over LAN, and wifi, to the phone, and the dell laptop in the other room. 

I did read somewhere that if they change the service/you change the modem, it could take a while for it all to catch up (?), but it's definitely close to what it should be.

I called about the tech visit this morning, they apparently canceled the appointment last night because "it works now".

I'll give it some more "soak time" to see if the upload comes around, but it's at least (more than) functional for work use now. The 1-5Mb upload the last couple of days was not enhancing my calm.

[FURRYe38]

Good to hear. ISP found something. 

Ya, there is a beta FW that fixes the 5Ghz Upload issue. Something you could ask NG support about if you feel the need.