Core Networking Upgrade: Act III


We’re making good progress so far.  The switch is up and the legacy configuration is working again.  It was time to make some configuration decisions.  What I settled on was this topology:

vdstopology

I decided to allocate one pNIC for vMotion exclusively and then pile everything else on the other pNIC.  With a topology in mind, it’s time to migrate the existing port groups from the vSS instances to the vDS.  This is pretty straightforward and vCenter should take care of everything if your environment is healthy.  Head over to the Networking section to get things started.  Before we get into migration, we need to create some port groups to migrate to.  Right-click on the vDS and select “New Port Group”:

Image

Not many options to worry about here surprisingly; just a name for the new port group and the maximum number of ports and whether or not VLAN tagging should be applied to the network:

Image

The above procedure should be repeated until all of the port groups required for migration are in place.  Next step is to actually migrate the vSS groups.  Right-click on the vDS and select “Migrate Virtual Machine Networking”:

Image

The first step is to choose the vSS port group to migrate and map it to a vDS port group:

Image

Next step is to select specific virtual machines within the legacy port group, or simply select all of them.  Note that there are none showing up here because the migration was already completed by the time I remembered to take a screen grab!

Image

With the machines selected, you can go ahead, click next, and finish the staging to start the migration.  In my case I moved 13 VMs at once and 12 of them went off without a hitch.  One failed with an obscure error indicating that attempting to move the guest caused a loss of host connectivity and so the change was rolled back.  Before attempting to figure that out I just gave it a second try and it worked immediately.  A bit concerning, but possibly just an anomaly.  Either way if this does come up, before worrying too much about it, do give the migration a second try.

With the VM Network migrated over, I dropped into the switch interface again and created VLAN support for VLAN4 (my dedicated vMotion VLAN).   The router was able to ping the hosts, so it was looking good, but the ultimate test of course is to perform the actual vMotion.  vMotion is nothing new obviously.  Right-click on a VM in a cluster and select Migrate, so we will walk through it stop motion photography style:

Screen Shot 2013-08-17 at 11.15.17 PM Screen Shot 2013-08-17 at 11.15.37 PM Screen Shot 2013-08-17 at 11.15.47 PM Screen Shot 2013-08-17 at 11.15.53 PM Screen Shot 2013-08-17 at 11.16.00 PM Screen Shot 2013-08-17 at 11.16.08 PM Screen Shot 2013-08-17 at 11.16.15 PM

Poof! Like magic vMotion is working which means our VLAN configuration is functional.  Before doing a test like this be sure to deselect vMotion on any other port groups to make sure that the new dedicated port group is actually in use!

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s