NSX-T Federation Global Tier0 realization error: The requested object could not be found

Products

• VMware NSX

Issue/Introduction

• You are running NSX Federated environment version 3.1.3.x or 3.2.x.
• A Tier 0 Logical router deployed from the Global Manager (GM), spanning a Local Manager (LM) has realization error on the LM:

The requested object : /global-infra/sites/<site>/enforcement-points/default/edge-clusters/########-####-####-####-############/edge-nodes/2 could not be found. Object identifiers are case sensitive.

• On the LM, /var/log/syslog shows the following error:

ERROR providerTaskExecutor-81 PolicyServiceImpl 4536 POLICY [nsx@6876 comp="nsx-manager" errorCode="PM500012" level="ERROR" subcomp="manager"] Entity /global-infra/sites/<site>/enforcement-points/default/edge-clusters/########-####-####-####-############/edge-nodes/2 not found

Environment

VMware NSX-T Data Center 3.x

Cause

• In an NSX Federation environment, if you create a Tier0 Gateway on the GM with uplinks, the GM assigns one index per edge node path which is used for the Tier0 uplinks.
• Later if the user deletes that uplink and the edge node is no longer in use, the GM Tier0 configuration object will still have that path which can later lead to T0 realization error on LM.

Resolution

This issue is resolved in NSX 3.2.4/4.1.2/4.2.0

The issue is partially resolved in NSX 3.2.3 as the fix prevents the issue from occurring but does NOT automatically clean up any stale entries that might already be there. Hence, a workaround will still need to be implemented to remediate the issue in this NSX version.

Workaround:
Please open a support request with Broadcom Support and refer to this KB article for a workaround