Third party monitoring tools (like OpsRamp) doesn't show BGP neighbor down alarms while NSX alerts correctly
search cancel

Third party monitoring tools (like OpsRamp) doesn't show BGP neighbor down alarms while NSX alerts correctly

book

Article ID: 395794

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

- NSX Alarms show correctly the BGP neighbors when they go down, so NSX side everything looks fine

- Few of the 3rd party monitoring tools like OpsRamp, etc not showing the BGP neighbors being down when BGP neighbors are actually down on NSX

For example, NSX many show the following alarm:

In Router 9e#####-###-###-########, BGP neighbor 86######-###-###-########(#.#.#.#) is down

But in the monitoring tool it may just show the Router UUID (9e#####-###-###-########) has some issues but not relating to BGP neighbors

Environment

VMware NSX

 

Cause

There is no issue from NSX, but the monitoring tool need few changes to include the monitoring for BGP neighbor UUIDs

Resolution

- We can use this API to get the BGP details and its UUIDs: GET https://<nsx-manager>/policy/api/v1/infr/tier-0s//locale-services/default/bgp/neighbors

- We can also get the status of all the BGP neighbors from the given Tier 0: GET https://<nsx-manager>/policy/api/v1/infr/tier-0s//locale-services/default/bgp/neighbors/status

Reference API doc: https://vdc-download.vmware.com/vmwb-repository/dcr-public/8e2a4b1a-659f-4be6-a4f4-7ca42b04cb84/9a2c1372-7174-40f0-89d2-27615bfd5d08/api_includes/method_GetTier0BgpNeighborsStatus.html

- Based on this GET API result, monitoring tool need to configured so that it can monitor the correct BGP UUIDs and their status