HP Matrix Operating Environment 7.3 Update 1 Installation and Configuration Guide for Provisioning with Virtual Resources

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 106).
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.)
Map mode: Define all networks in VC. Each VLAN carried by an uplink is explicitly
defined as a VC network. No VC network carries packets from multiple VLANs.
2. Discover Virtual Connect networks by refreshing the infrastructure orchestration console
Networks tab.
VC networks are displayed as “Physical” in the Type column.
VC networks that are configured as “tunnel VLAN tags are displayed as “Trunk, Physical”
in the Type column.
Configuring Matrix infrastructure orchestration resources 105