BGP4-V2-MIB-JUNIPER :: jnxBgpM2CfgPeerError

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsBGP4-V2-MIB-JUNIPERjnxBgpM2CfgPeerError

jnxBgpM2CfgPeerError

Module: BGP4-V2-MIB-JUNIPER

OID (symbolic): BGP4-V2-MIB-JUNIPER::jnxBgpM2CfgPeerError

OID (numeric): 1.3.6.1.4.1.2636.5.1.1.2.8.3.1.11

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: This value indicates the current error status of the row denoting the configured error status.

If this row is still under creation (has not been activated jnxBgpM2CfgPeerRowEntryStatus), then this instance will be set to not-activated (1).

At the point that the row is activated, jnxBgpM2CfgPeerError will reflect the error status of the row data itself. If there is another session already activated with the same local and remote addresses as denoted by {jnxBgpM2CfgPeerLocalAddrType, jnxBgpM2CfgPeerLocalAddr, jnxBgpM2CfgPeerRemoteAddr, jnxBgpM2CfgPeerRemotePort}, then the value of this will be set to err-duplicate-peering-session (2).

If this row is associated with a peer session whose initialization has been attempted, the value will be set to activated (3) (and, jnxBgpM2PeerCfgPeerEntry will be set to the row instance of the entry in the jnxBgpM2PeerTable which reflects the state of the peering session).

Note that this object only reflects the error as a function of the attempted activation of this row as containing data for a bgp peering session. The actual state of the session at the point of any protocol exchange or session state machine initiation is reflected in the jnxBgpM2PeerTable row instance (as reflected through jnxBgpM2CfgPeerPeerEntry) associated with this row instance.

What is jnxBgpM2CfgPeerError?

This read-only field reports the activation status of the peer configuration: unknown(0)=indeterminate, notActivated(1)=still under creation, errDuplicatePeeringSession(2)=conflict with existing peer, activated(3)=successfully activated. Helps diagnose configuration problems. Example: if this shows errDuplicatePeeringSession, two peer rows are trying to use the same local/remote address pair, which is invalid.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2636.5.1.1.2.8.3.1.11
snmpwalk -v2c -c public <target> BGP4-V2-MIB-JUNIPER::jnxBgpM2CfgPeerError

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.2636.5.1.1.2.8.3.1.11.1
snmpget -v2c -c public <target> BGP4-V2-MIB-JUNIPER::jnxBgpM2CfgPeerError.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::jnxBgpM2CfgPeerError 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 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.2636juniperMIBJUNIPER-SMI
1.3.6.1.4.1.2636.5jnxExperimentJUNIPER-EXPERIMENT-MIB
1.3.6.1.4.1.2636.5.1jnxBgpM2ExperimentJUNIPER-EXPERIMENT-MIB
Numeric OIDNameModule
1.3.6.1.4.1.2636.5.1.1jnxBgpM2BGP4-V2-MIB-JUNIPER
1.3.6.1.4.1.2636.5.1.1.2jnxBgpM2PeerBGP4-V2-MIB-JUNIPER
1.3.6.1.4.1.2636.5.1.1.2.8jnxBgpM2PeerConfigurationBGP4-V2-MIB-JUNIPER
1.3.6.1.4.1.2636.5.1.1.2.8.3jnxBgpM2CfgPeerTableBGP4-V2-MIB-JUNIPER
1.3.6.1.4.1.2636.5.1.1.2.8.3.1jnxBgpM2CfgPeerEntryBGP4-V2-MIB-JUNIPER
1.3.6.1.4.1.2636.5.1.1.2.8.3.1.11jnxBgpM2CfgPeerErrorBGP4-V2-MIB-JUNIPER