T0 or T1 remains in Failed state even after the alert causing configuration was corrected

Products

• VMware NSX

Issue/Introduction

Tier0 or Tier1 remains in a failed state with either of the below error messages:

• "Subnet should not overlap with other logical router port of same logical router"
• "LR port IP overlaps with NAT service(s)"

Log location: /var/log/proton/nsxapi.log

Impact to the customer: No data path impact but the stale alarm shows on the Tier-0 or Tier-1 with a failed status

Environment

NSX 4.1

 

Cause

Error on the UI is due to the stale entry of type "-dlrp" object type in 'GenericPolicyRealizedResource' Corfu table which had been created during the first time when the segment realization failed. But that object not getting cleared even if the overlapping configuration has been corrected. 

Resolution

This issue is resolved in VMware NSX 4.2.0

 

Workaround

If this issue is encountered on a VMware NSX version prior to 4.2, please open a case with Broadcom Support for assistance. 

Additional Information