NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

AndrewD0318's avatar
AndrewD0318
Aspirant
Jul 02, 2023

CAX80 Not Getting Plan Speed

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 wit...
AndrewD0318's avatar
AndrewD0318
Aspirant
Jul 02, 2023

Ok, it just kept giving me the error repeatedly.


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

TimePriorityDescription
Sun Jul 2 15:25:46 2023Critical (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 2023Notice (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 2023Notice (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 1970Notice (6)Honoring MDD; IP provisioning mode = IPv6
Thu Jan 1 00:00:44 1970Critical (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 1970Critical (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 2023Critical (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 1970Critical (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 1970Critical (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 2023Critical (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 2023Critical (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 2023Critical (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 2023Critical (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 2023Critical (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 2023Critical (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 2023Critical (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 2023Critical (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 2023Critical (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 2023Critical (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 2023Critical (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 1970Critical (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 1970Critical (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 2023Critical (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 2023Critical (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 2023Critical (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 2023Critical (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 2023Critical (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 1970Critical (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 1970Critical (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 2023Critical (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 1970Critical (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 1970Critical (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 2023Critical (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 1970Critical (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 1970Critical (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 2023Critical (3)Resetting the cable modem due to docsDevResetNow
Sat Jul 1 13:07:01 2023Critical (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 1970Critical (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 1970Critical (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 2023Critical (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 
ChannelLock StatusUS Channel TypeChannel IDSymbol RateFrequencyPower     
1LockedATDMA35120 Ksym/sec29200000 Hz36.3 dBmV     
2LockedATDMA25120 Ksym/sec22800000 Hz36.5 dBmV     
3LockedATDMA15120 Ksym/sec16400000 Hz36.5 dBmV     
4LockedATDMA45120 Ksym/sec35600000 Hz36.3 dBmV     
5Not LockedUnknown0000.0 dBmV     
6Not LockedUnknown0000.0 dBmV     
7Not LockedUnknown0000.0 dBmV     
8Not LockedUnknown0000.0 dBmV     
 
Downstream OFDM Channels 
ChannelLockModulation /ChannelFrequencyPowerSNR /Active SubcarrierUnerroredCorrectableUncorrectable 
StatusProfile IDIDMERNumber RangeCodewordsCodewordsCodewords 
1Locked0 ,1 ,2 ,3193957000000 Hz2.08 dBmV43.8 dB148 ~ 39471237297018115900 
2Not Locked000 Hz0 dBmV0 dB0 ~ 4095000 
 
Upstream OFDMA Channels 
ChannelLock StatusModulation / Profile IDChannel IDFrequencyPower      
1Not Locked000 Hz0 dBmV      
2Not Locked000 Hz0 dBmV      

 

Stats:

System Up Time 02:34:04

PortStatusTxPktsRxPktsCollisionsTx B/sRx B/sUp Time
WANLink Up1071927510385901845078445002:31:54
LAN1Link Down------------
LAN2Link Down------------
LAN3Link Down------------
LAN4Link Down------------
LAN52.5G/Full21024379301023789228902:32:35
2.4G WLAN b/g/n/ax1200M18048833654416276670616502:32:44
5G WLAN a/n/ac/ax4800M7345502494750347562733202:32:43

 

 

 

 

FURRYe38's avatar
FURRYe38
Guru - Experienced User
Jul 03, 2023

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's avatar
    AndrewD0318
    Aspirant
    Jul 03, 2023

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

  • FURRYe38's avatar
    FURRYe38
    Guru - Experienced User
    Jul 03, 2023

    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's avatar
    AndrewD0318
    Aspirant
    Jul 04, 2023

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

  • FURRYe38's avatar
    FURRYe38
    Guru - Experienced User
    Jul 04, 2023

    Keep on them. 

  • AndrewD0318's avatar
    AndrewD0318
    Aspirant
    Jul 05, 2023

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

  • FURRYe38's avatar
    FURRYe38
    Guru - Experienced User
    Jul 05, 2023

    👍

  • AndrewD0318's avatar
    AndrewD0318
    Aspirant
    Jul 08, 2023

    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's avatar
    FURRYe38
    Guru - Experienced User
    Jul 08, 2023

    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's avatar
    AndrewD0318
    Aspirant
    Jul 08, 2023

    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's avatar
    FURRYe38
    Guru - Experienced User
    Jul 09, 2023

    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.