NTP-MIB
Imported Objects
Objects
56 total| Object Name |
|---|
udel OBJECT IDENTIFIER .1.3.6.1.4.1.1277 |
ntpMIBThis MIB module defines a MIB which provides mechanisms to monitor and control an NTP server. MODULE-IDENTITY .1.3.6.1.4.1.1277.3 |
ntpSystem OBJECT IDENTIFIER .1.3.6.1.4.1.1277.3.1 |
ntpSysLeaptwo-bit code warning of an impending leap second to be inserted in the NTP timescale.ro NTPLeapIndicator .1.3.6.1.4.1.1277.3.1.1 |
ntpSysStratumindicating the stratum of the local clock. 0, unspecified 1, primary reference (e.g.,, calibrated atomic clock, radio clock) 2-255, secondary reference (via NTP)ro Integer32 .1.3.6.1.4.1.1277.3.1.2 |
ntpSysPrecisionsigned integer indicating the precision of the various clocks, in seconds to the nearest power of two.ro Integer32 .1.3.6.1.4.1.1277.3.1.3 |
ntpSysRootDelaythe total roundtrip delay to the primary reference source at the root of the synchronization subnet, in secondsro OCTET STRING .1.3.6.1.4.1.1277.3.1.4 |
ntpSysRootDispersionthe maximum error relative to the primary reference source at the root of the synchronization subnet, in seconds. Only positive values greater than zero are possiblero OCTET STRING .1.3.6.1.4.1.1277.3.1.5 |
ntpSysRefIdthe 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.In the case of stratum 2 and greater (secondary reference) this is the four-octet Internet address of the peer selected for synchronization.ro OCTET STRING .1.3.6.1.4.1.1277.3.1.6 |
ntpSysRefTimethe local time when the local clock was last updated. If the local clock has neverbeen synchronized, the value is zero.ro NTPTimeStamp .1.3.6.1.4.1.1277.3.1.7 |
ntpSysPollthe 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.ro Integer32 .1.3.6.1.4.1.1277.3.1.8 |
ntpSysPeerthe 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.ro Unsigned32 .1.3.6.1.4.1.1277.3.1.9 |
ntpSysPhasero OCTET STRING .1.3.6.1.4.1.1277.3.1.10 |
ntpSysFreqro OCTET STRING .1.3.6.1.4.1.1277.3.1.11 |
ntpSysErrorro OCTET STRING .1.3.6.1.4.1.1277.3.1.12 |
ntpSysClockthe current local time. Local time is derived from the hardware clock of the particular machine and increments at intervals depending on the design used.ro NTPTimeStamp .1.3.6.1.4.1.1277.3.1.13 |
ntpSysSystemthe type of the local Operating Systemro OCTET STRING .1.3.6.1.4.1.1277.3.1.14 |
ntpSysProcessorthe type of the local Processorro OCTET STRING .1.3.6.1.4.1.1277.3.1.15 |
ntpPeers OBJECT IDENTIFIER .1.3.6.1.4.1.1277.3.2 |
ntpPeersVarTable SEQUENCE OF NtpPeersVarEntry .1.3.6.1.4.1.1277.3.2.1 |
ntpPeersVarEntry NtpPeersVarEntry .1.3.6.1.4.1.1277.3.2.1.1 |
ntpPeersAssocId Unsigned32 .1.3.6.1.4.1.1277.3.2.1.1.1 |
ntpPeersConfiguredThis is a bit indicating that the association was created from configuration information and should not be demobilized if the peer becomes unreachable.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.1277.3.2.1.1.2 |
ntpPeersPeerAddressthe Internet address of the peerro IpAddress .1.3.6.1.4.1.1277.3.2.1.1.3 |
ntpPeersPeerPort16-bit port number of the peer.ro Unsigned32 .1.3.6.1.4.1.1277.3.2.1.1.4 |
ntpPeersHostAddressthe Internet address of the hostro IpAddress .1.3.6.1.4.1.1277.3.2.1.1.5 |
ntpPeersHostPort16-bit port number of the hostro Unsigned32 .1.3.6.1.4.1.1277.3.2.1.1.6 |
ntpPeersLeaptwo-bit code warning of an impending leap second to be inserted in the NTP timescale.ro NTPLeapIndicator .1.3.6.1.4.1.1277.3.2.1.1.7 |
ntpPeersModethe association mode,with values coded as follows: 0, unspecified 1, symmetric active 2, symmetric passive 3, client 4, server 5, broadcast 6, reserved for NTP control messages 7, reserved for private usero Enumeration .1.3.6.1.4.1.1277.3.2.1.1.8 |
ntpPeersStratumindicating the stratum of the peer clock. 0, unspecified 1, primary reference (e.g.,, calibrated atomic clock, radio clock) 2-255, secondary reference (via NTP)ro Integer32 .1.3.6.1.4.1.1277.3.2.1.1.9 |
ntpPeersPeerPollpoll interval of the peerro Integer32 .1.3.6.1.4.1.1277.3.2.1.1.10 |
ntpPeersHostPollpoll interval of the hostro Integer32 .1.3.6.1.4.1.1277.3.2.1.1.11 |
ntpPeersPrecisionthe same as the systemPrecision except this is for the peerro Integer32 .1.3.6.1.4.1.1277.3.2.1.1.12 |
ntpPeersRootDelaythe same as the systemRootDealy except this is for the peerro OCTET STRING .1.3.6.1.4.1.1277.3.2.1.1.13 |
ntpPeersRootDispersionthe same as the systemDispersion except this is for the peerro OCTET STRING .1.3.6.1.4.1.1277.3.2.1.1.14 |
ntpPeersRefIdthe same as the systemRefid except this is for the peerro OCTET STRING .1.3.6.1.4.1.1277.3.2.1.1.15 |
ntpPeersRefTimethe same as the systemRefTime except this is for the peerro NTPTimeStamp .1.3.6.1.4.1.1277.3.2.1.1.16 |
ntpPeersOrgTimethe local time at the peer when its latest NTP message was sent. If the peer becomes unreachable the value is set to zero.ro NTPTimeStamp .1.3.6.1.4.1.1277.3.2.1.1.17 |
ntpPeersReceiveTimethe local time when the latest NTP message from the peer arrived. If the peer becomes unreachable the value is set to zero.ro NTPTimeStamp .1.3.6.1.4.1.1277.3.2.1.1.18 |
ntpPeersTransmitTimethe local time at which the NTP message departed the sender.ro NTPTimeStamp .1.3.6.1.4.1.1277.3.2.1.1.19 |
ntpPeersUpdateTimero NTPTimeStamp .1.3.6.1.4.1.1277.3.2.1.1.20 |
ntpPeersReacha shift register of NTP.WINDOW bits 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.ro Unsigned32 .1.3.6.1.4.1.1277.3.2.1.1.21 |
ntpPeersTimerro Integer32 .1.3.6.1.4.1.1277.3.2.1.1.22 |
ntpPeersOffsetro OCTET STRING .1.3.6.1.4.1.1277.3.2.1.1.23 |
ntpPeersDelayro OCTET STRING .1.3.6.1.4.1.1277.3.2.1.1.24 |
ntpPeersDispersionro OCTET STRING .1.3.6.1.4.1.1277.3.2.1.1.25 |
ntpFilter OBJECT IDENTIFIER .1.3.6.1.4.1.1277.3.3 |
ntpFilterPeersVarTableThis table is an extension of the Peer Variables Table in the Peer Group. SEQUENCE OF NtpFilterPeersVarEntry .1.3.6.1.4.1.1277.3.3.1 |
ntpFilterPeersVarEntry NtpFilterPeersVarEntry .1.3.6.1.4.1.1277.3.3.1.1 |
ntpFilterValidEntriesThe number of valid entries for a peer in the Filter Register Table.ro Integer32 .1.3.6.1.4.1.1277.3.3.1.1.1 |
ntpFilterRegisterTable SEQUENCE OF NtpFilterRegisterEntry .1.3.6.1.4.1.1277.3.3.2 |
ntpFilterRegisterEntry NtpFilterRegisterEntry .1.3.6.1.4.1.1277.3.3.2.1 |
ntpFilterIndex Unsigned32 .1.3.6.1.4.1.1277.3.3.2.1.1 |
ntpFilterPeersOffsetthe offset of the peer clock relative to the local clock in secondsro OCTET STRING .1.3.6.1.4.1.1277.3.3.2.1.2 |
ntpFilterPeersDelayroundtrip 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.ro OCTET STRING .1.3.6.1.4.1.1277.3.3.2.1.3 |
ntpFilterPeersDispersionthe 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.ro OCTET STRING .1.3.6.1.4.1.1277.3.3.2.1.4 |
More MIBs from University of California, Davis
Browse all University of California, DavisMIBs →The UCD-SNMP-MIB provides standard extensions for monitoring system resource utilization, specifically CPU load averages, memory usage, and disk space, primarily on Unix-like operating systems running the University of California, Davis (UCD) SNMP agent. It enables the collection of performance counters and system state data essential for capacity planning and fault detection in network infrastructure.
SNMP MIB module
Standard SNMP MIB module defining data structures for UCD-SNMP-MIB-OLD.
The XIV-MIB enables SNMP-based monitoring and management of IBM XIV storage arrays by exposing critical performance metrics such as drive health, controller status, volume utilization, and I/O statistics. This module facilitates the tracking of system availability, capacity thresholds, and hardware fault conditions to support proactive infrastructure maintenance.
The UCD-IPFWACC-MIB module enables SNMP-based monitoring of IP firewall accounting rules and their associated traffic counters on Linux systems utilizing the UCD-SNMP framework. It provides read-only access to rule definitions and packet/byte statistics for network traffic analysis, explicitly excluding write capabilities for rule modification or counter resets.
Standard SNMP MIB module defining data structures for IPFWACC-MIB.