Start a Conversation

Unsolved

This post is more than 5 years old

685

August 10th, 2012 12:00

Which virtual switch type should a vCenter VM live on?

I have been mulling over a "Chicken & Egg" question for a while and could use some experienced feedback.  Start with the premise that vCenter 5 and its database should be virtualized.  If you disagree with that starting point, we will have to start a different discussion. 

Next, vCenter 5 begins life on a standard virtual switch tied to the configuration of one ESXi Host.  Why?  Because until at least one vCenter exists, no distributed virtual switch can exist.  That is the "Chicken & Egg" part. 

Now, to take advantage of the various highly available functions in VMware to protect my vCenter and database, the next logical step would be to move them to a distributed virtual switch.  Indeed, the VM migration tool will allow me to prepare for this step with only a vague warning about the uplink vnic and vmkernel port group access for management.  After making sure there is at least one uplink nic for the distrubuted virtual switch, along with a vmkernel port group for management, I commit the migration.

The migration is marked as completed, right before I am disconnected from vCenter.  The 2nd time through I expected this and go off to my ESXi console to re-configure my management network and restart it.  Long story short, it wasn't pretty, but I got it done after some steps I cannot recommend for a production implementation.

Does anyone have any experience accomplishing this migration in a graceful manner or is that my next side Project?

Does anyone feel that it is safer and more straightforward to just configure one Cluster of ESXi Hosts with identical standard virtual switches and just getting on with my life?  THX

7 Posts

August 13th, 2012 05:00

I've not been running a virtualised vCenter for very long, but in order to get my management to agree with the idea in the first place I had to show we could protect the vCenter from host failure in our 6 node cluster. I went for vCenter Heartbeat and advised the management that while it was pricey it would give us the required protection. It allows me to fail over the vCenter services and database to the secondary VM, and then carry out maintenance on the primary without loss of management functionality and obviously if the host on which the primary is running fails an automatic failover occurs.

Hope this helps

No Events found!

Top