Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


BGP Alarms on Provider Hubs

Starting in Release 6.3.0, CSO detects loss of BGP peering sessions between provider hubs connected through an IPVPN mesh. When a BGP neighborship between any of the hubs is down, an alarm is generated based on the syslog information of the hub device.

CSO uses the BGP Neighbor State Change syslog notification to generate or clear the alarm. If the syslog reports the state as Established, then CSO considers that the BGP peer is up. CSO considers that the BGP peer is down if the state changes to anything other than Established.

You can view the alarms on the Monitor > Alerts & Alarms > Alarms page. The alarm description includes information about the BGP peer, previous and new state, and AS number derived from the syslog notification. If the interface is down on the peering side, CSO waits for three consecutive hello packets to be dropped (around 180 seconds) before generating the alarm. If the interface is down on the hub side, then the alarm is generated immediately. The alarm is automatically cleared when the interface is up again and the BGP neighbor returns to the Established state. Note that you can view the alarms only at the global-level.

This alarm is supported only on provider hubs that are onboarded in CSO Release 6.3.0 and later releases. To enable this alarm on provider hub devices running a release prior to CSO 6.3.0, you must do the following:

  • Upgrade the release to CSO 6.3.0.

  • Upgrade the site to CSO 6.3.0.