How To Migrate from Standard Switch to Logical Switch in VMM 2012 R2? #SCVMM #VMM #SysCtr #HyperV

Hello folks,

In today’s blog post, I will show you how to migrate from VMM Standard Switch to VMM Logical Switch in System Center Virtual Machine Manager 2012 R2.

As of today 5/December/2014, SCVMM 2012 R2 doesn’t have a magic button to migrate between the two worlds.

In Virtual Machine Manager you can choose between two Virtual Switches; You can use either the new Logical Switch or you can use the Standard Virtual Switch.

The question is, what if we already have Hyper-V deployed with Standard Virtual Switch, and is managed by SCVMM, but we need to migrate to Logical Switch, would be possible?

The answer is “Yes!”.

In a nutshell, let’s have first an overview of Standard Switch vs. Logical Switch:

VMM Standard Switch

The Standard Virtual Switch is basically the normal Hyper-V Virtual Switch that has all the default Virtual Switch functions, and the configuration is the same as in the Hyper-V Manager. If you add a Hyper-V Host to VMM and you have previously created the Virtual Switch using Hyper-V Manager or PowerShell.

Existing Virtual Switches will be shown as Standard Switches in SCVMM as shown in below figure, you have to recreate the configuration if you want to use the Logical Switch which is our talk for today.



VMM Logical Switch

A Logical Switch includes Virtual Switch Extensions, Uplink Port Profiles which define the underlying physical network adapters used by the Hyper-V Virtual Switch for example for teaming and the Virtual Adapter Port Profiles mapped to Port Classifications which are the settings for the Virtual NICs of the virtual machines.

You can create multiple vNICs (vEthernet Adapters) as shown in below figure, for example a Hyper-V Converged Networking setup. Port Classifications and Virtual Adapter Port Profiles bring support for Bandwidth Management and Quality of Service (QoS).



So without further ado, let’s start the migration plan.

First question to ask, do you have Hyper-V Cluster host or Hyper-V Standalone host?

I will walk through both scenarios.

Scenario 1: Migration Plan from Standard Switch to Logical Switch in Hyper-V Cluster Host:

1. Prepare your environment before assigning a “Logical Switch”.

2. Clean up your Hyper-V cluster host (carefully…)
– Place your host in Maintenance Mode in VMM (move all Virtual Machines to a different host, because you will have network outage!).
– If you don’t have Hyper-V cluster and you have more than one host, then move all Virtual Machines to a different host using Shared-Nothing Live Migration (because you will have network outage as well!).
– Remove the Virtual Switch.
– Remove NIC Teaming (The IP will be moved to MGT NIC, so make sure your MGT adapter still has an IP address before you proceed).
– Refresh the Host in VMM, make sure Virtual Machine Manager has the same level of information, no virtual switch and no teaming.
– Apply your logical switch, and then create the Virtual Network adapters (vNICs) according to the plan you have, click OK and you are done!
– Stop Maintenance Mode in VMM (when you bring a host out of maintenance mode, VMM does not automatically restart the virtual machines and does not automatically move any migrated virtual machines back on to the host).

3. Virtual Machine Migration
– Relocate your VMs from the host with the Standard to the Logical Switch, because the other host is still probably has the standard vSwitch.
The name of the Standard and Logical Switch should be the same!
○ What about the Virtual Machines network when you move back the migrated VMs?
○ The answer is “Yes”, It will work and connect to the right Logical Switch.
– Planing for this
○ Warning! Downtime impact
○ Automation with PowerShell

Scenario 2: Migration Plan from Standard Switch to Logical Switch in Hyper-V Standalone Host:

1. Prepare your environment before assigning a “Logical Switch”.

2. Clean up your Hyper-V single host (carefully…)
– Planning for this
Warning! You will have downtime
○ Automation with PowerShell
– Document all your vmNICs of all virtual machines (IP Address, VLAN ID).
– Shutdown all virtual machines.
– Remove vmNICs from all virtual machines.
– Remove vNICs from the ManagementOS if you are using Hyper-V Converged Networking (Make sure your MGT adapter still has an IP address before you proceed).
– Remove Ethernet Resource Pool if you are using “VMResourcePool”.
– Remove Hyper-V Standard Virtual Switch.
– Remove NIC Teaming (IP moved to MGT NIC).
– Refresh Host in VMM.
– Apply your logical switch and then add the Virtual Network adapters (vNICs) according to the plan you have.

3. Virtual Machine
– Add vmNICs for all virtual machines.
– Assign the same static IP address for each VM according to the plan you have.
– Start all your virtual machines.

OK, so having the plan in place, let’s start the automation process with PowerShell Winking smile

I will automate scenario 2 since it’s more existing and it requires more manual intervention than scenario 1.


Sure enough there are different ways to accomplish the same result Just kidding, but nevertheless it has worked for me and I feel that it’s a much easier and less downtime than having to do each step manually, so that’s that version 1.0 and expect more enhancements on upcoming versions Winking smile

I’d like to shout big thanks to my great friend Mark Scholman for reviewing my script!.

Hope this helps.

Until then, enjoy your weekend!


About Charbel Nemnom 405 Articles
Charbel Nemnom is a Cloud Solutions Architect and Microsoft Most Valuable Professional (MVP), totally fan of the latest's IT platform solutions, accomplished hands-on technical professional with over 17 years of broad IT Infrastructure experience serving on and guiding technical teams to optimize performance of mission-critical enterprise systems. Excellent communicator adept at identifying business needs and bridging the gap between functional groups and technology to foster targeted and innovative IT project development. Well respected by peers through demonstrating passion for technology and performance improvement. Extensive practical knowledge of complex systems builds, network design and virtualization.

Be the first to comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.