NTP/2/NTP_SYNCHRONIZE_STATUS: NTP state changed from synchronized to unsynchronized. (SynchronizationSourceAddress = [Source] , VpnInstance = [VpnName], Reason = [Reason])
In VS mode, this log is supported only by the admin VS.
| Parameter Name | Parameter Meaning |
|---|---|
|
Source |
Indicates the server IP address used to synchronize local NTP clock. |
|
VpnName |
Indicates the VPN instance for local NTP clock synchronization. |
|
Reason |
Indicates the reason why NTP clock status changes to unsynchronized. |
NTP state changed from synchronized to unsynchronized state due to one of the following reasons:
Cause 1: VPN change detected.
Cause 2: Peer reachability lost.
Cause 3: Authentication failure.
Cause 4: Authentication configuration changed.
Cause 5: KOD DENY received.
Cause 6: Manycast discovery restarted.
Cause 7: Unicast server configuration removed.
Cause 8: Unicast peer configuration removed.
Cause 9: Reference clock configuration removed.
Cause 10: Stratum increase detected.
Cause 11: Peer clock unsynchronized/unselectable.
Cause 12: Manycast configuration removed.
Cause 13: Configuration changed.
Cause 14: Clock selection failed - Excessive falsetickers.
Cause 15: Clock selection failed - No selectable clock.
Cause 16: Clock change detected.
Cause 17: NTP IPv4 Service is disabled.
Cause 18: NTP IPv6 Service is disabled.
Cause 1: VPN change detected
Select another VPN.
Cause 2: Peer reachability lost
1. Check whether the link to the remote clock source is reachable.
2. If the link is unreachable, locate the network fault or configure another remote clock source.
3. If the link is reachable, check whether the source interface is configured properly.
Cause 3: Authentication failure
The authentication failure packet is discarded, and synchronization fails.
1. Check whether a key is configured. If not, configure a key. If yes, check whether the key is correct.
2. Check whether the key is configured as trusted.
3. Check whether the clock source is configured to carry a key.
Cause 4: Authentication configuration changed
The authentication configuration has been changed. For details, refer to the handling procedure for cause 3.
Cause 5: KOD DENY received
The client has received KOD packets with the DENY code, and the remote clock source restricts the client synchronization time. Reconfigure the remote clock source.
Cause 6: Manycast discovery restarted
The manycast client restarts the discovery process. This is normal, and no action is required.
Cause 7: Unicast server configuration removed
The unicast server configuration is deleted. Reconfigure the NTP unicast server.
Cause 8: Unicast peer configuration removed
The unicast peer configuration is deleted. Reconfigure the NTP unicast peer.
Cause 9: Reference clock configuration removed
The configuration of the master clock is deleted. Reconfigure the local NTP clock as the master NTP clock.
Cause 10: Stratum increase detected
1. Check whether the current clock is synchronized.
2. If the clock is synchronized, evaluate whether the clock precision meets the requirement. If not, configure a remote clock source with a higher precision.
3. If the clock is not synchronized, reconfigure a remote clock source.
Cause 11: Peer clock unsynchronized/unselectable
1. Check whether the current clock is synchronized.
2. If the clock is synchronized, no action is needed. If the problem still occurs frequently, configure anew remote clock source or locate the fault.
3. If the clock is not synchronized, reconfigure the remote clock source or locate the fault.
Cause 12: Manycast configuration removed
The configuration of the manycast client is deleted. Reconfigure an NTP manycast client.
Cause 13: Configuration changed
Check whether the NTP client configuration is deleted. If so, reconfigure the NTP client.
Cause 14: Clock selection failed - Excessive falsetickers
Excessive falsetickers result in a failure to select a clock. Delete invalid clock sources and reconfigure a valid clock source.
Cause 15: Clock selection failed - No selectable clock
No clock source is available, leading to a failure to select a clock source. Configure a valid clock source.
Cause 16: Clock change detected
The time of the clock source is detected to be abruptly changed unexpectedly. Check the time of the clock source or reconfigure a remote clock source.
Cause 17: NTP IPv4 Service is disabled
The IPv4 NTP service is disabled. Re-enable the IPv4 NTP service.
Cause 18: NTP IPv6 Service is disabled
The IPv6 NTP service is disabled. Re-enable the IPv6 NTP service.