NTP_1.3.6.1.4.1.2011.6.80.2.1 hwNtpStateChangeTrap

Description

NTP/1/NTP_TRAP_SYNCHRONIZE_STATUS: OID [oid] NTP synchronization state changed. (hwNtpState=[STRING], hwNtpSource=[STRING], hwNtpSourceVpnName=[STRING])

NTP synchronization status changed.

Attribute

Alarm ID	Alarm Severity	Alarm Type
1.3.6.1.4.1.2011.6.80.2.1	Critical	qualityOfServiceAlarm(3)

Parameters

Name	Meaning
oid	Indicates the MIB object ID of the alarm.
hwNtpState	NTP clock synchronization status
hwNtpSource	IP address of the synchronization source
hwNtpSourceVpnName	VPN name of the synchronization source

Impact on the System

NTP status becomes unsynchronous.

Possible Causes

NTP status changed from synchronous to unsynchronous due to the following reasons:

Cause 1: The system clock reset was configured.
Cause 2: The specified peer was deleted.
Cause 3: The specified peer was unreachable.
Cause 4: The specified peer failed to be authenticated.
Cause 5: The clock of the specified peer was not synchronized.
Cause 6: The source stratum was greater than the local stratum.
Cause 7: The clock service of the specified peer was disabled.
Cause 8: The clock source stratum of the specified peer was increased.

Procedure

Cause 1: The system clock reset was configured.
1. Specify a new clock and check whether NTP enters the synchronous state.
  - If NTP enters the synchronous state, go to Step 3.
  - If NTP does not enter the synchronous 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 substitute clock source and check whether NTP enters the synchronous state.
  - If NTP enters the synchronous state, go to Step 3.
  - If NTP does not enter the synchronous state, go to Step 2.
2. Collect alarm information and configuration information, and then contact technical support personnel.
3. End.
Cause 3: The specified peer was unreachable.
1. Check the network connectivity between the clock and its peer.
  - If the network is unreachable, go to Step 3.
  - If the network is reachable, go to Step 2.
2. Specify a new clock source and check whether NTP enters the synchronous state.
  - If NTP enters the synchronous state, go to Step 4.
  - If NTP does not enter the synchronous state, go to Step 3.
3. Collect alarm information and configuration information, and then contact technical support personnel.
4. End.
Cause 4: The specified peer failed to be authenticated.
1. Check whether NTP authentication has been configured for both the local and peer ends.
  - If NTP authentication has been configured for both the local and peer ends, go to Step 2.
  - If NTP authentication has not been configured for the local or peer end or for both ends, configure NTP authentication as required.
2. Check whether NTP authentication keys configured for the local and peer ends are the same.
  - If NTP authentication keys configured for the local and peer ends are the same, go to Step 3.
  - If NTP authentication keys configured for the local and peer ends are different, reconfigure the keys so that they are the same.
3. Collect alarm information and configuration information, and then contact technical support personnel.
4. End.
Cause 5: The clock of the specified peer was not synchronized.
1. Configure a substitute clock source and check whether NTP enters the synchronous state.
  - If NTP enters the synchronous state, go to Step 3.
  - If NTP does not enter the synchronous state, go to Step 2.
2. Collect alarm information and configuration information, and then contact technical support personnel.
3. End.
Cause 6: The source stratum was greater than the local stratum.
1. Run the display ntp status command to check the local stratum.
  - If the local stratum is less than the source stratum, go to Step 2.
  - If the local stratum is greater than the source stratum, go to Step 3.
2. Configure a substitute clock source, ensuring that the source stratum is less than the local stratum. Check whether NTP enters the synchronous state.
  - If NTP enters the synchronous state, go to Step 4.
  - If NTP does not enter the synchronous state, go to Step 3.
3. Collect alarm information and configuration information, and then contact technical support personnel.
4. End.
Cause 7: The clock service of the specified peer was disabled.
1. Configure a substitute clock source and check whether NTP enters the synchronous state.
  - If NTP enters the synchronous state, go to Step 3.
  - If NTP does not enter the synchronous state, go to Step 2.
2. Collect alarm information and configuration information, and then contact technical support personnel.
3. End.
Cause 8: The clock source stratum of the specified peer was increased.
1. Configure a substitute clock source and check whether NTP enters the synchronous state.
  - If NTP enters the synchronous state, go to Step 3.
  - If NTP does not enter the synchronous state, go to Step 2.
2. Collect alarm information and configuration information, and then contact technical support personnel.
3. End.

Related Information

None