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'.
    
Source file
Juniper-System-Clock-MIB
Last revised
Identity
juniSysClockMIB
Base OID
1.3.6.1.4.1.4874.2.2.56
Imported Objects
Juniper-MIBs juniMibs
Juniper-TC JuniEnable
SNMPv2-CONF MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI Integer32 IpAddress MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) Unsigned32
SNMPv2-TC DateAndTime DisplayString RowStatus TEXTUAL-CONVENTION (no object page) TruthValue
Net-SNMP examples using the junose MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'Juniper-System-Clock-MIB' -M '/opt/observium/mibs/junose:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'Juniper-System-Clock-MIB::juniSysClockMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'Juniper-System-Clock-MIB' -M '/opt/observium/mibs/junose:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'Juniper-System-Clock-MIB::juniSysClockMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (95)
.1.3.6.1.4.1.4874.2.2.56
.1.3.6.1.4.1.4874.2.2.56.1
.1.3.6.1.4.1.4874.2.2.56.1.1
.1.3.6.1.4.1.4874.2.2.56.1.1.1
OctetString
.1.3.6.1.4.1.4874.2.2.56.1.1.2
.1.3.6.1.4.1.4874.2.2.56.1.2
OctetString
.1.3.6.1.4.1.4874.2.2.56.1.2.1
.1.3.6.1.4.1.4874.2.2.56.1.2.10
.1.3.6.1.4.1.4874.2.2.56.1.2.11
.1.3.6.1.4.1.4874.2.2.56.1.2.12
.1.3.6.1.4.1.4874.2.2.56.1.2.13
.1.3.6.1.4.1.4874.2.2.56.1.2.14
.1.3.6.1.4.1.4874.2.2.56.1.2.15
minutesInteger32
.1.3.6.1.4.1.4874.2.2.56.1.2.2
Enumeration
.1.3.6.1.4.1.4874.2.2.56.1.2.3
.1.3.6.1.4.1.4874.2.2.56.1.2.4
.1.3.6.1.4.1.4874.2.2.56.1.2.5
.1.3.6.1.4.1.4874.2.2.56.1.2.6
.1.3.6.1.4.1.4874.2.2.56.1.2.7
.1.3.6.1.4.1.4874.2.2.56.1.2.8
.1.3.6.1.4.1.4874.2.2.56.1.2.9
.1.3.6.1.4.1.4874.2.2.56.2
.1.3.6.1.4.1.4874.2.2.56.2.0
.1.3.6.1.4.1.4874.2.2.56.2.1
Enumeration
.1.3.6.1.4.1.4874.2.2.56.2.1.1
ppmOctetString
.1.3.6.1.4.1.4874.2.2.56.2.1.10
.1.3.6.1.4.1.4874.2.2.56.2.1.2
.1.3.6.1.4.1.4874.2.2.56.2.1.3
.1.3.6.1.4.1.4874.2.2.56.2.1.4
.1.3.6.1.4.1.4874.2.2.56.2.1.5
Integer32
.1.3.6.1.4.1.4874.2.2.56.2.1.6
.1.3.6.1.4.1.4874.2.2.56.2.1.7
.1.3.6.1.4.1.4874.2.2.56.2.1.8
secondsOctetString
.1.3.6.1.4.1.4874.2.2.56.2.1.9
.1.3.6.1.4.1.4874.2.2.56.2.2
.1.3.6.1.4.1.4874.2.2.56.2.2.1
.1.3.6.1.4.1.4874.2.2.56.2.2.2
Integer32
.1.3.6.1.4.1.4874.2.2.56.2.2.3
microsecondsInteger32
.1.3.6.1.4.1.4874.2.2.56.2.2.4
.1.3.6.1.4.1.4874.2.2.56.2.2.5
.1.3.6.1.4.1.4874.2.2.56.2.2.5.1
.1.3.6.1.4.1.4874.2.2.56.2.2.5.1.1
Integer32
.1.3.6.1.4.1.4874.2.2.56.2.2.5.1.2
.1.3.6.1.4.1.4874.2.2.56.2.2.5.1.3
.1.3.6.1.4.1.4874.2.2.56.2.2.5.1.4
.1.3.6.1.4.1.4874.2.2.56.2.2.5.1.5
Integer32
.1.3.6.1.4.1.4874.2.2.56.2.2.5.1.6
Integer32
.1.3.6.1.4.1.4874.2.2.56.2.2.5.1.7
.1.3.6.1.4.1.4874.2.2.56.2.3
Integer32
.1.3.6.1.4.1.4874.2.2.56.2.3.1
.1.3.6.1.4.1.4874.2.2.56.2.3.2
.1.3.6.1.4.1.4874.2.2.56.2.4
.1.3.6.1.4.1.4874.2.2.56.2.4.1
.1.3.6.1.4.1.4874.2.2.56.2.4.1.1
.1.3.6.1.4.1.4874.2.2.56.2.4.1.1.1
Integer32
.1.3.6.1.4.1.4874.2.2.56.2.4.1.1.2
Integer32
.1.3.6.1.4.1.4874.2.2.56.2.4.1.1.3
.1.3.6.1.4.1.4874.2.2.56.2.4.1.1.4
.1.3.6.1.4.1.4874.2.2.56.2.4.1.1.5
.1.3.6.1.4.1.4874.2.2.56.2.4.2
.1.3.6.1.4.1.4874.2.2.56.2.4.2.1
OctetString
.1.3.6.1.4.1.4874.2.2.56.2.4.2.1.1
OctetString
.1.3.6.1.4.1.4874.2.2.56.2.4.2.1.10
.1.3.6.1.4.1.4874.2.2.56.2.4.2.1.11
.1.3.6.1.4.1.4874.2.2.56.2.4.2.1.12
.1.3.6.1.4.1.4874.2.2.56.2.4.2.1.13
.1.3.6.1.4.1.4874.2.2.56.2.4.2.1.14
.1.3.6.1.4.1.4874.2.2.56.2.4.2.1.15
.1.3.6.1.4.1.4874.2.2.56.2.4.2.1.16
.1.3.6.1.4.1.4874.2.2.56.2.4.2.1.17
.1.3.6.1.4.1.4874.2.2.56.2.4.2.1.18
.1.3.6.1.4.1.4874.2.2.56.2.4.2.1.19
Integer32
.1.3.6.1.4.1.4874.2.2.56.2.4.2.1.2
.1.3.6.1.4.1.4874.2.2.56.2.4.2.1.20
Enumeration
.1.3.6.1.4.1.4874.2.2.56.2.4.2.1.3
.1.3.6.1.4.1.4874.2.2.56.2.4.2.1.4
.1.3.6.1.4.1.4874.2.2.56.2.4.2.1.5
.1.3.6.1.4.1.4874.2.2.56.2.4.2.1.6
.1.3.6.1.4.1.4874.2.2.56.2.4.2.1.7
.1.3.6.1.4.1.4874.2.2.56.2.4.2.1.8
.1.3.6.1.4.1.4874.2.2.56.2.4.2.1.9
.1.3.6.1.4.1.4874.2.2.56.2.4.3
.1.3.6.1.4.1.4874.2.2.56.2.4.3.1
.1.3.6.1.4.1.4874.2.2.56.2.4.3.1.1
.1.3.6.1.4.1.4874.2.2.56.2.4.3.1.2
.1.3.6.1.4.1.4874.2.2.56.2.4.3.1.3
.1.3.6.1.4.1.4874.2.2.56.2.4.3.1.4
.1.3.6.1.4.1.4874.2.2.56.2.5
.1.3.6.1.4.1.4874.2.2.56.2.5.1
.1.3.6.1.4.1.4874.2.2.56.2.5.2
.1.3.6.1.4.1.4874.2.2.56.2.5.3
.1.3.6.1.4.1.4874.2.2.56.2.5.4
.1.3.6.1.4.1.4874.2.2.56.3
.1.3.6.1.4.1.4874.2.2.56.3.1
.1.3.6.1.4.1.4874.2.2.56.3.2
Dependencies (6) 5 direct · 1 transitive Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Dependency-first compile order
  1. SNMPv2-SMIrfc
  2. Juniper-UNI-SMIjunose
  3. Juniper-MIBsjunose
  4. SNMPv2-TCrfc
  5. Juniper-TCjunose
  6. SNMPv2-CONFrfc
  7. Juniper-System-Clock-MIBjunoseselected
Type Definitions (8)
OctetString range: 0..11
OctetString range: 0..11
OctetString range: 0..21
Enumeration
sunday(0)
monday(1)
tuesday(2)
wednesday(3)
thursday(4)
friday(5)
saturday(6)
Integer32 range: 0..23
Integer32 range: 0..59
Enumeration
january(1)
february(2)
march(3)
april(4)
may(5)
june(6)
july(7)
august(8)
september(9)
october(10)
november(11)
december(12)
Enumeration
weekFirst(0)
weekOne(1)
weekTwo(2)
weekThree(3)
weekFour(4)
weekFive(5)
weekLast(6)
Conformance Groups (11)
The management objects pertaining to the System Clock current date and
time.
.1.3.6.1.4.1.4874.2.2.56.3.2.1
The management objects pertaining to the System Clock daylight savings
time information.
.1.3.6.1.4.1.4874.2.2.56.3.2.2
Obsolete 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.
.1.3.6.1.4.1.4874.2.2.56.3.2.3
The management objects pertaining to the NTP client group.
.1.3.6.1.4.1.4874.2.2.56.3.2.4
The management objects pertaining to the NTP server group.
.1.3.6.1.4.1.4874.2.2.56.3.2.5
The management objects pertaining to the NTP peers group.
.1.3.6.1.4.1.4874.2.2.56.3.2.6
The management objects pertaining to the NTP per router access group.
.1.3.6.1.4.1.4874.2.2.56.3.2.7
The management notifications pertaining to NTP state changes.
.1.3.6.1.4.1.4874.2.2.56.3.2.8
The management objects pertaining to the system clock when NTP is
configured on the system.
.1.3.6.1.4.1.4874.2.2.56.3.2.9
Deprecated management objects pertaining to the system clock when NTP
is configured on the system.
.1.3.6.1.4.1.4874.2.2.56.3.2.10
The management objects pertaining to the NTP peers group.
.1.3.6.1.4.1.4874.2.2.56.3.2.11
Compliance Statements (3)

OID .1.3.6.1.4.1.4874.2.2.56.3.1.1
Obsolete compliance statement for entities that implement the Juniper
System Clock MIB. This statement became obsolete when NTP traps were
added.
Required groups

OID .1.3.6.1.4.1.4874.2.2.56.3.1.2
Obsolete compliance statement for entities that implement the Juniper
System Clock MIB. This statement became obsolete when new offset and
frequency error objects were added.
Required groups

OID .1.3.6.1.4.1.4874.2.2.56.3.1.3
The compliance statement for entities that implement the Juniper System
Clock MIB.
Required groups
Notifications / Traps (8)
NameOIDDescription
.1.3.6.1.4.1.4874.2.2.56.2.0.1
This trap will be generated at the start of frequency synchronization.
.1.3.6.1.4.1.4874.2.2.56.2.0.2
This trap will be generated when frequency synchronization completes
successfully.
.1.3.6.1.4.1.4874.2.2.56.2.0.3
This 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.
.1.3.6.1.4.1.4874.2.2.56.2.0.4
This 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.
.1.3.6.1.4.1.4874.2.2.56.2.0.5
This 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.
.1.3.6.1.4.1.4874.2.2.56.2.0.6
This 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.
.1.3.6.1.4.1.4874.2.2.56.2.0.7
This 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.
.1.3.6.1.4.1.4874.2.2.56.2.0.8
This 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.