Visitor
•
7 Messages
Netgear CM500 T3 or T4 Timeouts
I'm new to the forums here. I originally had the 200 Mbps Down/10 Mbps Up internet plan, but got upgraded to the 400 Mbps Down tier last October. Since my Netgear CM500 modem can only handle up to 300 Mbps, I downgraded back to the plan I had before. Speeds are consistently around 238 Mbps down/12 Mbps up, occasionally crossing above 240 Mbps. Lately, I seem to be having some issues, though. With random dropouts, disconnects, having to frequently reboot, the MyAccount app stating it can't connect to or send a signal to the router, etc. I recently disconnected the modem, unplugging all the cables (coax, ethernet, power), and reconnected them again as a result of these ongoing issues.
Regarding my personal set up, I have the modem directly connected via coax cable to the wall outlet. There are no splitters between the wall and the modem. I also have a TP-Link AC2300 wifi router connected to the modem. Btw, the modem has the latest firmware: V1.01.14 as well as the router, too. When I accessed the Netgear gateway for the modem, I saw some "critical" errors and such in the log:
Apply Cancel 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 579000000 Hz Locked Connectivity State OK Operational Boot State OK Operational Security Enabled BPI+ IP Provisioning Mode Honor MDD honorMdd(4) Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables 1 Locked QAM256 17 579000000 Hz 6.4 dBmV 41.1 dB 0 0 2 Locked QAM256 18 585000000 Hz 5.9 dBmV 40.7 dB 0 0 3 Locked QAM256 19 591000000 Hz 6.2 dBmV 40.8 dB 0 0 4 Locked QAM256 20 597000000 Hz 6.7 dBmV 41.1 dB 0 0 5 Locked QAM256 21 603000000 Hz 6.4 dBmV 41 dB 0 0 6 Locked QAM256 22 609000000 Hz 6.1 dBmV 40.7 dB 0 0 7 Locked QAM256 23 615000000 Hz 5.9 dBmV 40.3 dB 0 0 8 Locked QAM256 24 621000000 Hz 6 dBmV 40.4 dB 0 0 9 Locked QAM256 25 627000000 Hz 6 dBmV 40.3 dB 0 0 10 Locked QAM256 26 633000000 Hz 6.5 dBmV 40.3 dB 0 0 11 Locked QAM256 27 639000000 Hz 6.9 dBmV 40.3 dB 0 0 12 Locked QAM256 28 645000000 Hz 7.2 dBmV 40.8 dB 0 0 13 Locked QAM256 29 651000000 Hz 7.1 dBmV 40.6 dB 0 0 14 Locked QAM256 30 657000000 Hz 7.3 dBmV 40.8 dB 0 0 15 Locked QAM256 31 663000000 Hz 7.3 dBmV 40.9 dB 0 0 16 Locked QAM256 32 669000000 Hz 7.5 dBmV 40.9 dB 0 0 Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 8 5120 Ksym/sec 22800000 Hz 42.5 dBmV 2 Locked ATDMA 6 5120 Ksym/sec 35600000 Hz 42.8 dBmV 3 Locked ATDMA 7 5120 Ksym/sec 29200000 Hz 42.3 dBmV 4 Locked ATDMA 9 5120 Ksym/sec 16400000 Hz 43.8 dBmV Extended Upstream Transmit Power Enable Extended Upstream Transmit Power Current System Time:Fri Jan 27 20:20:05 2023 System Up Time:02:04:58
Time | Priority | Description |
1970-1-1, 00:00:31 | Notice (6) | Honoring MDD; IP provisioning mode = IPv6 |
1970-1-1, 00:00:28 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.0;CM-VER=3.0; |
1970-1-1, 00:00:22 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=;CM-QOS=1.0;CM-VER=3.0; |
1970-1-1, 00:00:21 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=;CM-QOS=1.0;CM-VER=3.0; |
2023-1-27, 17:33:59 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-MAC==1.1;CM-VER=3.0; |
2023-1-27, 17:29:33 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0; |
2023-1-27, 17:29:32 | Critical (3) | 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=;CMTS-MAC=-QOS=1.1;CM-VER=3.0; |
2023-1-27, 17:29:32 | Critical (3) | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=;CMTS-MAC=-QOS=1.1;CM-VER=3.0; |
2023-1-27, 17:29:07 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0; |
2023-1-27, 17:28:54 | Critical (3) | 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0; |
2023-1-27, 17:28:54 | Critical (3) | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0; |
2023-1-27, 17:21:16 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0; |
1970-1-1, 00:00:26 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.0;CM-VER=3.0; |
1970-1-1, 00:00:21 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=;CM-QOS=1.0;CM-VER=3.0; |
2023-1-27, 16:23:11 | Critical (3) | Resetting the cable modem due to docsDevResetNow |
2023-1-26, 10:42:11 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0; |
1970-1-1, 00:00:27 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.0;CM-VER=3.0; |
2023-1-25, 10:36:45 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=;CM-QOS=1.0;CM-VER=3.0; |
2023-1-25, 10:36:44 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=;CM-QOS=1.0;CM-VER=3.0; |
2023-1-25, 10:36:28 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=;CM-QOS=1.0;CM-VER=3.0; |
2023-1-25, 10:36:28 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=;CM-QOS=1.0;CM-VER=3.0; |
2023-1-25, 10:36:25 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0; |
2023-1-25, 10:36:17 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0; |
2023-1-25, 10:36:16 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0; |
2023-1-25, 10:36:13 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0; |
2023-1-25, 10:36:12 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0; |
2023-1-25, 10:36:09 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0; |
2023-1-25, 10:36:08 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0; |
2023-1-25, 10:33:49 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0; |
2023-1-25, 10:33:42 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0; |
2023-1-25, 10:33:36 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0; |
2023-1-25, 10:32:44 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0; |
2023-1-25, 10:32:37 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0; |
2023-1-25, 10:31:29 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0; |
2023-1-25, 10:31:05 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC==1.1;CM-VER=3.0; |
2023-1-25, 10:31:03 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0; |
2023-1-25, 10:30:12 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0; |
2023-1-25, 10:29:30 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0; |
2023-1-25, 10:29:23 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0; |
2023-1-25, 10:29:18 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0; |
From a quick search on the forums, it seems others had similar issues with this router. Is there anything I can do on my end, or should I just go ahead and give tech support a call, possibly to set up an appointment for a technician to come out? Lastly, there were quite a few outages in our subdivision community lately as I noted a presence of Xfinity trucks out and about. Not sure if they were upgrading or repairing the current infrastructure.
Thanks!
No Responses!