[External] - HCX Renaming or editing NSX-T backed HCX Network Extensions causes the segments to become connected

Products

• VMware HCX
• VMware NSX Networking

Issue/Introduction

Symptoms:
•    HCX Network Extension without Mobility Optimized Networking creates a disconnected segment.  
•    If the HCX Network Extensions are renamed or edited, the network becomes connected erroneously.

Environment

VMware NSX-T Data Center 2.x
VMware NSX-T Data Center
VMware NSX-T Data Center 2.5.x

Cause

•    The NSX-T Segment User Interface passes the connectivity status ON, even when the network is originally Isolated/Disconnected. 

Resolution

The segments created by HCX Network Extensions in environments using NSX-T 2.5.1 or older should not be renamed or edited with the NSX-T Segment interfaces.  
As workaround, use GET API to retrieve the segment, modify the payload and PATCH or PUT to update. Do not use PATCH with partial partial payload.
 
•    This issue is resolved in NSX-T 2.5.2 
•    This issues is resolved in NSX-T 3.0.0

Note: HCX Network Extension to NSX-T backed SDDCs in VMware Cloud on AWS automatically adjust the Segment Profile to allow DHCP requests.