BGP Down Alarm After Upgrading from Version 3.1.3.7 to 4.0.1.1

Products

• VMware NSX

Issue/Introduction

BGP Down Alarm Triggered After Upgrading from Version 3.1.3.7 to 4.0.1.1 for Inactive Idle BGP Peer

##.##.#.##                        6###0       Idle  never        NC  0       0       0      0
##.##.#.##                        6###0       Idle  never        NC  0       0       0      01

Cause

From the NSX perspective, it’s essential that every configured neighbor on the edge is active. If a BGP neighbor is not active, it indicates a potential issue that requires attention and may trigger an alarm

Resolution

If a BGP neighbor is not needed for a specific edge (i.e., the remote end won’t recognize this edge as a peer), we should refrain from configuring it