Contents

HH3C-NTP-MIB· 1

About this MIB· 1

MIB file name· 1

Notifications· 1

hh3cNTPSysStateChangeTrap· 1

hh3cNTPSysPeerChangeTrap· 3

hh3cNTPDynSessionLimit 3

hh3cNTPDynSessionLimitResume· 4

hh3cNTPSessionsLimit 5

hh3cNTPSessionLimitResume· 6

hh3cNTPSynchronizationResume· 6

hh3cNTPSysStratumChange· 7

hh3cNTPTimeOffsetThresExceed· 8

hh3cNTPTimeOffsetThresResume· 9

 

HH3C-NTP-MIB

About this MIB

Use this MIB to configure NTP of the device.

MIB file name

hh3c-ntp.mib

Notifications

This section contains HH3C-NTP-MIB notifications.

hh3cNTPSysStateChangeTrap

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.4.1.25506.8.22.1.2.0.1	NTP local time synchronization status changed.	Informational	Warning	N/A	ON

 

Notification triggers

This notification is generated when the NTP local time synchronization status changes.

Possible reasons for change of the NTP time status from synchronized to unsynchronized include:

·     Reason 1: The specified time server is deleted.

·     Reason 2: The specified time server fails authentication.

·     Reason 3: The clock of the specified time server is not synchronized.

·     Reason 4: The specified time server is not reachable.

·     Reason 5: The stratum level of the clock source is larger than that of the local clock.

·     Reason 6: The clock source is lost.

System impact

The local time is inaccurate.

Status control

The notification cannot be disabled.

Objects

This table does not have indexes.

OID (object name)	Description	Index nodes	Type	Value range
1.3.6.1.4.1.25506.8.22.1.1.10 (hh3cNTPSysState)	Local clock status.	N/A	INTEGER	noUpdateClock(0), getfreqInfo(1), clockBySet(2), clockBySetAndNoFreq(3), clockBySyns(4), findError(5)
1.3.6.1.4.1.25506.8.22.1.1.19 (hh3cNTPServerIP)	IP address of the NTP server.	N/A	IpAddress	OCTET STRING (4)
1.3.6.1.4.1.25506.8.22.1.1.22 (hh3cNTPSysSrcVpnName)	VPN instance to which the NTP server belongs.	N/A	DisplayString	OCTET STRING(0..255)

Recommended action

Reason 1: The specified time server is deleted

To resolve the issue:

1.     Specify another time server.

2.     If the issue persists, collect alarm information and configuration data, and then contact H3C Support for help.

Reason 2: The specified time server fails authentication

To resolve the issue:

1.     Execute the display this | include ntp-service authentication command in system view to identify whether the local device and time server are both configured with NTP authentication settings.

¡     If they are both configured with NTP authentication settings, make sure they use the same authentication key and the key is configured as a trust key.

¡     If NTP authentication settings are not configured, configure NTP authentication.

2.     If the issue persists, collect alarm information and configuration data, and then contact H3C Support for help.

Reason 3: The clock of the specified time server is not synchronized

To resolve the issue:

1.     Specify another NTP server.

2.     If the issue persists, collect alarm information and configuration data, and then contact H3C Support for help.

Reason 4: The specified time server is not reachable

To resolve the issue:

1.     Execute the ping command to test whether the time server is reachable.

¡     If the time server is reachable, proceed to the next step.

¡     If the time server is not reachable, resolve the network connectivity issue or replace another time server.

2.     If the issue persists, collect alarm information and configuration data, and then contact H3C Support for help.

Reason 5: The stratum level of the clock source is larger than that of the local clock

To resolve the issue:

1.     Execute the display ntp-service status command to view the stratum level of the local clock.

¡     If the stratum level of the clock source is larger than that of the local NTP clock, specify another clock source with a lower stratum level lower than the local clock.

¡     If the stratum level of the clock source is lower than that of the local NTP clock, proceed to the next step.

2.     If the issue persists, collect alarm information and configuration data, and then contact H3C Support for help.

Reason 6: The clock source is lost

To resolve the issue:

1.     Execute the display ntp-service sessions command to identify whether the clock source is lost. If the clock source is lost, specify another clock source.

2.     If the issue persists, collect alarm information and configuration data, and then contact H3C Support for help.

hh3cNTPSysPeerChangeTrap

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.4.1.25506.8.22.1.2.0.2	Change of the NTP time server.	Informational	Warning	N/A	ON

 

Notification triggers

This notification is generated when the NTP time server changes.

System impact

No negative impact on the system.

Status control

The notification cannot be disabled.

Objects

This table does not have indexes.

OID (object name)	Description	Index nodes	Type	Value range
1.3.6.1.4.1.25506.8.22.1.1.21 (hh3cNTPSysOldServerIP)	IP address of last NTP server.	N/A	IpAddress	Standard MIB values.
1.3.6.1.4.1.25506.8.22.1.1.23 (hh3cNTPSysOldSrcVpnName)	VPN instance to which the last NTP server belongs.	N/A	DisplayString	OCTET STRING (0..255)
1.3.6.1.4.1.25506.8.22.1.1.19 (hh3cNTPServerIP)	IP address of the current NTP server.	N/A	IpAddress	Standard MIB values.
1.3.6.1.4.1.25506.8.22.1.1.22 (hh3cNTPSysSrcVpnName)	VPN instance to which the current NTP server belongs.	N/A	DisplayString	OCTET STRING (0..255)

Recommended action

If the clock source is changed because another clock source is specified, no action is required.

If the clock source is changed because of a change in clock source properties, execute the display ntp-service sessions verbos command to view the clock source properties and conduct further investigation. You can see the recommended actions for the hh3cNTPSysStateChangeTrap.

hh3cNTPDynSessionLimit

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.4.1.25506.8.22.1.2.0.3	The number of dynamic NTP sessions reached the threshold.	Error	Major	1.3.6.1.4.1.25506.8.22.1.2.0.4 (hh3cNTPDynSessionLimitResume)	ON

Notification triggers

This notification is generated when the number of dynamic NTP sessions reaches the threshold.

System impact

New dynamic NTP sessions cannot be established.

Status control

The notification cannot be disabled.

Objects

This table does not have indexes.

OID (object name)	Description	Index nodes	Type	Value range
1.3.6.1.4.1.25506.8.22.1.1.24 (hh3cNTPSysMaxDynamicSessions)	Maximum number of dynamic NTP sessions.	N/A	Integer32	Integer32 (0..255)

Recommended action

Execute the ntp-service max-dynamic-sessions command to set the maximum number of dynamic sessions to a value large enough.

hh3cNTPDynSessionLimitResume

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.4.1.25506.8.22.1.2.0.4	The number of dynamic NTP sessions dropped below the threshold.	Recovery	Warning	N/A	ON

 

Notification triggers

This notification is generated when the number of dynamic NTP sessions drops below the threshold.

System impact

No negative impact on the system.

Status control

The notification cannot be disabled.

Objects

This table does not have indexes.

OID (object name)	Description	Index nodes	Type	Value range
1.3.6.1.4.1.25506.8.22.1.1.24 (hh3cNTPSysMaxDynamicSessions)	Maximum number of dynamic NTP sessions.	N/A	Integer32	Integer32 (0..255)

Recommended action

No action is required.

hh3cNTPSessionsLimit

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.4.1.25506.8.22.1.2.0.5	Number of NTP sessions reached the threshold.	Error	Major	1.3.6.1.4.1.25506.8.22.1.2.0.6(hh3cNTPSessionLimitResume)	ON

 

Notification triggers

This notification is generated when the number of NTP sessions reaches the threshold.

System impact

New NTP sessions cannot be established.

Status control

The notification cannot be disabled.

Objects

OID (object name)	Description	Index node	Type	Value range
hh3cNTPSysMaxSessions (1.3.6.1.4.1.25506.8.22.1.1.25)	Maximum number of NTP sessions.	N/A	Unsigned32	Unsigned32 (0..65535)

This table does not contain indexes. For information about the index or indexes of a MIB object instance in an SNMP variable binding, see the section for that MIB object.

 

Recommended action

Delete unused static NTP sessions.

hh3cNTPSessionLimitResume

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.4.1.25506.8.22.1.2.0.6	Number of NTP sessions fell below the threshold.	Recovery	Warning	N/A	ON

 

Notification triggers

This notification is generated when the number of NTP sessions falls below the threshold.

System impact

No negative impact on the system.

Status control

The notification cannot be disabled.

Objects

OID (object name)	Description	Index nodes	Type	Value range
hh3cNTPSysMaxSessions (1.3.6.1.4.1.25506.8.22.1.1.25)	Maximum number of NTP sessions.	N/A	Unsigned32	Unsigned32 (0..65535)

 

Recommended action

No action is required.

hh3cNTPSynchronizationResume

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.4.1.25506.8.22.1.2.0.8	The local NTP clock resumed time synchronization.	Recovery	Warning	N/A	ON

 

Notification triggers

This notification is generated when the local NTP clock resumes time synchronization.

System impact

No negative impact on the system.

Status control

The notification cannot be disabled.

Objects

OID (object name)	Description	Index nodes	Type	Value range
1.3.6.1.4.1.25506.8.22.1.1.10 (hh3cNTPSysState)	Local clock status.	N/A	INTEGER	noUpdateClock(0), getfreqInfo(1), clockBySet(2), clockBySetAndNoFreq(3), clockBySyns(4), findError(5)
1.3.6.1.4.1.25506.8.22.1.1.19 (hh3cNTPServerIP)	IP address of the NTP server.	N/A	IpAddress	OCTET STRING (4)

Recommended action

No action is required.

hh3cNTPSysStratumChange

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.4.1.25506.8.22.1.2.0.9	The stratum level of the local clock changed.	Informational	Warning	N/A	ON

 

Notification triggers

This notification is generated when the stratum level of the local clock changes.

System impact

The downstream NTP clock might become unsynchronized.

Status control

The notification cannot be disabled.

Objects

OID (object name)	Description	Index nodes	Type	Value range
1.3.6.1.4.1.25506.8.22.1.1.2 (hh3cNTPSysStratum)	Current stratum level of the local system clock.	N/A	Integer32	Integer32 (1..16)
1.3.6.1.4.1.25506.8.22.1.1.26 (hh3cNTPSysOldStratum)	Old stratum level of the local system clock.	N/A	Integer32	Integer32 (1..16)

 

Recommended action

No action is required.

hh3cNTPTimeOffsetThresExceed

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.4.1.25506.8.22.1.2.0.10	NTP clock offset reached the threshold.	Error	Major	1.3.6.1.4.1.25506.8.22.1.2.0.11(hh3cNTPTimeOffsetThresResume)	OFF

 

Notification triggers

This notification is generated when the time offset between the local NTP clock and the NTP time server reaches or exceeds the threshold.

System impact

The clock precision might be affected.

Status control

ON

CLI: Use the ntp-service time-offset-threshold trap trap-threshold command.

OFF

CLI: Use the undo ntp-service time-offset-threshold command.

Objects

OID (object name)	Description	Index nodes	Type	Value range
1.3.6.1.4.1.25506.8.22.1.1.11 (hh3cNTPSysOffset)	NTP time offset.	N/A	OCTET STRING	OCTET STRING (1..128)
1.3.6.1.4.1.25506.8.22.1.1.27 (hh3cNTPSysTimeOffsetThres)	NTP time offset threshold.	N/A	OCTET STRING	OCTET STRING (1..128)

 

Recommended action

1.     Execute the display ntp-service sessions verbose command to view detailed information about the NTP session.

¡     If the session meets the requirements, execute the ntp-service time-offset-threshold command to correct the alarm threshold.

¡     If the session does not meet the requirements, specify another clock source.

2.     If the issue persists, collect alarm information and configuration data, and then contact H3C Support for help.

hh3cNTPTimeOffsetThresResume

Basic information

OID	Event	Type	Severity	Recovery notification	Default status
1.3.6.1.4.1.25506.8.22.1.2.0.11	The NTP clock offset fell below the threshold to the normal range.	Recovery	Warning	N/A	OFF

 

Notification triggers

This notification is generated when the NTP clock offset falls below the threshold to the normal range.

System impact

No negative impact on the system.

Status control

ON

CLI: Use the ntp-service time-offset-threshold trap trap-threshold command.

OFF

CLI: Use the undo ntp-service time-offset-threshold command.

Objects

OID (object name)	Description	Index nodes	Type	Value range
1.3.6.1.4.1.25506.8.22.1.1.11 (hh3cNTPSysOffset)	NTP time offset.	N/A	OCTET STRING	OCTET STRING (1..128)
1.3.6.1.4.1.25506.8.22.1.1.27 (hh3cNTPSysTimeOffsetThres)	NTP time offset threshold.	N/A	OCTET STRING	OCTET STRING (1..128)

 

Recommended action

No action is required.