Unisphere-Data-System-Clock-MIB :: usdNtpPeerState

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsUnisphere-Data-System-Clock-MIBusdNtpPeerState

usdNtpPeerState

Module: Unisphere-Data-System-Clock-MIB

OID (symbolic): Unisphere-Data-System-Clock-MIB::usdNtpPeerState

OID (numeric): 1.3.6.1.4.1.4874.2.2.56.2.4.2.1.1

Node type: OBJECT-TYPE

Type: OCTET STRING

Access: read-only

Description: Displays 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. 

What is usdNtpPeerState?

An 8-bit flag field showing this peer's association state with the NTP client: bit 0 master (chosen as the master clock), bit 1 configured, bit 2 selected (a sync candidate), bit 3 unusable (fails master criteria), bit 4 preferred, bit 5 correct, bit 6 incorrect, bit 7 reserved. Admins read this to quickly see why a specific peer is or isn't being used as the time reference, e.g. seeing the unusable bit set on a misconfigured peer.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.4874.2.2.56.2.4.2.1.1
snmpwalk -v2c -c public <target> Unisphere-Data-System-Clock-MIB::usdNtpPeerState

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.4874.2.2.56.2.4.2.1.1.1
snmpget -v2c -c public <target> Unisphere-Data-System-Clock-MIB::usdNtpPeerState.1

Start monitoring Unisphere Networks (Juniper E-series/ERX) routing switches (system clock/NTP sync-state status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the Unisphere-Data-System-Clock-MIB::usdNtpPeerState OID value, configure state conditions and alerts, and monitor any Unisphere Networks (Juniper E-series/ERX) routing switches (system clock/NTP sync-state status) from a single console.

OID Breakdown

Upper-level ancestors (14 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.4874juniperUniJuniper-UNI-SMI
1.3.6.1.4.1.4874.2juniperUniMibsJuniper-UNI-SMI
1.3.6.1.4.1.4874.2.2juniMibsJuniper-MIBs
1.3.6.1.4.1.4874.2.2.56juniSysClockMIBJuniper-MIBs
1.3.6.1.4.1.4874.2.2.56.2juniNtpObjectsJuniper-System-Clock-MIB
1.3.6.1.4.1.4874.2.2.56.2.4juniNtpPeersJuniper-System-Clock-MIB
1.3.6.1.4.1.4874.2.2.56.2.4.2juniNtpPeerTableJuniper-System-Clock-MIB
1.3.6.1.4.1.4874.2.2.56.2.4.2.1juniNtpPeerEntryJuniper-System-Clock-MIB
Numeric OIDNameModule
1.3.6.1.4.1.4874.2.2.56.2.4.2.1.1usdNtpPeerStateUnisphere-Data-System-Clock-MIB