HP Matrix Operating Environment 7.2 Update 1 Infrastructure Orchestration User Guide

• Cannot be mapped to a multi-network VC profile NIC port
• Cannot be part of a shared uplink set
Virtual Connect mapped trunk configuration
A Virtual Connect mapped trunk configuration enables VC to play a more active role managing
traffic on the VLANs, including designating one of the VLANs to handle untagged packets from
the VM Host. This constitutes hybrid support for both tagged and untagged networks on the VM
Host.
Shared uplink sets (SUS) are commonly used in this configuration to provide a set of VLANs
associated with the trunk. As in the tunneled VLAN trunk case, the list of VLANs must be supplied
by the administrator in the infrastructure orchestration console or designer, a defined SUS, or from
an external LAN management tool.
Matrix infrastructure orchestration represents Virtual Connect networks based on the VC network
configuration. Virtual Connect networks capable of being mapped are:
• Always single network subnets
• Multiple mapped subnets that an be assigned to a single VC server blade NIC port creating
a per-VC profile trunk
For mapped trunks, each Virtual Connect network defined in the shared uplink set is discovered
by Matrix infrastructure orchestration. The mapped trunk to the VC server blade is created as a
multi-network containing a subset of the defined networks when the VC profile is created.
NOTE: In releases earlier than Virtual Connect 3.30, a VC module can be in "Map VLAN Tags"
mode or "Tunnel VLAN Tags" mode. Beginning with Virtual Connect 3.30, modules are always
in map mode, but a non-shared uplink set network can tunnel VLAN tags from an uplink port
through to a downlink port.
VLAN carving
VLAN carving enables a service request to be paused when a network allocation cannot be
satisfied. For example:
• There are no more IP addresses available for the subnet
• There are no IO networks or networks assigned to a organization in the inventory that satisfy
the “Allocation name Hint” with a attribute based network allocation
Configuring infrastructure orchestration resources in Systems Insight Manager 67