It seems the network segmentation 2.1 doesn’t support the isolation physically between the backplane and management.
So, it tries to isolate logically following this procedure.
ISOLATING THE BACKPLANE TRAFFIC LOGICALLY ON AN EXISTING CLUSTER (VLAN-BASED SEGMENTATION ONLY)
AOS5.15.1 / ESXi 6.7u3
Standard vSwitch, vSwitch0
Port Gourp: Backplane Network, CVM Backplane Network (for CVM)
it doesn’t recognize any port groups.
The procedure doesn’t mention about the vSwitch0 or port group condition.
Is there any information of this?
Best answer by lk541View original
From what you are doing I feel like this is the part of the guide you should be following Isolating the Backplane Traffic Physically on an Existing Cluster:
Let me know if that is what you were looking for.
The instructions on how to configure the vSwitch on ESXi can be found on the VMware documentations portal. For example, Create a vSphere Standard Switch (VMware vSphere 6.7)
I’m not sure why you believe that physical isolation isn’t supported.
From the post you refer to:
Maybe I am misunderstanding or misreading something? If so, my apologies in advance.
Thank you for the update.
It was settled.
This procedures works and could be to segment the backplane traffic physically.
ISOLATING THE BACKPLANE TRAFFIC PHYSICALLY ON AN EXISTING CLUSTER
This is also mentioned in AOS5.11.1 release notes.
NEW AND UPDATED FEATURES | AOS 5.11.1
Physical Backplane Segmentation
You can physically isolate the backplane traffic (intra cluster traffic) from the management traffic (Prism, SSH, SNMP) in to a separate VNIC on the CVM and using a dedicated virtual network that has its own physical NICs. This type of segmentation therefore offers true physical separation of the backplane traffic from the management traffic.