Visitor
•
3 Messages
Modem disconnects SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
Hello, been having issues with frequent modem disconnects. Started about a month ago. It would disconnect about 1-2 times a week. Since last week its now happening multiple times a day. I called tech support on April 2nd and they said the fixed the issue. They said it was a network clutter issue and "cleaned the congestion and clutter in the network". They had me restart my modem. It worked well for the rest of the day and most of today. But today (April 3rd) at 7:43pm PDT the modem disconnected again.
I logged in and grabbed the logs from the cable modem (removed mac address):
Time | Priority | Description |
Mon Apr 03 18:52:35 2023 | Critical (3) | No Ranging Response received - T3 time-out;;CM-QOS=1.0;CM-VER=3.0; |
Mon Apr 03 18:52:35 2023 | Warning (5) | B-INIT-RNG Failure - Retries exceeded;;CM-QOS=1.0;CM-VER=3.0; |
Mon Apr 03 18:52:39 2023 | Notice (6) | Honoring MDD; IP provisioning mode = IPv6 |
Mon Apr 03 18:53:19 2023 | Critical (3) | DHCP failed - DHCP Solicit sent, No DHCP Advertise received;;CM-QOS=1.0;CM-VER=3.0; |
Mon Apr 03 18:53:20 2023 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;;CM-QOS=1.0;CM-VER=3.0; |
Mon Apr 03 18:53:27 2023 | Warning (5) | Lost MDD Timeout;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
Mon Apr 03 18:53:37 2023 | Critical (3) | No UCDs Received - Timeout;;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
Mon Apr 03 18:53:40 2023 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
Mon Apr 03 18:53:47 2023 | Warning (5) | Lost MDD Timeout;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
Mon Apr 03 18:53:57 2023 | Critical (3) | No UCDs Received - Timeout;;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
Mon Apr 03 18:54:00 2023 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
Mon Apr 03 18:54:07 2023 | Warning (5) | Lost MDD Timeout;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
Mon Apr 03 18:54:17 2023 | Critical (3) | No UCDs Received - Timeout;;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
Mon Apr 03 18:54:20 2023 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
Mon Apr 03 18:54:27 2023 | Warning (5) | Lost MDD Timeout;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
Mon Apr 03 18:54:37 2023 | Critical (3) | No UCDs Received - Timeout;;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
Mon Apr 03 18:54:40 2023 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
Mon Apr 03 18:54:47 2023 | Warning (5) | Lost MDD Timeout;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
Mon Apr 03 18:54:57 2023 | Critical (3) | No UCDs Received - Timeout;;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
Mon Apr 03 18:55:08 2023 | Notice (6) | Honoring MDD; IP provisioning mode = IPv6 |
Mon Apr 03 18:55:45 2023 | Critical (3) | DHCP failed - DHCP Solicit sent, No DHCP Advertise received;;CM-QOS=1.0;CM-VER=3.0; |
Mon Apr 03 18:55:53 2023 | Warning (5) | Lost MDD Timeout;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
Mon Apr 03 18:56:03 2023 | Critical (3) | No UCDs Received - Timeout;;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
Mon Apr 03 18:56:13 2023 | Warning (5) | Lost MDD Timeout;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
Mon Apr 03 18:56:23 2023 | Critical (3) | No UCDs Received - Timeout;;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
Mon Apr 03 18:56:34 2023 | Warning (5) | Lost MDD Timeout;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
Mon Apr 03 18:56:44 2023 | Critical (3) | No UCDs Received - Timeout;;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
Mon Apr 03 18:58:59 2023 | Critical (3) | No Ranging Response received - T3 time-out;;CM-QOS=1.0;CM-VER=3.0; |
Mon Apr 03 18:59:43 2023 | Notice (6) | Honoring MDD; IP provisioning mode = IPv6 |
Mon Apr 03 19:00:07 2023 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;;CM-QOS=1.1;CM-VER=3.0; |
Mon Apr 03 19:01:13 2023 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;;CM-QOS=1.1;CM-VER=3.0; |
Mon Apr 03 19:01:23 2023 | Notice (6) | Honoring MDD; IP provisioning mode = IPv6 |
Any help would be greatly appreciated.
Thanks
No Responses!