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

Virtual Connect server profiles 122
• Before creating the first server profile:
o Select whether to use assigned serial numbers or factory default serial numbers.
o Select whether to use movable, 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 are 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 or FlexFabric modules, there are special considerations for server
power.
• When assigning a VC-assigned serial number, the server must be powered off.
• FC SAN connections appear in server profile screens only when an HP Virtual Connect Fibre Channel
module is 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 when editing existing profiles.
• FCoE connections appear in server profile screens only when an HP VC Flex Fabric 10Gb/24-port
Module is 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, you can add FCoE connections.
• iSCSI connections are not added to server profiles by default. You must add one or more iSCSI
connections. The GUI enables the creation of iSCSI connections only if at least one Flex-10 or FlexFabric
module exists in the domain. The CLI can be used to pre-provision this feature. iSCSI and FCoE
connections cannot share the same physical Flex-10 port since they use the same 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.
• 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,