HP Matrix Operating Environment 7.3 Update 1 Release Notes

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.
4. Create a placeholder logical server to prevent the MAC addresses from
being assigned to new logical servers:
1. Create a new logical server template without specifying any storage
entries in the storage configuration.
2. In the network selection page, click Add Network Entries.
NOTE: LSM shows the MAC addresses that were part of the
unmanaged logical server.
3. Click Next and then Finish to create the logical server template.
This Integrity VM logical server template cannot be activated because
it lacks storage entries, but the new template prevents the MAC
addresses of the unmanaged logical server from being used again.
You may now create and activate Integrity VM logical servers.
• To correct duplicate MAC and/or WWNs:
1. Delete the newly created Integrity VM logical server (after backing up its data,
if necessary).
2. Perform one of the procedures described above under To prevent duplicate
MACs and/or WWNs.
You may now create and activate Integrity VM logical servers.
HP Logical Server Automation service may run out of memory on large scale systems
On large scale systems, with large numbers of managed nodes and/or large numbers
(1000+) of logical servers on a 64-bit CMS, the HP Logical Server Automation service
may run out of memory and display out of memory errors in the /logs/
hp_lsa_service.log or /logs/vselog.lsm.log file. You may see the following
errors:
java.lang.OutOfMemoryError: GC overhead limit exceeded
java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: PermGen space
For more information, see “Configuring HP Insight Management for large environments”
in the HP Insight Management 7.3 Installation and Configuration Guide at Enterprise
Information Library.
44