This article describes VLAN and TRUNK MODE configuration concepts of VST.
Note: VMware recommends utilizing VLAN technology to establish dedicated subnets for ESX/ESXi management, VMotion, and iSCSI network traffic.
Only allowing through VLAN traffic on physical switch ports connecting to ESX reduces TCP/IP overhead. Native VLANs do not tag the out going VLAN packets toward ESX NICs and if the same VLAN ID is used to configure the vSwitch port group, the vSwitch drops any packet that is not tagged for it, causing the connection to fail. Unnecessary VLAN traffic on a TRUNK port that connects to ESX can cause major performance issues.
Note: Do not use the Native VLAN ID of a physical switch as a VLAN on ESX/ESXi portgroups.
Symptoms:
Case1
When testing network connection using the ping command, the response fails with the following nodes:
- Gateway IP address
- VLAN gateway IP address
- Host on the same subnet or other subnets are not able to ping each other
Case2
Traffic doesn't go through for sometime during ESXi boot-up, however it later normalizes
From vmkernel:
2021-07-29T13:09:36.314Z cpu10:2097715)TeamCheck: NTCCheckResult:962: Please check connectivity on DvsPortset-0!
2021-07-29T13:10:36.315Z cpu10:2097715)TeamCheck: NTCCheckResult:962: Please check connectivity on DvsPortset-0!
2021-07-29T13:11:36.315Z cpu10:2097715)TeamCheck: NTCCheckResult:962: Please check connectivity on DvsPortset-0!