HP Insight Orchestration 6.0 User Guide

In Systems Insight Manager, the Insight Orchestration error page The HP Insight Orchestration tool cannot
be displayed appears when listing server pools exceeds a one-minute timeout.
Issue
Possible cause
• The physical server or virtual machine Hypervisor is not responding.
• The Insight Orchestration service is down.
• The network is slow or disconnected.
Action
• Verify that the physical servers and virtual machine Hypervisors are available
• Verify that the Insight Orchestration service is started.
• Verify that your network settings are configured correctly.
• Refresh the Servers page.
The Insight Orchestration notification emails contain a URL that does not appear as a link in Microsoft Outlook
2003.
Issue
—Possible cause
Manually copy and paste the URL link into a browserAction
Insight Orchestration does not send email notifications to users assigned to, or unassigned from, a server pool.Issue
—Possible cause
Verify that the oo.user.pool.notification.enabled = true is set in the hpio.properties. The
hpio.properties file is located on the CMS at ..\Program Files\HP\Insight Orchestration\conf.
Action
VI3 server is not configured in Systems Insight Manager or becomes unavailable.
Insight Orchestration may generate a large number of these messages causing the Insight Orchestration log file
to grow very rapidly.
Issue
If there are ESX hosts registered with Insight Control virtual machine managmement, but Virtual Center Credentials
are not configured on Insight Control virtual machine management , Insight Orchestration keeps logging an
error that Insight Control virtual machine management is not configured to communicate with Virtual Center.
Possible cause
Action
• Register the credentials with Insight Control virtual machine management (through Systems Insight Manager
Options→virtual machine management→Security→VMware Virtual Center Settings menu).
• Verify that the “VMware VirtualCenter Management Webservices” service is started.
• As a work-around (if you are not doing VM Provisioning on ESX) and this message is causing the Insight
Orchestration log file to grow rapidly, configure Insight Orchestration to HyperV only mode. This will avoid
logging the virtual machine management entries. To do this, change the following in the C:\Program
Files\HP\Insight Orchestration\conf\hpio.properties file:
##########################
HYPERVISORS ########################## # Set this value to true if
the only hypervisors in the managed environment is # MS Hyper-V
only.hyperv.hypervisors
= true
After updating the hpio.properties file, restart the Insight Orchestration service.
How can I find out more details about an error?Issue
—Possible cause
See the hpio-controller.log file located at .. Program Files\HP\Insight Orchestration\logs
on the CMS.
Action
IPV6 Automatic and Static IP address assignment methods do not work.Issue
This is a known defect.Possible cause
The Automatic and Static assignment types are selectable in Designer when a network is specified as IPV6,
however only DHCP works correctly for IPV6 with this version of Insight Orchestration.
Action
Installing the Insight Orchestration v1.0.2 patch may change log4j customizations.Issue
Miscellaneous issues 75