Nortel-MsCarrier-MscPassport-BgpMIB :: mscVrIpBgpPeerConnectionState

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › Nortel-MsCarrier-MscPassport-BgpMIB › mscVrIpBgpPeerConnectionState

mscVrIpBgpPeerConnectionState

Module: Nortel-MsCarrier-MscPassport-BgpMIB

OID (symbolic): Nortel-MsCarrier-MscPassport-BgpMIB::mscVrIpBgpPeerConnectionState

OID (numeric): 1.3.6.1.4.1.562.36.2.1.100.6.21.2.12.1.3

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: This attribute indicates the current state of this BGP peer connection. The meaning of each state is as follows: idle - it is the initial state of the BGP peer connection. Error events will also cause BGP peer connection to transit to the idle state. connect - BGP has initiated a TCP connection request to this peer, and waiting for reply from that peer. active - BGP is not initiating a TCP connection request to this peer, because TCP connection failed and is waiting for connection retry time-out. openSent - a TCP connection to this peer has been established, but the OPEN message has not been successfully exchanged. openConfirm - OPEN message has been successfully exchanged with this peer, but the first KEEPALIVE message has not been received from that peer. established - the first KEEPALIVE message has been received from this peer, which means this BGP peer connection has been established. See RFC 1771 for a detailed description of BGP state transitions.

What is mscVrIpBgpPeerConnectionState?

Tracks this BGP peer session's progress through the RFC 1771 finite-state machine: idle, connect, active, openSent, openConfirm, and finally established once the first KEEPALIVE is received. An admin reads this to diagnose why a peer session isn't coming up, e.g. stuck at connect means the TCP handshake to the peer isn't completing.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.562.36.2.1.100.6.21.2.12.1.3
snmpwalk -v2c -c public <target> Nortel-MsCarrier-MscPassport-BgpMIB::mscVrIpBgpPeerConnectionState

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.562.36.2.1.100.6.21.2.12.1.3.1
snmpget -v2c -c public <target> Nortel-MsCarrier-MscPassport-BgpMIB::mscVrIpBgpPeerConnectionState.1

Start monitoring Nortel MsCarrier MscPassport switch/router (BGP) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the Nortel-MsCarrier-MscPassport-BgpMIB::mscVrIpBgpPeerConnectionState OID value, configure state conditions and alerts, and monitor any Nortel MsCarrier MscPassport switch/router (BGP) from a single console.

OID Breakdown

Upper-level ancestors (12 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.562nortelCPM-NORTEL-MIB
1.3.6.1.4.1.562.36msCarrierNortel-MsCarrier-MscPassport-UsefulDefinitionsMIB
1.3.6.1.4.1.562.36.2mscPassportNortel-MsCarrier-MscPassport-UsefulDefinitionsMIB
1.3.6.1.4.1.562.36.2.1mscComponentsNortel-MsCarrier-MscPassport-UsefulDefinitionsMIB
1.3.6.1.4.1.562.36.2.1.100mscVrNortel-MsCarrier-MscPassport-VirtualRouterMIB
1.3.6.1.4.1.562.36.2.1.100.6mscVrIpNortel-MsCarrier-MscPassport-IpMIB
Numeric OIDNameModule
1.3.6.1.4.1.562.36.2.1.100.6.21mscVrIpBgpNortel-MsCarrier-MscPassport-BgpMIB
1.3.6.1.4.1.562.36.2.1.100.6.21.2mscVrIpBgpPeerNortel-MsCarrier-MscPassport-BgpMIB
1.3.6.1.4.1.562.36.2.1.100.6.21.2.12mscVrIpBgpPeerOperTableNortel-MsCarrier-MscPassport-BgpMIB
1.3.6.1.4.1.562.36.2.1.100.6.21.2.12.1mscVrIpBgpPeerOperEntryNortel-MsCarrier-MscPassport-BgpMIB
1.3.6.1.4.1.562.36.2.1.100.6.21.2.12.1.3mscVrIpBgpPeerConnectionStateNortel-MsCarrier-MscPassport-BgpMIB