Summary; Results - HP Integrity BL890c - i2 Server Manual

Virtual connect ethernet cookbook:single and multi enclosure domain (stacked) scenarios
Hide thumbs Also See for Integrity BL890c - i2 Server:
Table of Contents

Advertisement

Summary

We created a couple different Virtual Connect Network solutions; base initially for bandwidth, which also
provided additional availability. Two VC networks were created, both with a single active uplink. We
later added two additional links; this increased the network bandwidth to the Virtual Connect networks,
while still maintaining availability.
When VC profile App-1 is applied to the server in bay1 and is powered up, it has two NICs connected to
"vNet-PROD-1" and "vNet-PROD-2", which connects to the network infrastructure through a two 1Gb
uplinks. 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.
When additional bandwidth was required, additional uplinks were added to each vNet.
As additional servers are added to the enclosure, simply create additional profiles, configure the NICs for
vNet-PROD-1 and vNet-PROD-2 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-29 Both NICs for Profile App-1are connected to the network through vNet-PROD-1 or vNet-PROD-2.
Scenario 1:2 – Multiple Simple Networks with Active\Active Uplinks and Optional Link Aggregation 802.3ad (LACP) - Windows
38

Advertisement

Table of Contents
loading

This manual is also suitable for:

Virtual connect

Table of Contents