HP Matrix Operating Environment 7.0 Release Notes

EXTENDEDFC Server profile has two or more FC Connections using the same connection
bay (with the same connectionBay attribute value), which identifies a server
profile created for an HP Integrity BL860c)
EXTENDEDFCOE Server profile has more than one Fibre Channel over Ethernet (FCoE)
connection associated with the same interconnect bay (IO bay)
ISCSI Server profile has at least one iSCSI connection
NAG Server profile has an associated Network Access Group
Applications that depend on IO hardware paths or legacy storage DSFs are not supported with
Integrity cross-technology logical servers
HP-UX applications that have a dependency on I/O hardware paths or Legacy Storage Device
Special Files (DSFs) might fail if these applications are running on Integrity cross-technology logical
servers. This occurs because I/O hardware paths and Legacy Storage DSFs may change during
cross-technology move operations. After a cross-technology logical server move operation,
Networking I/O Instance Numbers and Storage Agile DSFs will not cause application failure.
Major issues
A new Integrity VM logical server may be assigned MAC addresses and/or server WWNs belonging
to previously unmanaged Integrity VM logical servers, resulting in duplicate MAC addresses and/or
server WWNs
If you unmanage an Integrity VM logical server, then create a new Integrity VM logical server,
MAC addresses and/or WWNs from the unmanaged logical server may be assigned to the new
logical server resulting in duplicates. If this new logical server is then activated on the same Integrity
VM host as the host containing the previously unmanaged Integrity VM logical server, an activation
error occurs due to a conflict with a duplicate MAC address and/or server WWN assigned to the
unmanaged Integrity VM logical server. Additionally, the previously unmanaged Integrity VM
logical server cannot be imported again until the newly created logical server that introduced the
duplicate MAC addresses and/or server WWNs is corrected or deleted.
Suggested actions
• To prevent duplicate MACs and/or WWNs:
If possible, use the Delete action rather than the Unmanage action when removing an
Integrity VM logical server.
◦
◦ If possible, re-import any previously unmanaged Integrity VM logical servers.
◦ If you must unmanage an Integrity VM logical server, you may reserve its WWNs and
MAC addresses to prevent them from being reassigned by using this procedure:
1. Determine the WWNs of the unmanaged Integrity VM logical server by logging onto
the VM host and using the hpvmstatus command:
hpvmstatus –P Name_of_Unmanaged_VM | grep npiv
Sample output:
hba avio_stor 0 1 npiv /dev/fclp0-0x5001438002A30041,0x5001438002A30044
Make a note of the server WWNs, converting them to lsmutil format. In this example,
0x5001438002A30041 and 0x5001438002A30044 become
50:01:43:80:02:A3:00:41 and 50:01:43:80:02:A3:00:44.
2. If using Storage Pool Entries (SPEs), delete the SPE containing the WWNs of the
unmanaged Integrity VM logical server.
3. Reserve the WWNs that belonged to the unmanaged Integrity VM logical server by
using the lsmutil –reserve –WWN WWN command (where WWN is the worldwide
name that you made note of in Step 1. Issue this command once for each of the
WWNs associated with the unmanaged Integrity VM logical server.
32 Issues and suggested actions