Operating Environment Software Instruction Manual

Troubleshooting communication failures
Troubleshooting communication failures.Issue
—Possible cause
Action
• Verify that the vCenter credentials are correct on Systems Insight Manager.
• Verify that the virtual machine hosts are correctly registered to Insight Control virtual machine
management usage and are not reporting issues on Systems Insight Manager
• Verify that Matrix OE is correctly displaying the resources (physical or virtual)
• Verify the Onboard Administrator credentials were added to enclosure node on Systems Insight
Manager
Correct any communication issues and then wait for the next synchronization cycle. The resources
should display correctly in the infrastructure orchestration Unassigned Pool.
Resources not displaying and increasing timeouts
One or more types of infrastructure orchestration resources (for example, virtual networks) are not
displayed in infrastructure orchestration's user interfaces.
Issue
Due to a large number of resources to fetch, one or more of
infrastructure orchestration's resource fetch operations may have timed
Possible cause
out, waiting for completion. By default, infrastructure orchestration
is configured to fetch resources of each type for up to 5 minutes.
On the CMS on which infrastructure orchestration is running, timeouts can be configured in the
hpio.properties file, located for example at: ..\Program Files\HP\Matrix
infrastructure orchestration\conf\hpio.properties.
Action
The primary timeout properties that might need to be increased are the following:
• timeout.get.serverpools
• timeout.get.subnets
For large numbers of Software Automation (SA) or deployment images, the property is
timeout.get.images.
Other timeout properties available to configure are the following:
• timeout.get.storagepools
• timeout.generate.storage.entry
• timeout.get.vmtemplates
• timeout.get.deployment.services
For example, to increase fetch subnets timeout from the default value of 5 minutes to
15 minutes, modify the line: timeout.get.subnets = 5 to: timeout.get.subnets =
15.
Manual clean-up process (physical)
If an infrastructure orchestration physical server deployment or delete service request fails, perform
a manual clean-up process, which includes the following:
• Fully erase the operating system from the boot disks.
• Detach the blade from the storage.
• Return the blade to an infrastructure orchestration server pool for a future provisioning request.
This type of failure forces the server blade to move to the infrastructure orchestration Maintenance
pool and the Matrix OE logical server is renamed with the prefix “Clean-me-”.
Corrective procedures 195