After discovering and creating the BGP topology objects in its repository, Network Protocol Manager for BGP monitors the status of the BGP objects by periodically establishing SNMP sessions to the managed devices and polling the BGP4 MIB objects that are listed in Instrumentation MIB objects polled by NPM for BGP (IPv4).

Table 1. Instrumentation MIB objects polled by NPM for BGP (IPv4)

MIB object

OID

Description

Module

bgpPeerIdentifier

.1.3.6.1.2.1.15.3.1.1

BGP Identifier of this entry’s BGP peer.

BGP4 MIB

bgpPeerState

.1.3.6.1.2.1.15.3.1.2

BGP peer connection state.

BGP4 MIB

bgpPeerAdminStatus

.1.3.6.1.2.1.15.3.1.3

BGP peer administrative status.

BGP4 MIB

bgpPeerNegotiatedVersion

.1.3.6.1.2.1.15.3.1.4

Negotiated version of BGP that is running between two BGP peers.

BGP4 MIB

bgpPeerLocalAddr

.1.3.6.1.2.1.15.3.1.5

Local IP address of this entry’s BGP connection.

BGP4 MIB

bgpPeerLocalPort

.1.3.6.1.2.1.15.3.1.6

Local port for the TCP connection between the BGP peers.

BGP4 MIB

bgpPeerRemotePort

.1.3.6.1.2.1.15.3.1.8

Remote port for the TCP connection between the BGP peers.

BGP4 MIB

bgpPeerRemoteAS

.1.3.6.1.2.1.15.3.1.9

Remote autonomous system (AS) number.

BGP4 MIB

bgpPeerInUpdates

.1.3.6.1.2.1.15.3.1.10

Number of BGP UPDATE messages received on this connection. This object should be initialized to zero (0) when the connection is established.

BGP4 MIB

bgpPeerLastError

.1.3.6.1.2.1.15.3.1.14

Last error code and subcode seen by this BGP peer on this connection. If no error has occurred, this field is zero (0).

BGP4 MIB

Network Protocol Manager for BGP parses the SNMP response to obtain the status information, and then updates in real time the status of the appropriate BGP objects in its repository.