HP 1.10GB Virtual Connect Ethernet Module for c-Class BladeSystem - Manual (Page 93)

Server management 93
Virtual Connect domain that has existing profiles, an option to add FC connections appears in the
existing profiles during editing.
• Some server profile SAN boot settings (controller boot order) are applied by Virtual Connect only
after the server blade has been booted at least once with the final mezzanine card configuration.
• If PXE, controller boot order, or SAN boot settings are made outside of Virtual Connect (using RBSU
or other configuration tools), Virtual Connect will restore the settings defined by the server profile
after the server blade completes the next boot cycle.
• To boot properly from SAN when using Linux and VMware ESX 3.0.1 and ESX 3.0.2, change the
QLogic QMH2462 4Gb FC HBA connection option to 'point-to-point only' in the QLogic BIOS
configuration utility. The Emulex LPe 1105-HP 4Gb FC HBA does not require using the 'point-to-point'
connection option to boot properly from SAN.
Server profiles are associated with a specific enclosure device bay. After a profile is assigned, the Virtual
Connect Manager configures the server blade in that device bay with the appropriate
MAC/PXE/WWN/SAN boot settings and connects the appropriate networks and fabrics. Server blades
that have been assigned a profile and remain in the same device bay do not require further Virtual
Connect Manager configuration during a server or enclosure power cycle. They will boot and gain access
to the network and fabric when the server and interconnect modules are ready.
If a server blade is inserted into a device bay already assigned a server profile, Virtual Connect Manager
automatically updates the configuration of that server blade before it is allowed to power up and connect
to the network.
If a server blade is moved from a Virtual Connect managed enclosure to a non-Virtual Connect enclosure,
local MAC addresses and WWNs are automatically returned to the original factory defaults. This feature
prevents duplicate MAC addresses and WWNs from appearing in the data center because of a server
blade redeployment.
NOTE: If you are using server factory default MAC addresses WWNs and default Fibre
Channel boot parameters, you do not have to power off a server to make any profile
changes. If you are using HP assigned or user assigned MAC addresses or WWNs, you must
power a server off when moving a profile to the server or away from the server.
Multi-blade servers
Certain HP Integrity server blades can be conjoined using a Scalable BladeLink (SBL) to create a single
server. These servers are treated just like other server blades even though they are comprised of several
physical server blades.
IMPORTANT: The term server blade, when applied to a multi-blade server, means the entire
conjoined server, and not just a single server blade. For example, "a server profile is
assigned to a server blade" means that a single server profile is assigned to an entire multi-
blade server.
In each multi-blade server there is one blade that is identified as the monarch blade. The other blades are
referred to as auxiliary blades. In most multi-blade servers the lowest numbered bay in the server is the
monarch, but that is not always the case. Both the VCM CLI and GUI identify the monarch in the
information provided about a multi-blade server. All communication to a multi-blade server, such as to the
iLO user interface, is done through the monarch blade.
VCM displays multi-blade servers as a single entity showing the range of bays that comprise the server.
For example, if a multi-blade server occupies bays 1, 2, 3 and 4, then VCM represents the server as