HP Virtual Connect 8Gb 24-port Fibre Channel Module for c-Class BladeSystem - Manual (Page 139)

Configuring the Virtual Connect domain using the CLI 139
• 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 restores the settings defined by the server profile after the
server blade completes the next boot cycle.
• After Virtual Connect assigns a server profile to a server, RBSU cannot modify the protocol configuration
(iSCSI/FCoE) for any NIC, including the NC551m, even if the NIC is not connected to a Virtual
Connect module. Any protocol configuration changes must be made before the server profile is
assigned to the server.
• 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.
• If the VC domain is configured for double-dense server mode and a profile is assigned to an empty
server bay, 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 go into a failed state until the reconfiguration is complete. This
also might 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 can 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.
Creating server profiles
To create a new server profile, use the add profile command:
>add profile MyNewProfile
To copy the configuration from one profile to another profile, use the following command:
>copy ExistingProfile MyNewProfile
After an enclosure is imported into a Virtual Connect domain, server blades that have not been assigned a
server profile are isolated from all networks to ensure that only properly configured server blades are
attached to data center networks.
A server profile can be assigned and defined for each device bay so that the server blade can be powered
on and connected to a deployment network. These profiles can then later be modified or replaced by another
server profile.