The following table displays information about
the BGP4v2 per-peer session management information group. Use the show ip bgp neighborid command to
display the BGP4v2 per-peer session management information.
Name, OID, and syntax
Access
Description
bgp4V2PeerTable
1.3.6.1.4.1.1991.3.5.1.1.2
None
The BGP4v2 per-peer table. The table contains one entry per BGP peer and the information
about the connections with the BGP peers.
bgp4V2PeerInstance
1.3.6.1.4.1.1991.3.5.1.1.2.1.1
Syntax: Unsigned32
None
Specifies the routing instance index. Some of the BGP implementations permit the creation
of multiple instances of a BGP routing process. The implementations that do not support
multiple routing instances, return 1 for this object.
The VRF index is used to identify the peer instance. The VRF index is a zero-based
index.
bgp4V2PeerLocalAddrType
1.3.6.1.4.1.1991.3.5.1.1.2.1.2
Syntax:
InetAddressType
None
Specifies the address family of a local-end peering session.
The following address types are supported:
ipv4(1)
ipv6(2)
bgp4V2PeerLocalAddr
1.3.6.1.4.1.1991.3.5.1.1.2.1.3
Syntax: InetAddress
None
Specifies the local IP address of the received BGP connection.
bgp4V2PeerRemoteAddrType
1.3.6.1.4.1.1991.3.5.1.1.2.1.4
Syntax:
InetAddressType
None
Specifies the address family of a remote end peering session.
The following address types are supported:
ipv4(1)
ipv6(2)
bgp4V2PeerRemoteAddr
1.3.6.1.4.1.1991.3.5.1.1.2.1.5
Syntax: InetAddress
None
Specifies the remote IP address of the received BGP peer.
bgp4V2PeerLocalPort
1.3.6.1.4.1.1991.3.5.1.1.2.1.6
Syntax:
InetPortNumber
Read-only
Indicates the local port for the TCP connection between the BGP peers.
bgp4V2PeerLocalAs
1.3.6.1.4.1.1991.3.5.1.1.2.1.7
Syntax:
InetAutonomousSystemNumber
Read-only
Indicates a Autonomous System (AS) is the peering session that represents itself to
the remote peer.
Some implementations of BGP can represent itself as multiple autonomous systems.
bgp4V2PeerLocalIdentifier
1.3.6.1.4.1.1991.3.5.1.1.2.1.8
Syntax:
Bgp4V2IdentifierTC
Read-only
Specifies the BGP identifier of the local system for the peering session. It is required
that all the values of bgp4V2PeerLocalIdentifier and bgp4V2PeerInstance objects must
be identical.
bgp4V2PeerRemotePort
1.3.6.1.4.1.1991.3.5.1.1.2.1.9
Syntax:
InetPortNumber
Read-only
Specifies the remote port for the TCP connection between the BGP peers.
Note: The objects bgp4V2PeerLocalAddr, bgp4V2PeerLocalPort, bgp4V2PeerRemoteAddr, and bgp4V2PeerRemotePort
provides the appropriate references to the standard MIB TCP connection table or to
the IPv6 TCP MIB as referenced in RFC 4022.
bgp4V2PeerRemoteAs
1.3.6.1.4.1.1991.3.5.1.1.2.1.10
Syntax:
InetAutonomousSystemNumber
Read-only
Specifies the remote AS number received in the BGP OPEN message.
bgp4V2PeerRemoteIdentifier
1.3.6.1.4.1.1991.3.5.1.1.2.1.11
Syntax:
Bgp4V2IdentifierTC
Read-only
Specifies the BGP identifier of the received remote BGP peer.
The entry received must be 0.0.0.0 unless the bgp4V2PeerState is in the openconfirm(5)
or in established(6) state.
bgp4V2PeerAdminStatus
1.3.6.1.4.1.1991.3.5.1.1.2.1.12
Syntax: Integer
Read-only
Specifies whether the BGP finite state machine (FSM) for the remote peer is halted
or running, the BGP FSM for a remote peer is halted after processing a stop event.
Likewise, if in the running state after processing a start event.
The bgp4V2PeerState is in the idle state when the FSM is halted. Although, some extensions
such as Graceful Restart leaves the peer in the idle state with the FSM running.
halted(1)
running(2)
bgp4V2PeerState
1.3.6.1.4.1.1991.3.5.1.1.2.1.13
Syntax: Integer
Read-only
Indicates the BGP peer connection states:
idle(1)
connect(2)
active(3)
opensent(4)
openconfirm(5)
established(6)
bgp4V2PeerDescription
1.3.6.1.4.1.1991.3.5.1.1.2.1.14
Syntax:
SnmpAdminString
Read-only
Specifies a user-configured description identifying the peer. The object must contain
a description that is unique within the existing BGP instance for the peer.