HP Virtual Connect 1.10Gb-F Ethernet Module for c-Class BladeSystem - Manual (Page 9)

Setup 9
Pre-deployment planning
During the planning phase, the LAN and server administrator must determine how each server blade will
connect to the network and in which IP network and VLAN the server will reside. In a traditional network,
these connections are 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. In the event of a
server blade failure or move, 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 additional information, see "Firmware
requirements (on page 35 )."
• Be sure that OA, iLO, server blade system ROM, Ethernet option ROM, and FC option ROM
firmware are up-to-date. For additional information, see the HP Virtual Connect Release Notes and
Compatibility Matrix and 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 ).
• Determine the Ethernet stacking cable layout and ensure that the proper cable and transceiver
options are ordered. Stacking cables allow any Ethernet NIC from any server to be connected to any
of the Ethernet networks defined for the enclosure.
o For information on cable layout, see "Recommended stacking connections (on page 43 )."
o For information on supported cable and transceiver options, see the Virtual Connect module
QuickSpecs on the HP website (
http://www.hp.com ).
• Determine which Ethernet networks will be connected to or contained within the enclosure.
Most installations will have multiple Ethernet networks, each typically mapped to a specific IP subnet.
The HP Virtual Connect Manager enables definition of up to 64 different Ethernet networks that can
be used to provide network connectivity to server blades. Each physical NIC on a server blade can
be connected to any one of these Ethernet networks.
Virtual Connect Ethernet networks can be completely contained within the enclosure for server-to-
server communication or connected to external networks through rear panel ports (uplinks). For each
network, the administrator must use the Virtual Connect Manager to identify the network by name
and to define any external port connections.
• Determine which Fibre Channel fabrics will be connected to the enclosure.
Each uplink has a capability of aggregating up to 16 server HBA N-port links into an N-port uplink
through the use of NPIV.
• Coordinate with data center personnel to ensure Ethernet network cable connections and Fibre
Channel cable connections to the enclosure are installed or scheduled to be installed.
• Determine the Ethernet MAC address range to be used for the servers within the enclosure.