HP Virtual Connect for c-Class BladeSystem Setup and Install Guide

Planning the installation 12
3. Install stacking links ("Recommended stacking connections" on page 23).
4. Connect the VC-Enet module uplinks to data center networks. The network administrator should have
already installed the network cables into the rack with the proper labels. See "Connecting Virtual
Connect Ethernet module uplinks (on page 42)."
5. Connect data center FC fabric links (if applicable).
6. Note the default DNS name, user name, and password settings for the primary VC module, available
on the module Default Network Settings label.
The primary VC module is the first VC-Enet module in an odd-numbered interconnect bay.
7. Note the default DNS name, user name, and password for the HP Onboard Administrator, available on
the module Default Network Settings label. See the HP BladeSystem Onboard Administrator User
Guide on the HP website (http://www.hp.com/go/oa).
8. Apply power to the enclosures. See "Default module configuration (on page 12)." Also see the
appropriate HP BladeSystem enclosure quick install instructions on the HP website
(http://h17007.www1.hp.com/us/en/enterprise/servers/solutions/info-library/index.aspx?cat=bla
desystem).
9. Use the HP Onboard Administrator for basic setup of the enclosures (including enclosure name and
passwords). See the HP BladeSystem Onboard Administrator User Guide on the HP website
(http://www.hp.com/go/oa).
10. Be sure that all Virtual Connect interconnect module management interfaces and server blade iLO
interfaces have valid IP and gateway addresses using one of the following methods:
o Run DHCP on the management network connected to the Onboard Administrator.
o Configure the Onboard Administrator to set enclosure bay IP addresses. See "Virtual Connect and
EBIPA (on page 22)."
11. Be sure that OA, iLO, server blade system ROM, Ethernet option ROM, and FC option ROM firmware
are current.
12. Access VCM using one of the following methods:
o Use a web link from within the Onboard Administrator GUI or use the dynamic DNS name from the
Default Network Settings label. See "Accessing HP Virtual Connect Manager (on page 55)."
o Access the VCM CLI remotely through an SSH session. See the HP Virtual Connect Manager
Command Line Interface User Guide on the HP website (http://www.hp.com/go/vc/manuals).
IMPORTANT: For proper management of enclosure devices there must be an Ethernet
connection from the Onboard Administrator module to the external management network. For
information on Onboard Administrator module cabling, see the HP BladeSystem Onboard
Administrator User Guide.
Default module configuration
When VC modules are inserted into an enclosure that is not yet part of a Virtual Connect domain, the
modules are configured to provide basic connectivity. After a Virtual Connect domain is defined for an
enclosure, server blades within that enclosure are isolated from all external network and fabric connections
until configured explicitly within VCM.
When not part of a Virtual Connect domain, each VC-Enet module is configured so that all server ports
connected to that module are connected to a single network, which is then connected to a single uplink. To
provide greater bandwidth, you can use LACP to aggregate additional ports on that module, as long as they
are connected to the same external switch. For aggregation of links to an external switch, the external switch