Scenario 1:6 - Vlan Tagging (802.1Q) With Multiple Shared Uplink Sets (Sus) And Link Aggregation Using Lacp (802.3Ad) - Vmware Esx; Overview; Requirements; Configuring Uplinks To A Vnet (Lacp) - HP Integrity BL890c - i2 Server Manual

Scenario 1:6 – VLAN Tagging (802.1Q) with
Multiple Shared Uplink Sets (SUS) and Link
Aggregation using LACP (802.3ad) – VMware
ESX

Overview

This configuration uses the Virtual Connect Shared Uplink Set (SUS). The SUS provides the ability to
present a single or multiple VLANs to a server NIC. In this scenario, the upstream network switches
present several VLANs to two ports on each VC module.

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).
Scenario 1:6 – VLAN Tagging (802.1Q) with Multiple Shared Uplink Sets (SUS) and Link Aggregation using LACP (802.3ad) –
VMware ESX 73