All MIBs › TIMETRA-NTP-MIB › tmnxNtpPeersStatus
tmnxNtpPeersStatus
Module: TIMETRA-NTP-MIB
OID (symbolic): TIMETRA-NTP-MIB::tmnxNtpPeersStatus
OID (numeric): 1.3.6.1.4.1.6527.3.1.2.38.3.2.1.18
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-only
Description: The value of tmnxNtpPeersStatus indicates the status of the peer, with values coded as follows:
0, reject - The peer is rejected and will not be used for synchronization. Rejection reasons could be the peer is unreachable, the peer is synchronized to this local server so synchronizing with it would create a sync loop, or the synchronization distance is too large. 1, inaccurate - The peer is not maintaining an accurate clock. This peer will not be used for synchronization. 2, excess - The peer's synchronization distance is greater than ten other peers. This peer will not be used for synchronization. 3, outlyer - The peer is discarded as an outlyer. This peer will not be used for synchronization. 4, candidate - The peer is accepted as a possible source of synchronization. 5, selected - The peer is an acceptable source of synchronization, but it's synchronization distance is greater than six other peers. 6, syspeer - The peer is chosen as the source of synchronization. 7, ppspeer - The peer is chosen as the source of synchronization, but the actual synchronization is occurring from a pulse-per-second (PPS) signal.
What is tmnxNtpPeersStatus?
Reports where this peer stands in NTP's clock-selection algorithm, from outright rejected (unreachable, inaccurate, or creates a sync loop) through candidate and selected up to 'syspeer' (the actual chosen synchronization source) or 'ppspeer' (synchronized via a pulse-per-second signal). An admin looks for exactly one peer at 'syspeer' as the expected steady-state, and investigates if none, or more than one, holds that status.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.6527.3.1.2.38.3.2.1.18 snmpwalk -v2c -c public <target> TIMETRA-NTP-MIB::tmnxNtpPeersStatus
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.18.1 snmpget -v2c -c public <target> TIMETRA-NTP-MIB::tmnxNtpPeersStatus.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::tmnxNtpPeersStatus 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 OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.6527 | timetra | ALCATEL-IND1-TIMETRA-GLOBAL-MIB |
| 1.3.6.1.4.1.6527.3 | timetraProducts | ALCATEL-IND1-TIMETRA-GLOBAL-MIB |
| 1.3.6.1.4.1.6527.3.1 | tmnxSRMIB | ALCATEL-IND1-TIMETRA-GLOBAL-MIB |
| 1.3.6.1.4.1.6527.3.1.2 | tmnxSRObjs | ALCATEL-IND1-TIMETRA-GLOBAL-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.6527.3.1.2.38 | tmnxNtpObjs | TIMETRA-NTP-MIB |
| 1.3.6.1.4.1.6527.3.1.2.38.3 | tmnxNtpPeers | TIMETRA-NTP-MIB |
| 1.3.6.1.4.1.6527.3.1.2.38.3.2 | tmnxNtpPeersVarTable | TIMETRA-NTP-MIB |
| 1.3.6.1.4.1.6527.3.1.2.38.3.2.1 | tmnxNtpPeersVarEntry | TIMETRA-NTP-MIB |
| 1.3.6.1.4.1.6527.3.1.2.38.3.2.1.18 | tmnxNtpPeersStatus | TIMETRA-NTP-MIB |