BGP Peer table is incorrect on some Cisco ISR devices in Spectrum
search cancel

BGP Peer table is incorrect on some Cisco ISR devices in Spectrum


Article ID: 245893


Updated On:


CA Spectrum


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

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

For the CISCO ISR 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".


Release : 21.2

Component : Spectrum Discovery


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 in 10.4.3 so that if the device supports the CISCO-BGP4-MIB (and responds to attribute cbgpPeer2LocalIdentifier with oid 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 Spectrum will not create the original BGP4_App model.  It will only create the CiscoBGP4_App model.


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.  CiscoBGP4 mib     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. 

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


Additional Information

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

Model Type Editor