Community Forum

SYNC Timing Synchronization failure

Regular Visitor

SYNC Timing Synchronization failure

I am receiving numerous critical errors in my modem log.  Can anyone offer a clue about what is going on?

My status information is below.  This is from an Arris 6183 CableModem.

 

Event Log

The table below contains the log of events that the SB6183 has detected. This log can be important to the service provider to help diagnose and correct problems, if any should occur.

 
Time Priority Description
Tue Jul 31 15:35:29 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=d4:04:cd:98:0b:2c;CMTS-MAC=80:e0:1d:02:e7:22;CM-QOS=1.1;CM-VER=3.0;
Tue Jul 31 15:35:16 2018 Warning (5) MDD message timeout;CM-MAC=d4:04:cd:98:0b:2c;CMTS-MAC=80:e0:1d:02:e7:22;CM-QOS=1.1;CM-VER=3.0;
Tue Jul 31 15:35:16 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=d4:04:cd:98:0b:2c;CMTS-MAC=80:e0:1d:02:e7:22;CM-QOS=1.1;CM-VER=3.0;
Tue Jul 31 15:34:39 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=d4:04:cd:98:0b:2c;CMTS-MAC=80:e0:1d:02:e7:22;CM-QOS=1.1;CM-VER=3.0;
Tue Jul 31 15:34:38 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=d4:04:cd:98:0b:2c;CMTS-MAC=80:e0:1d:02:e7:22;CM-QOS=1.1;CM-VER=3.0;
Tue Jul 31 15:34:28 2018 Warning (5) MDD message timeout;CM-MAC=d4:04:cd:98:0b:2c;CMTS-MAC=80:e0:1d:02:e7:22;CM-QOS=1.1;CM-VER=3.0;
Tue Jul 31 15:34:28 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=d4:04:cd:98:0b:2c;CMTS-MAC=80:e0:1d:02:e7:22;CM-QOS=1.1;CM-VER=3.0;
Tue Jul 31 15:26:50 2018 Warning (5) MDD message timeout;CM-MAC=d4:04:cd:98:0b:2c;CMTS-MAC=80:e0:1d:02:e7:22;CM-QOS=1.1;CM-VER=3.0;
Tue Jul 31 15:26:50 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=d4:04:cd:98:0b:2c;CMTS-MAC=80:e0:1d:02:e7:22;CM-QOS=1.1;CM-VER=3.0;
Mon Jul 30 13:10:13 2018 Warning (5) MDD message timeout;CM-MAC=d4:04:cd:98:0b:2c;CMTS-MAC=80:e0:1d:02:e7:22;CM-QOS=1.1;CM-VER=3.0;
Mon Jul 30 13:10:10 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=d4:04:cd:98:0b:2c;CMTS-MAC=80:e0:1d:02:e7:22;CM-QOS=1.1;CM-VER=3.0;
Mon Jul 30 13:09:58 2018 Warning (5) MDD message timeout;CM-MAC=d4:04:cd:98:0b:2c;CMTS-MAC=80:e0:1d:02:e7:22;CM-QOS=1.1;CM-VER=3.0;
Mon Jul 30 13:09:58 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=d4:04:cd:98:0b:2c;CMTS-MAC=80:e0:1d:02:e7:22;CM-QOS=1.1;CM-VER=3.0;
Mon Jul 30 13:09:42 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=d4:04:cd:98:0b:2c;CMTS-MAC=80:e0:1d:02:e7:22;CM-QOS=1.1;CM-VER=3.0;
Mon Jul 30 13:01:40 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=d4:04:cd:98:0b:2c;CMTS-MAC=80:e0:1d:02:e7:22;CM-QOS=1.1;CM-VER=3.0;
Mon Jul 30 13:01:36 2018 Warning (5) MDD message timeout;CM-MAC=d4:04:cd:98:0b:2c;CMTS-MAC=80:e0:1d:02:e7:22;CM-QOS=1.1;CM-VER=3.0;
Mon Jul 30 13:01:36 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=d4:04:cd:98:0b:2c;CMTS-MAC=80:e0:1d:02:e7:22;CM-QOS=1.1;CM-VER=3.0;
Mon Jul 30 13:01:18 2018 Warning (5) MDD message timeout;CM-MAC=d4:04:cd:98:0b:2c;CMTS-MAC=80:e0:1d:02:e7:22;CM-QOS=1.1;CM-VER=3.0;
Mon Jul 30 13:01:08 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=d4:04:cd:98:0b:2c;CMTS-MAC=80:e0:1d:02:e7:22;CM-QOS=1.1;CM-VER=3.0;
Mon Jul 30 13:01:07 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=d4:04:cd:98:0b:2c;CMTS-MAC=80:e0:1d:02:e7:22;CM-QOS=1.1;CM-VER=3.0;
Mon Jul 30 13:01:04 2018 Warning (5) MDD message timeout;CM-MAC=d4:04:cd:98:0b:2c;CMTS-MAC=80:e0:1d:02:e7:22;CM-QOS=1.1;CM-VER=3.0;
Mon Jul 30 13:01:04 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=d4:04:cd:98:0b:2c;CMTS-MAC=80:e0:1d:02:e7:22;CM-QOS=1.1;CM-VER=3.0;

 

 

 

Status

The statuses listed show the connection state of the cable modem. They are used by your service provider to evaluate the operation of the cable modem.

 
Startup Procedure
Procedure Status Comment
Acquire Downstream Channel   Locked
Connectivity State OK Operational
Boot State OK Operational
Configuration File OK  
Security Enabled BPI+
DOCSIS Network Access Enabled Allowed  

 
Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Corrected Uncorrectables
1 Locked QAM256 21 597000000 Hz -4.5 dBmV 40.1 dB 191 129
2 Locked QAM256 31 657000000 Hz -4.9 dBmV 40.1 dB 163 0
3 Locked QAM256 17 573000000 Hz -3.6 dBmV 40.5 dB 29 0
4 Locked QAM256 18 579000000 Hz -3.8 dBmV 40.3 dB 43 0
5 Locked QAM256 19 585000000 Hz -4.0 dBmV 40.3 dB 55 0
6 Locked QAM256 20 591000000 Hz -4.0 dBmV 40.2 dB 21 0
7 Locked QAM256 22 603000000 Hz -4.7 dBmV 40.1 dB 42 0
8 Locked QAM256 23 609000000 Hz -4.6 dBmV 40.1 dB 52 0
9 Locked QAM256 24 615000000 Hz -5.2 dBmV 39.9 dB 76 27
10 Locked QAM256 25 621000000 Hz -5.0 dBmV 40.0 dB 89 0
11 Locked QAM256 26 627000000 Hz -5.0 dBmV 39.9 dB 103 0
12 Locked QAM256 27 633000000 Hz -5.5 dBmV 39.8 dB 123 0
13 Locked QAM256 28 639000000 Hz -5.4 dBmV 39.7 dB 86 0
14 Locked QAM256 29 645000000 Hz -5.2 dBmV 39.9 dB 138 0
15 Locked QAM256 30 651000000 Hz -5.3 dBmV 39.9 dB 119 0
16 Locked QAM256 16 567000000 Hz -3.6 dBmV 40.5 dB 15 0

 
Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 4 5120 Ksym/sec 18600000 Hz 45.2 dBmV
2 Locked ATDMA 1 5120 Ksym/sec 37800000 Hz 46.7 dBmV
3 Locked ATDMA 2 5120 Ksym/sec 31400000 Hz 48.2 dBmV
4 Locked ATDMA 3 5120 Ksym/sec 25000000 Hz 46.6 dBmV


 

Current System Time: Tue Jul 31 21:19:53 2018

 

Expert

Re: SYNC Timing Synchronization failure

The signal stats at that moment in time were o/k. Are you actually experiencing any connectivity problems or just focusing on the error log entries ?



I am not a Comcast Employee.
I am a fellow customer, volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.

Was your question answered? Mark the post as best answer!
Highlighted
Regular Visitor

Re: SYNC Timing Synchronization failure

There had been issues with connectivity and excessive buffering intermittently over the last week or so but not at the time when I was logged into the modem.. I guess I’ll just continue to keep an eye on it.