We did not receive an alarm for a BGP Failure on an ASR router.
#sh logg | i May 17.*BGP.*xxx.xxx.xxx.xxx
May 17 15:10:31 GMT: %BGP-3-NOTIFICATION: sent to neighbor xxx.xxx.xxx.xxx 4/0 (hold time expired) 0 bytes
May 17 15:10:31 GMT: %BGP-5-NBR_RESET: Neighbor xxx.xxx.xxx.xxx reset (BGP Notification sent)
May 17 15:10:31 GMT: %BGP-5-ADJCHANGE: neighbor xxx.xxx.xxx.xxx vpn vrf device Down BGP Notification sent
May 17 15:10:31 GMT: %BGP_SESSION-5-ADJCHANGE: neighbor xxx.xxx.xxx.xxx IPv4 Unicast vpn vrf device topology base removed from session BGP Notification sent
May 17 15:13:55 GMT: %BGP-5-ADJCHANGE: neighbor xxx.xxx.xxx.xxx vpn vrf device Up
Release : Any
Component: Events and Alarms
The device is configured to send BGP traps to Spectrum. The AlertMap file for processing BGP traps is located in the $SPECROOT/SS/CsVendor/Ctron_SNMP_Rtr/BGP4_App directory. Because it is located in this directory, the device model MUST have an associated BGP4_App model to process the BGP traps.
The model in this case does not have an associated BGP4_App model associated.
To resolve this issue, copy the contents of the $SPECROOT/SS/CsVendor/Ctron_SNMP_Rtr/BGP4_App/AlertMap file to the $SPECROOT/custom/Events/AlertMap file. This will make the BGP4 traps global for all model and does not require the BGP4_App model.
After copying the information, update the Event Configuration by doing the following:
- Log into OneClick as an ADMIN user
- Find and select the VNM model
- Click on the Information tab in the Component Detail panel
- Find and expand the SpectroSERVER Control subview
- Click on the Update Event Configuration button