Scenario 1:4 – VLAN Tagging (802.1Q) with a Shared Uplink Set (SUS) with Link Aggregation using LACP (802.3ad) –
Windows 60
Summary
We created a Virtual Connect Shared Uplink Set (SUS), to support 4 VLANs (101-104). The SUS was
created with both Active and standby uplinks, to provide both additional bandwidth and availability.
When VC profile App-1 is applied to the server in bay1 and is powered up, it has two NICs connected to
“PROD-A”, which connects to the network infrastructure through a two (active) 1Gb uplinks. These NICs
are configured in VLAN 104, however, Virtual Connect is removing the VLAN tags and presenting the
frames as untagged, so the operating system does not need to understand which VLAN it is on.
These NICs could now be configured as individual NICs with their own IP address or as a pair of
TEAMED NICs. Either NIC could be active. As a result, this server could access the network through
either NIC or either uplink cable, depending on which NIC is active at the time.
As additional servers are added to the enclosure, simply create additional profiles, configure the NICs for
the appropriate network and apply them to the appropriate server bays.
Results
The following graphic provides an example of a Windows 2003 server with TWO NICs connected to the
network, each NIC has its own TCP/IP address, either or both NICs could be actively working on the
network.
Figure 1-52
Both NICs for Profile App-1are connected to the network through PROD-A.
The following graphics provide an example of a Windows 2003 server with TWO NICs teamed and
connected to the network. One NIC will be active, the other in standby, in the event of an Uplink, switch
or VC module failure; the teaming software will fail the NIC over to the alternate path, as required.
Figure 1-53
Team both NICs, using the HP Network Configuration Utility.
