All MIBs › TIMETRA-NTP-MIB › tmnxNtpPeersMode
tmnxNtpPeersMode
Module: TIMETRA-NTP-MIB
OID (symbolic): TIMETRA-NTP-MIB::tmnxNtpPeersMode
OID (numeric): 1.3.6.1.4.1.6527.3.1.2.38.3.2.1.9
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-only
Description: The value of tmnxNtpPeersMode indicates the association mode, with values coded as follows:
0, unspecified 1, symmetric active - The host sends periodic messages regardless of the reachability state or stratum of this peer and so announces its willingness to synchronize and be synchronized by the peer. 2, symmetric passive - This association type is created upon receipt of a message from a peer operating in the symmetric active mode and lasts as long as the peer is reachable and operating at a stratum level less than or equal to the host. Else the association is dissolved. Such an association always lasts until at least one message has been sent in reply. A host in this mode announces its willingness to synchronize and be synchronized by the peer. 3, client - Periodic messages are sent regardless of the reachability state or stratum of the peer. A host in this mode announces its willingness to be synchronized by but not to synchronize the peer. 4, server - This association is created upon receipt of a client request message and exists only in order to reply to that request, after which the association is dissolved. A host in this mode announces its willingness to synchronize, but not to be synchronized by the peer. 5, broadcast - Periodic messages are sent regardless of the reachability state or stratum of the peers. A host in this mode announces its willingness to synchronize all of the peers but not to be synchronized by any of them. 6, reserved for NTP control messages 7, reserved for private use 8, broadcastclient - Messages are sent only in response to messages received from a broadcast server. A host in this mode is willing to be synchronized by any broadcast server.
What is tmnxNtpPeersMode?
Reports the NTP association mode for this peer: symmetric active/passive, client, server, broadcast, or broadcast client, each defining who is willing to synchronize whom. An admin reads this to understand the relationship type, for example confirming a peer shows 'client' mode when it should only be receiving time, not offering it.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.6527.3.1.2.38.3.2.1.9 snmpwalk -v2c -c public <target> TIMETRA-NTP-MIB::tmnxNtpPeersMode
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.9.1 snmpget -v2c -c public <target> TIMETRA-NTP-MIB::tmnxNtpPeersMode.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::tmnxNtpPeersMode 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.9 | tmnxNtpPeersMode | TIMETRA-NTP-MIB |