HP Matrix Operating Environment 7.2 Infrastructure Orchestration User Guide

adding the NICs to a vSwitch). This is best accomplished through naming conventions and
customized Operations Orchestration workflow scripts to configure the OS networking.
• A VLAN is carried by one or more Virtual Connect tunnel networks or other trunk networks in
the environment. A VLAN cannot be a trunk network.
Matrix infrastructure orchestration contains VLAN tagged network support to meet the following
objectives:
• Enable IO to be used to deploy a VM Host with a multi-network trunk connected to a server
blade network port
◦ Allow an IO administrator to manage and present trunk networks to be used in IO physical
provisioning
◦ Allow an architect to create a physical service template that designates a trunk network
◦ Provision physical server blades with a trunk connected to at least one of the available
NIC ports
• Enable Hyper-V VM provisioning to a Hyper-V server with a VLAN tagged virtual network
switch
◦ Provide the VLAN ID when creating a Hyper-V VM on a VLAN tagged virtual switch
Matrix infrastructure orchestration adds the ability to detail trunk networks and create templates
that represent a trunk network connected to a Virtual Connect server blade. From these definitions
IO is then able to orchestrate the creation of Virtual Connect profile with a trunk connection.
With properly configured networks, the service request contains sufficient information to enable
HP Operations Orchestration workflows scripts to configure the Virtual Connect server blade for
trunk aware applications, primarily VM Host clusters.
For information about configuring a trunk or VLAN in the infrastructure orchestration console, see
“Configuring trunk and VLAN networks” (page 68).
For information about specifying a trunk or VLAN in a VM Host or cluster service template, see
“Creating a template with a physical VM Host or ESXi VM cluster” (page 117).
Virtual Connect tunneled trunk configuration
HP Virtual Connect provides two types of network configurations to present a VLAN trunk to a VC
server blade. The HP Virtual Connect Ethernet Cookbook (available at http://
h20000.www2.hp.com/bc/docs/support/SupportManual/c01990371/c01990371.pdf) illustrates
these two configurations in scenarios 1:6 (mapped trunk) and 2:4 (tunneled trunk).
A Virtual Connect tunneled trunk configuration passes tagged traffic through to the target interface
unrestricted. The definitions of the VLANs can only be found on the LAN-side switch and configured
in the host-side network stack. VC does not maintain any information on the VLANs.
Configuration of the host requires knowledge of the VLANs to use. The definition of the VLANs
must be supplied by the administrator in the infrastructure orchestration console or designer, and
potentially from external sources, such as LAN management tools.
Configuring infrastructure orchestration resources in Systems Insight Manager 65