VMware Cloud Community
Tech15
Contributor
Contributor

vSwitch Standard Access Port To VST VLAN Questions

I’m reaching out to see if there are any ideas on how to best handle this situation I have found some knowledge base articles from VMware regarding network configuration, specifically VST VLAN tagging. I have a vCenter Server appliance installed on a Dell server ESXi host as I would like to take advantage of updates and other functionality that a standalone ESXi host doesn’t seem to offer. Also for expansion for a secondary server that will be for a secondary of the DNS / DHCP VM’s.

Here’s the scenario:

  1. ESXi 7 host has a vCenter Server appliance installed and managing this host.
  2. I’m planning on having multiple tagged VLAN’s available on the physical managed switch this ESXi host is connected to so various VM’s can be separated into the appropriate VLAN after adding additional vSwitches.
  3. As of now the Management Network (VMKernal) and the VM Network don’t have a VLAN ID configured in VSphere.
  4. Both the Management Network and VM Network terminate to the Dell server network port.
  5. Standard vSwitch
  6. Configuration as of now is using a switch access port connected to the Dell server.

Here are the order of configuration changes to allow VST tagging on this host I was thinking about:

  1. From vSphere / select host / Configure / Networking / Virtual Switches / Edit VM Network – Change the VLAN ID to match the managed switch tagged VLAN
  2. From the Dell server iDRAC / Virtual Console  / select the ESXi host / Configure Management Network - Change the VLAN ID to match the managed switch tagged VLAN
  3. From the managed switch tag the interface connected to the Dell server per: https://kb.vmware.com/s/article/1004074

Does this order seem correct or ideas? I don't want to make a wrong move and not be able regain connectivity to the VM's already configured.

ESXi_Management_VLAN_iDRAC.JPGvSphere_Client_Standard_vSwitch.JPG

Reply
0 Kudos
2 Replies
DavoudTeimouri
Virtuoso
Virtuoso

The instruction is correct. You need to apply trunk configuration on physical switch port and then apply the configuration on ESXi.

But you lose network connectivity during these changes.

-------------------------------------------------------------------------------------
Davoud Teimouri - https://www.teimouri.net - Twitter: @davoud_teimouri Facebook: https://www.facebook.com/teimouri.net/
Tech15
Contributor
Contributor

I had to modify the steps slightly to complete the task of VST configuration. Here are the steps used:

  1. From vSphere disconnect the ESXi host (otherwise an error message was presented when attempting to set VLAN ID 600 on the VM Network). I'm assuming due to the vServer appliance being on this host
  2. Login to the ESXi host / vSwitch / Edit VM Network / Change the VLAN ID to match the managed switch tagged VLAN.
  3. From the Dell server iDRAC / Virtual Console  / select the ESXi host / Configure Management Network - Change the VLAN ID to match the managed switch tagged VLAN. Could probably do this from within the ESXi host - vSwitch settings, although I thought that using iDRAC would be best in case I needed to back out the VST changes.
  4. From the managed switch tag the interface connected to the Dell server per: https://kb.vmware.com/s/article/1004074
  5. From vSphere / select host / Delete (Otherwise the settings made on the ESXi host directly would of been overridden per the vSphere warning message if selecting reconnect host option).
  6. From vSphere / add host to inventory / step through wizard to add back the ESXi host.

    Best practice here seems to be having a separate server that hosts vSphere separate from any ESXi hosts. Unfortunately this was not possible with our single server.
Reply
0 Kudos