New Poster
•
2 Messages
Random disconnects have come back
I was facing random disconnects which gradually got worse, comcast eventually ran a new cable for me claiming my current one was too old and could not handle modern internet speeds, things were fine for a bit but now I am dealing with those disconnects again. I cannot access the modem until I reset it. It would be great if someone at comcast can take a look at this and help me troubleshoot the issue because obviously running a new line has not solved it.
Tue May 19 09:41:40 2020 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=00:40:36:65:7a:3c;CMTS-MAC=00:01:5c:83:2e:67;CM-QOS=1.1;CM-VER=3.0; |
Tue May 19 09:41:40 2020 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:65:7a:3c;CMTS-MAC=00:01:5c:83:2e:67;CM-QOS=1.1;CM-VER=3.0; |
Tue May 19 09:41:43 2020 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=00:40:36:65:7a:3c;CMTS-MAC=00:01:5c:83:2e:67;CM-QOS=1.1;CM-VER=3.0; |
Tue May 19 09:41:46 2020 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=00:40:36:65:7a:3c;CMTS-MAC=00:01:5c:83:2e:67;CM-QOS=1.1;CM-VER=3.0; |
Tue May 19 09:41:52 2020 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=00:40:36:65:7a:3c;CMTS-MAC=00:01:5c:83:2e:67;CM-QOS=1.1;CM-VER=3.0; |
Tue May 19 09:41:55 2020 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=00:40:36:65:7a:3c;CMTS-MAC=00:01:5c:83:2e:67;CM-QOS=1.1;CM-VER=3.0; |
Tue May 19 09:41:56 2020 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=00:40:36:65:7a:3c;CMTS-MAC=00:01:5c:83:2e:67;CM-QOS=1.1;CM-VER=3.0; |
Tue May 19 09:41:58 2020 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=00:40:36:65:7a:3c;CMTS-MAC=00:01:5c:83:2e:67;CM-QOS=1.1;CM-VER=3.0; |
Tue May 19 09:42:00 2020 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=00:40:36:65:7a:3c;CMTS-MAC=00:01:5c:83:2e:67;CM-QOS=1.1;CM-VER=3.0; |
Tue May 19 09:42:02 2020 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=00:40:36:65:7a:3c;CMTS-MAC=00:01:5c:83:2e:67;CM-QOS=1.1;CM-VER=3.0; |
Tue May 19 09:42:03 2020 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=00:40:36:65:7a:3c;CMTS-MAC=00:01:5c:83:2e:67;CM-QOS=1.1;CM-VER=3.0; |
Tue May 19 09:42:04 2020 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=00:40:36:65:7a:3c;CMTS-MAC=00:01:5c:83:2e:67;CM-QOS=1.1;CM-VER=3.0; |
Tue May 19 09:42:08 2020 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=00:40:36:65:7a:3c;CMTS-MAC=00:01:5c:83:2e:67;CM-QOS=1.1;CM-VER=3.0; |
Tue May 19 09:42:10 2020 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=00:40:36:65:7a:3c;CMTS-MAC=00:01:5c:83:2e:67;CM-QOS=1.1;CM-VER=3.0; |
Tue May 19 09:42:10 2020 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:65:7a:3c;CMTS-MAC=00:01:5c:83:2e:67;CM-QOS=1.1;CM-VER=3.0; |
Tue May 19 09:42:12 2020 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=00:40:36:65:7a:3c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
Tue May 19 09:42:13 2020 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=00:40:36:65:7a:3c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
Thu May 28 07:16:41 2020 | Critical (3) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:65:7a:3c;CMTS-MAC=00:01:5c:83:2e:67;CM-QOS=1.1;CM-VER=3.0; |
Time Not Established | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=00:40:36:65:7a:3c;CMTS-MAC=00:01:5c:83:2e:67;CM-QOS=1.0;CM-VER=3.0; |
Tue Jun 02 04:07:10 2020 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=00:40:36:65:7a:3c;CMTS-MAC=00:01:5c:83:2e:67;CM-QOS=1.1;CM-VER=3.0; |
Tue Jun 02 04:09:49 2020 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=00:40:36:65:7a:3c;CMTS-MAC=00:01:5c:83:2e:67;CM-QOS=1.1;CM-VER=3.0; |
Tue Jun 02 04:09:49 2020 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:65:7a:3c;CMTS-MAC=00:01:5c:83:2e:67;CM-QOS=1.1;CM-VER=3.0; |
Tue Jun 02 04:10:17 2020 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=00:40:36:65:7a:3c;CMTS-MAC=00:01:5c:83:2e:67;CM-QOS=1.1;CM-VER=3.0; |
Tue Jun 02 04:10:17 2020 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:65:7a:3c;CMTS-MAC=00:01:5c:83:2e:67;CM-QOS=1.1;CM-VER=3.0; |
Tue Jun 02 04:10:46 2020 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=00:40:36:65:7a:3c;CMTS-MAC=00:01:5c:83:2e:67;CM-QOS=1.1;CM-VER=3.0; |
Tue Jun 02 04:10:46 2020 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:65:7a:3c;CMTS-MAC=00:01:5c:83:2e:67;CM-QOS=1.1;CM-VER=3.0; |
Tue Jun 02 04:11:05 2020 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=00:40:36:65:7a:3c;CMTS-MAC=00:01:5c:83:2e:67;CM-QOS=1.1;CM-VER=3.0; |
Tue Jun 02 04:11:05 2020 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:65:7a:3c;CMTS-MAC=00:01:5c:83:2e:67;CM-QOS=1.1;CM-VER=3.0; |
Tue Jun 02 04:11:08 2020 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=00:40:36:65:7a:3c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
Tue Jun 02 04:13:54 2020 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=00:40:36:65:7a:3c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
Time Not Established | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=00:40:36:65:7a:3c;CMTS-MAC=00:01:5c:83:2e:67;CM-QOS=1.0;CM-VER=3.0; |
Time Not Established | Notice (6) | Honoring MDD; IP provisioning mode = IPv6 |
Connection
EG
Expert
•
111.6K Messages
5 years ago
The signal stats are o/k but the error log entries indicate that something is going on. Perhaps there is noise ingress into the line(s) somewhere.
There are other signal stat figures that can't be read by the modem. They are the "Upstream Rx Power" (Upstream Receive Power Level), the "Upstream SNR Ch." (Upstream Signal To Noise Ratio), and the "Upstream ICFR" (In Channel Frequency Response). These are as equally important in diagnosing connectivity issues as are the modem's stats.
I'm going to escalate your issue to the Comcast corporate employees that are available to these boards. They will be able to poll the CMTS to see whether or not everything is in the green zone, see your node / cable plant and modem health, and also see a history plot for the modem. You should get a reply here in your topic. Good luck !
0
0
XfinityJoeTru
Official Employee
•
7K Messages
5 years ago
Hi ishtar96. We appreciate you visiting and posting on our Forums. I can assist with further troubleshooting your intermittent connectivity issues. I will start with polling your CMTS for real-time and also historical RF signal reports produced by your modem. I can also check your local Node/Plant for degradation or error reports. So I can get started, please send me a private message and include your full name so I can access your equipment.
0
ishtar96
New Poster
•
2 Messages
5 years ago
Thanks Joe, it just randomly went down again and I had to restart the modem.
0
0