HP Matrix Operating Environment 7.3 Release Notes

6. Select the line with the long name and click Remove.
7. Click Add, enter Matrix_Administrators and click Search. If no results are returned enter
HPIO_Administrators. Select the resulting group and click OK.
8. Repeat Step 3 but select the Matrix Architect link, then follow Step 4, Step 5 and Step 6. For
Step 7 click Add, enter Matrix Designers and click search. Repeat the search and enter
HPIO_Architects.
9. Repeat Step 3 but select the Matrix User link, then follow Step 4, Step 5 and Step 6. For Step
7 click Add, enter Matrix Users and click search. Repeat the search and enter
HPIO_Users.
Windows 2012 R2 Hyper-V Generation-2 VMs
Generation-2 VMs are not supported for use as VM templates. These VMs are also not supported
for Import VM functionality. If you try to import VMs, the following error message appears:
Import failed for Virtual Machine UUID Check that the VM Host is
configured appropriately with HP Insight Control virtual machine
management on the CMS and then refresh logical server virtual machine
resources.
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
Logical server management 39