CISCO-NTP-MIB
- Registered at
- 1.3.6.1.4.1.9.9.168
- Last updated
- 2006-07-31 00:00
- Organization
- Cisco Systems, Inc.
- Revisions
- 2006-07-31 00:00, 2004-07-23 00:00, 2003-07-29 00:00, 2003-07-07 00:00, 2002-02-20 00:00, 2000-06-16 00:00
- Namespace
- cisco
- Source file
CISCO-NTP-MIB- Digest
sha256:f0a1321b78d56a9c29a8f2021523b264e210224a56ea4e7af14075e5f62351ee
Description
This MIB module defines a MIB which provides mechanisms to monitor an NTP server. The MIB is derived from the Technical Report #Management of the NTP with SNMP# TR No. 98-09 authored by A.S. Sethi and Dave Mills in the University of Delaware. Below is a brief overview of NTP system architecture and implementation model. This will help understand the objects defined below and their relationships. NTP Intro: The Network Time Protocol (NTP) Version 3, is used to synchronize timekeeping among a set of distributed time servers and clients. The service model is based on a returnable-time design which depends only on measured clock offsets, but does not require reliable message delivery. The synchronization subnet uses a self-organizing, hierarchical master-slave configuration, with synchronization paths determined by a minimum-weight spanning tree. While multiple masters (primary servers) may exist, there is no requirement for an election protocol. System Archiecture: In the NTP model a number of primary reference sources, synchronized by wire or radio to national standards, are connected to widely accessible resources, such as backbone gateways, and operated as primary time servers. The purpose of NTP is to convey timekeeping information from these servers to other time servers via the Internet and also to cross-check clocks and mitigate errors due to equipment or propagation failures. Some number of local-net hosts or gateways, acting as secondary time servers, run NTP with one or more of the primary servers. In order to reduce the protocol overhead, the secondary servers distribute time via NTP to the remaining local-net hosts. In the interest of reliability, selected hosts can be equipped with less accurate but less expensive radio clocks and used for backup in case of failure of the primary and/or secondary servers or communication paths between them. NTP is designed to produce three products: clock offset, round-trip delay and dispersion, all of which are relative to a selected reference clock. Clock offset represents the amount to adjust the local clock to bring it into correspondence with the reference clock. Roundtrip delay provides the capability to launch a message to arrive at the reference clock at a specified time. Dispersion represents the maximum error of the local clock relative to the reference clock. Since most host time servers will synchronize via another peer time server, there are two components in each of these three products, those determined by the peer relative to the primary reference source of standard time and those measured by the host relative to the peer. Each of these components are maintained separately in the protocol in order to facilitate error control and management of the subnet itself. They provide not only precision measurements of offset and delay, but also definitive maximum error bounds, so that the user interface can determine not only the time, but the quality of the time as well. Implementation Model: In what may be the most common client/server model a client sends an NTP message to one or more servers and processes the replies as received. The server interchanges addresses and ports, overwrites certain fields in the message, recalculates the checksum and returns the message immediately. Information included in the NTP message allows the client to determine the server time with respect to local time and adjust the local clock accordingly. In addition, the message includes information to calculate the expected timekeeping accuracy and reliability, as well as select the best from possibly several servers. While the client/server model may suffice for use on local nets involving a public server and perhaps many workstation clients, the full generality of NTP requires distributed participation of a number of client/servers or peers arranged in a dynamically reconfigurable, hierarchically distributed configuration. It also requires sophisticated algorithms for association management, data manipulation and local-clock control. Glossary: 1. Host: Refers to an instantiation of the NTP protocol on a local processor. 2. Peer: Refers to an instantiation of the NTP protocol on a remote processor connected by a network path from the local host.
Contact
Cisco Systems Customer Service Postal: 170 W. Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS E-mail: cs-snmp@cisco.com
Imports
| From | Symbols |
|---|---|
| CISCO-SMI | ciscoMgmt |
| INET-ADDRESS-MIB | InetAddress, InetAddressType |
| SNMPv2-CONF | MODULE-COMPLIANCE, NOTIFICATION-GROUP, OBJECT-GROUP |
| SNMPv2-SMI | Gauge32, Integer32, IpAddress, MODULE-IDENTITY, NOTIFICATION-TYPE, OBJECT-IDENTITY, OBJECT-TYPE, Unsigned32, iso |
| SNMPv2-TC | DisplayString, RowStatus, TEXTUAL-CONVENTION, TruthValue |
Imported by
Nothing in this corpus imports this module.
Load order
Every file a consumer needs in order to load this module, dependencies first.
CISCO-NTP-MIB CISCO-SMI INET-ADDRESS-MIB SNMPv2-CONF SNMPv2-SMI SNMPv2-TC
Textual conventions
| Name | OID | Syntax | Access | Status |
|---|---|---|---|---|
| NTPAssocIdentifier TEXTUAL-CONVENTION The association identifier of the peer. Every peer with which an NTP server is associated with is identified by an association identifier. | current | |||
| NTPLeapIndicator TEXTUAL-CONVENTION 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) | current | |||
| NTPPollInterval TEXTUAL-CONVENTION The minimum interval between transmitted NTP messages, in seconds as a power of two. For instance, a value of six indicates a minimum interval of 64 seconds. | current | |||
| NTPRefId TEXTUAL-CONVENTION The reference clock identifier. In the case of stratum 0 (unspecified) or stratum 1 (primary reference source), this is a four-octet, left-justified, zero-padded ASCII string as defined in RFC-1305. In the case of stratum 2 and greater (secondary reference) this is the four-octet Internet address of the peer selected for synchronization. Some examples of stratum 0 identifiers are, DCN, DCN routing protocol NIST, NIST public modem TSP, TSP time protocol DTS, Digital Time Service Some examples of stratum 1 identifiers are, ATOM, Atomic clock (calibrated) VLF, VLF radio (OMEGA,, etc.) LORC, LORAN-C radionavigation GOES, GOES UHF environment satellite GPS, GPS UHF satellite positioning | current | |||
| NTPSignedTimeValue TEXTUAL-CONVENTION The time in seconds that could represent signed quantities like time delay with respect to some source. This textual-convention is specific to Cisco implementation of NTP where 32-bit integers are used for such quantities. The signed integer part is in the first 16 bits and the fraction part is in the last 16 bits. | current | |||
| NTPStratum TEXTUAL-CONVENTION Indicates the stratum of the clock. The stratum defines the accuracy of a time server. Higher the stratum, lower the accuracy. 0, unspecified 1, primary reference (e.g., calibrated atomic clock, radio clock) 2-255, secondary reference (via NTP) | current | |||
| NTPTimeStamp TEXTUAL-CONVENTION NTP timestamps are represented as a 64-bit unsigned fixed-point number, in seconds relative to 00:00 on 1 January 1900. The integer part is in the first 32 bits and the fraction part is in the last 32 bits. | current | |||
| NTPUnsignedTimeValue TEXTUAL-CONVENTION The time in seconds that could represent unsigned quantities like maximum error of the local clock with respect to some source. This textual-convention is specific to Cisco implementation of NTP where 32-bit integers are used for such quantities. The unsigned integer part is in the first 16 bits and the fraction part is in the last 16 bits. | current |
Objects
| Name | OID | Syntax | Access | Status |
|---|---|---|---|---|
| ciscoNtpMIBNotifs OBJECT-IDENTITY | 1.3.6.1.4.1.9.9.168.0 | |||
| ciscoNtpMIBObjects OBJECT-IDENTITY | 1.3.6.1.4.1.9.9.168.1 | |||
| cntpSystem OBJECT-IDENTITY | 1.3.6.1.4.1.9.9.168.1.1 | |||
| cntpSysLeap OBJECT-TYPE Two-bit code warning of an impending leap second to be inserted in the NTP timescale. This object can be set only when the cntpSysStratum has a value of 1. | 1.3.6.1.4.1.9.9.168.1.1.1 | NTPLeapIndicator | read-write | current |
| cntpSysStratum OBJECT-TYPE The stratum of the local clock. If the value is set to 1, i.e., this is a primary reference, then the Primary-Clock procedure described in Section 3.4.6, in RFC-1305 is invoked. | 1.3.6.1.4.1.9.9.168.1.1.2 | NTPStratum | read-write | current |
| cntpSysPrecision OBJECT-TYPE Signed integer indicating the precision of the system 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). | 1.3.6.1.4.1.9.9.168.1.1.3 | Integer32 (-20..20) | read-only | current |
| cntpSysRootDelay OBJECT-TYPE A signed fixed-point number indicating the total round-trip delay in seconds, to the primary reference source at the root of the synchronization subnet. | 1.3.6.1.4.1.9.9.168.1.1.4 | NTPSignedTimeValue | read-only | current |
| cntpSysRootDispersion OBJECT-TYPE The maximum error in seconds, relative to the primary reference source at the root of the synchronization subnet. Only positive values greater than zero are possible. | 1.3.6.1.4.1.9.9.168.1.1.5 | NTPUnsignedTimeValue | read-only | current |
| cntpSysRefId OBJECT-TYPE The reference identifier of the local clock. | 1.3.6.1.4.1.9.9.168.1.1.6 | NTPRefId | read-only | current |
| cntpSysRefTime OBJECT-TYPE The local time when the local clock was last updated. If the local clock has never been synchronized, the value is zero. | 1.3.6.1.4.1.9.9.168.1.1.7 | NTPTimeStamp | read-only | current |
| cntpSysPoll OBJECT-TYPE The interval at which the NTP server polls other NTP servers to synchronize its clock. | 1.3.6.1.4.1.9.9.168.1.1.8 | NTPPollInterval | read-only | current |
| cntpSysPeer OBJECT-TYPE The current synchronization source. This will contain the unique association identifier cntpPeersAssocId of the corresponding peer entry in the cntpPeersVarTable of the peer acting as the synchronization source. If there is no peer, the value will be 0. | 1.3.6.1.4.1.9.9.168.1.1.9 | NTPAssocIdentifier | read-only | current |
| cntpSysClock OBJECT-TYPE The current local time. Local time is derived from the hardware clock of the particular machine and increments at intervals depending on the design used. | 1.3.6.1.4.1.9.9.168.1.1.10 | NTPTimeStamp | read-only | current |
| cntpSysSrvStatus OBJECT-TYPE Current state of the NTP server with values coded as follows: 1: server status is unknown 2: server is not running 3: server is not synchronized to any time source 4: server is synchronized to its own local clock 5: server is synchronized to a local hardware refclock (e.g. GPS) 6: server is synchronized to a remote NTP server | 1.3.6.1.4.1.9.9.168.1.1.11 | INTEGER {unknown(1), notRunning(2), notSynchronized(3), syncToLocal(4), syncToRefclock(5), syncToRemoteServer(6)} | read-only | current |
| cntpPeers OBJECT-IDENTITY | 1.3.6.1.4.1.9.9.168.1.2 | |||
| cntpPeersVarTable OBJECT-TYPE 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. | 1.3.6.1.4.1.9.9.168.1.2.1 | not-accessible | current | |
| cntpPeersVarEntry OBJECT-TYPE 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: cntpPeersPeerAddress or cntpPeersPeerName, cntpPeersHostAddress and cntpPeersMode and making the cntpPeersEntryStatus as active(1). At the least, the management station has to set a value for cntpPeersPeerAddress or cntpPeersPeerName to make the row active. | 1.3.6.1.4.1.9.9.168.1.2.1.1 | not-accessible | current | |
| cntpPeersAssocId OBJECT-TYPE An integer value greater than 0 that uniquely identifies a peer with which the local NTP server is associated. | 1.3.6.1.4.1.9.9.168.1.2.1.1.1 | NTPAssocIdentifier | not-accessible | current |
| cntpPeersConfigured OBJECT-TYPE This is a bit indicating that the association was created from configuration information and should not be de-associated even if the peer becomes unreachable. | 1.3.6.1.4.1.9.9.168.1.2.1.1.2 | TruthValue | read-only | current |
| cntpPeersPeerAddress OBJECT-TYPE The IP address of the peer. When creating a new association, a value should be set either for this object or the corresponding instance of cntpPeersPeerName, before the row is made active. | 1.3.6.1.4.1.9.9.168.1.2.1.1.3 | IpAddress | read-create | current |
| cntpPeersPeerPort OBJECT-TYPE The UDP port number on which the peer receives NTP messages. | 1.3.6.1.4.1.9.9.168.1.2.1.1.4 | Integer32 (1..65535) | read-only | current |
| cntpPeersHostAddress OBJECT-TYPE The IP address of the local host. Multi-homing can be supported using this object. | 1.3.6.1.4.1.9.9.168.1.2.1.1.5 | IpAddress | read-create | current |
| cntpPeersHostPort OBJECT-TYPE The UDP port number on which the local host receives NTP messages. | 1.3.6.1.4.1.9.9.168.1.2.1.1.6 | Integer32 (1..65535) | read-only | current |
| cntpPeersLeap OBJECT-TYPE Two-bit code warning of an impending leap second to be inserted in the NTP timescale of the peer. | 1.3.6.1.4.1.9.9.168.1.2.1.1.7 | NTPLeapIndicator | read-only | current |
| cntpPeersMode OBJECT-TYPE The association mode of the NTP server, with values coded as follows, 0, unspecified 1, symmetric active - A host operating in this mode sends periodic messages regardless of the reachability 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 reachability 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 reachability 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. When creating a new peer association, if no value is specified for this object, it defaults to symmetricActive(1). | 1.3.6.1.4.1.9.9.168.1.2.1.1.8 | INTEGER {unspecified(0), symmetricActive(1), symmetricPassive(2), client(3), server(4), broadcast(5), reservedControl(6), reservedPrivate(7)} | read-create | current |
| cntpPeersStratum OBJECT-TYPE The stratum of the peer clock. | 1.3.6.1.4.1.9.9.168.1.2.1.1.9 | NTPStratum | read-only | current |
| cntpPeersPeerPoll OBJECT-TYPE The interval at which the peer polls the local host. | 1.3.6.1.4.1.9.9.168.1.2.1.1.10 | NTPPollInterval | read-only | current |
| cntpPeersHostPoll OBJECT-TYPE The interval at which the local host polls the peer. | 1.3.6.1.4.1.9.9.168.1.2.1.1.11 | NTPPollInterval | read-only | current |
| cntpPeersPrecision OBJECT-TYPE 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). | 1.3.6.1.4.1.9.9.168.1.2.1.1.12 | Integer32 (-20..20) | read-only | current |
| cntpPeersRootDelay OBJECT-TYPE A signed fixed-point number indicating the total round-trip delay in seconds, from the peer to the primary reference source at the root of the synchronization subnet. | 1.3.6.1.4.1.9.9.168.1.2.1.1.13 | NTPSignedTimeValue | read-only | current |
| cntpPeersRootDispersion OBJECT-TYPE The maximum error in seconds, 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. | 1.3.6.1.4.1.9.9.168.1.2.1.1.14 | NTPUnsignedTimeValue | read-only | current |
| cntpPeersRefId OBJECT-TYPE The reference identifier of the peer. | 1.3.6.1.4.1.9.9.168.1.2.1.1.15 | NTPRefId | read-only | current |
| cntpPeersRefTime OBJECT-TYPE The local time at the peer when its clock was last updated. If the peer clock has never been synchronized, the value is zero. | 1.3.6.1.4.1.9.9.168.1.2.1.1.16 | NTPTimeStamp | read-only | current |
| cntpPeersOrgTime OBJECT-TYPE The local time at the peer, when its latest NTP message was sent. If the peer becomes unreachable the value is set to zero. | 1.3.6.1.4.1.9.9.168.1.2.1.1.17 | NTPTimeStamp | read-only | current |
| cntpPeersReceiveTime OBJECT-TYPE The local time, when the latest NTP message from the peer arrived. If the peer becomes unreachable the value is set to zero. | 1.3.6.1.4.1.9.9.168.1.2.1.1.18 | NTPTimeStamp | read-only | current |
| cntpPeersTransmitTime OBJECT-TYPE The local time at which the NTP message departed the sender. | 1.3.6.1.4.1.9.9.168.1.2.1.1.19 | NTPTimeStamp | read-only | current |
| cntpPeersUpdateTime OBJECT-TYPE The local time, when the most recent NTP message was received from the peer that was used to calculate the skew dispersion. This represents only the 32-bit integer part of the NTPTimestamp. | 1.3.6.1.4.1.9.9.168.1.2.1.1.20 | Integer32 (0..2147483647) | read-only | deprecated |
| cntpPeersReach OBJECT-TYPE A shift register of used to determine the reachability 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 i.e, if the value of this object is non-zero. The data in the shift register would be populated by the NTP protocol procedures. | 1.3.6.1.4.1.9.9.168.1.2.1.1.21 | Integer32 (0..255) | read-only | current |
| cntpPeersTimer OBJECT-TYPE The interval in seconds, between transmitted NTP messages from the local host to the peer. | 1.3.6.1.4.1.9.9.168.1.2.1.1.22 | Integer32 (0..2147483647) | read-only | current |
| cntpPeersOffset OBJECT-TYPE The estimated offset of the peer clock relative to the local clock, in seconds. The host determines the value of this object using the NTP clock-filter algorithm. | 1.3.6.1.4.1.9.9.168.1.2.1.1.23 | NTPSignedTimeValue | read-only | current |
| cntpPeersDelay OBJECT-TYPE The estimated round-trip delay of the peer clock relative to the local clock over the network path between them, in seconds. The host determines the value of this object using the NTP clock-filter algorithm. | 1.3.6.1.4.1.9.9.168.1.2.1.1.24 | NTPSignedTimeValue | read-only | current |
| cntpPeersDispersion OBJECT-TYPE The estimated maximum error of the peer clock relative to the local clock over the network path between them, in seconds. The host determines the value of this object using the NTP clock-filter algorithm. | 1.3.6.1.4.1.9.9.168.1.2.1.1.25 | NTPUnsignedTimeValue | read-only | current |
| cntpPeersFilterValidEntries OBJECT-TYPE The number of valid entries for a peer in the Filter Register Table. Since, the Filter Register Table is optional, this object will have a value 0 if the Filter Register Table is not implemented. | 1.3.6.1.4.1.9.9.168.1.2.1.1.26 | Gauge32 | read-only | current |
| cntpPeersEntryStatus OBJECT-TYPE 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(1). | 1.3.6.1.4.1.9.9.168.1.2.1.1.27 | RowStatus | read-create | current |
| cntpPeersUpdateTimeRev1 OBJECT-TYPE The local time, when the most recent NTP message was received from the peer that was used to calculate the skew dispersion. This represents only the 32-bit integer part of the NTPTimestamp. | 1.3.6.1.4.1.9.9.168.1.2.1.1.28 | Unsigned32 | read-only | current |
| cntpPeersPrefPeer OBJECT-TYPE This object specifies whether this peer is the preferred one over the others. By default, when the value of this object is 'false', NTP chooses the peer with which to synchronize the time on the local system. If this object is set to 'true', NTP will choose the corresponding peer to synchronize the time with. If multiple entries have this object set to 'true', NTP will choose the first one to be set. This object is a means to override the selection of the peer by NTP. | 1.3.6.1.4.1.9.9.168.1.2.1.1.29 | TruthValue | read-create | current |
| cntpPeersPeerType OBJECT-TYPE Represents the type of the corresponding instance of cntpPeersPeerName object. | 1.3.6.1.4.1.9.9.168.1.2.1.1.30 | InetAddressType | read-create | current |
| cntpPeersPeerName OBJECT-TYPE The address of the peer. When creating a new association, a value must be set for either this object or the corresponding instance of cntpPeersPeerAddress object, before the row is made active. | 1.3.6.1.4.1.9.9.168.1.2.1.1.31 | InetAddress | read-create | current |
| cntpFilter OBJECT-IDENTITY | 1.3.6.1.4.1.9.9.168.1.3 | |||
| cntpFilterRegisterTable OBJECT-TYPE The following table contains NTP state variables used by the NTP clock filter and selection algorithms. This table depicts a shift register. Each stage in the shift register is a 3-tuple consisting of the measured clock offset, measured clock delay and measured clock dispersion associated with a single observation. An important factor affecting the accuracy and reliability of time distribution is the complex of algorithms used to reduce the effect of statistical errors and falsetickers due to failure of various subnet components, reference sources or propagation media. The NTP clock-filter and selection algorithms are designed to do exactly this. The objects in the filter register table below are used by these algorthims to minimize the error in the calculated time. | 1.3.6.1.4.1.9.9.168.1.3.2 | not-accessible | current | |
| cntpFilterRegisterEntry OBJECT-TYPE Each entry corresponds to one stage of the shift register, i.e., one reading of the variables clock delay, clock offset and clock dispersion. Entries are automatically created whenever a peer is configured and deleted when the peer is removed. | 1.3.6.1.4.1.9.9.168.1.3.2.1 | not-accessible | current | |
| cntpFilterIndex OBJECT-TYPE An integer value in the specified range that is used to index into the table. The size of the table is fixed at 8. Each entry identifies a particular reading of the clock filter variables in the shift register. Entries are added starting at index 1. The index wraps back to 1 when it reaches 8. When the index wraps back, the new entries will overwrite the old entries effectively deleting the old entry. | 1.3.6.1.4.1.9.9.168.1.3.2.1.1 | Integer32 (1..8) | not-accessible | current |
| cntpFilterPeersOffset OBJECT-TYPE The offset of the peer clock relative to the local clock in seconds. | 1.3.6.1.4.1.9.9.168.1.3.2.1.2 | NTPSignedTimeValue | read-only | current |
| cntpFilterPeersDelay OBJECT-TYPE 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. | 1.3.6.1.4.1.9.9.168.1.3.2.1.3 | NTPSignedTimeValue | read-only | current |
| cntpFilterPeersDispersion OBJECT-TYPE 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. | 1.3.6.1.4.1.9.9.168.1.3.2.1.4 | NTPUnsignedTimeValue | read-only | current |
| ciscoNtpMIBConformance OBJECT-IDENTITY | 1.3.6.1.4.1.9.9.168.2 | |||
| ciscoNtpMIBCompliances OBJECT-IDENTITY | 1.3.6.1.4.1.9.9.168.2.1 | |||
| ciscoNtpMIBGroups OBJECT-IDENTITY | 1.3.6.1.4.1.9.9.168.2.2 |
Notifications
| Name | OID | Status |
|---|---|---|
| ciscoNtpSrvStatusChange NOTIFICATION-TYPE This notification is generated whenever the value of cntpSysSrvStatus changes. | 1.3.6.1.4.1.9.9.168.0.1 | current |
| ciscoNtpHighPriorityConnFailure NOTIFICATION-TYPE A failure to connect with an high priority NTP server (e.g. a server at the lowest stratum) is detected. | 1.3.6.1.4.1.9.9.168.0.2 | current |
| ciscoNtpHighPriorityConnRestore NOTIFICATION-TYPE A connection with an high priority NTP server (e.g. a server at the lowest stratum) is restored. | 1.3.6.1.4.1.9.9.168.0.3 | current |
| ciscoNtpGeneralConnFailure NOTIFICATION-TYPE This trap is sent when the device loses connectivity to all NTP servers. | 1.3.6.1.4.1.9.9.168.0.4 | current |
| ciscoNtpGeneralConnRestore NOTIFICATION-TYPE This trap is sent when the connection with at least one NTP server has been restored (e.g. after a ciscoNtpGeneralConnFailure). | 1.3.6.1.4.1.9.9.168.0.5 | current |
Conformance
| Name | OID | Status |
|---|---|---|
| ciscoNtpMIBCompliance MODULE-COMPLIANCE The compliance statement for Cisco agents which implement the Cisco NTP MIB. | 1.3.6.1.4.1.9.9.168.2.1.1 | deprecated |
| ciscoNtpMIBComplianceRev1 MODULE-COMPLIANCE The compliance statement for Cisco agents which implement the Cisco NTP MIB. | 1.3.6.1.4.1.9.9.168.2.1.2 | deprecated |
| ciscoNtpMIBComplianceRev2 MODULE-COMPLIANCE The compliance statement for Cisco agents which implement the Cisco NTP MIB. | 1.3.6.1.4.1.9.9.168.2.1.3 | deprecated |
| ciscoNtpMIBComplianceRev3 MODULE-COMPLIANCE The compliance statement for Cisco agents which implement the Cisco NTP MIB. | 1.3.6.1.4.1.9.9.168.2.1.4 | deprecated |
| ciscoNtpMIBComplianceRev4 MODULE-COMPLIANCE The compliance statement for Cisco agents which implement the Cisco NTP MIB. | 1.3.6.1.4.1.9.9.168.2.1.5 | current |
| ciscoNtpSysGroup OBJECT-GROUP The NTP system variables. | 1.3.6.1.4.1.9.9.168.2.2.1 | current |
| ciscoNtpPeersGroup OBJECT-GROUP The NTP peer variables. | 1.3.6.1.4.1.9.9.168.2.2.2 | deprecated |
| ciscoNtpFilterGroup OBJECT-GROUP The NTP clock-filter variables. | 1.3.6.1.4.1.9.9.168.2.2.3 | current |
| ciscoNtpPeersGroupRev1 OBJECT-GROUP The NTP peer variables. | 1.3.6.1.4.1.9.9.168.2.2.4 | deprecated |
| ciscoNtpPeerExtGroup OBJECT-GROUP The extended set of NTP peer variable(s). | 1.3.6.1.4.1.9.9.168.2.2.5 | current |
| ciscoNtpPeersGroupRev2 OBJECT-GROUP The NTP peer variables. | 1.3.6.1.4.1.9.9.168.2.2.6 | current |
| ciscoNtpSysExtGroup OBJECT-GROUP The extended set of NTP system variable(s). | 1.3.6.1.4.1.9.9.168.2.2.7 | current |
| ciscoNtpSrvNotifGroup NOTIFICATION-GROUP The collection of notifications for the NTP Server. | 1.3.6.1.4.1.9.9.168.2.2.8 | current |