Smarts NPM for BGP: What MIB and OIDs are used to discover devices running the Border Gateway Protocol?

Products

• VMware Smart Assurance

Environment

VMware Smart Assurance - SMARTS

Resolution

What MIB and OIDs are used in Smarts Network Protocol Manager (Smarts NPM) for BGP discovery?
What MIB and OIDs are required by Smarts NPM for BGP to discover devices running the Border Gateway Protocol?

What MIB is required in Smarts NPM for BGP discovery?




Discovery of a device in Smarts NPM for BGP is based on the presence of the SNMP BGP MIB. The following OIDs in this MIB are used:

bgpVersion         .1.3.6.1.2.1.15.1
bgpIdentifier      .1.3.6.1.2.1.15.4
bgpLocalAs         .1.3.6.1.2.1.15.2
bgpPeerIdentifier  .1.3.6.1.2.1.15.3.1.1
bgpPeerLocalAddr   .1.3.6.1.2.1.15.3.1.5

Smarts NPM for BGP discovery process and requirements
Smarts Availability Manager (Smarts AM) creates the initial BGP topology by querying a device's SNMP agent for MIB value bgpPeerLocalAddr (.1.3.6.1.2.1.15.3.1.5). If the bgpPeerLocalAddr OID exists for the device, Smarts AM will create a BGP service element on that device. Smarts NPM for BGP then imports this initial BGP topology from Smarts IP before doing further BGP discovery. A device will not be discovered by Smarts NPM for BGP unless its SNMP agent has the MIB value for the bgpPeerLocalAddr OID specified, even it is certified for discovery in Smarts IP.