NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
smjpja
Jan 01, 2023Follower
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 |
|
| Time | Priority | Description |
| 2023-01-01 12:43:20 | Notice (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:37 | Notice (6) | Honoring MDD; IP provisioning mode = IPv6 |
| 1970-01-01 00:00:29 | Critical (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:28 | Critical (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:23 | Critical (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:34 | Critical (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:29 | Critical (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:36 | Critical (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:29 | Critical (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:30 | Critical (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:25 | Critical (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:34 | Critical (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:24 | Critical (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:58 | Critical (3) | Resetting the cable modem due to docsDevResetNow |
| 1970-01-01 00:00:35 | Critical (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:29 | Critical (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:41 | Critical (3) | Resetting the cable modem due to docsDevResetNow |
| 1970-01-01 00:00:28 | Critical (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:24 | Critical (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:28 | Critical (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:24 | Critical (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:28 | Critical (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:25 | Critical (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:30 | Critical (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:25 | Critical (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:32 | Critical (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:29 | Critical (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:36 | Critical (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:30 | Critical (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:33 | Critical (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:29 | Critical (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:33 | Critical (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:29 | Critical (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:31 | Critical (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:25 | Critical (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:28 | Critical (3) | Resetting the cable modem due to docsDevResetNow |
| 1970-01-01 00:00:30 | Critical (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:25 | Critical (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:30 | Critical (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:24 | Critical (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; |
1 Reply
- FURRYe38Guru - Experienced User
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-modem-modem-routerHave 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-Modems/m-p/1530376#M12853
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