Aggregate routes are deleted from routing table when deleting static route for same subnet

Products

• VMware NSX

Issue/Introduction

• An aggregate route is configured under BGP configuration when a static route for the same subnet is already present in the routing table.
• When the original static route is deleted, aggregate route also gets deleted, causing an outage for the more specific routes from within the aggregate route which are present in the routing table but are not being advertised to the BGP peers.
• This issue can occur if a Tier1 component is removed and its subnet matches an aggregate route configured in Tier0's BGP.

Environment

VMware NSX 3.2.x, 4.1.x, 4.2.x

Cause

Aggregate route installation fails when an aggregate route is configured and static route for the same subnet is already present in the routing table.

Resolution

This issue will be fixed in a future NSX version.

Workaround

- Remove the static route
- Reconfigure (remove and then re-add) the aggregate route under BGP configuration

 

If you believe you have encountered this issue and are unable to implement the workaround, please open a support case with Broadcom Support and refer to this KB article.
For more information, see Creating and managing Broadcom support cases.

Provide:

• NSX Manager support bundle
• Edge support bundle

Handling Log Bundles for offline review with Broadcom support.

• Collect Support Bundles for Troubleshooting NSX-T
• Uploading files to cases on the Broadcom Support Portal