HP Matrix Operating Environment 7.3 and 7.3 Update 1 Infrastructure Orchestration User Guide

NOTE: NCU (HP Network Configuration Utility) is only supported through Hyper-V 2008 R2.
For Hyper-V 2012 and later, use the Network Teaming functionality that is available on the Windows
Server Manager page.
Non-disruptive (workaround) method
The non-disruptive method is a workaround that does not disrupt your existing configuration or
existing VM guests. You can continue to use existing vNics created with NCU. This is intended as
a temporary workaround until you can migrate your environment using the disruptive method
below.
1. On the HyperV VM Host, rename each virtual switch associated with the VLAN tagging vNics
to a name that is different than the VLAN name discovered in infrastructure orchestration. (The
switch is actually a promiscuous switch that carries only one VLAN.)
2. Discover virtual networks by refreshing the infrastructure orchestration console Networks tab.
3. On the Networks tab, select the new network for the virtual switch, then click Edit Network.
a. Select the Trunk tab.
b. Click to select the Trunk check box next to the newly renamed virtual switch to mark it as
a trunk.
c. Click to select the VLANs Carried By This Trunk check box next to the IO network with
the old virtual switch name to mark it as a child of the new virtual switch trunk. There
should be only one VLAN for each of the renamed virtual switches.
d. Click Save.
Disruptive method
The disruptive method creates one “promiscuous mode” vSwitch that supports multiple VLANs. This
is the intended way for Hyper-V VLAN tagging to be configured in infrastructure orchestration 7.0
and later.
1. Use NCU to delete the vNics created for VLAN tagging.
2. Delete the HyperV virtual switch from the VM Host associated with the deleted vNics.
3. Attach the multi-VLAN interface to a “promiscuous” Hyper-V switch. (The multi-VLAN interface
is likely a NCU interface that is teaming two interfaces.)
4. If any existing VMs were using the deleted vNics, redefine the networks for each VM to connect
to the promiscuous switch with the appropriate VLAN ID.
Configuring DIO networking
Matrix infrastructure orchestration supports DIO (Direct Input Output) networking for Integrity VM
and vPars virtualization. Administrators can configure DIO networks on the VM host to make them
available for use in IO, including for use in templates.
To use DIO networking, you must have one VM host with one of the following DIO cards:
• DLA (Device Level Assignment)
For DLA cards, if the network ports of the same card are assigned to multiple guests, only one
of them can be running at the same time. Alternatively, the different ports of the same DLA
card can be assigned to the same guest and it can be running. An example is HP NC532m
2p Flex-10 10GbE BL-c Adapter.
• FLA (Function Level Assignment)
For FLA cards, different network ports of the same card can be assigned to multiple guests,
and all the guests can be running at the same time. An example is HP NC552m 2p Flex-10
10GbE BL-c Adapter.
To configure DIO networking, perform the following:
Configuring infrastructure orchestration resources in Systems Insight Manager 79