VMware ESX virtual machine networking is pretty straightforward. A virtual switch (vSwitch) is created on each host by default and is associated with one or more physical NICs. When multiple physical NICs are used, virtual machines benefit from added redundancy and load balancing by simply connecting to such a vSwitch.
However, VMs don’t connect directly to vSwitches, they connect to port groups on a vSwitch. Port groups offer a means of configuring different settings, like VLAN and security, on a single vSwitch. ESX virtual network administrators perform the infrequent task of creating port groups on hosts. Later, virtual machine administrators simply select appropriate port groups when configuring VMs, seen as friendly names like this in the VI Client:
VM administrators do not necessarily know or care about VLAN or security settings, so this model abstracts some of the complexity that is a result of this network configuration flexibility. Here is what a vSwitch with two port groups and two physical NICs looks like:
Unfortunately, if you use Microsoft System Center Virtual Machine Manager (SCVMM) to configure your VMware ESX virtual machines, you are only offered vSwitches in the configuration interfaces, not port groups:
When creating a new VM, or modifying an existing one, SCVMM simply introduces new port groups on the fly into your environment. Well, that’s one way to avoid having to figure out which existing port group to use, but it might have been better if the SCVMM interface actually presented the correct objects in the first place.
After making such a configuration change, the VM is then connected to a cryptically-named network like this:
And new port groups are added to the vSwitches on all ESX hosts, something the virtual network administrator might not appreciate:
Are you thinking about managing VMware ESX with SCVMM? Are you also the virtual network administrator? If not, you may have some explaining to do.
So in a 32 host cluster with a couple of 100 vm’s this would mean a couple of 100 portgroups? and probably a lot with the same vlan ID. would be a nice environment to do troubleshooting.
Fortunately, no. As far as I can tell, SCVMM will create one new port group per vSwitch per VLAN (times 32).
I will be interested to know if Microsofts plans on integrating the upcoming VI4 and the Cisco Nexus 1000V.
I would bet they wont fully integrate. But I would be happy to be surprised.
I have no visibility into that, but if history is a guide the integration would be minimal at best.
You would be happy because you intend to use SCVMM with VMware? I would be interested in hearing your perspective on this, if you don’t mind.
Pingback: How to recover from the modifications made to vCenter by SCVMM | VCritical