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

Server management 96
IMPORTANT: Be sure to review the following list of guidelines before creating and deploying
server profiles.
• The server blade firmware and option card firmware must be at a revision that supports Virtual Connect
profile assignment. See the HP website (
http://www.hp.com/go/bladesystemupdates ).
• Before creating the first server profile, select whether to use moveable, administered MAC addresses
and WWNs, or the local server blade factory default MAC addresses and WWNs.
• After an enclosure is imported into a Virtual Connect domain, server blades remain isolated from the
networks and SAN fabrics until a server profile is created and assigned.
• Server blades must be powered off to receive or relinquish a server profile assignment when using
Virtual Connect-administered MAC addresses or WWNs, or when changing Fibre Channel boot
parameters. When using Flex-10, there are special considerations for server power.
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 )."
• When assigning a VC-assigned serial number (logical), the server must be powered off.
• FC SAN connections appear in server profile screens only when there is an HP Virtual Connect Fibre
Channel Module in the enclosure managed by Virtual Connect. FC SAN connections are added in pairs
and cannot be deleted. If an HP Virtual Connect Fibre Channel Module is added to a Virtual Connect
domain with existing profiles, an option to add FC connections appears in the existing profiles during
editing.
• FCoE connections appear in server profile screens only when there is an HP VC Flex Fabric
10Gb/24-port Module in the enclosure managed by Virtual Connect. FCoE SAN connections are
added in pairs. If an HP VC Flex Fabric 10Gb/24-port Module is added to a Virtual Connect domain
with existing profiles, the user can use the add fcoe-connection command to add FCoE
connections.
• iSCSI connections are not added to server profiles by default. User action is required to add one or
more iSCSI connections. The GUI enables the creation of iSCSI connection only if at least one Flex-10
module exists in the domain. The CLI can be used to pre-provision this feature. For more information, see
"iSCSI offload and boot (on page 110 )." It is possible to have both iSCSI and FCoE connections on the
same server as they share the same Flex-10 (" Flex-10 overview " on page 98 ) physical function.
• 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.