HP Matrix Operating Environment Software - Manual (Page 59)

•
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 up-link 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 up-link set network can tunnel VLAN tags from an up-link port
through to a down-link port.
Configuring trunk and VLAN networks
To define trunk and VLAN networks, perform the following steps. For information about support
for Hyper-V VLAN tagging, see
“Configuring trunk and VLAN networks to enable support for
Hyper-V VLAN tagging” (page 61) .
1. Define Virtual Connect networks using Virtual Connect Manager.
•
Tunnel mode: Define each tunnel trunk in VC, which passes tagged packets unmodified.
(There is no need to inform VC which VLANs are carried by the tunnel.)
Configuring infrastructure orchestration resources in Systems Insight Manager 59