You’ll get a list of all standard switches. We need to find an unclaimed port ID for vmnic0. esxcli network vswitch standard uplink remove –uplink-name=vmnic0 –vswitch-name=vSwitch1Īdd vmnic0 back to distributed vSwitch dvs-LAN-1. To remove a vmnic from a standard switch, issue this command. Logout from ESXI Shell and switch view to DCUI with +. You may now configure that NIC for management in the DCUI.
Now you have standard switch with one uplink (vmnic0). On April 9th VMware published the first ESXi 6.0 patch (see the ESXi Patch Tracker and KB2111976), and at the same time the Imageprofiles of both this patch and the ESXi 6.0 GA release appeared in the VMware Online Depot.Unfortunately they did not also upload all the ESXi 6.0 VIB packages at that time, but only the one that was updated with the first patch. vicfg-vswitch -Q vmnic0 -dvp 18 dvs-LAN-1 Add vmnic to standard switch esxcli network vswitch standard uplink add -uplink-name=vmnic0 -vswitch-name=vSwitch1 It is recommended to use the vicfg-vswitch command instead of esxcfg, which will become obsolte in the future.
In our example the command would be: esxcfg-vswitch -Q vmnic0 -V 18 dvs-LAN-1Īn alternate (modern) command is vicfg-vswitch (vSphere4 and later): vicfg-vswitch -Q -dvp Port ID of vmnic0 is 18 and name of the dvSwitch is dvs-LAN-1. In our example vmnic0 and vmnic1 are connected to the distributed vswitch. We need to unclaim a vmnic from the dvSwitch to use it with the new standard switch vSwitch1. Now, let’s have a look at our distributed vSwitches. esxcli network vswitch standard add -v vSwitch1. Select a vmnic to drop from the vdSwitch. Add a standard vswitch with name vSwitch1 (or any other non-existing name). There you’ll see all vmnics used as uplinks on that dvSwitch. You’ll get a long list with switch details, ports and connected clients. esxcli network vswitch standard add -v vSwitch1 Add new Standard SwitchĪdd a standard vswitch with name vSwitch1 (or any other non-existing name). Press + to access the shell and login as user root. On the right hand side you can see the current status of the ESXi Shell. In Troubleshooting section select “Enable ESXi Shell”. Login to DCUI console, select “Troubleshooting Options” in the main menu. There’s help, but you need to access the CLI of DCUI. Reassigning NICs in the DCUI didn’t work, because they were all claimed by Distributed-vSwitches thus not available for standard switches. The customer was short on vmnics in the past and has configured Management Network on a distributed Portgroup on a distributed vSwitch. After restoring configuration, for some reason vmnics were swapped between vdSwitches and it wasn’t possible to configure that host neither with hostclient nor with vCenter. In case something bad happens, you can still access the host and make changes on the interface. Call me old fashioned but I prefer to have at least the hosts management interface on a standard switch. Because you have a centralized configuration over all hosts they’re less error prone to configuration errors than standard switches. Virtual Distributed Switches have many advantages over standard switches.