TIMETRA-NTP-MIB :: tmnxNtpPeersStatusFlags

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsTIMETRA-NTP-MIBtmnxNtpPeersStatusFlags

tmnxNtpPeersStatusFlags

Module: TIMETRA-NTP-MIB

OID (symbolic): TIMETRA-NTP-MIB::tmnxNtpPeersStatusFlags

OID (numeric): 1.3.6.1.4.1.6527.3.1.2.38.3.2.1.19

Node type: OBJECT-TYPE

Type: Bits

Access: read-only

Description: The value of tmnxNtpPeersStatusFlags contains bits which indicate the status of the peer, where 1 or more bits may be set, with values coded as follows:

0, config - If 1, the peer is a configured association. If 0, the peer is a temporary association. 1, authenable - If 1, the peer requires authentication. If 0, the peer does not require authentication. 2, authentic - If authenable is 1, if 1 the peer has passed authentication, if 0, the peer has failed authentication. If authenable is 0, this bit has no meaning. 3, reachable - If 1, the peer has been reached in 1 of the last 8 polls. If 0, the peer is not reachable in the last 8 polls. 4, broadcastclient - If 1, the peer is a broadcast client temporary association created in response to discovering a broadcast server. If 0, the peer is not a broadcast client association. 5, multicastclient - If 1, the peer is a multicast client temporary association created in response to discovering a multicast server. If 0, the peer is not a multicast client association. 6, broadcast - If 1, the peer is a broadcast server association. If 0, the peer is not a broadcast association. 7, multicast - If 1, the peer is a multicast server association. If 0, the peer is not a multicast association.

What is tmnxNtpPeersStatusFlags?

Reports a set of bit flags describing this peer's association: whether it's statically configured, requires authentication, has passed authentication, was reached in the last 8 polls, and whether it's a broadcast/multicast client or server association. An admin checks the 'reachable' bit first when a peer seems stuck at low status, and the 'authentic' bit when authentication was expected to succeed but the peer never advances past candidate.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.6527.3.1.2.38.3.2.1.19
snmpwalk -v2c -c public <target> TIMETRA-NTP-MIB::tmnxNtpPeersStatusFlags

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.6527.3.1.2.38.3.2.1.19.1
snmpget -v2c -c public <target> TIMETRA-NTP-MIB::tmnxNtpPeersStatusFlags.1

Start monitoring Nokia/Alcatel-Lucent 7xxx SROS routers (NTP client/server sync-status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the TIMETRA-NTP-MIB::tmnxNtpPeersStatusFlags OID value, configure state conditions and alerts, and monitor any Nokia/Alcatel-Lucent 7xxx SROS routers (NTP client/server sync-status) from a single console.

OID Breakdown

Upper-level ancestors (10 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.6527timetraALCATEL-IND1-TIMETRA-GLOBAL-MIB
1.3.6.1.4.1.6527.3timetraProductsALCATEL-IND1-TIMETRA-GLOBAL-MIB
1.3.6.1.4.1.6527.3.1tmnxSRMIBALCATEL-IND1-TIMETRA-GLOBAL-MIB
1.3.6.1.4.1.6527.3.1.2tmnxSRObjsALCATEL-IND1-TIMETRA-GLOBAL-MIB
Numeric OIDNameModule
1.3.6.1.4.1.6527.3.1.2.38tmnxNtpObjsTIMETRA-NTP-MIB
1.3.6.1.4.1.6527.3.1.2.38.3tmnxNtpPeersTIMETRA-NTP-MIB
1.3.6.1.4.1.6527.3.1.2.38.3.2tmnxNtpPeersVarTableTIMETRA-NTP-MIB
1.3.6.1.4.1.6527.3.1.2.38.3.2.1tmnxNtpPeersVarEntryTIMETRA-NTP-MIB
1.3.6.1.4.1.6527.3.1.2.38.3.2.1.19tmnxNtpPeersStatusFlagsTIMETRA-NTP-MIB