AT-NTP-MIB
AI MIB Summary
The AT-NTP-MIB module enables the monitoring and configuration of Network Time Protocol (NTP) parameters, including server associations, synchronization status, and stratum levels, on Allied Telesis networking hardware. It facilitates the retrieval of time synchronization metrics and the management of NTP client/server settings to ensure accurate clock alignment across the network infrastructure.
This MIB file contains definitions of managed objects for the Allied Telesis Network Time Protocol configuration.
Main OID:
atNtp.1.3.6.1.4.1.207.8.4.4.4.502
34
Objects
Active
Status
3
Dependencies
Imported Objects
Objects
34 total| Object Name |
|---|
atNtpThis MIB file contains definitions of managed objects for the Allied Telesis Network Time Protocol configuration. MODULE-IDENTITY .1.3.6.1.4.1.207.8.4.4.4.502 |
atNtpPeerIndexNextThis object represents the next available value for the object 'atNtpPeerIndex'. For creation of a new entry in the 'atNtpPeerTable', a management application should read this object, get the value and use the same.ro INTEGER .1.3.6.1.4.1.207.8.4.4.4.502.6 |
atNtpPeerTableThis table contains information on the Network Time Protocol (NTP) peers' configurations in the system. SEQUENCE OF AtNtpPeerEntry .1.3.6.1.4.1.207.8.4.4.4.502.7 |
atNtpPeerEntryA conceptual entry in atNtpPeerTable. AtNtpPeerEntry .1.3.6.1.4.1.207.8.4.4.4.502.7.1 |
atNtpPeerIndexThis object represents the index corresponding to a particular NTP server or peer configuration in the system. For creation of a new entry, the value of this object should be same as that of the value of 'atNtpPeerIndexNext' object. If this is not the case, then the entry creation will fail. INTEGER .1.3.6.1.4.1.207.8.4.4.4.502.7.1.1 |
atNtpPeerNameAddrThis object represents host name, or the IP address, of the NTP peer. This object is a current object for row creation. When a new row is created, this object is set with a default value '0.0.0.0', and the management application should change it to a desired value by a SET operation.rw DisplayString (SNMPv2-TC) .1.3.6.1.4.1.207.8.4.4.4.502.7.1.2 |
atNtpPeerModeThis object represents the mode of the peer. It's value is coded as follows: server(1), peer(2)rw Enumeration .1.3.6.1.4.1.207.8.4.4.4.502.7.1.3 |
atNtpPeerPreferenceThis object specifies whether this peer is the preferred one over the others. It's value is encoded as follows: 0 - unknown 1 - not preferred 2 - preferred When the value of this object is 'not preferred', NTP chooses the peer with which to synchronize the time on the local system. If this object is set to 'preferred', NTP will choose the corresponding peer to synchronize the time with.rw INTEGER .1.3.6.1.4.1.207.8.4.4.4.502.7.1.4 |
atNtpPeerVersionThis object represents the NTP version the peer supports. It's value is encoded as follows: 0 - unknown 1 - version 1 2 - version 2 3 - version 3 4 - version 4rw INTEGER .1.3.6.1.4.1.207.8.4.4.4.502.7.1.5 |
atNtpPeerKeyNumberThis object represents the authentication key number.rw Unsigned32 .1.3.6.1.4.1.207.8.4.4.4.502.7.1.6 |
atNtpPeerRowStatusThe status of this row. The reading of this object should have a value of 'active(1)'. For creation of new entry, a management application should set this object with value 'createAndGo(4)', and using the same value as that got from reading object 'atNtpPeerIndexNext', as the index for the new entry. When an entry is created, the object 'atNtpPeerNameAddr' in the entry is set with a default value '0.0.0.0'. The management application should change it to a desired value with a SET operation. The management application may need to take additional SET operations to set values for other objects, to ensure they have desired values. For deletion of entry, a management application should set this object with value 'destroy(6)'. Once an entry is deleted, other entries in the table which have bigger index than the deleted one, will be indexed again. Therefore a management application can effectively delete multiple entries by repeating the SET operation using the same index.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.207.8.4.4.4.502.7.1.7 |
atNtpAssociationTableThis table contains NTP association information. SEQUENCE OF AtNtpAssociationEntry .1.3.6.1.4.1.207.8.4.4.4.502.10 |
atNtpAssociationEntryAn conceptual entry in atNtpAssociationTable. AtNtpAssociationEntry .1.3.6.1.4.1.207.8.4.4.4.502.10.1 |
atNtpAssociationIndexThis object represents the index corresponding to a particular NTP association. Integer32 .1.3.6.1.4.1.207.8.4.4.4.502.10.1.1 |
atNtpAssociationPeerAddrThis object represents the peer's IP address or host name.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.207.8.4.4.4.502.10.1.2 |
atNtpAssocaitionStatusThis object indicates the association's status. It's value is defined as follows: master(synced), master(unsynced), selected, candidate, configured, unknown.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.207.8.4.4.4.502.10.1.3 |
atNtpAssociationConfiguredThis object indicates whether the association is from configuration or not. It's value can be either 'configured' or 'dynamic'.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.207.8.4.4.4.502.10.1.4 |
atNtpAssociationRefClkAddrThis object indicates the IP address for the reference clock.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.207.8.4.4.4.502.10.1.5 |
atNtpAssociationStratumThis object indicates the stratum of the peer clock.ro Integer32 .1.3.6.1.4.1.207.8.4.4.4.502.10.1.6 |
atNtpAssociationPollThis object indicates the time between NTP requests from the device to the server.ro Integer32 UNITS "seconds" .1.3.6.1.4.1.207.8.4.4.4.502.10.1.7 |
atNtpAssociationReachThis object indicates the reachability status of the peer.ro Integer32 .1.3.6.1.4.1.207.8.4.4.4.502.10.1.8 |
atNtpAssociationDelayThis object indicates the round trip delay between the device and the server.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.207.8.4.4.4.502.10.1.9 |
atNtpAssociationOffsetThis object indicates the difference between the device clock and the server clock.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.207.8.4.4.4.502.10.1.10 |
atNtpAssociationDispThis object indicates the lowest measure of error associated with peer offset based on delay, in seconds.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.207.8.4.4.4.502.10.1.11 |
atNtpStatus OBJECT IDENTIFIER .1.3.6.1.4.1.207.8.4.4.4.502.11 |
atNtpSysClockSyncThis object indicates whether the system clock is synchronized.ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.207.8.4.4.4.502.11.1 |
atNtpSysStratumThis object represents the stratum of the local clock.ro Integer32 .1.3.6.1.4.1.207.8.4.4.4.502.11.2 |
atNtpSysReferenceThis object represents the current synchronization source.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.207.8.4.4.4.502.11.3 |
atNtpSysFrequencyThis object represents the actual clock frequency. source.ro Integer32 UNITS "Hz" .1.3.6.1.4.1.207.8.4.4.4.502.11.4 |
atNtpSysPrecisionSigned integer indicating the precision of the system clock, in seconds to the nearest power of two. The value is 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).ro Integer32 .1.3.6.1.4.1.207.8.4.4.4.502.11.5 |
atNtpSysRefTimeThis object indicates the local time when the local clock was last updated. If the local clock has never been synchronized, the value is zeroro OCTET STRING .1.3.6.1.4.1.207.8.4.4.4.502.11.6 |
atNtpSysClkOffsetThis object indicates the offset of the local clock relative to the server clock, in milliseconds.ro Integer32 UNITS "millisecond" .1.3.6.1.4.1.207.8.4.4.4.502.11.7 |
atNtpSysRootDelayThis object indicats the total round-trip delay in milliseconds, to the primary reference source at the root of the synchronization subnet.ro Integer32 UNITS "millisecond" .1.3.6.1.4.1.207.8.4.4.4.502.11.8 |
atNtpSysRootDispThis object indicates the maximum error in milliseconds, relative to the primary reference source at the root of the synchronization subnet.ro Integer32 UNITS "millisecond" .1.3.6.1.4.1.207.8.4.4.4.502.11.9 |