NSX-T logical router interface created in Global Manager (GM) is not to realized on Local Manager (LM) edge node

Products

• VMware NSX

Issue/Introduction

Symptoms:

• You are running NSX-T Federation.
• This environment has been upgraded in the past and was on NSX-T versions 3.0.x or 3.1.x.
• You recently upgraded to NSX-T 3.2.x or 4.x.
• Creating a interface for a logical router on the GM which spans a LM, does not get realized on the edge node of the LM.
• In the LM log /var/log/proton/nsxapi.log we see the interface is received from the GM and is SUCCESS:

INFO policyProviderTaskScheduler-9 ConsolidatedRealizedStateServiceImpl 4306 POLICY [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Updated consolidated state for intentPath:/global-infra/tier-0s/T0-LR01/locale-services/default/interfaces/T0-LR01-int1 to:SUCCESS

• We then see a NULL Pointer Exception (NPE) for the logical router port creation:

ERROR workerTaskExecutor-5 EdgeWorkItemExceptionAspect 4297 - [nsx@6876 comp="nsx-manager" errorCode="MP11268" level="ERROR" subcomp="manager"] Failed to process work-items [WorkItem{identifier=LrPort/<PORT_UUID>, Timestamp{epoch=156, address=2583700354}}] of lr LogicalRouter/<Logical-Router-UUID> by method processLrLrpWorkItems
java.lang.NullPointerException: null
at com.vmware.nsx.management.edge.publish.worker.LrLrpCCPPublisher.handleLrLrpContainer(LrLrpCCPPublisher.java:780) ~[?:?]

• New logical routers created in the upgraded version 3.2.x or 4.x are ok and you are able to create a new logical router interface.

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Environment

VMware NSX-T Data Center
VMware NSX-T Data Center 3.x

Cause

NSX-T 3.2.0 onwards uses a new data structure. During the migration from 3.0.x and 3.1.x to 3.2.x, there was a missing mapping for the Federation flag for the logical router.
This occurs when the logical router was only spanning 1 site, the Federation mapping is not added.
NSX-T 3.2 onwards, expects the mapping to be there, if not, it results in a NPE, as seen above.

Resolution

This issue is resolved in NSX-T Data center 3.2.3 and VMware NSX 4.1.0

Workaround:

• If you believe you have encountered this issue, please open a support request with Broadcom Support and refer to this KB article.