HP Matrix Operating Environment 7.0 Release Notes

Suggested action 1
Before adding servers to a VM cluster server group, ensure the Maximum number of sharers
is greater than or equal to the maximum number of servers (after the server is added) in the VM
cluster server group for the storage pool entry. To change this value:
1. Select the Matrix OE visualization logical server management Modify→Logical Server Storage
Pools screen and click Modify for the storage pool entry.
2. Increase the value of Maximum Number of Sharers and click Update Maximum Sharers,
then save the storage pool entry.
Suggested action 2
If the server was added without an available connection:
1. Select the Matrix OE visualization logical server management Modify→Logical Server Storage
Pools screen, and click Modify for the storage pool entry.
2. Increase the value of Maximum Number of Sharers and click Update Maximum Sharers.
3. In the Manage Server WWNs table at the bottom of the screen, check Ready for the newly
added server WWN and save the storage pool entry.
4. Deactivate the logical server.
5. Reactivate the logical server.
The Virtual Connect profile will then contain the correct server WWN with the logical server's data
storage pool entry.
Minor issues
Delete service request leaves "clean-me" logical servers when used with Integrity servers
if disk is not erased before delete service request
After successfully provisioning a physical Integrity server blade (using Ignite-UX, or through a
secondary CMS in a federated CMS environment), there are manual steps you must perform to
allow the disk to be erased during de-provisioning. Erasing the disk is part of a successful
de-provisioning (delete request) for an Integrity service.
If the disk is not erased, the delete service request may fail and “clean me” logical servers will
remain. In that case, a manual cleanup procedure is required. (See the Suggested action for the
cleanup procedure.)
Before you start a delete service request from infrastructure orchestration:
1. Make sure that the Integrity service was successfully provisioned (the Integrity service is running).
2. Discover the Integrity blade where the Integrity service is running using its IP address from
Systems Insight Manager. In a federated CMS environment, discover the Integrity blade on
the primary CMS using its IP address from Systems Insight Manager. The Integrity node's
identification information should contain the UUID and UUID (logical). You can discover the
blade in either of the following ways:
a. Use the Systems Insight Manager menu selection Options→Discovery..., or
b. Use the Systems Insight Manager command: mxnode -a <ip-address> -w
where <ip-address> is the IP address that was assigned to the Integrity blade after
provisioning.
Add the root login of the Integrity blade using the Systems Insight Manager menu selection
Options→Security→Credentials→System Credentials....
3. Set up an SSH connection between the CMS and the Integrity blade by entering the command:
mxagentconfig -a -n <ip-address> -u root -p <root password>
4. If the IP address was discovered on the primary CMS in a federated CMS environment (in
step 2 above), manually delete the Systems Insight Manager node.
Use the Systems Insight Manager command: mxnode -r <ip-address>
22 Issues and suggested actions