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

Server management 97
• If the VC domain is configured for double-dense server mode, and a profile is assigned to an empty
server bay, then a hot-plug installation of a single-dense server into that server bay results in the profile
not being activated. To recover the profile, unassign the profile, and then reassign it.
• During a profile assignment, if the port number of an existing fabric has been changed to another
physical port, the fabric and the domain will go into a failed state until the reconfiguration is complete.
This also may result in SNMP traps being sent to report the interim failed state.
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,
and 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 boot and gain access to the network and fabric
when the server and interconnect modules are ready.
If a server blade is installed in 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 on 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.
IMPORTANT: Before assigning a profile, unassigning a profile, or modifying a profile, be sure to
review the "Server blade power on and power off guidelines (on page 145 )."
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 “Bays 1-4
(HP Integrity BL890c i2)”. This is true in the left navigation tree, in the Server Bays summary screen, in the list
of bays that a profile can be assigned to in the Edit Server Profile screen, and so on.
A profile is assigned to an entire multi-blade server, not to the individual blades in the server. If a profile is
assigned to an auxiliary blade (for example, a profile is assigned to an empty bay and then a multi-blade
server is installed) that profile is ignored (in this case it’s the same as a profile assigned to a covered bay).
In such a case VCM identifies the bay that the profile is assigned to as “Covered – Auxiliary”.
VCM maps the profile connection entries to ports on the blades in a multi-blade server as follows: