HP Insight Orchestration 6.3 User Guide

Insight Orchestration email messages such as approval and notification) are not sent.Issue
Possible cause
• SMTP configuration parameters are not correct.
• SMTP credentials are not correct.
• SMTP server is not responding.
• CMS is not able to communicate with SMTP server.
Action
• Make sure that the SMTP configuration parameters and credentials are correct. See “Specifying
SMTP credentials and system properties” (page 80).
• Check CMS and SMTP server connectivity.
• Check to make sure that the SMTP server is working correctly.
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 browser.Action
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
Access error on Insight Orchestration web pages from email notification using private network.Issue
In some cases, the administrator cannot access the approve/reject web page (and other HP Insight
Orchestration pages) from the notification email that asks the administrator to continue or reject a
Possible cause
user request. An access page error appears instead of the expected Insight Orchestration request
web page.
This error occurs when the HP Insight Orchestration CMS is configured to use a private network,
and the private network communicates with a public network. The private network is only accessible
from the HP Insight Orchestration CMS, and it is used to provision virtual and physical infrastructures.
Insight Orchestration notification email is set with the private network settings which does not allow
external access to the URLs contained in the notification email.
Action 1. Open HP Operations Orchestration Studio and log in using valid credentials.
2. Expand the Configuration node.
3. Expand the System Properties node.
4. Double click the HpioCmsIp property.
5. Click the Lock button to check out the property.
6. Update the property value to the hostname of the CMS.
7. Click Save and Check in.
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 management, but vCenter
Credentials are not configured on Insight Control virtual machine management , Insight Orchestration
Possible cause
108 Troubleshooting