Scenario 1:1 – Simple vNet with Active/Standby Uplinks and Optional Link Aggregation 802.3ad (LACP) - Windows 23
Figure 1-12
Link aggregation confirmed - Bay 2.
Summary
We created a couple different Virtual Connect Network solutions; base initially for availability, one link
was active while the second was in standby mode. We later added two additional links; this increased
the network bandwidth to the Virtual Connect network, while still maintaining availability.
When VC profile App-1 is applied to the server in bay1 and is powered up, it has one NIC through each
module connected to “vNet-PROD”, which connects to the network infrastructure through a pair of 1Gb
uplinks. These NICs could now be configured as individual NICs (
Figure 1-8
) with their own IP address or
as a pair of TEAMED NICs (
Figure 1-9
). Either NIC could be active. As a result, this server could access
the network through either NIC or either uplink cable, depending on which is active at the time.
When additional bandwidth was required, additional uplinks were added to the existing vNet, this
process had no effect on the server profile.
As additional servers are added to the enclosure, simply create additional profiles, or copy existing
profiles, configure the NICs for vNet-PROD 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.
