Upgrade of NSX-T from version 3.2.3.x to 4.1.2.x, communication between the Overlay VM and DVPG VM via L2 bridging would get disrupted.

Products

• VMware NSX

Issue/Introduction

- Following upgrade of NSX-T from version 3.2.3.x to 4.1.2.x would disrupt the communication between Overlay VM and DVPG VM via L2 bridging.

- From the NSX Manager Logs : /var/log/proton/nsxapi.log:
2025-06-05T00:40:40.246Z  INFO providerTaskExecutor-1-15 GroupingObjectsEntityListener 86816 INVENTORY [nsx@6876 comp="nsx-manager" level="INFO" s2comp="grouping" subcomp="manager"] GroupingObjectsEntityListener : Start Grouping Framework received Event com.vmware.nsx.management.entitylistener.service.EntityEvent@543f79f4 for resource LogicalPort [id=4######1-8##c-4##e-b##4-e##########1, intentPath=/infra/segments/c######2-0##f-4##8-9##5-3##########9/ports/default:4######1-8##c-4##e-b##4-e##########1, logicalPortState=UP, ephemeral=false, logicalSwitchId=LogicalSwitch/7######c-9##6-4##e-a##8-4##########2, transportZoneId=TransportZone/6######f-6##0-4##c-8##1-1##########0, transportZoneType=OVERLAY, attachmentId=null, attachmentType=bridgeendpoint, internalPortAttachment=attachment_type: ATTACHMENT_TYPE_EDGE_BRIDGE_ENDPOINT

- Corfu table InternalLogicalPort would not contain attachmentId.

- Impacted Version: NSX-T 3.2.x, NSX-T 4.0.x, NSX-T 4.1.x, NSX-T 4.2.0

Environment

VMware NSX
VMware NSX-T Datacenter

Cause

During the time of upgrade, for BridgeEndpoint port, all of these -> attachmentId, attachmentType and internalPortAttachment are expected to be present, when the issue occurs no attachmentId in SegmentPort and SegmentPort intent is updated.

Resolution

This issue is resolved in NSX-T 4.2.1

Release notes of NSX-T 4.2.1 indicating the issue is resolved in this version:

Fixed Issue 3405848: Multiple NSX backed VLANs went down during the NSX Manger upgrade due to incorrect bridge configuration being pushed.

- Create a new bridge profile with the exact same configuration as the existing one.  
- Deleted existing profile from the segment  Applied the new profile to the segment  
- After applying the new segment profile the Edge instance would come up and the issue should be resolved.