I noticed I had named some vSwitches in the new hosts builds I had. This was nice. However I also noticed I couldn’t name a vSwitch when creating in vCenter. So how did I name them.<\/p>\n
I quickly searched google, but the primary results were not what I was expecting….<\/p>\n
1<\/a>, 2<\/a>, 3<\/a>, 4<\/a><\/p>\n All of which either stated to edit the host config file, or use cli commands… well I know I did do the first thing, and I don’t remember using the CLI. Also I don’t remember having to reboot the host. The only diff I can think of is that I named them at creation, not after the fact, but the vCenter wizard has no option for that… but sure enough I checked my documentation.<\/p>\n If you login into a host directly, you can name a vSwitch right when creating it. This just requires to be done on each host in the cluster. It’s nice but is it worth it<\/a>?<\/p>\n Once you have it setup it is really nice to have named vSwitches.<\/p>\n of course this doesn’t include dvSwitches, as those you can name and usually require uplinks to communicate between hosts. However you can still deploy a test dvSwitch to multiple hosts without an uplink though those VMs would only be useful on a single host… which defeats the purpose of it, but you can move the VMs as a whole group between VMs, and if that “Test switch” need any change it would be distributed between all hosts.<\/p>\n","protected":false},"excerpt":{"rendered":" I noticed I had named some vSwitches in the new hosts builds I had. This was nice. However I also noticed I couldn’t name a vSwitch when creating in vCenter. So how did I name them. I quickly searched google, but the primary results were not what I was expecting…. 1, 2, 3, 4 All … <\/p>\n