One of things I’ve been working on most recently is “nested vESX” – where you run ESX inside a VM running on physical ESX (pESX). There’s lots of reasons to do that – testing, VCP preparation, and not least testing scripts out in a sandbox before they get used in a production environment. Just a couple of days ago we released PowerCLI 5.1 Update2 which adds support for Distributed vSwitches, together with recognising the new functionality in vCloud Director 5.1.
Anyway, I thought I would make use of my vINCEPTION Lab to kick the tires on the command-lets (are you reading this Alan Renouf? 😉 ) and see what gives.
Before I embarked on that work I thought I should apply the latest updates to my ESX hosts. I’m currently running on build which I have as offline .ZIP update – so I uploaded this to the vESX local VMFS volume and applied it. Do this sort of “offline” without VMware VUM patching, you merely need the .ZIP VIB Bundle. I initially picked up this method from my colleague William Lam in his blogpost “A Pretty Cool Method of Upgrading to ESXi 5.1“
esxcli software vib update –depot=/vmfs/volumes/esx01nj_local/ESXi510-201210001.zip
What’s new in PowerCLI for DvSwitches
Before I document how I created my DvSwitches lets just take a quick run through on what fun-ctionality is. Firstly there’s whole raft of command-lets that will help you create DvSwitches, add hosts, assign nics and create portgroups. If you using vSphere5.1 you can also export and import the DvSwitch functionality – that might be interesting way of creating a new environment – by capturing the DvSwitch configuration from lab environment for example, and pushing it into production.