vSAN storage traffic isolated to VDS with vmnic0/1 uplinks.

Products

• VMware Cloud Foundation

Issue/Introduction

This article will let the customers know about this change in advance , so that customer can plan backend network configuration accordingly.

Symptoms:

SDDC Manager UI Switch Pre-configured Profiles Physical NIC association issue with VDS numbering

Detail description:

Step-:1 Host Selection:

Step-2: Switch Configuration Profile section for Traffic Isolation:

Step-3: The profiles Storage Traffic Selection, Storage Traffic, and NSX Traffic Separation show VDS-02 getting associated with physical NICs vmnic0,vmnic1 for VSAN storage isolation.

Storage Traffic Separation:


NSX Traffic Separation:

 

Environment

VMware Cloud Foundation 5.1.1
VMware Cloud Foundation 5.1.x
VMware Cloud foundation 5.x

Cause

Due to the backend logic issue, the numbering of physical NICs is out of sync with VDS numbering. This will be fixed in future release.

Resolution

VMware is aware of this issue and working to resolve this in a future release.

Workaround:

The user has multiple options to change NIC association with VDS:

Option-1:

1. Use the default profile which contains a single VDS and choose to create the second VDS and associate NICs and networks

Please follow the below steps:

• Step-1: Click on Change Selection:

• Step-2: Choose Create Custom Switch Configuration

• Step-3: Choose Storage Traffic Separation/ Storage Traffic and NSX Traffic Separation

• Step-4: if any free NICs available like vmnic4,vminic5 , then assign the free nics VDS-02 and change physical NICS of VDS-01 with vmnic0,vmnic1 and edit VDS-02 and change physical NICs vmnic2,vmnic3

 

• Step-5: if no free NICs are available then Delete VDS-02 with vmnic0,vmnic1

 

• Step-6: Edit VDS-01 with vminic2,vmnic3 and change to vmnic0,vmnic1

 

• Step-7: Create a VDS-02 with NICs vmnic1, vmnic2