BGP Peer table is incorrect on some Cisco devices in Spectrum

Products

Spectrum Network Observability

Issue/Introduction

The BGP Peer table is incorrect on some Cisco devices in Spectrum.

To force a Peer down I have to ask to network manager responsible to administer mentioned device

For the CISCO devices that show the correct BGP values, they use the application model "BGP4_App".

For those that don't, they use the "Cisco BGP4_App".

After performing Reconfigure Model command, the working models can switch to the "CiscoBGP4_App" and starts to display wrong value for "Remote Value".

Environment

All supported releases of DX NetOps Spectrum

Cause

Cisco started supporting the CISCO-BGP4-MIB mib in favor of the standard BGP4-Mib to add IPv6 BGP peer session monitoring.
Spectrum was updated so that if the device supports the CISCO-BGP4-MIB (and responds to attribute cbgpPeer2LocalIdentifier with oid 1.3.6.1.4.1.9.9.187.1.2.5.1.9) then a CiscoBGP4_App model will be created.

If the device does still support the old BGP4-Mib (and responds to attribute bgpLocalAs with oid 1.3.6.1.2.1.15.2.0) Spectrum will not create the original BGP4_App model. It will only create the CiscoBGP4_App model.

Resolution

If the information is incorrect in the CiscoBGP4 app, and the devices responds to both oids below, we can force Spectrum to prioritize the standard BGP4-Mib.

1.3.6.1.4.1.9.9.187.1.2.5.1.9 CiscoBGP4 mib

1.3.6.1.2.1.15.2 standard BGP4-Mib

To create BGP4_APP (standard BGP MIB) instead of CISCOBGP4_app (proprietary MIB).

1. From ModelTypeEditor (MTE);

change the Model_Precedence (0x00230010) attribute of CISCOBGP4_APP to 5 and save the catalog.
The higher the number for the precendence value will have precendence. BGP_4APP model precedence is 10.

2. Start SpectroServer

3. Delete all CISCOBGP4_app models and rediscover SNMP MIB (right click - Reconfiguration - Rediscover SNMP Mibs)

4. Now, you should see the BGP4 Peer Table with the expected remote addresses.

Additional Information

If you are not able to use MTE, you can utilize the "dbtool" utility which will process xml files into the SS db. This does require SpectroSERVER downtime.

Create a new file in the $SPECROOT/SS directory with an .xml extension. For example: change_cisco_bgp4.xml

The xml file changes the Cisco_BGP4app precedence from 20 to 5. In the file, put this and only this:

Save the file

Import the changes using dbtool:

1. Copy the mte xml file to the $SPECROOT/SS directory of the other SpectroSERVER system(s)
2. Log into the system as the user that owns the Spectrum installation
3. Shutdown the SpectroSERVER as normal
4. On Windows, open a bash shell by running "bash -login", on linux use a standard shell
5. cd to the $SPECROOT/SS directory
6. Run the following command where <XML> is the name of mte xml file to import::

../SS-Tools/dbtool import <XML>

7. Start the SS

8. Delete all CISCOBGP4_app models and rediscover SNMP MIB (right click - Reconfiguration - Rediscover SNMP Mibs)

9. Now you should see the BGP4 Peer Table with the expected remote addresses.

Here is how both the apps look in a locator search.