Community Forum

Random SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

Highlighted
Frequent Visitor

Random SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

So for the close a week, I've been having random short drops of internet connectivity.. All the lights are still on and my modem still says it has a connection eventhough pings to google or anywhere time out. I'm running the coax from the modem straight to the wall. I've contacted customer support and they said everything looked good on their end. So I'm super confused.

Here are my logs, Up/Down, and SNR

Thank you advance for any insight provided πŸ™‚

 

1970-1-1, 00:07:35 Warning (5) ToD request sent - No Response received;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:01:5c:66:b0:6c;CM-QOS=1.1;CM-VER=3.0;
1970-1-1, 00:07:19 Warning (5) ToD request sent - No Response received;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:01:5c:66:b0:6c;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:07:05 Notice (6) Honoring MDD; IP provisioning mode = IPv6
1970-1-1, 00:06:55 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:06:49 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:06:48 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:06:47 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:06:47 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:06:44 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:06:44 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:06:44 Critical (3) No UCDs Received - Timeout;;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:06:34 Warning (5) Lost MDD Timeout;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:06:27 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:06:26 Critical (3) No UCDs Received - Timeout;;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:06:16 Warning (5) Lost MDD Timeout;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:06:09 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:06:08 Critical (3) No UCDs Received - Timeout;;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:05:58 Warning (5) Lost MDD Timeout;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:05:51 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:01:5c:66:b0:6c;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:05:49 Critical (3) DHCP failed - DHCP Solicit sent, No DHCP Advertise received;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:01:5c:66:b0:6c;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:05:12 Notice (6) Honoring MDD; IP provisioning mode = IPv6
1970-1-1, 00:05:08 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:01:5c:66:b0:6c;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:05:02 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:01:5c:66:b0:6c;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:05:00 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:01:5c:66:b0:6c;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:04:58 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:01:5c:66:b0:6c;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:04:57 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:01:5c:66:b0:6c;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:04:56 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:01:5c:66:b0:6c;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:04:55 Critical (3) DHCP failed - DHCP Solicit sent, No DHCP Advertise received;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:01:5c:66:b0:6c;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:04:17 Notice (6) Honoring MDD; IP provisioning mode = IPv6
1970-1-1, 00:04:10 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:01:5c:66:b0:6c;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:04:05 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:01:5c:66:b0:6c;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:04:04 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:01:5c:66:b0:6c;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:04:02 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:01:5c:66:b0:6c;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:03:59 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:01:5c:66:b0:6c;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:03:58 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:01:5c:66:b0:6c;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:03:57 Critical (3) DHCP failed - DHCP Solicit sent, No DHCP Advertise received;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:01:5c:66:b0:6c;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:03:13 Notice (6) Honoring MDD; IP provisioning mode = IPv6
1970-1-1, 00:03:03 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:03:02 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:03:01 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;



Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 13 573000000 Hz -3.8 dBmV 40.3 dB 0 0
2 Locked QAM256 14 579000000 Hz -3.6 dBmV 40.3 dB 0 0
3 Locked QAM256 15 585000000 Hz -3.8 dBmV 40.3 dB 0 0
4 Locked QAM256 16 591000000 Hz -3.8 dBmV 40 dB 0 0
5 Locked QAM256 17 597000000 Hz -3.9 dBmV 40 dB 0 0
6 Locked QAM256 18 603000000 Hz -4 dBmV 40.1 dB 0 0
7 Locked QAM256 19 609000000 Hz -3.8 dBmV 40 dB 0 0
8 Locked QAM256 20 615000000 Hz -3.6 dBmV 40.4 dB 0 0
9 Locked QAM256 21 621000000 Hz -3.6 dBmV 40.3 dB 0 0
10 Locked QAM256 22 627000000 Hz -3.7 dBmV 40.4 dB 0 0
11 Locked QAM256 23 633000000 Hz -4.2 dBmV 40.3 dB 0 0
12 Locked QAM256 24 639000000 Hz -4.1 dBmV 40 dB 0 0
13 Locked QAM256 25 645000000 Hz -4.4 dBmV 40.3 dB 0 0
14 Locked QAM256 26 651000000 Hz -4.5 dBmV 40.1 dB 0 0
15 Locked QAM256 27 657000000 Hz -4.7 dBmV 39.9 dB 0 0
16 Locked QAM256 28 663000000 Hz -5.1 dBmV 39.8 dB 0 0
17 Locked QAM256 29 669000000 Hz -6.2 dBmV 38.4 dB 0 0
18 Locked QAM256 30 675000000 Hz -6.6 dBmV 38.1 dB 0 0
19 Locked QAM256 31 681000000 Hz -6.7 dBmV 37.9 dB 0 0
20 Locked QAM256 32 687000000 Hz -6.8 dBmV 38.2 dB 0 0
21 Locked QAM256 33 693000000 Hz -7 dBmV 38.2 dB 0 0
22 Locked QAM256 34 699000000 Hz -7.2 dBmV 37.8 dB 0 0
23 Locked QAM256 35 705000000 Hz -7.3 dBmV 38.1 dB 0 0
24 Locked QAM256 36 711000000 Hz -7.5 dBmV 37.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 16600000 Hz 46.3 dBmV
2 Locked ATDMA 5 5120 Ksym/sec 35800000 Hz 48 dBmV
3 Locked ATDMA 6 5120 Ksym/sec 29400000 Hz 47.8 dBmV
4 Locked ATDMA 7 5120 Ksym/sec 23000000 Hz 47 dBmV
5 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
6 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
7 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
8 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
Highlighted
Frequent Visitor

Re: Random SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

This is the kind of packet loss I'm having.. This is getting ridiculous at this point.. EVERYTHING was working fine till about a week ago. Now I can't work.

 

sorry if you can't see the image

https://i.imgur.com/oGp1hNo.png

Highlighted
Frequent Visitor

Re: Random SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

I've timed the dropouts to about every 10-20 minutes there's packetloss for all together 1min. There are periods where there's no problems for almost up to an hour but overall in a one hour period, there will be atleast 2-4 minutes of packet loss.

Any image I try and upload just shows a big triangle, here is an imgur link


https://i.imgur.com/3utslci.png

 

 

I hope anyone can provide any help on this.. I feel this is a semi-common thing now.

Thank you reading this mess

Highlighted
Frequent Visitor

Re: Random SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

It means a lot of the issues are coming from 

be-20214-cr02.miami.fl.ibone.comcast.net
be-3211-pe11.nota.fl.ibone.comcast.net
and 
2001:4860::9:4000:dd70

They have the highest packet loss

https://imgur.com/AifyRsk

Highlighted
Frequent Visitor

Re: Random SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

Just an update:

Internet went completely down around 230 PM and did not come back until about 8ish AM this morning. It's still unstable and after several phone calls to Customer Support, I come to find a technician won't be able to come out here for about a month. A MONTH! My livelihood is affected by this, I would love to pay my bills, but with the shooty, unstable connection we all seem to be experiencing, I feel Comcast might be one of those that doesn't get paid this month. 

I understand the situation going on. But really? The infrastructure is practically collapsing under the weight of it's subscribers.

The highest amount of packet loss comes from these two locations:
be-20214-cr02.miami.fl.ibone.comcast.net
be-12274-pe01.nota.fl.ibone.comcast.net

Why is that happening?

Highlighted
Frequent Visitor

Re: Random SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

5/3 Update:

 

Since my last update my internet had corrected itself for about 5 days. Then a few times it dropped for a few seconds and continued to work as expected. Now as of 2AM today, it's a repeat of my original post. 

No one from Comcast has contacted me or replied to any of my posts or requests on here or twitter.. This is getting ridiculous. 

Here is the last 6 hours
https://imgur.com/gGaGrXj

Logs:

Startup Procedure
Procedure Status Comment
Acquire Downstream Channel 465000000 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 37 465000000 Hz -3.8 dBmV 40.3 dB 0 0
2 Locked QAM256 38 471000000 Hz -4 dBmV 40.2 dB 0 0
3 Locked QAM256 39 477000000 Hz -4.3 dBmV 40.4 dB 0 0
4 Locked QAM256 40 483000000 Hz -4.2 dBmV 40.5 dB 0 0
5 Locked QAM256 1 489000000 Hz -4.4 dBmV 40.3 dB 0 0
6 Locked QAM256 2 495000000 Hz -4.6 dBmV 40.2 dB 0 0
7 Locked QAM256 3 507000000 Hz -3.9 dBmV 39.9 dB 0 0
8 Locked QAM256 4 513000000 Hz -2.5 dBmV 41.4 dB 0 0
9 Locked QAM256 5 519000000 Hz -2.3 dBmV 40.9 dB 0 0
10 Locked QAM256 6 525000000 Hz -2.1 dBmV 41.8 dB 0 0
11 Locked QAM256 7 531000000 Hz -2.2 dBmV 41.1 dB 0 0
12 Locked QAM256 8 537000000 Hz -2.5 dBmV 41.4 dB 0 0
13 Locked QAM256 9 543000000 Hz -2.7 dBmV 41.7 dB 0 0
14 Locked QAM256 10 555000000 Hz -3 dBmV 41.8 dB 0 0
15 Locked QAM256 11 561000000 Hz -2.9 dBmV 40.5 dB 0 0
16 Locked QAM256 12 567000000 Hz -3.1 dBmV 41.8 dB 0 0
17 Locked QAM256 13 573000000 Hz -3.9 dBmV 41.4 dB 0 0
18 Locked QAM256 14 579000000 Hz -4 dBmV 41.3 dB 0 0
19 Locked QAM256 15 585000000 Hz -4.2 dBmV 41.3 dB 0 0
20 Locked QAM256 16 591000000 Hz -4.2 dBmV 40.4 dB 0 0
21 Locked QAM256 17 597000000 Hz -4.1 dBmV 40.9 dB 0 0
22 Locked QAM256 18 603000000 Hz -4.3 dBmV 40.8 dB 0 0
23 Locked QAM256 19 609000000 Hz -3.9 dBmV 40.8 dB 0 0
24 Locked QAM256 20 615000000 Hz -3.8 dBmV 41.5 dB 0 0
 
Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 5 5120 Ksym/sec 35800000 Hz 47.5 dBmV
2 Locked ATDMA 6 5120 Ksym/sec 29400000 Hz 47.5 dBmV
3 Locked ATDMA 7 5120 Ksym/sec 23000000 Hz 46.5 dBmV
4 Locked ATDMA 8 5120 Ksym/sec 16600000 Hz 45.8 dBmV
5 Locked ATDMA 9 1280 Ksym/sec 39800000 Hz 47.3 dBmV
6 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
7 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
8 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
 
Extended Upstream Transmit Power
Enable Extended Upstream Transmit Power
 
Current System Time:Sun May 03 13:24:41 2020
System Up Time:02:59:30

 

 
 
Time Priority Description
1970-1-1, 00:00:52 Notice (6) Honoring MDD; IP provisioning mode = IPv6
1970-1-1, 00:00:45 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:01:5c:66:b0:6c;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:41 Notice (6) WiFi Interface [wl1] set to Channel 153 (Side-Band Channel:N/A) - Reason:INIT
1970-1-1, 00:00:41 Notice (6) WiFi Interface [wl0] set to Channel 10 (Side-Band Channel:N/A) - Reason:INIT
1970-1-1, 00:00:39 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:46 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:01:5c:66:b0:6c;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:39 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:45 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:01:5c:66:b0:6c;CM-QOS=1.0;CM-VER=3.0;
2020-4-28, 23:16:20 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2020-4-28, 23:16:19 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2020-4-28, 23:16:15 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2020-4-28, 23:16:14 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2020-4-28, 23:16:13 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2020-4-28, 23:16:13 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2020-4-28, 23:16:04 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2020-4-28, 23:16:04 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2020-4-28, 23:15:23 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2020-4-28, 23:15:23 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2020-4-28, 23:15:21 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2020-4-28, 23:15:21 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2020-4-28, 23:14:42 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2020-4-28, 23:14:42 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2020-4-28, 23:14:41 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2020-4-28, 23:14:41 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2020-4-28, 23:14:38 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2020-4-28, 23:14:38 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2020-4-28, 23:14:34 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2020-4-28, 23:14:34 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2020-4-28, 23:14:30 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2020-4-28, 23:14:30 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2020-4-28, 23:14:27 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2020-4-28, 23:14:26 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2020-4-28, 23:14:24 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2020-4-28, 23:14:23 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2020-4-28, 23:14:11 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:01:5c:66:b0:6c;CM-QOS=1.1;CM-VER=3.0;
2020-4-28, 23:14:02 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:01:5c:66:b0:6c;CM-QOS=1.1;CM-VER=3.0;
2020-4-28, 23:14:01 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:01:5c:66:b0:6c;CM-QOS=1.1;CM-VER=3.0;
2020-4-28, 23:13:19 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:01:5c:66:b0:6c;CM-QOS=1.1;CM-VER=3.0;
2020-4-28, 23:13:18 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:01:5c:66:b0:6c;CM-QOS=1.1;CM-VER=3.0;
2020-4-28, 23:13:15 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=bc:a5:11:f4:8b:5c;CMTS-MAC=00:01:5c:66:b0:6c;CM-QOS=1.1;CM-VER=3.0;

 

 

Very similar to EVERYONE elses problem. FIX YOUR NODES! Can't imagine how employees of the company are dealing with this if they are experiencing the same problems. Like how is anyone suppose to work and live when the means of doing that is UNRELIABLE.

Highlighted
New Poster

Re: Random SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

Didn't necessarily see a resolution, but wanted to share w/ the forum that I'm going thru the same thing now (10-14-20) w/ Comcast.  

 

Yes, I have the same dropped packed loss msgs (SYNC) in my NetGear's C7800 event log, and my connection is behaving similarly to how this original posted described their own connection issues.

 

Being in IT all my life and familiar with Cisco router,s networking TCP/IP architectures, and physical cabling infrastructures, I had Comcast come out today and I had them first test the connection from the street to the service box outside of my apt building.  No issues there...

 

Next, I had them test from the service box to the interior wall jack in my office.  As I had suspected, the physical cable going from the box, thru the attic, to my wall jack is the culprit.  How?  Because I had them run some egress/ingress testing on the physical line (i.e. the coax cable), and we could see exactly the level of attenuation, noise, signal interference, etc. on that piece of the line was way beyond acceptable parameters, hence the packets were being dropped by the time they reached the wall jack, and eventually to my router.

 

Bottom line:  replace the coax cable.  Since Comcast (not AT&T) refuses to go in the attic to replace the cable, and the landlord isn't legally obligated to replace the internet cable (landlords in CA are legally obligated to provide a hard-wired "connection" for a landline for purposes of 911 emergency services to meet the definition of "basic human occupancy".  An internet coax cable isn't a requirement of that legal definition (although it should be by today's infrastructure standards).

 

Anyways, the landlord in now in the process of obtaining a quote from a 3rd party cabling provider to run a new cable line from the service box....to the wall jack in my office so I can continue working from home (like many ppl are doing now in today's times).

 

Once the new "attic" cable gets installed, packet loss should be reduced to an absolute minimum (FYI...it's impossible to eliminate 100% of all packet loss, but one can minimize it to almost nothing, as well as significantly reduce any dropped connection due to a degradation of the physical wiring coming from the wall jack).

 

Yeah, I thought of going to AT&T, but switching services doesn't fix the actual problem:  the bad wire in the attic.  It's just unfortunate that, if we don't own the building, then we're at the mercy of 3rd party providers to do the work for us...on their own timelines & schedules.

 

If I owned my own home (I'm working on it...lol!), this would have all be solved w/n a hour. πŸ˜

 

Well, hope this info helps anyone who's going through the same experience as myself.

Oh yeah...friendly reminder, once you get your connection re-established, make sure to clear out your router's logs so, if errors persist, they can be tracked & acted upon...assuming the onsite tech nows what to look for in the router's output, and what the error codes mean.... πŸ˜‰

 

Thanks!