HP Virtual Connect 1Gb Ethernet Cookbook

Scenario 6 – VLAN Tagging (802.1Q) with Multiple Shared Uplink Sets (SUS) and Link Aggregation using LACP (802.3ad) –
VMware ESX 79
Summary
We created two independent but identical Shared Uplink Sets (SUS), to support several VLANs (1,
101-105, 2101-2150). Each SUS was created with Active uplinks, to provide both additional
bandwidth and availability.
When VC profile ESX-1 is applied to the server in bay1 and is powered up, it has two NICs each
connected to “Multiple VLANs”, which connects to the network infrastructure through two (active)
1Gb uplinks. These NICs are configured for VLANs 101-105, 2101,2110,2120, all VLAN tagged are
passed to the server, with the exception of VLAN 101, which we configured as Untagged.
Both NICs are connected to the SAME vSwitch. Port Groups are defined for each VLAN.
As additional servers are added to the enclosure, simply create additional profiles or copy the
ESX-1 profile, configure it for the appropriate network and apply them to the appropriate server
bays.
Results
The following graphic provides an example of an ESX Server with TWO NICs connected to the
network. Both NICs are configured to support VLANs 101-105 and VLANs 2101, 2110, 2120.
VLAN 101 is not tagged. Port Groups are added to support each VLAN.
Figure 78 - As VLAN-101 was set as Untagged within the Server Profile, you need to ensure that
the Hypervisor in NOT configured for VLAN tagging. However, if you want to put this server onto
a VLAN that is tagged, this setting will need to be configured with that VLAN tag.