Portgroup names with specific pattern translate into single logical segment during migration from VDS to N-VDS

Products

• VMware Cloud Foundation

Issue/Introduction

Symptoms:

• All the vmkernels (mgmt, vsan, vmotion) are connected to single logical segment in N-VDS. This happens when portgroup names given have the same suffix. 
• In the example below, each end with "-Cluster":

SDDC-DPortGroup-Mgmt-Cluster
SDDC-DPortGroup-VSAN-Cluster
SDDC-DPortGroup-vMotion-Cluster

• These get translated to same logical segment, which is "ls-vi-vcenter-1-cluster2-cluster" in the example above.

Environment

VMware Cloud Foundation 3.10.x

Resolution

This issue will be fixed in a future 3.x release.

Workaround:
To workaround this, it is required to create separate segments for VSAN and VMOTION and move the respective vmkernels over. Please use the the steps to perform this workaround:

1. Rename management logical segment (currently created) to end with "mgmt". From the example above "ls-vi-vcenter-1-cluster2-cluster" will become "ls-vi-vcenter-1-cluster2-mgmt"
2. Create new logical segments for vMotion and vSAN. Add the required respective VLAN ID, and choose VLAN Transport Zone. Following the example above create the below mentioned logical segments:

ls-vi-vcenter-1-cluster2-vmotion
ls-vi-vcenter-1-cluster2-vsan

3. Find the cluster Tranport Node Profile (TNP).
4. Modify the TNP to have vmkernels on newly created vSAN and vMotion logical segments. Map the vmkernels as below:

vmk1: ls-vi-vcenter-1-cluster2-vmotion
vmk2: ls-vi-vcenter-1-cluster2-vsan

5. Apply the TNP the cluster.
6. Detach the TNP from the cluster.
7. From the vCenter Web Client, confirm that the vmkernels are on newly create segments.