NTP/2/NTP_TRAP_SYNCHRONIZE_STATUS

Message

NTP/2/NTP_TRAP_SYNCHRONIZE_STATUS: NTP synchronization state changed. (hwNtpState=[state], hwNtpSource=[source], hwNtpSourceVpnName=[VpnName])

In VS mode, this log is supported only by the admin VS.

Description

There has been a change in the state of an NTP local clock.

Parameters

Parameter Name	Parameter Meaning
state	Indicates the NTP local clock state.
source	Specifies server IP address to which local NTP clock is synchronized.
VpnName	Indicates Vpn instance associated with the peer to which the local NTP clock is synchronized.

Possible Causes

NTP state changed from synchronized to unsynchronized due to reasons listed below

Cause 1: System clock is reset by configuration.

Cause 2: Selected peer is deleted by configuration.

Cause 3: Selected peer is unreachable.

Cause 4: Authentication failed for selected peer.

Cause 5: Selected peer clock is not synchronized.

Cause 6: Time elapsed since peer clock's last update is not within permissible limit.

Cause 7: Source stratum is greater than the local stratum.

Cause 8: System synchronization source lost.

Cause 9: NTP mode mismatch for selected peer.

Procedure

Cause 1: System clock resetting was configured.

1. Specify a new clock. Then, check whether the NTP source enters the synchronized state.

the NTP source enters the synchronized state, go to Step 3.
If the NTP source does not enter the synchronized state, go to Step 2.

2. Collect alarm information and configuration information, and then contact technical support personnel.

3. End.

Cause 2: The specified peer was deleted.

1. Configure a replacement clock source. Then, check whether the NTP source enters the synchronized state.

If the NTP source enters the synchronized state, go to Step 3.
If the NTP source does not enter the synchronized state, go to Step 2.

2 Collect alarm information and configuration information, and then contact technical support personnel.

3. End.

Cause 3: The peer was unreachable.

1. Check the connectivity between the NTP clock source and the peer.

If the NTP clock source and the peer cannot communicate properly, go to Step 3.
If the NTP clock source and the peer can communicate properly, go to Step 2.

2. Specify a new clock source. Then, check whether the NTP source enters the synchronized state.

If the NTP source enters the synchronized state, go to Step 4.
If the NTP source does not enter the synchronized state, go to Step 3.

3. Collect alarm information and configuration information, and then contact technical support personnel.

4. End.

Cause 4: The peer authentication failed.

1. Check whether NTP authentication has been configured on both the local and peer.

If NTP authentication has been configured on both the local and peer, go to Step 2.
If NTP authentication has been configured on both the local and peer, configure NTP authentication.

2. Check whether the NTP authentication keys configured on the local and peer are consistent.

If they are consistent, go to Step 3.
If they are not consistent, reconfigure the NTP authentication keys.

3. Collect alarm information and configuration information, and then contact technical support personnel.

4. End.

Cause 5: The peer clock was not synchronized.

1. Configure a replacement clock source. Then, check whether the NTP source enters the synchronized state.

If the NTP source enters the synchronized state, go to Step 3.
If the NTP source does not enter the synchronized state, go to Step 2.

2. Collect alarm information and configuration information, and then contact technical support personnel.

3. End.

Cause 6: The update interval for the peer clock exceeded the threshold.

1. Configure a replacement clock source. Then, check whether the NTP source enters the synchronized state.

If the NTP source enters the synchronized state, go to Step 3.
If the NTP source does not enter the synchronized state, go to Step 2.

2. Collect alarm information and configuration information, and then contact technical support personnel.

3. End.

Cause 7: The source level was higher than the local level.

1. Run the command to view the level where the local NTP source resides.

If the level where the local NTP source resides is lower than that of the peer, go to Step 2.
If the level where the local NTP source resides is higher than that of the peer, go to Step 3.

2. Configure a replacement clock source with the level lower than that of the local NTP source. Then, check whether the NTP source enters the synchronized state.

If the NTP source enters the synchronized state, go to Step 4.
If the NTP source does not enter the synchronized state, go to Step 3.

3. Collect alarm information and configuration information, and then contact technical support personnel.

4. End.

Cause 8: The system clock source was lost.

1. Configure a replacement clock source. Then, check whether the NTP source enters the synchronized state.

If the NTP source enters the synchronized state, go to Step 3.
If the NTP source does not enter the synchronized state, go to Step 2.

2. Collect alarm information and configuration information, and then contact technical support personnel.

3. End.

Cause 9: The NTP mode did not match the peer.

1. Run the display ntp sessions command to view the NTP mode.

If the NTP mode matches the peer, go to Step 3.
If the NTP mode does not match the peer, go to Step 2.

2. Configure the NTP mode. Then, check whether the NTP source enters the synchronized state.

If the NTP source enters the synchronized state, go to Step 4.
If the NTP source does not enter the synchronized state, go to Step 3.

3. Collect alarm information and configuration information, and then contact technical support personnel.

4. End.