HP Matrix Operating Environment 7.2 Update 1 Infrastructure Orchestration User Guide

Failure to add a service to a Matrix recovery management Recovery Group
An attempt to add a service to a Recovery Group fails and the following error message displays:Issue
Two or more services have the same name in different Organizations.
Service-ids are unique across organizations but service-names are not.
The service name is not unique across all organizations.Possible cause
Make sure that your service name is unique before trying to add the service to a Recovery Group.Action
When creating recoverable services, prefix the service name with your organization name and a
special character supported in service names to limit the possibility of non-unique service names.
The service name can contain up to 15 characters using letters (A-Z, a-z), numbers (0-9), and the
following special characters: space, underscore, and hyphen.
Matrix infrastructure orchestration times out while concurrently provisioning Integrity VMs
When infrastructure orchestration attempts to provision Integrity VMs, the request can take longer
than 60 seconds, causing a timeout.
Issue
The default timeout is 60 seconds.Possible cause
The timeout must be increased from the default of 60 seconds:Action
1. Configure the timeout by adding the following entry to the hpvmm.conf file, found in the
Insight Control virtual machine management\bin folder.
VirtQueryTimeout= <time in ms> i.e. XX000
The default value is 60000. Change this to a higher value.
2. Restart Insight Control virtual machine management by right-clicking Insight Control virtual
machine management, and then selecting Restart.
Service deletion
Physical service deletion
Matrix infrastructure orchestration Delete Service request leaves “clean-me” logical servers
Matrix infrastructure orchestration Delete Service request leaves “clean-me” logical serversIssue
If using Insight Control server deployment, the job “Erase ProLiant ML/DL/BL Array
Configuration {LinuxPE}” has not been modified for infrastructure orchestration.
Possible cause
If using Ignite-UX, the client has not been set up with permission to run the erase disk job in Systems
Insight Manager.
If using Insight Control server deployment, follow Step 9 in the Creating server deployment job
folders procedure. The job must have only two steps:
DetailsTask
Action
Wipe DiskRun Script
Shutdown (if
available)
Power Control
Service deletion 191