All MIBs › BGP4-V2-MIB-JUNIPER › jnxBgpM2PeerIndex
jnxBgpM2PeerIndex
Module: BGP4-V2-MIB-JUNIPER
OID (symbolic): BGP4-V2-MIB-JUNIPER::jnxBgpM2PeerIndex
OID (numeric): 1.3.6.1.4.1.2636.5.1.1.2.1.1.1.14
Node type: OBJECT-TYPE
Type: Unsigned32
Access: read-only
Description: This value is a unique index for the remote peer entry in the jnxBgpM2PeerTable. It is assigned by the agent at the point of creation of the jnxBgpM2PeerTable row entry. While its value is guaranteed to be unique at any time, it is otherwise opaque to the management application with respect to its value or the contiguity of jnxBgpM2PeerIndex row instance values across rows of the jnxBgpM2PeerTable. It is used to provide an index structure for other tables whose data is logically per-peer.
For explicitly configured peers, this value will remain consistent until this row is deleted by deleting the configured peers. Unconfigured peers will generate a monotonically increasing number when a BGP FSM is built to process the peering session. Values in the jnxBgpM2PeerTable and other tables utilizing jnxBgpM2PeerIndex are expected to remain in existence for an arbitrary time after the unconfigured peer has been deleted in order to allow management applications to extract useful management information for those peers. Thus, an unconfigured peer using the same indices as the jnxBgpM2PeerTable that comes up while this row still exists will re-utilize the same row.
What is jnxBgpM2PeerIndex?
This Unsigned32 is a unique index for the peer in the peer table, assigned by the agent at row creation. Example: an index of 5 uniquely identifies this peer within the table (non-contiguous indices are possible).
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2636.5.1.1.2.1.1.1.14 snmpwalk -v2c -c public <target> BGP4-V2-MIB-JUNIPER::jnxBgpM2PeerIndex
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.2636.5.1.1.2.1.1.1.14.1 snmpget -v2c -c public <target> BGP4-V2-MIB-JUNIPER::jnxBgpM2PeerIndex.1
Start monitoring Juniper Networks routers with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the BGP4-V2-MIB-JUNIPER::jnxBgpM2PeerIndex OID value, configure state conditions and alerts, and monitor any Juniper Networks routers from a single console.
OID Breakdown
Upper-level ancestors (9 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.2636 | juniperMIB | JUNIPER-SMI |
| 1.3.6.1.4.1.2636.5 | jnxExperiment | JUNIPER-EXPERIMENT-MIB |
| 1.3.6.1.4.1.2636.5.1 | jnxBgpM2Experiment | JUNIPER-EXPERIMENT-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.2636.5.1.1 | jnxBgpM2 | BGP4-V2-MIB-JUNIPER |
| 1.3.6.1.4.1.2636.5.1.1.2 | jnxBgpM2Peer | BGP4-V2-MIB-JUNIPER |
| 1.3.6.1.4.1.2636.5.1.1.2.1 | jnxBgpM2PeerData | BGP4-V2-MIB-JUNIPER |
| 1.3.6.1.4.1.2636.5.1.1.2.1.1 | jnxBgpM2PeerTable | BGP4-V2-MIB-JUNIPER |
| 1.3.6.1.4.1.2636.5.1.1.2.1.1.1 | jnxBgpM2PeerEntry | BGP4-V2-MIB-JUNIPER |
| 1.3.6.1.4.1.2636.5.1.1.2.1.1.1.14 | jnxBgpM2PeerIndex | BGP4-V2-MIB-JUNIPER |