HP Matrix Operating Environment Software - Manual (Page 103)

No virtual resources are displayed under the HP IO Servers tab. Issue
Five minutes after clicking HP IO UI Servers refresh button, the HPIO Servers tab still shows
no virtual hosts (you can see a TimeoutException from the HPIO getVMHostServerPools call in
the stack trace within the 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. Possible cause
Fix the environmental issues or increase the timeout property setting within HPIO. 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 of unavailable servers.
1. Navigate to the C:\Program Files\HP\Insight Orchestration\conf\
hpio.properties
file.
2. Set timeout.get.serverpools to a longer interval (for a 15–minute interval, for example,
set timeout.get.serverpools=15 ).
Action
A check in HPIO's 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:
• In Insight Ochestration\conf\ioassist.properties, set timeout.await to a
value greater than 120 seconds.
• In a Windows Command Prompt, execute the ioassist command line.
Action
The HPIO Server pools tree was not removed from HP SIM during the Insight Orchestration
uninstallation process. Issue
HP SIM was not available when Insight Orchestration was being uninstalled. Possible cause
• Stop the Insight Orchestration service.
• Manually remove the SIM collections.
• Start the Insight Orchestration service.
Action
Corrective procedures
Manual clean-up process
If an Insight Orchestration physical server deployment fails or Insight Orchestration delete service
request fails, you must perform a manual cleanup 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-”.
The server profile and boot disk are preserved, enabling an administrator to determine the cause
of the failure and perform any required maintenance before returning the server blade to a user
pool. Manual clean-up of the failed server blade depends on the deployment server used to
provision it.
For Insight Control server deployment:
Corrective procedures 103