The I/O connection profile, or server profile, provides a link between the server and the networks and fabrics defined in VC. The server profile can include MAC and WWN addresses, as well as boot parameters for the various connection protocols supported by VC. After being defined, the server profile can be assigned to any server blade within the Virtual Connect domain. VCM supports up to 256 profiles within the domain. A Virtual Connect server profile consists of connections that group attributes related to server connectivity for the various protocols supported by Virtual Connect modules. These protocols are Ethernet, iSCSI, Fibre Channel over Ethernet (FCoE), and Fibre Channel.
•
For Ethernet connections, VC provides the ability to assign VC-assigned MAC addresses and configure PXE boot settings as well as allocate bandwidth on Flex-10 connections.•
For iSCSI connections, VC provides the ability to assign VC-assigned MAC addresses and configure iSCSI boot settings as well as allocate bandwidth. This protocol is only available on Flex-10 server ports that support iSCSI.•
For FCoE connections, VC provides the ability to assign VC-assigned WWN and MAC addresses and configure Fibre Channel boot settings and bandwidth. This protocol is only available on FlexFabric server connections.•
For FC connections, VC provides the ability to assign VC-assigned WWN addresses and configure Fibre Channel boot settings.
IMPORTANT: The term "server blade" also applies to HP Integrity multi-blade servers. For more information on multi-blade servers, see "Multi-blade servers (on page 159)."
When a server profile is assigned to a server blade, VCM configures the connections with the appropriate MAC/WWN addresses and boot settings. USE BIOS is an option for all connection boot settings that preserves the options set in the RBSU or through other configuration utilities. Virtual Connect Manager automatically connects the server blade Ethernet, iSCSI, FCoE, and Fibre Channel ports to the specified networks and SAN fabrics. This server profile can then be re-assigned to another server blade as needed, while maintaining the server's network and SAN identity and connectivity.
VCM can be configured so that server blades use server factory default MACs/WWNs or Virtual
Connect-administered MACs/WWNs. These administered values override the default MAC addresses and WWNs when a server profile is assigned to a server, and appear to pre-boot environments and the host operating system software as the hardware addresses. To use administered MAC/WWN addresses, select a range of HP pre-defined or user-specified MAC addresses.
Review the following list of guidelines before creating and deploying server profiles:
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 272)."
•
The server blade firmware and option card firmware must be at a revision that supports Virtual Connect•
Before creating the first server profile, do the following: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-portModule or HP VC Flex-10/10D Module is in the enclosure managed by Virtual Connect. FCoE SAN connections are added in pairs. If either of these modules 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 afterthe 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, the MAC addresses and WWNs for the blade 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.