HP Insight Orchestration 6.3 User Guide

Not all virtual resources are displayed under the Servers tab.Issue
Five minutes after clicking the refresh button, the Servers tab still shows no virtual hosts. (You can
see a TimeoutException from the getVMHostServerPools call in the stack trace within the
Possible cause
hpio-controller.log file on the CMS). This may be caused by environmental issues that cause
VMM to take an unexpectedly long time to communicate with some VM hosts, or by a large-scale
setup that takes VMM a long time to retrieve information from all VM hosts. VM hosts that respond
within the time period return their results to the Servers tab.
Check the hpio-controller.log file for warning messages of the form: ”Unable to get all VM
host data in the allotted time. The data from some hosts will not be returned.” and ”Unable to get
VM host data in the allotted time for host : <hostname>.”
Fix the environmental issues or increase the following timeout property settings. If a blade is not
expected to ever be available again for provisioning (especially under actions 3 and 4, above), it
can be moved to another server pool created especially for unavailable servers.
Action
1. Navigate to the ..\Program Files\HP\Insight Orchestration\conf\
hpio.properties file.
2. Set timeout.get.serverpools to a longer interval. (For example, for a 15 minute interval,
set timeout.get.serverpools=15).
3. Set timeout.get.vmhost to a longer interval, but less than timeout.get.serverpools.
(For example, for a 10 minute interval, set timeout.get.vmhost=10).
The value of timeout.get.vmhost should always be less than the value of
timeout.get.serverpools.
A check in ioassist failed to communicate with Insight Orchestration, generating a TimeoutException.Issue
There was a delay in Insight Control virtual machine management (VMM) responding with VM host
details.
Possible cause
Choose one of the following:Action
• In Insight Orchestration\conf\ioassist.properties, set timeout.await to a
value greater than 120 seconds.
• In a Windows Command Prompt, execute the ioassist command line.
The Insight Orchestration Server pools tree was not removed from Systems Insight Manager during
the Insight Orchestration uninstallation process.
Issue
Systems Insight Manager was not available when Insight Orchestration was being uninstalled.Possible cause
Action
• Stop the Insight Orchestration service.
• Manually remove the SIM collections.
• Start the Insight Orchestration service.
Corrective procedures
Manual clean-up process (physical)
If an Insight Orchestration physical server deployment or delete service request fails, you must
perform a manual clean-up process to fully erase the operating system from the boot disks, detach
the blade from the storage, and return the blade to an Insight Orchestration server pool for a future
provisioning request. With those failures, the server blade is moved to the Insight Orchestration
Maintenance pool and the Insight Dynamics logical server is renamed with the prefix “Clean-me-”.
112 Troubleshooting