User's Manual

FCoE SAN connections
The mapping of FCoE connection entries is much the same as the FC connection entry mapping,
but with a small twist. Each blade in the BL8x0c i4 family can have up to four embedded FCoE
ports active which would appear in the VCM server profile mapping as LOM:1-b, LOM:2-b,
LOM:3-b, and LOM:4-b. VCM will map FCoE connection entries from a profile to the Monarch
blade LOM1 and LOM2 first, then to any FCoE mezzanine cards on the Monarch. If there are still
entries in the profile, they will be mapped to the first Auxiliary blade LOM1 and LOM2 followed
by any FCoE mezzanine card ports on that blade. After all blades have had connection entries
mapped to LOM1, LOM2, and the FCoE mezzanine cards, if there are still entries left in the profile,
they will be mapped to the Monarch blade LOM3 and LOM4, then to the first Auxiliary blade
LOM3 and LOM4, and etc. until all FCoE connection entries have been mapped or the ports in
the server have been exhausted. The twist, then, is only in the mapping of FCoE connection entries
to LOM3 and LOM4 ports. If a profile assigned to the original server has no connection entries
mapped to LOM3 and LOM4, then the FCoE entries will remain mapped to the same ports on the
same blades after the upgrade. However, if there are FCoE connection entries mapped to LOM3
and LOM4 then those entries will get mapped to LOM1 and LOM2 ports on the new blades in the
upgraded server.
Below is an example upgrading a BL860c i4 to a BL870c i4 where VC-assigned WWNs are used
and the VCM server profile contains five FCoE connection entries. Notice that the first four entries
map to the same ports on both the original and the upgraded server, but the fifth entry, mapped
to LOM3 on the original server, is mapped to LOM1 of the Auxiliary blade in the upgrade.
Mapping to BL870c i4
ports
Mapping to BL860c i4
portsVCM assigned WWNAssigned SANProfile entry
Monarch LOM:1-bMonarch LOM:1-b50:06:0B:00:00:C3:26:10SAN-11
Monarch LOM:2-bMonarch LOM:2-b50:06:0B:00:00:C3:26:12SAN-22
Monarch MEZZ1:1Monarch MEZZ1:150:06:0B:00:00:C3:26:14SAN-33
Monarch MEZZ1:2Monarch MEZZ1:250:06:0B:00:00:C3:26:16SAN-44
Auxiliary LOM:1-bMonarch LOM:3-b50:06:0B:00:00:C3:26:18SAN-55
The WWN is assigned in this example by VCM (as opposed to using HW default WWNs) so the
WWN does not change, but the HW path as seen by HP-UX is different so this would be seen as
a new device. If the OS boot disk were attached on SAN-5, then the boot path in UEFI Boot
Manager would no longer be valid. If it's okay that the HW path has changed, then HP-UX could
be configured to use the new HW path and a new HP-UX boot path entry could be made in UEFI
Boot Manager, if necessary. If the HW path must remain the same, then four connection entries
can be added to the profile before assigning the profile to the upgraded server. This is shown
below.
Mapping to BL870c i4 portsVCM assigned WWNAssigned SANProfile entry
Monarch LOM:1-b50:06:0B:00:00:C3:26:10SAN-11
Monarch LOM:2-b50:06:0B:00:00:C3:26:12SAN-22
Monarch MEZZ1:1-b50:06:0B:00:00:C3:26:14SAN-33
Monarch MEZZ1:2-b50:06:0B:00:00:C3:26:16SAN-44
Auxiliary LOM:1-b50:06:0B:00:00:C3:26:18unassigned5
Auxiliary LOM:2-b50:06:0B:00:00:C3:26:1Aunassigned6
Auxiliary MEZZ1:1-b50:06:0B:00:00:C3:26:1Cunassigned7
Installing internal components 73