HP Virtual Connect 4Gb Fibre Channel Module for c-Class BladeSystem - Manual (Page 183)

Virtual Connect server profiles 183
mapped to LOMs 1 and 2 on blades 1 and 2. The next pair of entries for I/O bays 1 and 2 would get
mapped to LOMs 1 and 2 on the third blade, and the fourth set of entries for I/O bays 1 and 2 would get
mapped to LOMs 1 and 2 on the fourth blade.
To have FCoE entries mapped to LOMs 3 and 4 on each blade in the server, you must add three extra sets
of FCoE entries, and then add the additional entries for I/O bays 1 and 2. See ports 17-24 in the figure
below.
Creating FCoE HBA connections for a BL870c i4
Referencing the previous figures, entries 1-8 would be mapped as shown. Entries 9 and 10 would then be
mapped to LOMs 3 and 4 on the first blade in the BL870c i4, entries 11-12 would be as in this example
except that they would be UNMAPPED, and entries 13-14 would be mapped to LOMs 3 and 4 on the second
blade. The remaining entries would not be needed.
Limited Ethernet connections when using HP Virtual Connect Flex-10/10D modules
Introduction of the dual-hop FCoE support in VCM v4.01 enabled the ability to map newly created FCoE
connections to the HP VC Flex-10/10D module.
With the extension of the support for FCoE to Flex-10/10D modules, mapping of the Ethernet and FCoE
connections to the FlexNIC and FlexHBA ports on the FlexFabric adapters changed. In the newly created
profiles, if a FlexFabric adapter was found in a LOM or Flexible LOM location while being connected to a
Flex-10/10D module, the first FCoE connection was assigned to that adapter. In the previous releases only
Ethernet connections could be assigned to a FlexFabric adapter that was connected to a Flex-10/10D
module. Only an FCoE network created on a Shared Uplink Set originating on a Flex-10/10D module can
be assigned to the corresponding FCoE connection. FCoE connections that map to the FlexFabric modules
can be assigned to either an FC SAN Fabric or an FCoE Network created on a Shared Uplink Set originating
on this module.
All profiles created prior to the upgrade remain unchanged and continue to operate similar to pre-4.01
behavior.
Example: