Operating Environment Software Instruction Manual

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 HP Network Configuration
Utility (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. Check Trunk next to the newly renamed virtual switch to mark it as a trunk.
c. Check VLANs Carried By This Trunk 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 higher.
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 pools
Pools are groups of resources used to submit requests to create new infrastructure services or add
to existing infrastructure services. A new pool must be created and users must be assigned to it
before initiating any requests.
The infrastructure orchestration console Servers tab displays the following types of resources,
depending on the selection in the Display list.
• Pools and Compute Resources
Summary of all pools and resources (default)
• Compute Resources
Summary of all physical servers, VM Hosts, ESX resource pools, and cloud resources
• Pools
Summary of all server pools (physical, VM Host, or combined), ESX resource pools, and cloud
resources
ESX resource pools and cloud capacity pools
In addition to physical servers and VM Hosts, infrastructure orchestration includes the following
types of provisionable resources:
• ESX resource pools
ESX resource pools are a type of compute resource created using VMware vCenter or the
virtual machine management CLI, and are discovered by infrastructure orchestration. ESX
Configuring infrastructure orchestration resources in Systems Insight Manager 67