HP Virtual Connect for c-Class BladeSystem Version 3.00 Setup and Installation Guide for HP Integrity BL8x0c i2 Series Server Blades
Setup 10
4.
Connect Virtual Connect Ethernet 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 57)."
5. Connect data center FC fabric links (if applicable).
6. Note the default DNS name, user name, and password settings for the Virtual Connect Ethernet
module in interconnect bay 1, available on the module Default Network Settings label.
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/bladesystem/documentation).
8. Apply power to the enclosures. See "Default module configuration (on page 10)." See also the
appropriate HP BladeSystem enclosure setup and installation guide.
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.
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 40)."
11. 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 or the HP website (
http://www.hp.com/go/bladesystemupdates).
12. Access the HP Virtual Connect Manager using one of the following methods:
o Use a web link from within the HP Onboard Administrator graphical user interface or use the
dynamic DNS name from the Default Network Settings label. See "Accessing HP Virtual Connect
Manager (on page
65)."
o Access the Virtual Connect Manager 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/bladesystem/documentation).
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 Virtual Connect 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 explicitly configured within the Virtual Connect Manager. The following describes
the default module configuration prior to the creation of a Virtual Connect domain.
When not part of a Virtual Connect domain, each Virtual Connect Ethernet 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. Additional ports on that module can be aggregated using LACP to provide greater
bandwidth as long as they are connected to the same external switch. (For aggregation of links to an
external switch, the external switch must support dynamic creation of link aggregation groups using the