SYNC Timing Synchronization failure - Loss of Sync and REGISTRATION COMPLETE - Waiting for Operational s

[bhambi]

Hi,

I have upgraded from Hub 3 to Hub 5 and have the following issues below, called Virgin ISP but have been told to reboot and wait. The Hub 5 is set to a modem and it did take 16 hours to set up as it was flashing green and next morning the package in my virgin account changed to the new one the Hub was on a solid white with the errors below.

What do I do next to resolve them please help!

1.  SYNC Timing Synchronization failure - Loss of Sync

2. REGISTRATION COMPLETE - Waiting for Operational status

Network Log

Time Priority Description

19-11-2022 15:07:15	notice	REGISTRATION COMPLETE - Waiting for Operational status
19-11-2022 15:07:11	notice	US profile assignment change. US Chan ID: 6; Previous Profile: 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-11-2022 15:07:06	notice	DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-11-2022 15:07:02	notice	TLV-11 - unrecognized OID;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-11-2022 15:07:00	warning	DHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-11-2022 15:06:58	notice	Honoring MDD; IP provisioning mode = IPv4
19-11-2022 15:06:43	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-11-2022 15:06:43	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-11-2022 15:06:43	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-11-2022 15:06:38	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-11-2022 15:06:37	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-11-2022 15:06:34	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-11-2022 15:06:33	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-11-2022 15:06:26	critical	Cable Modem Reboot due to power button reset

[jbrennand]

Try this...

Do a Hub “pinhole reset” - first make sure the 2 passwords on the Hub sticker are still there and legible first ! Disconnect any ethernet cables from the Hub (leave the coax connected), and then with the Hub still "switched on" throughout, press pin in firmly with paper clip/SIM tray tool or similar "thin thing" and hold it firmly for at least 60 (a timed sixty) seconds, release the pin, leave for 5’ to stabilise - dont manually switch it off at any time. Passwords and SSID’s will reset to those on the sticker.

See if that sorts it.

[jem101]

---

@bhambi wrote:

Hi,

I have upgraded from Hub 3 to Hub 5 and have the following issues below, called Virgin ISP but have been told to reboot and wait. The Hub 5 is set to a modem and it did take 16 hours to set up as it was flashing green and next morning the package in my virgin account changed to the new one the Hub was on a solid white with the errors below.

What do I do next to resolve them please help!

1.  SYNC Timing Synchronization failure - Loss of Sync

2. REGISTRATION COMPLETE - Waiting for Operational status

Network Log

Time Priority Description

19-11-2022 15:07:15	notice	REGISTRATION COMPLETE - Waiting for Operational status
19-11-2022 15:07:11	notice	US profile assignment change. US Chan ID: 6; Previous Profile: 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-11-2022 15:07:06	notice	DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-11-2022 15:07:02	notice	TLV-11 - unrecognized OID;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-11-2022 15:07:00	warning	DHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-11-2022 15:06:58	notice	Honoring MDD; IP provisioning mode = IPv4
19-11-2022 15:06:43	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-11-2022 15:06:43	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-11-2022 15:06:43	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-11-2022 15:06:38	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-11-2022 15:06:37	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-11-2022 15:06:34	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-11-2022 15:06:33	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-11-2022 15:06:26	critical	Cable Modem Reboot due to power button reset

---

There's actually nothing unduly wrong with those messages, if you just rebooted the hub at 15:06, then all of those 'critical' notifications are simply the hub booting up - and registering itself on the cable network. It can take quite a few minutes to become fully operational and in the meantime it's in a bit of a 'messy' state - the messages are just reflecting that.

[Chris_W1]

Hi bhambi, thanks for the message and welcome to the forums. 

Thanks for the community for answering you question and I hope that this resolves things for you. 

Please let us know if you require any further assistance. 

Kind regards, Chris.