HP Matrix Operating Environment 7.2 Update 1 Infrastructure Orchestration User Guide

NOTE: When using the mxnode command, enter the root/<root password> for the
provisioned server into the global credentials for Systems Insight Manager
(Options→Security→Credential→Global Credentials).
mxagentconfig –a –n <target IP or DNS name> –u <user> –p <password>
Where:
<user>
is root
<target IP or DNS name>
is the IP address of the newly created Systems Insight Manager node
<password>
is the root password of the newly created Systems Insight Manager node
An infrastructure service has been deleted, but I did not delete it
An infrastructure service has been deleted, but I did not delete it.Issue
Matrix infrastructure orchestration may be configured to remove infrastructure services when the
lease period expires. When an infrastructure service lease period expires and the service is deleted,
Possible cause
My History and Request Details displays a message stating the owner initiated the delete process
even though the delete process was triggered by the lease period expiring.
Email notices of lease expiration and service deletion can be sent one week, and then one day, in
advance of the event. The emails are sent to the address set in the Operations Orchestration System
Action
Property: HpioNotificationRecipients. Use Operations Orchestration Studio to set this
configuration parameter.
A delete request failed
A delete request has failed. The environment must be manually cleaned.Issue
—Possible cause
For virtual logical servers, infrastructure orchestration creates a folder under the virtual machine
Host with the same name as the infrastructure service provided by the user. This folder contains all
the folders and files corresponding to the virtual logical servers. Delete this folder and all its contents.
Action
For virtual logical servers, verify that all the virtual machines and the infrastructure folder name are
removed from the vCenter Server. Locate the infrastructure orchestration folder under the virtual
machine Host with the same name as the infrastructure provided by the user. Matrix infrastructure
orchestration creates the virtual machines under this folder. If these still exist, remove the virtual
machines and the infrastructure folder.
For physical logical servers, perform a manual clean-up process for the affected logical servers.
See “Manual clean-up process (physical)” (page 209).
Virtual service deletion
Matrix infrastructure orchestration unable to successfully reserve resources
In some circumstances, when processing a create request for a template containing a network
specified by attributes and a virtual logical server group, infrastructure orchestration may be unable
to successfully reserve resources even though they exist.
Issue
There is not a specific failure message for this issue, although the problem is indicated by a server
reservation failure message. The issue applies only to virtual logical servers.
Matrix infrastructure orchestration performs subnet allocation prior to server allocation. Consider
the following case:
Possible cause
Two subnets (Subnet1, Subnet2) match LogicalSubnetA.
Subnet1 is associated with VmHost1 and no others.
192 Troubleshooting