Tier-0 system prefix lists do no match the configured value.

Products

• VMware NSX

Issue/Introduction

Symptoms:

• System prefix lists on a newly created Tier-0 do no match the configured value.
• There was a Tier-0 with the same name in the past and it was deleted.
• The new Tier-0 system prefix list has the old deleted Tier-0 values.

Environment

VMware NSX-T Data Center

Cause

When a Tier-0 is deleted, the entry in corfu GenericPolicyRealizedResource (GPRR) table is not deleted but remains, so when a Tier-0 is created again with the same name, the old GPRR entry is referenced and the new Tier0's system prefix list values are not reflected as configured.

Resolution

This issue is resolved in NSX-T 3.2.3 and NSX 4.1.1.

Workaround:
If you believe you have encountered this issue and are unable to upgrade, please open a support request with Broadcom Support NSX-T GSS and refer to this KB article.
For more information, see Creating and managing Broadcom support cases.

Additional Information

Impact/Risks:
Data plane communication can be impacted if a route map is created on the Tier-0 using the system prefix list.