For the past few months we have been running multiple labs, two physical blades each, to do development against the vCloud 5.1 Beta. With the capacity that we have available in our overall lab, a nested approach like the VMworld labs would be a nice fit for our development team. Ideally we could spin up full vCloud instances in minutes. My experience thus far with nested environments was running vSphere in workstation to study for my VCP exam.
The first thing I did was try to build this out in a brand new vCloud 5.1 environment. For the actual setup I followed this article by William Lam. This also provided a nice graphic of what my network setup would look like.
Inside the nested vCenter I migrated the management vmk nic to vDS. Next I wanted to add another vmk for vMotion on the isolated vMOT network I created. I initially statically IP’d the nics on each vESXiHost and my first vmotion attempt failed to complete due to a connectivity problem. I eventually setup DHCP on the isolated vMOT network and neither host would receive a DHCP address (They end up with your typical 169.x.x.x address).
To test that my isolated network was setup properly I added NICs to my Windows JumpBox and built a new Ubuntu box on the vMOT network. They both received DHCP addresses and could ping between the two successfully.
The virtual ESXi hosts have three NICs that are plugged into the vMGMT, vMOT and vCUST network. Again the vmk that is there by default works perfectly, but as soon as I add another vmk for vMotion there is no network connectivity. Below is the vSS from the nested ESXi host.
I have tested this also by trying to put another vmk on vSwitch0 and it results in the same outcome, no connectivity. Again in this case I am able to put Ubuntu boxes on these networks and verify network connectivity. It is only in the case of virtual ESXi that I cannot get another vmk or port group to have connectivity.