HP Virtual Connect for c-Class BladeSystem Version 3.00 Setup and Installation Guide for HP Integrity BL8x0c i2 Series Server Blades

Setup 8
By stacking (cabling) the Ethernet modules within the domain and connecting the FC modules to the same
set of FC SANs, every server blade in the domain can be configured to access any external network
connection. With this configuration, the administrator can use Virtual Connect Manager to deploy and
migrate a server blade profile to any server in the Virtual Connect domain without changing external LAN
or SAN configurations.
Using multiple enclosures
Multiple enclosure support enables up to four c7000 enclosures to be managed within a single Virtual
Connect domain for a total of 128 servers, if double-dense support is enabled. Multiple enclosure
domains are not supported on c3000 enclosures. The VC-Enet modules use stacking cables between
enclosures so that network traffic can be routed from any server Ethernet port to any uplink within the VC
domain.
By stacking (cabling) the Ethernet modules within the domain, every server blade in the domain can be
configured to access any external network connection. Fibre Channel modules within different enclosures
are each connected directly to the same set of FC SANs. With this configuration, the administrator can
use Virtual Connect Manager to deploy and migrate a server blade profile to any server in the Virtual
Connect domain without changing external LAN or SAN configurations.
Using multiple c7000 enclosures, you can install up to 16 VC-Enet modules and up to 16 VC-FC modules
in the same domain, with a maximum of 8 VC-Enet or 4 VC-FC modules per enclosure.
The management interfaces for all enclosure OAs and VC modules within the same VC domain must be
on the same lightly loaded subnet. The OA IP addresses used must be configured to be static.
Pre-deployment planning
During the planning phase, the LAN and server administrator must determine how each server blade will
connect to the network and on which IP network and VLAN the server will reside. In a traditional network,
these connections are established through physical cables. If a move from one network to another is
required, the cables must also be moved. Virtual Connect provides a wire-once implementation when VC
modules are connected to upstream or core switches and the VC networks and server profiles are defined.
Assigning a server profile to a server blade completes the physical connection to the core network. If a
server blade fails or moves, all of the configuration parameters can be transferred easily to the new
server.
Before beginning installation, complete the following tasks:
• Be sure that the firmware revisions on all Virtual Connect modules in the domain are at the same
revision level. The active Virtual Connect manager does not allow incompatible modules to be
managed as part of the same Virtual Connect domain. For more information, see "Firmware
requirements."
• Be sure that OA, iLO, server blade system ROM, Ethernet option ROM, and FC option ROM
firmware are up-to-date. For more information, see the HP Virtual Connect Release Notes and
Compatibility Matrix on the HP website (
http://www.hp.com/go/bladesystemupdates).
• Determine which mezzanine cards, HBAs, and interconnect modules are going to be used and
where they will be installed in the enclosure. For installation and information on mapping server
ports to interconnect bays, see the appropriate HP BladeSystem enclosure setup and installation
guide on the HP website (
http://www.hp.com/go/bladesystem/documentation).