HP Virtual Connect for c-Class BladeSystem Version 3.30 User Guide

Virtual Connect server profiles 122
In a multi-enclosure environment, all enclosures must have the same VC-FC and FlexFabric module
configuration. For example, if the local enclosure has VC-FC modules in bays 3 and 4, each remote
enclosure must also have VC-FC modules in bays 3 and 4. This is called an FC bay group. Support for FC bay
groups with FlexFabric modules is similar to support for existing VC-FC modules. FlexFabric module bay
groups cannot contain any other type of VC-FC module, and any other VC-FC bay group cannot contain a
FlexFabric module. These module types are incompatible in the same bay group. For more information, see
the HP Virtual Connect for c-Class BladeSystem Setup and Installation Guide on the Installing tab of the HP
BladeSystem Technical Resources website (http://www.hp.com/go/bladesystem/documentation).
When an available port is used for Ethernet, it is no longer available for FC configuration, and vice-versa.
Likewise, a port that is removed from a network, shared uplink set, or fabric becomes available for
configuration of another network or fabric.
The FlexFabric VC module requirements also imply some additional constraints with current VC FC
requirements for bay groups. When a network is configured on a FlexFabric module using FC-capable ports,
those ports across the bay group are configured as Ethernet ports, becoming unavailable for FC. The similar
case applies when selecting the port type as FC.
There is a limitation on the NC551i LOM and the NC551m mezzanine card. FCoE and iSCSI connections
are not supported on the same adapter at the same time. By default, if a FlexFabric module is found in the
enclosure, FCoE connections are created for each server profile. If you do not wish to configure FCoE
connections, delete the default connections to allow the ports to be used for other connections, such as iSCSI
or additional Ethernet connections. To delete the connections, right-click the connection, and then select
Delete Connection.
There are additional limitations with the supported LOMs and mezzanine cards that support FlexFabric
configurations. Both FCoE boot and PXE can be configured on the same port with the NC551i LOM and the
NC551m mezzanine card on different physical functions. Alternatively, iSCSI and PXE can be configured on
the same port. Only one PF can be configured for FCoE on a port.
When configuring FCoE connections, the port speed can be set to 1Gb, 2Gb, 4Gb, 8Gb, custom, or
disabled. The port speed is limited to a total of 10Gb, which must be shared between all defined connections
for that port. The custom speed allows you to better control the bandwidth between FC and Ethernet
connections. Valid custom speeds are between 100Mb and 10Gb, in 100Mb increments. After all
connections are defined for a port, the actual allocated bandwidth is calculated by VCM. For bandwidth
information, see “Bandwidth Assignment (on page 126)."
PXE settings
Virtual Connect Manager v1.20 and higher supports three PXE options:
• Enable—VC Manager sends a configuration update to the mezzanine NIC or embedded NIC
associated with the port to enable PXE operations.
• Disable—VC Manager sends a configuration update to the associated mezzanine NIC or embedded
NIC to disable PXE operations.
• Use BIOS—Current BIOS settings are used for embedded NICs and mezzanine NIC PXE operations.
VC Manager makes no changes to the current settings.
This is not applicable to Flex-10 LOM ports when used with Flex-10 interconnect modules. In this
situation, the USE-BIOS option for PXE boot in a VC profile always allows a server to PXE boot from a
LOM port irrespective of the initial LOM settings in the BIOS utility (F9 screen).
HP BladeSystem c-Class server blades have a factory default configuration for PXE to be enabled on
embedded NIC 1 only, included as the last entry in the RBSU IPL priority list (boot order). VC Manager and