Summary; Result - HP Integrity BL890c - i2 Server Manual

Summary

This profile will present NIC 1 to network "PROD-A-1" & NIC 2 to network PROD-A-2 which are mapped
to VLAN 101 (management network); frames for VLAN 101 will be passed to NICs 1&2 untagged. NICs
3&4 are connected to "Multiple Networks" (Production VLANs), PROD-B-1 – PROD-E-1 and PROD-B-2 –
PROD-E-2, which are mapped to VLANs 102 – 105; frames will be passed to NICs 3&4 will be tagged.
If additional NICs are required, simply add the NICs to the server profile, this configuration will support
up to 8 NICs without adding additional hardware. If the performance demands of a NIC change, the
speed of a NIC could be adjusted up or down
When the blade occupying enclosure Bay 1 is powered up, it will have 4 physical NICs connected to
networks, PROD-A-1, PROD-A-2, PROD-B-1 and PROD-B-2. If additional NICs are required, simply go to
the virtual connect profile and add the required number of NICs, configure them for the appropriate
networks, speed and apply the profile. Verify the configuration change through the OA, VCEM and/or
ILO.
In order for Hyper-v to provide network redundancy Windows NIC teaming will be utilized. It is
important to note that the Hyper-V role should be installed BEFORE the HP ProLiant Network teaming
Software is installed.

Result

The following graphics provide an example of a Windows 2008R2 server with 4 NICs configured and
connected to the VC Networks as discussed earlier. The Disabled network connections are the 4
remaining and un-configured FlexNICs.
This configuration has provided us with 4 NICs total. Two of the NICs are configured for a 2.5Gb link,
this will be connected to the management network. The last two NICs are configured for 7.5Gb link and
will be used to support several VLANs.
In order to provide network redundancy each of these NIC pairs will be teamed using the HP ProLiant
Network Teaming Software.
As Windows 2008R2 network adapter enumeration order is not clear, will need to determine with NIC is
connected to which VC module/port. In order to provide NIC teaming redundancy, we want to team
NIC a NIC connect to the VC module in Bay 1 with a NIC connected to the VC module in Bay 2. The
simplest way to determine which NIC is which, is by locating the MAC address of each NIC.
Open the Network Connections screen in Windows 2008R2, as in the following graphic. You can see
that four of the NICs are disconnected, this can be disabled in this interface as they are unused FlexNICs.
The remaining NICs should be identified by their MAC address. Rename each Connection with a name
that can be referred to later when building the NIC teams.
Scenario 2:2 - Flex-10 - VLAN Tagging (802.1Q) with Multiple Shared Uplink Sets (SUS) and Mapped VLANs - Windows 2008
Hyper-V 133