HP Matrix Operating Environment 7.0 Release Notes

Minor issues
Performing operations on logical servers outside of Matrix OE visualization may cause
incorrect information to be displayed
If you use tools other than Matrix OE visualization to manage logical servers, modifications to the
underlying resources managed by logical server management are not immediately reflected in the
logical server.
For example, if you modify the power state of a managed resource outside of logical server
management, the power state of the logical server is displayed incorrectly until logical server
management resets its data.
Suggested action
Wait several minutes for the logical server to reset its data, or use Tools→Logical Servers→Refresh...
to manually refresh server resources.
Activating an Integrity VM virtual machine logical server with three or more vCPUs may
fail with entitlement error in VM Host
If you attempt to activate an Integrity VM logical server with three or more vCPUs on an Integrity
VM Host with 1596 Mhz processor speed or more, and the entitlement value used to create the
virtual machine on the VM Host falls below the minimum 5% value, the activation may fail with
the error “Value x.x for entitlement_min is below minimum, setting to 5.0.” This error is displayed
on the VM Host.
Suggested action
On the Integrity VM Host, set the Integrity VM configuration variable GUESTMHZMIN to the nearest
integer value that is five percent of the host processor speed in cycles. The following commands
can be used to perform the GUESTMHZMIN variable setting on the Integrity VM Host:
# typeset -i i j k
# i=$(hpvmstatus -sM | cut -d: -f3)
# j=i/20
# k=j*20
# if ((i>k)) ; then j=j+1 ; fi
# ch_rc -a -p GUESTMHZMIN=$j /etc/rc.config.d/hpvmconf
Unmanaging an active physical logical server with shared storage pool entry
If you unmanage a physical logical server that is currently active on a server with Virtual Connect,
and the logical server is configured with a shared storage pool entry, the logical server may be
automatically re-imported in a subsequent refresh unless the associated storage pool entry is deleted.
If the storage pool entry is defined as part of the logical server and is not shared, the storage pool
entry is automatically deleted when the logical server is unmanaged.
Suggested action
Immediately after unmanaging a logical server, delete its associated storage pool entry, or modify
the storage pool entry to remove the unmanaged logical server’s WWNs.
Modifying a catalog storage pool entry and unmasking the volume removes candidates
By default, the “Masked” checkbox is checked and grayed out when you create a SAN Catalog
Storage Entry on the Create Storage Pool Entry screen. After the volume is activated in SPM, if you
subsequently modify the storage pool entry, the user interface allows you to deselect the “Masked”
checkbox for newly added volumes. However, if you deselect “Masked” (thereby unmasking the
volume) and press Show Candidates, storage candidates are not displayed in the Candidates
drop-down menu for this new volume, and this sequence renders the volume and entire storage
pool entry unusable.
34 Issues and suggested actions