HP Matrix Operating Environment 7.3 and 7.3 Update 1 Infrastructure Orchestration User Guide

Matrix infrastructure orchestration Windows service
Matrix infrastructure orchestration may time out while waiting for the server to be recognized
Matrix infrastructure orchestration may time out while waiting for the server to be recognized.Issue
Long server post times, particularly when using the BL620c G7 or the BL680c G7.Possible cause
To avoid this issue on any server:Action
1. Edit ..\Program Files\HP\Matrix infrastructure orchestration\conf\
hpio.properties and set the retry.count.ares.pxe parameter to a value greater than
30.
2. Restart the HP Matrix infrastructure orchestration service.
HP Matrix infrastructure orchestration service may not start automatically after a system restart with
error Unable to retrieve database password from mxpassword
HP Matrix infrastructure orchestration service may not start automatically after a system restart. The
following error is displayed: Unable to retrieve HPIO's database password from
mxpassword.
Issue
When the CMS is under a high usage (mostly during services startup), the Systems Insight Manager
mxpassword command can take more than one minute to return, causing a failure during
infrastructure orchestration startup pre-conditions checking.
Possible cause
Perform one of the following actions.Action
• Manually start the HP Matrix infrastructure orchestration service after other services have
completed startup.
• Increase the timeout and the number of attempts performed by IO to retrieve the required
information. Increase the following properties in ..\Matrix infrastructure
orchestration\conf\hpio.properties
◦ launcher.mxpasswd.retry.count
Number of times that IO executes the mxpassword command if it fails. Default is 6.
◦ launcher.mxpasswd.retry.timeout
Time, in seconds, between each attempt. Default is 30 seconds.
CMS crash recovery
Create Service request does not complete successfully after CMS crash recovery
Create Service request does not complete successfully when resumed after CMS is recovered from
a crash. Manual steps recommended by IO are inadequate to recover the logical server and re-issue
the request successfully.
Issue
VCEM and Virtual Connect Manager (VCM) are out of sync due to a CMS crash that occurred
while assigning a server profile.
Possible cause
Action
• Perform VC Domain maintenance. See HP Virtual Connect Enterprise Manager User Guide for
more information.
• Delete the clean-me-<LS>logical server for any that are listed.
• Move the blade from Maintenance to another server pool which frees up the server IP address
and marks the blade as available.
• Refresh server resources from logical server management.
• Re-issue the infrastructure orchestration Create Service request.
228 Troubleshooting