HP Virtual Connect 1Gb Ethernet Cookbook

Scenario 5 – VLAN Tagging (802.1Q) with a Shared Uplink Set (SUS) with Link Aggregation using LACP (802.3ad) –
VMware ESX 66
Summary
We created a Virtual Connect Shared Uplink Set (SUS), to support several VLANs (1, 101-105,
2101-2150). The SUS was created with both Active and Standby uplinks, to provide both
additional bandwidth and availability. In addition, the single SUS was used to promote better
East/West traffic patterns between servers within the same VLAN.
When VC profile ESX-1 is applied to the server in bay1 and is powered up, it has two NICs
connected to “Multiple VLANs”, which connects to the network infrastructure through a two
(active) 1Gb uplinks. These NICs are configured for VLANs 101-105, 2101,2110,2120, all VLAN
tags 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(s) 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 63 - 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.