Smarts NPM: Switch is not being discovered into BGP topology; BGPPeerLocalPort and BGPPeerIdentifier values both have an IP address of 0.0.0.0

Products

• VMware Smart Assurance

Issue/Introduction

Symptoms:




Switch is not being discovered in Smarts NPM BGP topology

BGPPeerLocalPort and BGPPeerIdentifier values in Smarts NPM BGP topology both have an IP address of 0.0.0.0 from a walk of the device as in the following example (where x.x.x.x is the index value):

.1.3.6.1.2.1.15.3.1.1.x.x.x.x: 0.0.0.0

.1.3.6.1.2.1.15.3.1.5.x.x.x.x: 0.0.0.0

Environment

VMware Smart Assurance - SMARTS

Cause

This is a local configuration issue. The following MIB objects identify BGP availability on a device.

BGPPeerIdentifier
.1.3.6.1.2.1.15.3.1.1.x.x.x.2: x.x.x.3   
 OID                             index    : Peer IP

BGPPeerLocalPort 

.1.3.6.1.2.1.15.3.1.5.x.x.x.2: x.x.x.4

  OID                            index    : local IP

The pair with the same index number x.x.x.2 will describe a BGP session between the two devices with IP x.x.x.3 and x.x.x.4. The second OID (BGPPeerLocalPort) which identifies the IP address where BGP is configured locally on the system.  

Resolution

To resolve this issue, you must resolve the local configuration issue on the device.