L2 extended segment naming convention changes after upgrading to HCX 4.11.3

Products

• VMware HCX

Issue/Introduction

• Pre-HCX 4.11.3: When extending a network named SOURCE_HCX_NETWORK, the L2 extended segment at the destination is created with a name similar to:
  

  L2E_SOURCE_HCX_NETWORK-<Network_Id>-<Resource_Id>

• HCX 4.11.3: When extending the same network, the L2 extended segment at the destination is created with a name similar to:
  

  L2E_SOURCE_HCX_NE-<Network_Id>-<Network_Hash>-<Resource_Id>

Environment

VMware HCX

Cause

In HCX 4.11.3, the naming convention specification for L2 extended destination segments was updated to include a hash value of up to 5 digits. As a result, the original network name portion within the destination segment name may appear truncated by up to 5 characters. In some cases, the <Resource_Id> portion may also be truncated by a few characters.

Resolution

This is the expected behavior by design. No action is required.