BGP Down alarm reported on NSX-T Edges nodes even though BGP connections remain as established and Up

Products

• VMware NSX

Issue/Introduction

• Running NSX-T 3.1.2
• Using the command 'get bgp neighbor summary' on the Edge logical router, indicates the BGP relationship is up and established:

169.254.0.130 4221215723 Estab 01w5d03h NC 1048811 1048809 101 101
169.254.0.131 4221215723 Estab 01w5d03h NC 1048807 1048812 101 101

• No evidence in the Edge syslogs and frr logs that the BGP relationship went down at the time reported by the alarm.
• The BGP alarm does not get resolved and remains as open.

Environment

VMware NSX

Cause

The BGP session state was not getting relayed to RCPM (Routing Control Plane Manager), which caused these alarms to be generated.

Resolution

This issue is resolved in NSX-T 3.2.0.

Workaround:

1. Place the edge node in maintenance mode and bringing it back out of maintenance mode.
2. Manually resolve the stale alarm.

Additional Information

NSX 4.x have implemented additional fixes addressing stale BGP/BFD alarms, these fixes are not available in NSX-T 3.2.x releases.