Share via

Set up logical switches

  • Article

This article describes how to create logical switches in the System Center Virtual Machine Manager (VMM) fabric.

How to create logical switches

This article describes how to create logical switches in the System Center Virtual Machine Manager (VMM) fabric, convert a host virtual switch to a logical switch, and set up virtual switch extensions if you need them.

A logical switch brings virtual switch extensions, port profiles, and port classifications together so that you can configure each network adapter with the settings you need and have consistent settings on network adapters across multiple hosts. You can team multiple network adapters by applying the same logical switch and uplink port profile to them.

Set up virtual switch extensions

You install switch extensions on the VMM server and then include them in a logical switch. There are a few types of switch extensions:

  • Monitoring extensions can be used to monitor and report on network traffic, but they can't modify packets.
  • Capturing extensions can be used to inspect and sample traffic, but they can't modify packets.
  • Filtering extensions can be used to block, modify, or defragment packets. They can also block ports.
  • Forwarding extensions can be used to direct traffic by defining destinations, and they can capture and filter traffic. To avoid conflicts, only one forwarding extension can be active on a logical switch.

You can set up a virtual switch extension manager (network manager) if you want to manage extensions using a vendor management console and the VMM console together.

Set up a virtual switch extension manager

  1. Obtain the provider software from your vendor and install the provider on the VMM management server. If you've a cluster, install it on all the nodes.
  2. Select Fabric > Home > Show > Fabric Resources > Networking > Switch Extension Managers.
  3. In Add Virtual Switch Extension Manager Wizard > General, specify the manufacturer and enter the connection string. For example, myextmanager1.contoso.com:443. The exact syntax is defined by the vendor. Specify the account you want to use to connect to the resource.
  4. In Host Groups, specify the host groups for which you want to use the extension manager.
  5. In Summary, review settings and select Finish. Check that the extension appears in the Virtual Switch Extension Managers pane.

Set up a logical switch

  1. Ensure that you've at least one uplink port profile before you begin.

  2. Select Fabric tab > Networking > Logical Switches > Create Logical Switch.

  3. In Create Logical Switch Wizard > Getting Started, review the information.

  4. In General, specify a name and optional description.

  5. In Uplink Mode, select:

    • No Uplink Team - if you're not using teaming.
    • Embedded Team - if you want to deploy the switch with SET-based teaming
    • Team - if you want to use NIC teaming

  6. In Settings, select the minimum bandwidth mode. If you've deployed Microsoft network controller, you can specify that it must manage the switch. If you enable this setting, you won't be able to add extensions to the switch.

  7. Enable SR-IOV if you need to. SR-IOV enables virtual machines to bypass the switch and directly address the physical network adapter. If you want to enable:

    • Ensure that you've SR-IOV support in the host hardware and firmware, the physical network adapter, and drivers in the management operating system and in the guest operating system.
    • Create a native port profile for virtual network adapters that is also SR-IOV enabled.
    • When you configure networking settings on the host (in the host property called Virtual switches), attach the native port profile for virtual network adapters to the virtual switch by using a port classification. You can use the SR-IOV port classification that is provided in VMM or create your own port classification.

  8. In Extensions, if you're using virtual switch extensions, select them and arrange the order. Extensions process network traffic through the switch in the order you specify.

Note

Only one forwarding extension can be enabled.

  1. In Virtual Port, add one or more port classifications and virtual network adapter port profiles. You can also create a port classification and set a default classification.
  2. In Uplink, add an uplink port profile or create a new one. When you add an uplink port profile, it's placed in a list of profiles that are available through that logical switch. However, when you apply the logical switch to a network adapter in a host, the uplink port profile is applied to that network adapter only if you select it from the list of available profiles.
  3. In Summary, review the settings and select Finish. Verify if the switch created appears in Logical Switches.

Convert virtual switch to logical switch

If a host in the VMM fabric has a standard virtual switch, you can convert it to use as a logical switch.

Note

  • The following procedure isn't applicable for SET, use the script instead.
  • Before you can convert, you need a logical switch in place with specific settings.
  • You must be a member of the Administrator user role, or a member of the Delegated Administrator user role, where the management scope includes the host group in which the Hyper-V host is located.

Compare switch settings

  1. In Server Manager on the host, select Hyper-V. Close Server Manager.

  2. Right-click the host > Configure NIC Teaming, and record any teaming and load balancing settings.

  3. In Hyper-V Manager, right-click the host > Virtual Switch Manager. Select the virtual switch and verify whether Enable single-root I/O virtualization (SR-IOV) is selected. Close the Hyper-V Manager.

  4. In the VMM console > Fabric > Servers > All Hosts, right-click the host > Properties.

  5. In Virtual Switches, note the properties, including logical network and minimum bandwidth mode.

  6. In Fabric > Networking > Logical Switches, right-click the logical switch that you want to convert the host configuration to and select Properties.

  7. In Logical Switches, record the information:

    • In General, record the uplink mode, whether SR-IOV is enabled, and minimum bandwidth mode.
    • In Extensions, note whether any forwarding extensions have been added to the logical switch.
    • In Virtual port, record the names of the port profiles that are listed. Ensure to note if one of them has SR-IOV in the name.
    • In Uplinks, record the network sites, whether uplink mode is teamed, the load balancing algorithm, and teaming mode.

  8. In Fabric > Networking, select Port Profiles. For any relevant port profiles, select Properties. In Offload Settings, see if Enable Single-root I/O virtualization is checked.

  9. Now compare the recorded information that you recorded for the logical switch and port profiles, with the virtual switch information.

  10. Review the following table to see whether you can convert the host to use the logical switch.

    Item Conversion
    SR-IOV The SR-IOV setting (enabled or disabled) must be the same in the logical switch as it's in the virtual switch.

    If SR-IOV is enabled, it must be enabled in the logical switch itself, and in at least one virtual network adapter port profile within the logical switch.
    Uplink mode

    Load balancing algorithm

    Teaming mode    		 The Uplink mode setting must match.

    If the uplink mode is Team, then the Load balancing algorithm and Teaming mode must also match.
    Minimum bandwidth mode Must match.
    Network sites The logical switch must be configured for the correct network sites (in the correct logical network) for this host.

  11. If the settings in the logical switch don't match as described in the table, you need to find or create a logical switch that does match.

Convert a host to use a logical switch

Note

  • The conversion will not interrupt network traffic.
  • If any operation in the conversion fails, no settings will be changed, and the switch won't be converted.
  1. In VMM, select Fabric > Servers > All Hosts. Right-click the host > Properties.
  2. On the Virtual Switches tab, select Convert to Logical Switch.
  3. Select the logical switch to which you want to convert the host. Select the uplink port profile to use and select Convert.
  4. The Jobs dialog might appear depending on your settings. Ensure that the job has a status of Completed, and then close the dialog.
  5. To verify that the switch was converted, right-click the host, select Properties, and then select the Virtual Switches tab.

Script for SET switch conversion

Note

Create a logical switch in VMM with the same name as the SET switch that is deployed on the host. Standard switch will be converted to this logical switch after you run the following script on the host.

#Replace Virtual Switch name with already deployed switch name on host
$VirtualSwitchName="SETswitch"

#Replace logical switch ID below with the one got from Get-SCLogicalSwitch cmdlet for the switch created in VMM
$LogicalSwitchId="45b98a8d-1887-4431-9f20-8b9beed853ce"

#Replace the port profile set name with the one created and associated with the above logical switch in VMM
$PortProfileSetName="Mgmt_UPP"

#Replace uplink port profile set ID with the one got from Get-SCUplinkPortProfileSet for the port profile set created in VMM
$PortProfileSetId="fd9e4c9a-4ffa-4845-808d-930e6616b62f"

$vswitch=Get-VMSwitch -Name $VirtualSwitchName
$VMMPortFeatureId="1f59a509-a6ba-4aba-8504-b29d542d44bb"
$defaultPortFeature = Get-VMSystemSwitchExtensionPortFeature -FeatureId $VMMPortFeatureId
$VMMFeatureId="8b54c928-eb03-4aff-8039-99171dd900ff"
$currentFeature = Get-VMSwitchExtensionSwitchFeature -SwitchName $VirtualSwitchName -FeatureId $VMMFeatureId
$defaultFeature = Get-VMSystemSwitchExtensionSwitchFeature -FeatureId $VMMFeatureId
$defaultFeature.SettingData.LogicalSwitchId=$LogicalSwitchId
$defaultFeature.SettingData.LogicalSwitchName=$VirtualSwitchName
Add-VMSwitchExtensionSwitchFeature -SwitchName $VirtualSwitchName -VMSwitchExtensionFeature $defaultFeature

$defaultPortFeature = Get-VMSystemSwitchExtensionPortFeature -FeatureId $VMMPortFeatureId
$defaultPortFeature.SettingData.PortProfileSetId=$PortProfileSetId
$defaultPortFeature.SettingData.PortProfileSetName=$PortProfileName
$defaultPortFeature.SettingData.NetCfgInstanceId="{" + $vswitch.Id +"}"
Add-VMSwitchExtensionPortFeature -SwitchName $VirtualSwitchName -VMSwitchExtensionFeature $defaultPortFeature –ExternalPort

After you run the script, refresh the host in VMM, and verify if VMM recognizes the switch as a logical switch.

How to create logical switches

This article describes how to create logical switches in the System Center Virtual Machine Manager (VMM) fabric, convert a host virtual switch to a logical switch, and set up virtual switch extensions if you need them.

A logical switch brings virtual switch extensions, port profiles, and port classifications together so that you can configure each network adapter with the settings you need and have consistent settings on network adapters across multiple hosts. You can team multiple network adapters by applying the same logical switch and uplink port profile to them.

Set up virtual switch extensions

You install switch extensions on the VMM server and then include them in a logical switch. There are a few types of switch extensions:

  • Monitoring extensions can be used to monitor and report on network traffic, but they can't modify packets.
  • Capturing extensions can be used to inspect and sample traffic, but they can't modify packets.
  • Filtering extensions can be used to block, modify, or defragment packets. They can also block ports.
  • Forwarding extensions can be used to direct traffic by defining destinations, and they can also capture and filter traffic. To avoid conflicts, only one forwarding extension can be active on a logical switch.

You can set up a virtual switch extension manager (network manager) if you want to manage extensions using a vendor management console and the VMM console together.

Set up a virtual switch extension manager

  1. Obtain the provider software from your vendor and install the provider on the VMM management server. If you have a cluster, install it on all the nodes.
  2. Select Fabric > Home > Show > Fabric Resources > Networking > Switch Extension Managers.
  3. In Add Virtual Switch Extension Manager Wizard > General, specify the manufacturer and enter the connection string. For example, myextmanager1.contoso.com:443. The exact syntax is defined by the vendor. Specify the account you want to use to connect to the resource.
  4. In Host Groups, specify the host groups for which you want to use the extension manager.
  5. In Summary, review settings and select Finish. Check that the extension appears in the Virtual Switch Extension Managers pane.

Set up a logical switch

Note

Ensure you've at least one uplink port profile before you begin.

  1. Select Fabric > Networking

  2. Right-click Logical Switches, and then select Create Logical Switch.

  3. In Create Logical Switch Wizard > Getting Started, review the information.

  4. In General,

    • Specify a name
    • Provide a description (optional).

  5. In Uplink Mode, select:

    • Embedded Team - if you're using Windows Server 2016 or later
    • Team - if you're using Windows Server 2012 and want to use NIC teaming
    • No Uplink Team - if you're not using any teaming.

    From VMM 2019 UR2, Embedded Team is the default Uplink mode.

  6. In Settings, select the minimum bandwidth mode. If you've deployed Microsoft network controller, you can specify that it must manage the switch. If you enable this setting, you won't be able to add extensions to the switch.

    • Weight - Weight is the default minimum bandwidth mode. Weight specifies a percentage of bandwidth rather than a specific number of bits per second. Minimum bandwidth is a value ranging from 1 to 100.
    • Default - The system sets the mode to Weight if the switch isn't IOV enabled, or None if the switch is IOV enabled.
    • Absolute - Minimum bandwidth will be in bits per second.
    • None - Minimum bandwidth is disabled on the switch. Users can't configure it on any network adapter that is connected to the switch.

  7. Enable SR-IOV if you need to. SR-IOV enables virtual machines to bypass the switch and directly address the physical network adapter. If you want to enable:

    • Ensure you've SR-IOV support in the host hardware and firmware, the physical network adapter, and drivers in the management operating system and in the guest operating system.
    • Create a native port profile for virtual network adapters that is SR-IOV enabled.
    • When you configure networking settings on the host (in the host property called Virtual switches), attach the native port profile for virtual network adapters to the virtual switch by using a port classification. You can use the SR-IOV port classification that is provided in VMM or create your own port classification.

  8. In Extensions, if you're using virtual switch extensions, select them and arrange the order. Extensions process network traffic through the switch in the order you specify.

Note

Only one forwarding extension can be enabled. From VMM 2019 UR2, none of the extensions are enabled by default.

  1. In Virtual Port, add one or more port classifications and virtual network adapter port profiles. Every Port Classification must be mapped to a Port Profile. From VMM 2019 UR2, you can view Port Classification to Port Profile mapping on the Virtual Port screen.

  2. In Uplink, add an uplink port profile, or create a new one. When you add an uplink port profile, it's placed in a list of profiles that are available through that logical switch. However, when you apply the logical switch to a network adapter in a host, the uplink port profile is applied to that network adapter only if you select it from the list of available profiles.

    If Uplink is chosen as Embedded Team (Switch Embedded Team or SET), then only Hyper-V Port and Dynamic load balancing algorithms are supported. Hyper-V Port is the default load balancing algorithm. If Uplink mode is chosen as Embedded Team, then Hyper-V Port is the recommended load balancing algorithm; Dynamic isn't recommended.

  3. In Summary, review the settings and select Finish. Verify if the switch created appears in Logical Switches.

View logical switch topology

Note

This feature is available from VMM 2019 UR2.

From VMM 2019 UR2, you can view the logical switch topology. To view, right-click the logical switch name, and then select View Topology. The topology diagram displays the following information.

  • Uplink Port Profiles - Includes information about Load Balancing algorithm, Teaming mode, and Network sites.
  • Virtual Network Adapters - Includes information about VM Networks, VLANs, and Port Classifications.

Convert virtual switch to logical switch

If a host in the VMM fabric has a standard virtual switch with or without SET, you can convert it to use as a logical switch.

Note

  • Before you can convert, you need a logical switch in place with specific settings.
  • You must be a member of the Administrator user role, or a member of the Delegated Administrator user role, where the management scope includes the host group in which the Hyper-V host is located.

Compare switch settings

  1. Record if NIC Teaming (LBFO) or SET is being used on the host.

  2. If you're using NIC teaming on the host, record teaming and load balancing settings by running the PowerShell commandlet Get-NetLbfoTeam.

  3. In Hyper-V Manager, right-click the host > Virtual Switch Manager. Select the virtual switch and verify whether Enable single-root I/O virtualization (SR-IOV) is selected. Close Hyper-V Manager.

  4. In the VMM console > Fabric > Servers > All Hosts, right-click the host > Properties.

  5. In Virtual Switches, note the properties, including logical network and minimum bandwidth mode.

  6. In Fabric > Networking > Logical Switches, right-click the logical switch that you want to convert the host configuration to and select Properties.

  7. In Logical Switches, record the information:

    • In General, record the uplink mode, whether SR-IOV is enabled, and minimum bandwidth mode.
    • In Extensions, note whether any forwarding extensions have been added to the logical switch.
    • In Virtual port, record the names of the port profiles that are listed. Ensure to note if one of them has SR-IOV in the name.
    • In Uplinks, record the network sites, whether uplink mode is teamed, the load balancing algorithm, and teaming mode.

  8. In Fabric > Networking, select Port Profiles. For any relevant port profiles, select Properties. In Offload Settings, see if Enable Single-root I/O virtualization is checked.

  9. Now compare the recorded information that you recorded for the logical switch and port profiles, with the virtual switch information.

  10. Review the following table to see whether you can convert the host to use the logical switch.

    Item Conversion
    SR-IOV The SR-IOV setting (enabled or disabled) must be the same in the logical switch as it's in the virtual switch.

    If SR-IOV is enabled, it must be enabled in the logical switch itself, and in at least one virtual network adapter port profile within the logical switch.
    Uplink mode

    Load balancing algorithm

    Teaming mode    		 The Uplink mode setting must match.

    If the uplink mode is Team, then the Load balancing algorithm and Teaming mode must also match.
    Minimum bandwidth mode Must match.
    Network sites The logical switch must be configured for the correct network sites (in the correct logical network) for this host.

  11. If the settings in the logical switch don't match as described in the table, you need to find or create a logical switch that does match.

Convert a host to use a logical switch

Note

  • The conversion will not interrupt network traffic.
  • If any operation in the conversion fails, no settings will be changed and the switch will not be converted.
  1. In VMM, select Fabric > Servers > All Hosts. Right-click the host > Properties.
  2. On the Virtual Switches tab, select Convert to Logical Switch.
  3. Select the logical switch to which you want to convert the host. Select the uplink port profile to use and select Convert.
  4. The Jobs dialog box might appear, depending on your settings. Ensure the job has a status of Completed and then close the dialog.
  5. To verify that the switch was converted, right-click the host, select Properties, and then select the Virtual Switches tab.

How to create logical switches

This article describes how to create logical switches in the System Center Virtual Machine Manager (VMM) fabric, convert a host virtual switch to a logical switch, and set up virtual switch extensions if you need them.

A logical switch brings virtual switch extensions, port profiles, and port classifications together so that you can configure each network adapter with the settings you need and have consistent settings on network adapters across multiple hosts. You can team multiple network adapters by applying the same logical switch and uplink port profile to them.

Set up virtual switch extensions

You install switch extensions on the VMM server and then include them in a logical switch. There are a few types of switch extensions:

  • Monitoring extensions can be used to monitor and report on network traffic, but they can't modify packets.
  • Capturing extensions can be used to inspect and sample traffic, but they can't modify packets.
  • Filtering extensions can be used to block, modify, or defragment packets. They can also block ports.
  • Forwarding extensions can be used to direct traffic by defining destinations, and they can also capture and filter traffic. To avoid conflicts, only one forwarding extension can be active on a logical switch.

You can set up a virtual switch extension manager (network manager) if you want to manage extensions using a vendor management console and the VMM console together.

Set up a virtual switch extension manager

  1. Obtain the provider software from your vendor and install the provider on the VMM management server. If you have a cluster, install it on all the nodes.
  2. Select Fabric > Home > Show > Fabric Resources > Networking > Switch Extension Managers.
  3. In Add Virtual Switch Extension Manager Wizard > General, specify the manufacturer and enter the connection string. For example, myextmanager1.contoso.com:443. The exact syntax is defined by the vendor. Specify the account you want to use to connect to the resource.
  4. In Host Groups, specify the host groups for which you want to use the extension manager.
  5. In Summary, review settings and select Finish. Check that the extension appears in the Virtual Switch Extension Managers pane.

Set up a logical switch

Note

Ensure you've at least one uplink port profile before you begin.

  1. Select Fabric > Networking

  2. Right-click Logical Switches, and then select Create Logical Switch.

  3. In Create Logical Switch Wizard > Getting Started, review the information.

  4. In General,

    • Specify a name
    • Provide a description (optional).

  5. In Uplink Mode, select:

    • Embedded Team - if you're using Windows Server 2016 or later
    • Team - if you're using Windows Server 2012 and want to use NIC teaming
    • No Uplink Team - if you're not using any teaming.

    Embedded Team is the default Uplink mode.

  6. In Settings, select the minimum bandwidth mode. If you've deployed Microsoft network controller, you can specify that it must manage the switch. If you enable this setting, you won't be able to add extensions to the switch.

    • Weight - Weight is the default minimum bandwidth mode. Weight specifies a percentage of bandwidth rather than a specific number of bits per second. Minimum bandwidth is a value ranging from 1 to 100.
    • Default - The system sets the mode to Weight if the switch isn't IOV enabled, or None if the switch is IOV enabled.
    • Absolute - Minimum bandwidth will be in bits per second.
    • None - Minimum bandwidth is disabled on the switch. Users can't configure it on any network adapter that is connected to the switch.

  7. Enable SR-IOV if you need to. SR-IOV enables virtual machines to bypass the switch and directly address the physical network adapter. If you want to enable:

    • Ensure you've SR-IOV support in the host hardware and firmware, the physical network adapter, and drivers in the management operating system and in the guest operating system.
    • Create a native port profile for virtual network adapters that is SR-IOV enabled.
    • When you configure networking settings on the host (in the host property called Virtual switches), attach the native port profile for virtual network adapters to the virtual switch by using a port classification. You can use the SR-IOV port classification that is provided in VMM or create your own port classification.

  8. In Extensions, if you're using virtual switch extensions, select them and arrange the order. Extensions process network traffic through the switch in the order you specify.

Note

Only one forwarding extension can be enabled. None of the extensions are enabled by default.

  1. In Virtual Port, add one or more port classifications and virtual network adapter port profiles. Every Port Classification must be mapped to a Port Profile. You can view Port Classification to Port Profile mapping on the Virtual Port screen.

  2. In Uplink, add an uplink port profile, or create a new one. When you add an uplink port profile, it's placed in a list of profiles that are available through that logical switch. However, when you apply the logical switch to a network adapter in a host, the uplink port profile is applied to that network adapter only if you select it from the list of available profiles.

    If Uplink is chosen as Embedded Team (Switch Embedded Team or SET), then only Hyper-V Port and Dynamic load balancing algorithms are supported. Hyper-V Port is the default load balancing algorithm. If Uplink mode is chosen as Embedded Team, then Hyper-V Port is the recommended load balancing algorithm; Dynamic isn't recommended.

  3. In Summary, review the settings and select Finish. Verify if the switch created appears in Logical Switches.

Convert virtual switch to logical switch

If a host in the VMM fabric has a standard virtual switch with or without SET, you can convert it to use as a logical switch.

Note

  • Before you can convert, you need a logical switch in place with specific settings.
  • You must be a member of the Administrator user role, or a member of the Delegated Administrator user role, where the management scope includes the host group in which the Hyper-V host is located.

Compare switch settings

  1. Record if NIC Teaming (LBFO) or SET is being used on the host.

  2. If you're using NIC teaming on the host, record teaming and load balancing settings by running the PowerShell commandlet Get-NetLbfoTeam.

  3. In Hyper-V Manager, right-click the host > Virtual Switch Manager. Select the virtual switch and verify whether Enable single-root I/O virtualization (SR-IOV) is selected. Close Hyper-V Manager.

  4. In the VMM console > Fabric > Servers > All Hosts, right-click the host > Properties.

  5. In Virtual Switches, note the properties, including logical network and minimum bandwidth mode.

  6. In Fabric > Networking > Logical Switches, right-click the logical switch that you want to convert the host configuration to and select Properties.

  7. In Logical Switches, record the information:

    • In General, record the uplink mode, whether SR-IOV is enabled, and minimum bandwidth mode.
    • In Extensions, note whether any forwarding extensions have been added to the logical switch.
    • In Virtual port, record the names of the port profiles that are listed. Ensure to note if one of them has SR-IOV in the name.
    • In Uplinks, record the network sites, whether uplink mode is teamed, the load balancing algorithm, and teaming mode.

  8. In Fabric > Networking, select Port Profiles. For any relevant port profiles, select Properties. In Offload Settings, see if Enable Single-root I/O virtualization is checked.

  9. Now compare the recorded information that you recorded for the logical switch and port profiles, with the virtual switch information.

  10. Review the following table to see whether you can convert the host to use the logical switch.

    Item Conversion
    SR-IOV The SR-IOV setting (enabled or disabled) must be the same in the logical switch as it's in the virtual switch.

    If SR-IOV is enabled, it must be enabled in the logical switch itself, and in at least one virtual network adapter port profile within the logical switch.
    Uplink mode

    Load balancing algorithm

    Teaming mode    		 The Uplink mode setting must match.

    If the uplink mode is Team, then the Load balancing algorithm and Teaming mode must also match.
    Minimum bandwidth mode Must match.
    Network sites The logical switch must be configured for the correct network sites (in the correct logical network) for this host.

  11. If the settings in the logical switch don't match as described in the table, you need to find or create a logical switch that does match.

Convert a host to use a logical switch

Note

  • The conversion will not interrupt network traffic.
  • If any operation in the conversion fails, no settings will be changed and the switch will not be converted.
  1. In VMM, select Fabric > Servers > All Hosts. Right-click the host > Properties.
  2. On the Virtual Switches tab, select Convert to Logical Switch.
  3. Select the logical switch to which you want to convert the host. Select the uplink port profile to use and select Convert.
  4. The Jobs dialog box might appear, depending on your settings. Ensure the job has a status of Completed and then close the dialog.
  5. To verify that the switch was converted, right-click the host, select Properties, and then select the Virtual Switches tab.

How to create logical switches

This article describes how to create logical switches in the System Center Virtual Machine Manager (VMM) fabric, convert a host virtual switch to a logical switch, and set up virtual switch extensions if you need them.

A logical switch brings virtual switch extensions, port profiles, and port classifications together so that you can configure each network adapter with the settings you need and have consistent settings on network adapters across multiple hosts. You can team multiple network adapters by applying the same logical switch and uplink port profile to them.

Set up virtual switch extensions

You install switch extensions on the VMM server and then include them in a logical switch. There are a few types of switch extensions:

  • Monitoring extensions can be used to monitor and report on network traffic, but they can't modify packets.
  • Capturing extensions can be used to inspect and sample traffic, but they can't modify packets.
  • Filtering extensions can be used to block, modify, or defragment packets. They can also block ports.
  • Forwarding extensions can be used to direct traffic by defining destinations, and they can also capture and filter traffic. To avoid conflicts, only one forwarding extension can be active on a logical switch.

You can set up a virtual switch extension manager (network manager) if you want to manage extensions using a vendor management console and the VMM console together.

Set up a virtual switch extension manager

  1. Obtain the provider software from your vendor and install the provider on the VMM management server. If you have a cluster, install it on all the nodes.
  2. Select Fabric > Home > Show > Fabric Resources > Networking > Switch Extension Managers.
  3. In Add Virtual Switch Extension Manager Wizard > General, specify the manufacturer and enter the connection string. For example, myextmanager1.contoso.com:443. The exact syntax is defined by the vendor. Specify the account you want to use to connect to the resource.
  4. In Host Groups, specify the host groups for which you want to use the extension manager.
  5. In Summary, review settings and select Finish. Check that the extension appears in the Virtual Switch Extension Managers pane.

Set up a logical switch

Note

Ensure you've at least one uplink port profile before you begin.

  1. Select Fabric > Networking

  2. Right-click Logical Switches, and then select Create Logical Switch.

  3. In Create Logical Switch Wizard > Getting Started, review the information.

  4. In General,

    • Specify a name
    • Provide a description (optional).

  5. In Uplink Mode, select:

    • Embedded Team - if you're using Windows Server 2019 or later.
    • No Uplink Team - if you're not using any teaming.

    Embedded Team is the default Uplink mode.

  6. In Settings, select the minimum bandwidth mode. If you've deployed Microsoft network controller, you can specify that it must manage the switch. If you enable this setting, you won't be able to add extensions to the switch.

    • Weight - Weight is the default minimum bandwidth mode. Weight specifies a percentage of bandwidth rather than a specific number of bits per second. Minimum bandwidth is a value ranging from 1 to 100.
    • Default - The system sets the mode to Weight if the switch isn't IOV enabled, or None if the switch is IOV enabled.
    • Absolute - Minimum bandwidth will be in bits per second.
    • None - Minimum bandwidth is disabled on the switch. Users can't configure it on any network adapter that is connected to the switch.

  7. Enable SR-IOV if you need to. SR-IOV enables virtual machines to bypass the switch and directly address the physical network adapter. If you want to enable:

    • Ensure that you've SR-IOV support in the host hardware and firmware, the physical network adapter, and drivers in the management operating system and in the guest operating system.
    • Create a native port profile for virtual network adapters that is SR-IOV enabled.
    • When you configure networking settings on the host (in the host property called Virtual switches), attach the native port profile for virtual network adapters to the virtual switch by using a port classification. You can use the SR-IOV port classification that is provided in VMM or create your own port classification.

  8. In Extensions, if you're using virtual switch extensions, select them and arrange the order. Extensions process network traffic through the switch in the order you specify.

Note

Only one forwarding extension can be enabled. None of the extensions are enabled by default.

  1. In Virtual Port, add one or more port classifications and virtual network adapter port profiles. Every Port Classification must be mapped to a Port Profile. You can view Port Classification to Port Profile mapping on the Virtual Port screen.

  2. In Uplink, add an uplink port profile, or create a new one. When you add an uplink port profile, it's placed in a list of profiles that are available through that logical switch. However, when you apply the logical switch to a network adapter in a host, the uplink port profile is applied to that network adapter only if you select it from the list of available profiles.

    If Uplink is chosen as Embedded Team (Switch Embedded Team or SET), then only Hyper-V Port and Dynamic load balancing algorithms are supported. Hyper-V Port is the default load balancing algorithm. If Uplink mode is chosen as Embedded Team, then Hyper-V Port is the recommended load balancing algorithm; Dynamic isn't recommended.

  3. In Summary, review the settings and select Finish. Verify if the switch created appears in Logical Switches.

Convert virtual switch to logical switch

If a host in the VMM fabric has a standard virtual switch with or without SET, you can convert it to use as a logical switch.

Note

  • Before you can convert, you need a logical switch in place with specific settings.
  • You must be a member of the Administrator user role, or a member of the Delegated Administrator user role, where the management scope includes the host group in which the Hyper-V host is located.

Compare switch settings

  1. Record if NIC Teaming (LBFO) or SET is being used on the host.

  2. If you're using NIC teaming on the host, record teaming and load balancing settings by running the PowerShell commandlet Get-NetLbfoTeam.

  3. In Hyper-V Manager, right-click the host > Virtual Switch Manager. Select the virtual switch and verify whether Enable single-root I/O virtualization (SR-IOV) is selected. Close Hyper-V Manager.

  4. In the VMM console > Fabric > Servers > All Hosts, right-click the host > Properties.

  5. In Virtual Switches, note the properties, including logical network and minimum bandwidth mode.

  6. In Fabric > Networking > Logical Switches, right-click the logical switch that you want to convert the host configuration to and select Properties.

  7. In Logical Switches, record the information:

    • In General, record the uplink mode, whether SR-IOV is enabled, and minimum bandwidth mode.
    • In Extensions, note whether any forwarding extensions have been added to the logical switch.
    • In Virtual port, record the names of the port profiles that are listed. Ensure that you note if one of them has SR-IOV in the name.
    • In Uplinks, record the network sites, whether uplink mode is teamed, the load balancing algorithm, and teaming mode.

  8. In Fabric > Networking, select Port Profiles. For any relevant port profiles, select Properties. In Offload Settings, see if Enable Single-root I/O virtualization is checked.

  9. Now compare the recorded information that you recorded for the logical switch and port profiles, with the virtual switch information.

  10. Review the following table to see whether you can convert the host to use the logical switch.

    Item Conversion
    SR-IOV The SR-IOV setting (enabled or disabled) must be the same in the logical switch as it's in the virtual switch.

    If SR-IOV is enabled, it must be enabled in the logical switch itself, and in at least one virtual network adapter port profile within the logical switch.
    Uplink mode

    Load balancing algorithm

    Teaming mode    		 The Uplink mode setting must match.

    If the uplink mode is Team, then the Load balancing algorithm and Teaming mode must also match.
    Minimum bandwidth mode Must match.
    Network sites The logical switch must be configured for the correct network sites (in the correct logical network) for this host.

  11. If the settings in the logical switch don't match as described in the table, you need to find or create a logical switch that does match.

Convert a host to use a logical switch

Note

  • The conversion will not interrupt network traffic.
  • If any operation in the conversion fails, no settings will be changed, and the switch will not be converted.
  1. In VMM, select Fabric > Servers > All Hosts. Right-click the host > Properties.
  2. On the Virtual Switches tab, select Convert to Logical Switch.
  3. Select the logical switch to which you want to convert the host. Select the uplink port profile to use and select Convert.
  4. The Jobs dialog box might appear, depending on your settings. Ensure the job has a status of Completed and then close the dialog.
  5. To verify that the switch was converted, right-click the host, select Properties, and then select the Virtual Switches tab.

Next steps

Apply network settings on a host with a logical switch.