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 71
Scenario 6 – VLAN Tagging (802.1Q) with
Multiple Shared Uplink Sets (SUS) and Link
Aggregation using LACP (802.3ad) –
VMware ESX
Overview
In this scenario, the upstream network switch connects multiple VLANs to two ports on each VC
module. This scenario configuration uses TWO Virtual Connect Shared Uplink Sets (SUS). The SUS
provides the ability to present a single or multiple VLANs to a server NIC. Utilizing TWO identical
SUS provides the ability to redundantly connect all VLANs to the server NICs as required and
leverage all connected uplinks.
The dual SUS is a popular configuration when supporting primarily North/South traffic patterns,
as this configuration maximizes the use of all external connections.
Requirements
In order to implement this scenario, an HP BladeSystem c7000 enclosure with one of more server
blades and TWO Virtual Connect Ethernet modules, installed in Bays 1& 2 are required. In
addition, we will require ONE or TWO external Network switches. As Virtual Connect does not
appear to the network as a switch and is transparent to the network, any standard managed
switch will work with Virtual Connect.
Configuring Uplinks to a vNet (LACP)
When all uplinks configured within a vNet connect a VC module to an upstream switch, ALL links
could be active, providing additional bandwidth, using Link Aggregation Protocol (LACP 802.3ad),
this requires the upstream switch to be configured, on these ports, for link aggregation control
protocol (LACP).
When some of the uplinks configured within a vNet connect a VC module to different upstream
switches, some links will be active and the remaining will be Standby, providing additional
bandwidth and/or availability, using Link Aggregation Protocol (LACP 802.3.ad). This scenario
will have ALL uplinks Active.