HP Matrix Operating Environment 7.0 Release Notes

Suggested action
If you did not perform the preceding steps before you started a delete request for the Integrity
service, the automatic delete service will not succeed completely. In that case, you must clean up
the logical server associated with the Integrity blade and manually erase the disk.
1. Power on the server blade. (The blade was powered off when delete service request completed
or failed.)
2. Perform steps 2 and 3 in the preceding section, if you did not do so before starting the delete
service request.
3. To erase the disk, enter the following command from the CMS where the discovery was
executed (in step 2 in the preceding section):
mxexec -t "Ignite Erase Disks" -n <ip-address>
4. If the IP address was discovered on the primary CMS in a federated CMS environment (in
step 2 in the preceding section), manually delete the Systems Insight Manager node.
Use the Systems Insight Manager command: mxnode -r <ip-address>
Service creation fails for physical requests when Windows Server OS is selected
Matrix OE infrastructure orchestration service creation fails when a physical template with Windows
Server OS is selected. This failure occurs when infrastructure orchestration times out waiting for
Insight Control server deployment to complete installation of Insight Management Agents on the
target server.
Suggested action
When a request fails, infrastructure orchestration automatically retries the request and a new server
is provisioned with the requested service. The original server is moved to the maintenance pool
and can be cleaned and moved back to a valid server pool. If the failure is observed frequently,
the following steps can be followed to disable the installation of Insight Management WBEM
providers. Insight Management SNMP agents continue to provide management capabilities when
WBEM providers are not installed.
1. Edit the install.cmd file, found under the <Insight Software installation>\rdp\
deployment server\hpfeatures\hpagents-ws\components folder.
2. Remove the following two lines:
call :installsc wbem%PROCESSOR_ARCHITECTURE%
if %cpresult% geq 1 set /a cpresults=cpresults+1
“Any Of” and “All Of” requirements in SPM are not displayed correctly in infrastructure
orchestration designer
Using SPM, you can define complex requirements with nested “Any of” (or) and “All of” (and)
constructs. These requirements are applied when provisioning storage in SPM, but infrastructure
orchestration designer does not display these requirements correctly. The IO template architect
may be allowed to enter values when defining storage that will cause storage provisioning to fail.
Suggested action
When using a specific SPM storage template in infrastructure orchestration designer, be aware of
the storage template's Capacity, RAID, and Tag requirements. Do not specify values that conflict
with these requirements.
Provisioning a service may fail when storage volumes in a logical server group contain
different tags
In an IO template, different storage tags can be assigned to the individual volumes in a logical
server group. When storage is auto-generated, each volume is provisioned based on a number
Infrastructure orchestration 23