HUAWEI-NTP-MIB

All MIBs › HUAWEI-NTP-MIB

Organization: Hangzhou H3C Tech. Co., Ltd.

Last Updated: 2003-03-15

Category: Protocol: NTP, Technology: Time Synchronization, Vendor: Huawei

Description: Huawei NTP (Network Time Protocol) MIB for managing NTP server associations, authentication, and synchronization status.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is HUAWEI-NTP-MIB?

HUAWEI-NTP-MIB is a Huawei private MIB for monitoring the Network Time Protocol client/server behavior of a Huawei device. It exposes NTP association configuration (configured servers, authentication) and runtime synchronization status such as stratum and sync state. Its monitoring role is software/system health rather than physical hardware: confirming the device remains synchronized to its configured time source, and detecting a lost or degraded NTP association, matters because unsynchronized clocks break log correlation, certificate validation, and time-stamped security events across the device. It models the standard NTP protocol (as defined in RFC 5905) as a Huawei-specific private MIB rather than adopting an existing IETF NTP MIB. It is deployed on essentially any Huawei router or switch that relies on NTP for accurate system time. Network engineers evaluating or troubleshooting this functionality can download the HUAWEI-NTP-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in HUAWEI-NTP-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

Huawei routers and switches using NTP for time synchronization

Monitoring Examples

No sample object names were provided for this module. In general, an operator would poll the device's NTP association/status objects to confirm the client remains synchronized to its configured server and to read the current stratum level. A sync-status change away from 'synchronized', an unexpected stratum jump, or a server becoming unreachable indicates the device has lost its time reference, which would be flagged before it starts affecting log timestamps or certificate-based authentication.

What Can Be Monitored

NTP server association status
synchronization/stratum state
clock offset from reference
NTP authentication status
peer reachability

Imported Objects

From HUAWEI-3COM-OID-MIB

huaweiDatacomm

OBJECT-IDENTITY

From SNMPv2-SMI

Counter32
Integer32
IpAddress
MODULE-IDENTITY
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

RowStatus
TruthValue

How to Use in IPNetwork Monitor

Example using hwNTPPeerReceived OID:

Select a Huawei router or switch using NTP for time synchronization as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type hwNTPPeerReceived into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. The number of received massages. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
hwNTP	1.3.6.1.4.1.2011.5.25.22			This MIB provides mechanisms to monitor a NTP server.
hwNTPSystemMIB	1.3.6.1.4.1.2011.5.25.22.1
hwNTPSystemMIBObjects	1.3.6.1.4.1.2011.5.25.22.1.1
INT hwNTPSysLeap	1.3.6.1.4.1.2011.5.25.22.1.1.1	INTEGER	read-only	Leap Indicator (LI): This is a two-bit code warning of an impending leap second to be inserted/deleted in the last minute of the current day, with bit 0 and bit 1, respectively, coded as follows: 00, no warning 01, last minute has 61 seconds 10, last minute has 59 seconds) 11, alarm condition (clock not synchronized).
I32 hwNTPSysStratum	1.3.6.1.4.1.2011.5.25.22.1.1.2	Integer32	read-only	This is an eight-bit integer indicating the stratum level of the local clock, with values defined as follows: 0, unspecified 1, primary reference (e.g.,, radio clock) 2-255, secondary reference (via NTP)
I32 hwNTPSysPrecision	1.3.6.1.4.1.2011.5.25.22.1.1.3	Integer32	read-only	Precision : This is a signed integer indicating the precision of the various clocks, in seconds to the nearest power of two. The value must be rounded to the next larger power of two; for instance, a 50-Hz (20 ms) or 60-Hz (16.67ms) power-frequency clock would be assigned the value -5 (31.25 ms), while a 1000-Hz (1 ms) crystal-controlled clock would be assigned the value -9 (1.95 ms).
OCT hwNTPSysRootdelay	1.3.6.1.4.1.2011.5.25.22.1.1.4	OCTET STRING	read-only	Root Delay : This is a signed fixed-point number indicating the total roundtrip delay to the primary reference source at the root of the synchronization subnet, in seconds. Note that this variable can take on both positive and negative values, depending on clock precision and skew.
OCT hwNTPSysRootdispersion	1.3.6.1.4.1.2011.5.25.22.1.1.5	OCTET STRING	read-only	Root Dispersion : This is a signed fixed-point number indicating the maximum error relative to the primary reference source at the root of the synchronization subnet, in seconds. Only positive values greater than zero are possible.
OCT hwNTPSysRefid	1.3.6.1.4.1.2011.5.25.22.1.1.6	OCTET STRING	read-only	Reference Clock Identifier : This is a 32-bit code identifying the particular reference clock. In the case of stratum 0 (unspecified) or stratum 1 (primary reference source), this is a four-octet, left-justified, zero-padded ASCII string. Stratum, Code, Meaning 0, DCN, DCN routing protocol 0, TSP, TSP time protocol 1, ATOM, Atomic clock (calibrated) 1, WWVB, WWVB LF (band 5) radio 1, GOES, GOES UHF (band 9) satellite 1, WWV, WWV HF (band 7) radio
OCT hwNTPSysReftime	1.3.6.1.4.1.2011.5.25.22.1.1.7	OCTET STRING	read-only	Reference Timestamp : This is the local time, in timestamp format, when the local clock was last updated. If the local clock has never been synchronized, the value is zero.
I32 hwNTPSysPoll	1.3.6.1.4.1.2011.5.25.22.1.1.8	Integer32	read-only	Poll Interval : This is a signed integer indicating the minimum interval between transmitted messages, in seconds as a power of two. For instance, a value of six indicates a minimum interval of 64 seconds.
I32 hwNTPSysPeer	1.3.6.1.4.1.2011.5.25.22.1.1.9	Integer32	read-only	This is a selector identifying the current synchronization source. Usually this will be a pointer to a structure containing the peer variables. The special value NULL indicates There is no currently valid synchronization source.
INT hwNTPSysState	1.3.6.1.4.1.2011.5.25.22.1.1.10	INTEGER	read-only	This is a integer indicating the state of local clock.
OCT hwNTPSysOffset	1.3.6.1.4.1.2011.5.25.22.1.1.11	OCTET STRING	read-only	The offset of two clocks is the time difference between them.
OCT hwNTPSysDrift	1.3.6.1.4.1.2011.5.25.22.1.1.12	OCTET STRING	read-only	Real clocks exhibit some variation in skew (second derivative of offset with time), which is called drift.
OCT hwNTPSysCompliance	1.3.6.1.4.1.2011.5.25.22.1.1.13	OCTET STRING	read-only	This is a string indicating the system error.
OCT hwNTPSysClock	1.3.6.1.4.1.2011.5.25.22.1.1.14	OCTET STRING	read-only	This is the current local time, in timestamp format. Local time is derived from the hardware clock of the particular machine and increments at intervals depending on the design used.
OCT hwNTPSysStabil	1.3.6.1.4.1.2011.5.25.22.1.1.15	OCTET STRING	read-only	This is a indicating that stability of a clock is how well it can maintain a constant frequency.
INT hwNTPSysAuthenticate	1.3.6.1.4.1.2011.5.25.22.1.1.16	INTEGER	read-write	This is a integer indicating that system support authentication.
I32 hwNTPSysPollSec	1.3.6.1.4.1.2011.5.25.22.1.1.17	Integer32	read-write	PollSec Interval : This is a integer indicating the minimum interval between transmitted messages. For instance, a value of six indicates a minimum interval of 6 seconds.
I32 hwNTPSysClockSec	1.3.6.1.4.1.2011.5.25.22.1.1.18	Integer32	read-only	This is the current local time, in integer format. Local time is derived from the hardware clock of the particular machine and increments at intervals depending on the design used.
IP hwNTPServerIP	1.3.6.1.4.1.2011.5.25.22.1.1.19	IpAddress	read-write	The NTP server ip address. It must be a unicast address, rather than a broadcast address, a multicast address or the IP address of the local clock. To delete a configured NTP server ip address, please set hwNTPServerIP to 0.
hwNTPPeerMIB	1.3.6.1.4.1.2011.5.25.22.2
hwNTPPeerMIBObjects	1.3.6.1.4.1.2011.5.25.22.2.1
hwNTPPeerTable	1.3.6.1.4.1.2011.5.25.22.2.1.1		not-accessible	This table provides information on the peers with which the local NTP server has associations. The peers are also NTP servers but running on different hosts.
hwNTPPeerEntry	1.3.6.1.4.1.2011.5.25.22.2.1.1.1		not-accessible	Each peers' entry provides NTP information retrieved from a particular peer NTP server. Each peer is identified by a unique association identifier. Entries are automatically created when the user configures the NTP server to be associated with remote peers. Similarly entries are deleted when the user removes the peer association from the NTP server. Entries can also be created by the management station by setting values for the following objects: hwNTPPeerRemAdr and making the hwNTPPeerRowStatus as 'active'. At the least, the management station has to set a value for hwNTPPeerRemAdr to make the row active.
T/F hwNTPPeerConfig	1.3.6.1.4.1.2011.5.25.22.2.1.1.1.1	TruthValue	read-only	This is a bit indicating that the association was created from configuration information and should not be demobilized if the peer becomes unreachable.
T/F hwNTPPeerAuthenable	1.3.6.1.4.1.2011.5.25.22.2.1.1.1.2	TruthValue	read-only	This is a bit indicating that system support authentication.
T/F hwNTPPeerAuthentic	1.3.6.1.4.1.2011.5.25.22.2.1.1.1.3	TruthValue	read-only	This is a bit indicating that massage pass authentication which is authentic.
IP hwNTPPeerRemAdr	1.3.6.1.4.1.2011.5.25.22.2.1.1.1.4	IpAddress	not-accessible	The IP address of the peer. When creating a new association, a value for this object should be set before the row is made active.
I32 hwNTPPeerRemPort	1.3.6.1.4.1.2011.5.25.22.2.1.1.1.5	Integer32	read-only	The UDP port number on which the peer receives NTP messages.
IP hwNTPPeerLocAdr	1.3.6.1.4.1.2011.5.25.22.2.1.1.1.6	IpAddress	read-only	The IP address of the local host. Multi-homing can be supported using this object.
I32 hwNTPPeerLocPort	1.3.6.1.4.1.2011.5.25.22.2.1.1.1.7	Integer32	read-only	The UDP port number on which the local host receives NTP messages.
INT hwNTPPeerLeap	1.3.6.1.4.1.2011.5.25.22.2.1.1.1.8	INTEGER	read-only	This is a two-bit code warning of an impending leap second to be inserted in the NTP timescale. The bits are set before 23:59 on the day of insertion and reset after 00:00 on the following day. This causes the number of seconds (rollover interval) in the day of insertion to be increased or decreased by one. The two bits are coded as below, 00, no warning 01, last minute has 61 seconds 10, last minute has 59 seconds 11, alarm condition (clock not synchronized)
INT hwNTPPeerHMode	1.3.6.1.4.1.2011.5.25.22.2.1.1.1.9	INTEGER	not-accessible	This is an integer indicating the association mode, with values coded as follows, 0, unspecified 1, symmetric active - A host operating in this mode sends periodic messages regardless of the reach ability state or stratum of its peer. By operating in this mode the host announces its willingness to synchronize and be synchronized by the peer 2, symmetric passive - This type of association is ordinarily created upon arrival of a message from a peer operating in the symmetric active mode and persists only as long as the peer is reachable and operating at a stratum level less than or equal to the host; otherwise, the association is dissolved. However, the association will always persist until at least one message has been sent in reply. By operating in this mode the host announces its willingness to synchronize and be synchronized by the peer 3, client - A host operating in this mode sends periodic messages regardless of the reach ability state or stratum of its peer. By operating in this mode the host, usually a LAN workstation, announces its willingness to be synchronized by, but not to synchronize the peer 4, server - This type of association is ordinarily created upon arrival of a client request message and exists only in order to reply to that request, after which the association is dissolved. By operating in this mode the host, usually a LAN time server, announces its willingness to synchronize, but not to be synchronized by the peer 5, broadcast - A host operating in this mode sends periodic messages regardless of the reach ability state or stratum of the peers. By operating in this mode the host, usually a LAN time server operating on a high-speed broadcast medium, announces its willingness to synchronize all of the peers, but not to be synchronized by any of them 6, reserved for NTP control messages 7, reserved for private use 8, broadcastclient 9, multicastclient
I32 hwNTPPeerStratum	1.3.6.1.4.1.2011.5.25.22.2.1.1.1.10	Integer32	read-only	This is a integer indicating the stratum level of the local clock, with values defined as follows: 0, unspecified 1, primary reference (e.g.,, radio clock) 2-255, secondary reference (via NTP)
I32 hwNTPPeerPPoll	1.3.6.1.4.1.2011.5.25.22.2.1.1.1.11	Integer32	read-only	The interval at which the peer polls the local host.
I32 hwNTPPeerHPoll	1.3.6.1.4.1.2011.5.25.22.2.1.1.1.12	Integer32	read-only	The interval at which the local host polls the peer.
I32 hwNTPPeerPrecision	1.3.6.1.4.1.2011.5.25.22.2.1.1.1.13	Integer32	read-only	This is a signed integer indicating the precision of the peer clock, in seconds to the nearest power of two. The value must be rounded to the next larger power of two; for instance, a 50-Hz (20 ms) or 60-Hz (16.67 ms) power-frequency clock would be assigned the value -5 (31.25 ms), while a 1000-Hz (1 ms) crystal-controlled clock would be assigned the value -9 (1.95 ms).
OCT hwNTPPeerRootDelay	1.3.6.1.4.1.2011.5.25.22.2.1.1.1.14	OCTET STRING	read-only	This is a signed fixed-point number indicating the total roundtrip delay to the primary reference source at the root of the synchronization subnet, in seconds. Note that this variable can take on both positive and negative values, depending on clock precision and skew.
OCT hwNTPPeerRootDispersion	1.3.6.1.4.1.2011.5.25.22.2.1.1.1.15	OCTET STRING	read-only	This is a signed fixed-point number indicating the maximum error of the peer clock relative to the primary reference source at the root of the synchronization subnet. Only positive values greater than zero are possible.
OCT hwNTPPeerRefId	1.3.6.1.4.1.2011.5.25.22.2.1.1.1.16	OCTET STRING	read-only	The reference identifier of the peer. This is a 32-bit code identifying the particular reference clock. In the case of stratum 0 (unspecified) or stratum 1 (primary reference source), this is a four-octet, left-justified, zero-padded ASCII string. Stratum, Code, Meaning 0, DCN, DCN routing protocol 0, TSP, TSP time protocol 1, ATOM, Atomic clock (calibrated) 1, WWVB, WWVB LF (band 5) radio 1, GOES, GOES UHF (band 9) satellite 1, WWV, WWV HF (band 7) radio
OCT hwNTPPeerRefTime	1.3.6.1.4.1.2011.5.25.22.2.1.1.1.17	OCTET STRING	read-only	This is the local time at the peer, in timestamp format, when the local clock was last updated. If the local clock has never been synchronized, the value is zero.
OCT hwNTPPeerOrg	1.3.6.1.4.1.2011.5.25.22.2.1.1.1.18	OCTET STRING	read-only	This is the local time, in timestamp format, at the peer when it's latest NTP message was sent. If the peer becomes unreachable the value is set to zero
OCT hwNTPPeerRec	1.3.6.1.4.1.2011.5.25.22.2.1.1.1.19	OCTET STRING	read-only	This is the local time, in timestamp format, when the latest NTP message from the peer arrived. If the peer becomes unreachable the value is set to zero.
OCT hwNTPPeerXmt	1.3.6.1.4.1.2011.5.25.22.2.1.1.1.20	OCTET STRING	read-only	This is the local time, in timestamp format, at which the NTP message departed the sender.
I32 hwNTPPeerReach	1.3.6.1.4.1.2011.5.25.22.2.1.1.1.21	Integer32	read-only	This is a shift register of NTP.WINDOW bits used to determine the reach ability status of the peer, with bits entering from the least significant (rightmost) end. A peer is considered reachable if at least one bit in this register is set to one
I32 hwNTPPeerValid	1.3.6.1.4.1.2011.5.25.22.2.1.1.1.22	Integer32	read-only	This is an integer counter indicating the valid samples remaining in the filter register. It is used to determine the reach ability state and when the poll interval should be increased or decreased.
I32 hwNTPPeerTimer	1.3.6.1.4.1.2011.5.25.22.2.1.1.1.23	Integer32	read-only	This is an integer counter used to control the interval of transmitted NTP messages from the local host to the peer.
OCT hwNTPPeerDelay	1.3.6.1.4.1.2011.5.25.22.2.1.1.1.24	OCTET STRING	read-only	This is a signed fixed-point number indicating the roundtrip delay of the peer clock relative to the local clock over the network path between them, in seconds. Note that this variable can take on both positive and negative values, depending on clock precision and skew-error accumulation.
OCT hwNTPPeerOffset	1.3.6.1.4.1.2011.5.25.22.2.1.1.1.25	OCTET STRING	read-only	This is a signed, fixed-point number indicating the offset of the peer clock relative to the local clock, in seconds.
OCT hwNTPPeerJitter	1.3.6.1.4.1.2011.5.25.22.2.1.1.1.26	OCTET STRING	read-only	This is an indicating that peer of sample Variance
OCT hwNTPPeerDispersion	1.3.6.1.4.1.2011.5.25.22.2.1.1.1.27	OCTET STRING	read-only	This is a signed fixed-point number indicating the maximum error of the peer clock relative to the local clock over the network path between them, in seconds. Only positive values greater than zero are possible.
U32 hwNTPPeerKeyId	1.3.6.1.4.1.2011.5.25.22.2.1.1.1.28	Unsigned32	read-only	This is an unsigned integer identifying the cryptographic key used to generate the message-authentication code.
OCT hwNTPPeerFiltDelay	1.3.6.1.4.1.2011.5.25.22.2.1.1.1.29	OCTET STRING	read-only	Round-trip delay of the peer clock relative to the local clock over the network path between them, in seconds. This variable can take on both positive and negative values, depending on clock precision and skew-error accumulation.
OCT hwNTPPeerFiltOffset	1.3.6.1.4.1.2011.5.25.22.2.1.1.1.30	OCTET STRING	read-only	The offset of the peer clock relative to the local clock in seconds.
OCT hwNTPPeerFiltError	1.3.6.1.4.1.2011.5.25.22.2.1.1.1.31	OCTET STRING	read-only	The maximum error of the peer clock relative to the local clock over the network path between them, in seconds. Only positive values greater than zero are possible.
INT hwNTPPeerPMode	1.3.6.1.4.1.2011.5.25.22.2.1.1.1.32	INTEGER	read-only	This is an integer indicating the association mode, with values coded as follows, 0, unspecified 1, symmetric active - A host operating in this mode sends periodic messages regardless of the reach ability state or stratum of its peer. By operating in this mode the host announces its willingness to synchronize and be synchronized by the peer 2, symmetric passive - This type of association is ordinarily created upon arrival of a message from a peer operating in the symmetric active mode and persists only as long as the peer is reachable and operating at a stratum level less than or equal to the host; otherwise, the association is dissolved. However, the association will always persist until at least one message has been sent in reply. By operating in this mode the host announces its willingness to synchronize and be synchronized by the peer 3, client - A host operating in this mode sends periodic messages regardless of the reach ability state or stratum of its peer. By operating in this mode the host, usually a LAN workstation, announces its willingness to be synchronized by, but not to synchronize the peer 4, server - This type of association is ordinarily created upon arrival of a client request message and exists only in order to reply to that request, after which the association is dissolved. By operating in this mode the host, usually a LAN time server, announces its willingness to synchronize, but not to be synchronized by the peer 5, broadcast - A host operating in this mode sends periodic messages regardless of the reach ability state or stratum of the peers. By operating in this mode the host, usually a LAN time server operating on a high-speed broadcast medium, announces its willingness to synchronize all of the peers, but not to be synchronized by any of them 6, reserved for NTP control messages 7, reserved for private use 8, broadcastclient 9, multicastclient When creating a new peer association, if no value is specified for this object, it defaults to 'symmetricActive'.
C32 hwNTPPeerReceivedEx	1.3.6.1.4.1.2011.5.25.22.2.1.1.1.33	Counter32	read-only	The number of received massages.
C32 hwNTPPeerSent	1.3.6.1.4.1.2011.5.25.22.2.1.1.1.34	Counter32	read-only	The number of send massages.
BIT hwNTPPeerFlash	1.3.6.1.4.1.2011.5.25.22.2.1.1.1.35	Bits	read-only	The information about the massage.
ROW hwNTPPeerRowStatus	1.3.6.1.4.1.2011.5.25.22.2.1.1.1.36	RowStatus	read-create	The status object for this row. When a management station is creating a new row, it should set the value for cntpPeersPeerAddress at least, before the row can be made 'active'.

RFC description

Monitors and manages Network Time Protocol (NTP) server synchronization on Huawei devices.

Start monitoring Huawei router or switch using NTP for time synchronization with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download HUAWEI-NTP-MIB