Start a New Discussion

Start a New Discussion

Orbi WiFi 7 RBE973
Reply

Takes HOURS for CAX30 to restore functionality after power cycle.

smjpja
Follower
Follower
‎2023-01-01 10:40 AM
‎2023-01-01 10:40 AM

Takes HOURS for CAX30 to restore functionality after power cycle.

EVERYTIME I cycle power on my CAX30 Nighthawk it takes HOURS for it to start working again.  Event Log included.

 

 
Cable Information
Hardware VersionV1.01
 
Firmware VersionV1.4.11.2
 
Cable Firmware VersionV1.04.10
 
Cable Modem Serial Number6PK114W6004C4
 
CM certificateInstalled

 

 

 

 

TimePriorityDescription
2023-01-01 12:43:20Notice (6)DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=6c:cd:d6:88:ae:bc;CMTS-MAC=00:01:5c:b3:b2:65;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:37Notice (6)Honoring MDD; IP provisioning mode = IPv6
1970-01-01 00:00:29Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=6c:cd:d6:88:ae:bc;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:28Critical (3)No Ranging Response received - T3 time-out;CM-MAC=6c:cd:d6:88:ae:bc;CMTS-MAC=00:01:5c:b3:b2:65;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:23Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=6c:cd:d6:88:ae:bc;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:34Critical (3)No Ranging Response received - T3 time-out;CM-MAC=6c:cd:d6:88:ae:bc;CMTS-MAC=00:01:5c:b3:b2:65;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:29Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=6c:cd:d6:88:ae:bc;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:36Critical (3)No Ranging Response received - T3 time-out;CM-MAC=6c:cd:d6:88:ae:bc;CMTS-MAC=00:01:5c:b3:b2:65;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:29Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=6c:cd:d6:88:ae:bc;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:30Critical (3)No Ranging Response received - T3 time-out;CM-MAC=6c:cd:d6:88:ae:bc;CMTS-MAC=00:01:5c:b3:b2:65;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:25Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=6c:cd:d6:88:ae:bc;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:34Critical (3)No Ranging Response received - T3 time-out;CM-MAC=6c:cd:d6:88:ae:bc;CMTS-MAC=00:01:5c:b3:b2:65;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:24Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=6c:cd:d6:88:ae:bc;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2022-12-31 22:17:58Critical (3)Resetting the cable modem due to docsDevResetNow
1970-01-01 00:00:35Critical (3)No Ranging Response received - T3 time-out;CM-MAC=6c:cd:d6:88:ae:bc;CMTS-MAC=00:01:5c:b3:b2:65;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:29Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=6c:cd:d6:88:ae:bc;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2022-12-31 22:13:41Critical (3)Resetting the cable modem due to docsDevResetNow
1970-01-01 00:00:28Critical (3)No Ranging Response received - T3 time-out;CM-MAC=6c:cd:d6:88:ae:bc;CMTS-MAC=00:01:5c:b3:b2:65;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:24Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=6c:cd:d6:88:ae:bc;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:28Critical (3)No Ranging Response received - T3 time-out;CM-MAC=6c:cd:d6:88:ae:bc;CMTS-MAC=00:01:5c:b3:b2:65;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:24Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=6c:cd:d6:88:ae:bc;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:28Critical (3)No Ranging Response received - T3 time-out;CM-MAC=6c:cd:d6:88:ae:bc;CMTS-MAC=00:01:5c:b3:b2:65;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:25Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=6c:cd:d6:88:ae:bc;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:30Critical (3)No Ranging Response received - T3 time-out;CM-MAC=6c:cd:d6:88:ae:bc;CMTS-MAC=00:01:5c:b3:b2:65;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:25Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=6c:cd:d6:88:ae:bc;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:32Critical (3)No Ranging Response received - T3 time-out;CM-MAC=6c:cd:d6:88:ae:bc;CMTS-MAC=00:01:5c:b3:b2:65;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:29Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=6c:cd:d6:88:ae:bc;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:36Critical (3)No Ranging Response received - T3 time-out;CM-MAC=6c:cd:d6:88:ae:bc;CMTS-MAC=00:01:5c:b3:b2:65;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:30Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=6c:cd:d6:88:ae:bc;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:33Critical (3)No Ranging Response received - T3 time-out;CM-MAC=6c:cd:d6:88:ae:bc;CMTS-MAC=00:01:5c:b3:b2:65;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:29Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=6c:cd:d6:88:ae:bc;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:33Critical (3)No Ranging Response received - T3 time-out;CM-MAC=6c:cd:d6:88:ae:bc;CMTS-MAC=00:01:5c:b3:b2:65;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:29Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=6c:cd:d6:88:ae:bc;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:31Critical (3)No Ranging Response received - T3 time-out;CM-MAC=6c:cd:d6:88:ae:bc;CMTS-MAC=00:01:5c:b3:b2:65;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:25Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=6c:cd:d6:88:ae:bc;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2022-12-06 15:02:28Critical (3)Resetting the cable modem due to docsDevResetNow
1970-01-01 00:00:30Critical (3)No Ranging Response received - T3 time-out;CM-MAC=6c:cd:d6:88:ae:bc;CMTS-MAC=00:01:5c:b3:b2:65;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:25Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=6c:cd:d6:88:ae:bc;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:30Critical (3)No Ranging Response received - T3 time-out;CM-MAC=6c:cd:d6:88:ae:bc;CMTS-MAC=00:01:5c:b3:b2:65;CM-QOS=1.1;CM-VER=3.1;
1970-01-01 00:00:24Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=6c:cd:d6:88:ae:bc;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Message 1 of 2
0 Kudos
Reply
FURRYe38
Guru Guru
Guru
‎2023-01-01 10:57 AM
‎2023-01-01 10:57 AM

Re: Takes HOURS for CAX30 to restore functionality after power cycle.

You have lots of criticals that the ISP needs to review and resolve.

 

 

What Firmware version is currently loaded?
Please post a copy and paste of the modems connection status page.
https://kb.netgear.com/30007/How-do-I-obtain-the-cable-connection-information-from-a-NETGEAR-cable-m...

 

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

Message 2 of 2
0 Kudos
Reply
Top Contributors
See All
Discussion stats
  • 1 reply
  • ‎2023-01-01 10:40 AM
  • 465 views
  • 0 kudos
  • 2 in conversation
Announcements

Orbi 770 Series