Juniper-System-Clock-MIB
The System Clock and Network Time Protocol (NTP) MIB for the Juniper Networks enterprise. The System Clock section of the MIB allows setting the system clock time, date and timezone. All definitions are based on the Gregorian calendar. The NTP portion of the MIB provides management for the local NTP client/server, which adheres to RFC 1305, the 'Network Time Protocol (Version 3) Specification, Implementation and Analysis'.
Main OID:
juniSysClockMIB.1.3.6.1.4.1.4874.2.2.56
117
Objects
Active
Status
5
Dependencies
Imported Objects
Objects
117 total| Object Name |
|---|
juniSysClockMIBThe System Clock and Network Time Protocol (NTP) MIB for the Juniper Networks enterprise. The System Clock section of the MIB allows setting the system clock time, date and timezone. All definitions are based on the Gregorian calendar. The NTP portion of the MIB provides management for the local NTP client/server, which adheres to RFC 1305, the 'Network Time Protocol (Version 3) Specification, Implementation and Analysis'. MODULE-IDENTITY .1.3.6.1.4.1.4874.2.2.56 |
juniSysClockObjects OBJECT IDENTIFIER .1.3.6.1.4.1.4874.2.2.56.1 |
juniSysClockTime OBJECT IDENTIFIER .1.3.6.1.4.1.4874.2.2.56.1.1 |
juniSysClockDateAndTimeThis object is used to manage the system clock time, date and timezone. If the Network Time Protocol (NTP) is enabled, attempts to set this object will result in an inconsistantValue error. For sets, the implementation may check the value of the year and if it is outside of a 'reasonable' range (e.g., 1999..2035) it may return an inconsistantValue error. Only system clock time and date will be set if the timezone offset is not set along with the timezone name.rw DateAndTime (SNMPv2-TC) .1.3.6.1.4.1.4874.2.2.56.1.1.1 |
juniSysClockTimeZoneNameName of the timezone. Timezone name take effects only with its offset set along with it.rw DisplayString .1.3.6.1.4.1.4874.2.2.56.1.1.2 |
juniSysClockDst OBJECT IDENTIFIER .1.3.6.1.4.1.4874.2.2.56.1.2 |
juniSysClockDstNameThe name of the daylight savings time (DST) zone. Setting any standard US DST timezone name with recurrent mode will result in turning on corresponding DST recurrent mode values for the timezone.rw DisplayString .1.3.6.1.4.1.4874.2.2.56.1.2.1 |
juniSysClockDstOffsetThe offset, in minutes, from the base timezone for the DST.rw Integer32 .1.3.6.1.4.1.4874.2.2.56.1.2.2 |
juniSysClockDstStatusThe state of DST. With each state, only corresponding objects can be set. When the state is off(0), set values will be ignored.rw Enumeration .1.3.6.1.4.1.4874.2.2.56.1.2.3 |
juniSysClockDstAbsoluteStartTimeThis object represents the start time for absolute DST. Only the year, month, day, hour and minutes fields of the object are used. The other fields will be ignored for a Set operation and will return zeroes for a Get operation.rw DateAndTime (SNMPv2-TC) .1.3.6.1.4.1.4874.2.2.56.1.2.4 |
juniSysClockDstAbsoluteStopTimeThis object represents the stop time for absolute DST. Only the year, month, day, hour and minutes fields of the object are used. The other fields will be ignored for a Set operation and will return zeroes when read.rw DateAndTime (SNMPv2-TC) .1.3.6.1.4.1.4874.2.2.56.1.2.5 |
juniSysClockDstRecurStartMonthThe start month for DST recurrence. The default value is based on the 2007 law for the USA.rw JuniSysClockMonth .1.3.6.1.4.1.4874.2.2.56.1.2.6 |
juniSysClockDstRecurStartWeekThe start week of the month for DST recurrence. The default value is based on the 2007 law for the USA.rw JuniSysClockWeekOfTheMonth .1.3.6.1.4.1.4874.2.2.56.1.2.7 |
juniSysClockDstRecurStartDayThe start day of the week for DST recurrence. The default value is based on the 2007 law for the USA.rw JuniSysClockDayOfTheWeek .1.3.6.1.4.1.4874.2.2.56.1.2.8 |
juniSysClockDstRecurStartHourThe start hour for DST recurrence. The default value is based on the 2007 law for the USA.rw JuniSysClockHour .1.3.6.1.4.1.4874.2.2.56.1.2.9 |
juniSysClockDstRecurStartMinuteThe start minute for DST recurrence. The default value is based on the 2007 law for the USA.rw JuniSysClockMinute .1.3.6.1.4.1.4874.2.2.56.1.2.10 |
juniSysClockDstRecurStopMonthThe stop month for DST recurrence. The default value is based on the 2007 law for the USA.rw JuniSysClockMonth .1.3.6.1.4.1.4874.2.2.56.1.2.11 |
juniSysClockDstRecurStopWeekThe stop week of the month for DST recurrence. The default value is based on the 2007 law for the USA.rw JuniSysClockWeekOfTheMonth .1.3.6.1.4.1.4874.2.2.56.1.2.12 |
juniSysClockDstRecurStopDayThe stop day of the week for DST recurrence. The default value is based on the 2007 law for the USA.rw JuniSysClockDayOfTheWeek .1.3.6.1.4.1.4874.2.2.56.1.2.13 |
juniSysClockDstRecurStopHourThe stop hour for DST recurrence. The default value is based on the 2007 law for the USA.rw JuniSysClockHour .1.3.6.1.4.1.4874.2.2.56.1.2.14 |
juniSysClockDstRecurStopMinuteThe stop minutes for DST recurrence. The default value is based on the 2007 law for the USA.rw JuniSysClockMinute .1.3.6.1.4.1.4874.2.2.56.1.2.15 |
juniNtpObjects OBJECT IDENTIFIER .1.3.6.1.4.1.4874.2.2.56.2 |
juniNtpTraps OBJECT IDENTIFIER .1.3.6.1.4.1.4874.2.2.56.2.0 |
juniNtpFrequencyCalibrationStartThis trap will be generated at the start of frequency synchronization. NOTIFICATION-TYPE .1.3.6.1.4.1.4874.2.2.56.2.0.1 |
juniNtpFrequencyCalibrationEndThis trap will be generated when frequency synchronization completes successfully. NOTIFICATION-TYPE .1.3.6.1.4.1.4874.2.2.56.2.0.2 |
juniNtpTimeSynUpThis trap indicates that some kind of time synchronization has started. This trap will be generated at the start of time synchronization with the configured time servers irrespective of whether time synchronization is done with all the configured time servers or any one of them (there may be reachability or other problems) when NTP is enabled on the router. NOTIFICATION-TYPE .1.3.6.1.4.1.4874.2.2.56.2.0.3 |
juniNtpTimeSynDownThis trap will be generated when the NTP client is not able to time synchronize with any of the configured time servers for any reasons when NTP is enabled on the router. NOTIFICATION-TYPE .1.3.6.1.4.1.4874.2.2.56.2.0.4 |
juniNtpTimeServerSynUpThis trap will be generated to report the time synchronization status of each configured time server on the router when it starts time synchronization with the NTP client. NOTIFICATION-TYPE .1.3.6.1.4.1.4874.2.2.56.2.0.5 |
juniNtpTimeServerSynDownThis trap will be generated to report the time synchronization status of each configured time server on the router when it stops time synchronization with the NTP client for any reasons. NOTIFICATION-TYPE .1.3.6.1.4.1.4874.2.2.56.2.0.6 |
juniNtpFirstSystemClockSetThis trap will be generated to report when the system clock offset error is set for the first time from the good time sample taken, enabling the time synchronization. This is usually the case after a system reboot. NOTIFICATION-TYPE .1.3.6.1.4.1.4874.2.2.56.2.0.7 |
juniNtpClockOffSetLimitCrossedThis trap will be generated whenever the system clock's offset error is more than 15 minutes. This is an indication that something is not set properly, since an offset of 15 minutes is not considered to be a normal offset error compared to the accuracy of the time servers and system clock. For example, it may indicate an improper setting of the timezone. NOTIFICATION-TYPE .1.3.6.1.4.1.4874.2.2.56.2.0.8 |
juniNtpSysClock OBJECT IDENTIFIER .1.3.6.1.4.1.4874.2.2.56.2.1 |
juniNtpSysClockStateDisplays the state of the NTP on the system clock. Clock states are: 0 - Clock has never been calibrated for frequency errors 1 - Clock frequency errors calibration has done 2 - Clock time has set to server time 3 - Clock frequency errors calibration is going on 4 - Clock has synchronized its time 5 - Clock has detected spikero Enumeration .1.3.6.1.4.1.4874.2.2.56.2.1.1 |
juniNtpSysClockOffsetErrorDisplays the estimated offset error of the system clock relative to the master clock in seconds. This variable can take on both positive and negative values; the value will be positive if the system clock is ahead of the master clock; the value will be negative if the system clock is behind the master clock. This offset value will be used by the internal NTP filter algorithm to adjust the system clock to correct any error it may have. This object has been deprecated in favor of the juniNtpSysClockOffsetErrorNew object, which uses DisplayString for its SYNTAX.rodeprecated JuniNtpClockSignedTime UNITS "seconds" .1.3.6.1.4.1.4874.2.2.56.2.1.2 |
juniNtpSysClockFrequencyErrorDisplays the system clock frequency error in parts per million (ppm). It will always be a positive value. This error adjustment happens when the system reboots or the NTP is enabled for the first time and it may take up to fifteen minutes to complete. Each system clock oscillator interrupts to update its clock. If, for example, it interrupts one million time per second then it has a resolution of microseconds. This is also the frequency of the clock update. Frequency error means that this system clock failed to update by parts per millionth of a second. For example, if the frequency error is 1ppm, it means the clock is ahead by 0.864 second in a day, and therefore the clock will need to be corrected by that amount in the next 24 hours for the clock to be accurate. The frequency error varies with temperature. Therefore the system clock will usually need to be corrected when the system boots, based on the temperature at which it is operating. This object has been deprecated in favor of the juniNtpSysClockFrequencyErrorNew object, which uses DisplayString for its SYNTAX.rodeprecated Integer32 UNITS "ppm" .1.3.6.1.4.1.4874.2.2.56.2.1.3 |
juniNtpSysClockRootDelayThis indicates the NTP time message total Network 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.ro JuniNtpClockSignedTime UNITS "seconds" .1.3.6.1.4.1.4874.2.2.56.2.1.4 |
juniNtpSysClockRootDispersionThis indicates 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.ro JuniNtpClockUnsignedTime UNITS "seconds" .1.3.6.1.4.1.4874.2.2.56.2.1.5 |
juniNtpSysClockStratumNumberDisplays the stratum number of the system clock. -1 - shows stratum is not set 1 - primary reference (e.g. calibrated atomic clock, radio clock) 2-255 - secondary reference (via NTP)ro Integer32 (-1..255) .1.3.6.1.4.1.4874.2.2.56.2.1.6 |
juniNtpSysClockLastUpdateTimeDisplays the time of the system clock at the time when it was last updated by any associated NTP server(peer).ro JuniNtpTimeStamp UNITS "seconds" .1.3.6.1.4.1.4874.2.2.56.2.1.7 |
juniNtpSysClockLastUpdateServerDisplays the IP address of the NTP server (peer) which done last update to the system clock.ro IpAddress .1.3.6.1.4.1.4874.2.2.56.2.1.8 |
juniNtpSysClockOffsetErrorNewDisplays the estimated offset error of the system clock relative to the master clock in seconds. This variable can take on both positive and negative values; the value will be positive if the system clock is ahead of the master clock; the value will be negative if the system clock is behind the master clock. This offset value will be used by the internal NTP filter algorithm to adjust the system clock to correct any error it may have.ro DisplayString .1.3.6.1.4.1.4874.2.2.56.2.1.9 |
juniNtpSysClockFrequencyErrorNewDisplays the system clock frequency error in parts per million (ppm). It will always be a positive value. This error adjustment happens when the system reboots or the NTP is enabled for the first time and it may take up to fifteen minutes to complete. Each system clock oscillator interrupts to update its clock. If, for example, it interrupts one million time per second then it has a resolution of microseconds. This is also the frequency of the clock update. Frequency error means that this system clock failed to update by parts per millionth of a second. For example, if the frequency error is 1ppm, it means the clock is ahead by 0.864 second in a day, and therefore the clock will need to be corrected by that amount in the next 24 hours for the clock to be accurate. The frequency error varies with temperature. Therefore the system clock will usually need to be corrected when the system boots, based on the temperature at which it is operating.ro DisplayString .1.3.6.1.4.1.4874.2.2.56.2.1.10 |
juniNtpClient OBJECT IDENTIFIER .1.3.6.1.4.1.4874.2.2.56.2.2 |
juniNtpClientAdminStatusBy enabling/disabling the NTP admin status, the router is enabled/ disabled to run as NTP client for the correction and synchronization of the system clock time with the reliable time sources (stratum time servers). At any given time, only one NTP client can run on any router on the system. Sets the NTP admin status along with the routerIndex where NTP client has be enabled in that router context.rw JuniEnable (Juniper-TC) .1.3.6.1.4.1.4874.2.2.56.2.2.1 |
juniNtpClientSystemRouterIndexThe index of the router to be enabled or disabled as the system-wide NTP client. Always set along with juniNtpClientAdminStatus. This is also the router context when NTP is enabled.ro Unsigned32 .1.3.6.1.4.1.4874.2.2.56.2.2.2 |
juniNtpClientPacketSourceIfIndexWhen the NTP client sends an NTP packet, the source IP address is normally set to the address of the interface through which the NTP packet is sent. Sets all the outgoing NTP packets' source ifIndex to one specific ifIndex on the NTP client from which the source ifIndex is taken. This ifIndex will be the index of the IP interface as NTP is IP/UDP based. If the value is zero, it means no interface has configured.rw Integer32 .1.3.6.1.4.1.4874.2.2.56.2.2.3 |
juniNtpClientBroadcastDelayAllows to set the estimated round-trip broadcast delay between the system client and broadcast servers (peers).rw Integer32 .1.3.6.1.4.1.4874.2.2.56.2.2.4 |
juniNtpClientIfTableLists all the NTP client's interfaces enabled for NTP. All the IP interfaces on the NTP client are by default enabled for NTP communications and can be disabled individually on each IP interface. If desired, any IP interface can be blocked from participating in NTP communication. SEQUENCE OF JuniNtpClientIfEntry .1.3.6.1.4.1.4874.2.2.56.2.2.5 |
juniNtpClientIfEntryEach entry is per interface config for NTP. JuniNtpClientIfEntry .1.3.6.1.4.1.4874.2.2.56.2.2.5.1 |
juniNtpClientIfRouterIndexThe index of the router to be enabled or disabled as an NTP client. Unsigned32 .1.3.6.1.4.1.4874.2.2.56.2.2.5.1.1 |
juniNtpClientIfIfIndexThe ifIndex of the interface on the NTP client. Integer32 .1.3.6.1.4.1.4874.2.2.56.2.2.5.1.2 |
juniNtpClientIfDisableEnable/disable NTP on the interface.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.4874.2.2.56.2.2.5.1.3 |
juniNtpClientIfIsBroadcastClientEnable/disable NTP client's interface as broadcast client. As NTP client's broadcast interface, it receives the broadcast NTP messages from the associated servers (peers).rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.4874.2.2.56.2.2.5.1.4 |
juniNtpClientIfIsBroadcastServerEnable/disable NTP interface as broadcast server. As NTP server's broadcast interface, it broadcast NTP messages on the interfac.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.4874.2.2.56.2.2.5.1.5 |
juniNtpClientIfIsBroadcastServerVersionNTP Server Version on the NTP broadcast server interface. Default version is 3rw Integer32 .1.3.6.1.4.1.4874.2.2.56.2.2.5.1.6 |
juniNtpClientIfIsBroadcastServerDelayPoll Interval for broadcasting NTP messages in seconds as a power of two. Default value is 6(64s). Minimal value is 4(16s) and maximum value is 17 (36.4h).rw Integer32 .1.3.6.1.4.1.4874.2.2.56.2.2.5.1.7 |
juniNtpServer OBJECT IDENTIFIER .1.3.6.1.4.1.4874.2.2.56.2.3 |
juniNtpServerStratumNumberConfigure the stratum number (level) of the NTP server. Due to one system clock, setting the stratum number have a effect of setting all the NTP servers' stratum to one stratum number(level) on the system.rw Integer32 .1.3.6.1.4.1.4874.2.2.56.2.3.1 |
juniNtpServerAdminStatusEnable/disable the NTP server on the router.rw JuniEnable (Juniper-TC) .1.3.6.1.4.1.4874.2.2.56.2.3.2 |
juniNtpPeers OBJECT IDENTIFIER .1.3.6.1.4.1.4874.2.2.56.2.4 |
juniNtpPeerCfgTableThis table provides information on the peers with which the NTP client has associations. The associated peers(servers) to client will be running different hosts. SEQUENCE OF JuniNtpPeerCfgEntry .1.3.6.1.4.1.4874.2.2.56.2.4.1 |
juniNtpPeerCfgEntryEach entry provides one NTP server's configuration information. Each peer is uniquely identified by the routerIndex of the client to which it has to be associated and the Ip address of the remote server(peer) itself. Entries are automatically created when the user configures the remote peer NTP server info on the system which has to be associated with the NTP client and deleted when the user removes the peer association from the NTP server. JuniNtpPeerCfgEntry .1.3.6.1.4.1.4874.2.2.56.2.4.1.1 |
juniNtpPeerCfgIpAddressPeer's IP address. IpAddress .1.3.6.1.4.1.4874.2.2.56.2.4.1.1.1 |
juniNtpPeerCfgNtpVersionDisplays the peer server NTP software version.rw Integer32 .1.3.6.1.4.1.4874.2.2.56.2.4.1.1.2 |
juniNtpPeerCfgPacketSourceIfIndexAll the outgoing NTP packets' source address can be configured to one specific interface address on the NTP peer server. This object allows to configure all the outgoing NTP packets' source IP ifIndex to one specific IP ifIndex on the NTP server.rw Integer32 .1.3.6.1.4.1.4874.2.2.56.2.4.1.1.3 |
juniNtpPeerCfgIsPreferredSelect whether this NTP server is a preferred time source to the NTP client to which it has association.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.4874.2.2.56.2.4.1.1.4 |
juniNtpPeerCfgRowStatusControls creation/deletion of entries in this table according to the RowStatus textual convention, constrained to support the following values only: createAndGo destroy To create an entry in this table, the following entry objects MUST be explicitly configured: juniNtpPeerCfgRowStatusrw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.4874.2.2.56.2.4.1.1.5 |
juniNtpPeerTableThis table provides information on the peers with which the NTP client has associations. The associated peers (servers) to client will be running different hosts. SEQUENCE OF JuniNtpPeerEntry .1.3.6.1.4.1.4874.2.2.56.2.4.2 |
juniNtpPeerEntryEach entry provides one NTP server (peer) information. Each peer is uniquely identified by the routerIndex of the client to which it has to be associated and the Ip address of the remote server (peer) itself. Entries are automatically created when the user configures the remote peer NTP server info on the system which has to be associated with the NTP client and deleted when the user removes the peer association from the NTP server. JuniNtpPeerEntry .1.3.6.1.4.1.4874.2.2.56.2.4.2.1 |
juniNtpPeerStateDisplays the peer server association state to NTP client on the system. Bit Peer State Description --- ---------- ------------------------------------------------ 0 master Means NTP client on the system has chosen this peer server as the master. 1 configured Confirms peer server configured for the NTP client. 2 selected NTP client will consider this peer server when it chooses the master. 3 unusable Indication that the server does not meet the initial criteria for the master 4 preferred Indicates as preferred time source. 5 correct NTP client considers the peer server's clock is reasonably correct. 6 incorrect NTP client considers the peer server's clock is not reasonably correct 7 reserved Each bit position value of 0 and 1 disables and enables that peer state respectively.ro OCTET STRING .1.3.6.1.4.1.4874.2.2.56.2.4.2.1.1 |
juniNtpPeerStratumNumberDisplays the peer server system clock stratum number.ro Integer32 .1.3.6.1.4.1.4874.2.2.56.2.4.2.1.2 |
juniNtpPeerAssociationModeDisplays the peer server association mode to the NTP client on the router. broadcastServer - Broadcast only NTP messages. multicastServer - Broadcast only NTP messages for IGMP multicast Network. unicastServer - Only sends NTP poll messages to the peer servers.ro Enumeration .1.3.6.1.4.1.4874.2.2.56.2.4.2.1.3 |
juniNtpPeerBroadcastIntervalDisplays the broadcast time interval of the NTP time messages from the peer when the peer is enabled either as broadcast server or multicast server.ro Integer32 UNITS "seconds" .1.3.6.1.4.1.4874.2.2.56.2.4.2.1.4 |
juniNtpPeerPolledIntervalDisplays the time interval at which peer will be polled by NTP client with which peer has associations when it is enabled as unicast server.ro Integer32 UNITS "seconds" .1.3.6.1.4.1.4874.2.2.56.2.4.2.1.5 |
juniNtpPeerPollingIntervalDisplays the time interval at which peer will poll the servers with which peer has associations when it is enabled as unicast server.ro Integer32 UNITS "seconds" .1.3.6.1.4.1.4874.2.2.56.2.4.2.1.6 |
juniNtpPeerDelayDisplays the peer server broadcast delay.ro JuniNtpClockSignedTime UNITS "seconds" .1.3.6.1.4.1.4874.2.2.56.2.4.2.1.7 |
juniNtpPeerDispersionDisplays the peer server dispersion.ro JuniNtpClockUnsignedTime UNITS "seconds" .1.3.6.1.4.1.4874.2.2.56.2.4.2.1.8 |
juniNtpPeerOffsetErrorDisplays the peer server offset error.ro JuniNtpClockSignedTime UNITS "seconds" .1.3.6.1.4.1.4874.2.2.56.2.4.2.1.9 |
juniNtpPeerReachabilityDisplays the peer reachability status. An 8-bit number that shows whether or not the peer server responded to the last eight requests to the server to which it has association; one indicates a response, zero indicates no response. Count from rightmost to leftmost as latest to later requests as reachability states. For example, 0b11111111 indicates that the peer server responded to the last eight requests. If the system client reaches one peer server less often than it does other peer servers, that server is not a good choice for the masterro OCTET STRING .1.3.6.1.4.1.4874.2.2.56.2.4.2.1.10 |
juniNtpPeerRootDelayDisplays the peer server root delay.ro JuniNtpClockSignedTime UNITS "seconds" .1.3.6.1.4.1.4874.2.2.56.2.4.2.1.11 |
juniNtpPeerRootDispersionDisplays the peer server root dispersion.ro JuniNtpClockUnsignedTime UNITS "seconds" .1.3.6.1.4.1.4874.2.2.56.2.4.2.1.12 |
juniNtpPeerRootSyncDistanceDisplays the peer server synchronization distance. Measure of the total time error since the update in the path to the stratum 1 server.ro JuniNtpClockSignedTime UNITS "seconds" .1.3.6.1.4.1.4874.2.2.56.2.4.2.1.13 |
juniNtpPeerRootTimeLast time at which the stratum 1 server sent clock update reply to the this peer server.ro JuniNtpTimeStamp UNITS "seconds" .1.3.6.1.4.1.4874.2.2.56.2.4.2.1.14 |
juniNtpPeerRootTimeUpdateServerIP address of the stratum 1 server last updated the peer server.ro IpAddress .1.3.6.1.4.1.4874.2.2.56.2.4.2.1.15 |
juniNtpPeerReceiveTimeIf the peer server is either broadcast or multicast server, this will represent time stamp at which NTP client received the broadcast message. If it is unicast server, it represents the time stamp at which the peer has sent the response to the NTP client poll message.ro JuniNtpTimeStamp .1.3.6.1.4.1.4874.2.2.56.2.4.2.1.16 |
juniNtpPeerTransmitTimeIf the peer server is either broadcast or multicast server, this will represent time stamp at which peer sent the broadcast message. If it is unicast server, it represents the time stamp at which the NTP client has received response from the peer.ro JuniNtpTimeStamp .1.3.6.1.4.1.4874.2.2.56.2.4.2.1.17 |
juniNtpPeerRequestTimeFor unicast server, it represents the time stamp at which the system client sent NTP request to the peer.ro JuniNtpTimeStamp .1.3.6.1.4.1.4874.2.2.56.2.4.2.1.18 |
juniNtpPeerPrecisionLength of the clock tick (interrupt interval) of the server's clock.ro JuniNtpClockSignedTime UNITS "seconds" .1.3.6.1.4.1.4874.2.2.56.2.4.2.1.19 |
juniNtpPeerLastUpdateTimeDisplays the seconds since the last update from the NTP serverro Unsigned32 UNITS "seconds" .1.3.6.1.4.1.4874.2.2.56.2.4.2.1.20 |
juniNtpPeerFilterRegisterTableThe 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. The NTP clock-filter and selection algorithms are designed to minimize the error in the calculated time by using the objects values in the filter table. SEQUENCE OF JuniNtpPeerFilterRegisterEntry .1.3.6.1.4.1.4874.2.2.56.2.4.3 |
juniNtpPeerFilterRegisterEntryEach entry corresponds to one stage of the shift register and reading one set of values clock delay, clock offset and clock dispersion. Entries are automatically created whenever a peer is configured and deleted when the peer is removed. JuniNtpPeerFilterRegisterEntry .1.3.6.1.4.1.4874.2.2.56.2.4.3.1 |
juniNtpPeerFilterIndexAn 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. Unsigned32 .1.3.6.1.4.1.4874.2.2.56.2.4.3.1.1 |
juniNtpPeerFilterOffsetThe offset of the peer clock relative to the system clock in seconds.ro JuniNtpClockSignedTime UNITS "seconds" .1.3.6.1.4.1.4874.2.2.56.2.4.3.1.2 |
juniNtpPeerFilterDelayRoundtrip delay of the peer clock relative to the system 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 JuniNtpClockSignedTime UNITS "seconds" .1.3.6.1.4.1.4874.2.2.56.2.4.3.1.3 |
juniNtpPeerFilterDispersionThe maximum error of the peer clock relative to the system clock over the network path between them, in seconds. Only positive values greater than zero are possible.ro JuniNtpClockUnsignedTime UNITS "seconds" .1.3.6.1.4.1.4874.2.2.56.2.4.3.1.4 |
juniNtpAccessGroup OBJECT IDENTIFIER .1.3.6.1.4.1.4874.2.2.56.2.5 |
juniNtpRouterAccessGroupPeerConfigure the name of the peer access list for the NTP enabled router.rw DisplayString (SNMPv2-TC) .1.3.6.1.4.1.4874.2.2.56.2.5.1 |
juniNtpRouterAccessGroupServeConfigure the name of the serve access list for the NTP enabled router.rw DisplayString (SNMPv2-TC) .1.3.6.1.4.1.4874.2.2.56.2.5.2 |
juniNtpRouterAccessGroupServeOnlyConfigure the name of the serve-only access list for the NTP enabled router.rw DisplayString (SNMPv2-TC) .1.3.6.1.4.1.4874.2.2.56.2.5.3 |
juniNtpRouterAccessGroupQueryOnlyConfigure the name of the peer query-only list for the NTP enabled router.rw DisplayString (SNMPv2-TC) .1.3.6.1.4.1.4874.2.2.56.2.5.4 |
juniSysClockConformance OBJECT IDENTIFIER .1.3.6.1.4.1.4874.2.2.56.3 |
juniSysClockCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.4874.2.2.56.3.1 |
juniSysClockComplianceObsolete compliance statement for entities that implement the Juniper System Clock MIB. This statement became obsolete when NTP traps were added.obsolete Unknown .1.3.6.1.4.1.4874.2.2.56.3.1.1 |
juniSysClockCompliance2Obsolete compliance statement for entities that implement the Juniper System Clock MIB. This statement became obsolete when new offset and frequency error objects were added.obsolete Unknown .1.3.6.1.4.1.4874.2.2.56.3.1.2 |
juniSysClockCompliance3The compliance statement for entities that implement the Juniper System Clock MIB. Unknown .1.3.6.1.4.1.4874.2.2.56.3.1.3 |
juniSysClockGroups OBJECT IDENTIFIER .1.3.6.1.4.1.4874.2.2.56.3.2 |
juniSysClockTimeGroupThe management objects pertaining to the System Clock current date and time. Unknown .1.3.6.1.4.1.4874.2.2.56.3.2.1 |
juniSysClockDstGroupThe management objects pertaining to the System Clock daylight savings time information. Unknown .1.3.6.1.4.1.4874.2.2.56.3.2.2 |
juniNtpSysClockGroupObsolete management objects pertaining to the system clock when NTP is configured on the system. This group became obsolete when replacement clock offset and frequency error objects with DisplaySting syntax were added.obsolete Unknown .1.3.6.1.4.1.4874.2.2.56.3.2.3 |
juniNtpClientGroupThe management objects pertaining to the NTP client group. Unknown .1.3.6.1.4.1.4874.2.2.56.3.2.4 |
juniNtpServerGroupThe management objects pertaining to the NTP server group. Unknown .1.3.6.1.4.1.4874.2.2.56.3.2.5 |
juniNtpPeersGroupThe management objects pertaining to the NTP peers group.obsolete Unknown .1.3.6.1.4.1.4874.2.2.56.3.2.6 |
juniNtpAccessGroupGroupThe management objects pertaining to the NTP per router access group. Unknown .1.3.6.1.4.1.4874.2.2.56.3.2.7 |
juniNtpNotificationGroupThe management notifications pertaining to NTP state changes. Unknown .1.3.6.1.4.1.4874.2.2.56.3.2.8 |
juniNtpSysClockGroup2The management objects pertaining to the system clock when NTP is configured on the system. Unknown .1.3.6.1.4.1.4874.2.2.56.3.2.9 |
juniNtpSysClockDeprecatedGroupDeprecated management objects pertaining to the system clock when NTP is configured on the system.deprecated Unknown .1.3.6.1.4.1.4874.2.2.56.3.2.10 |
juniNtpPeersGroup1The management objects pertaining to the NTP peers group. Unknown .1.3.6.1.4.1.4874.2.2.56.3.2.11 |