HP Insight Orchestration 6.3 User Guide

keeps logging an error that Insight Control virtual machine management is not configured to
communicate with vCenter.
Action
• Register the credentials with Insight Control virtual machine management using the Systems
Insight Manager Options→VMware® vCenter Settings menu.
• Verify that the “VMware vCenter 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 Hyper-V only
mode. This will avoid logging the virtual machine management entries. To do this, change the
following in the ..\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
Insight Orchestration provides a set of default values for the parameters listed below because some
combinations can cause memory leaks. If you have made log4j customizations to Insight
Possible cause
Orchestration 1.0.2 and are upgrading to Insight Orchestration 6.2, you could lose your
customizations.
Before installing the patch you should backup the following log4j parameters so that you can
restore the customizations in the event of a patch uninstall.
Action
• log4j.appender.dailyFile=org.apache.log4j.RollingFileAppender
• log4j.appender.dailyFile.DatePattern='.'yyyy-MM-dd
• log4j.appender.ws=org.apache.log4j.DailyRollingFileAppender
• log4j.appender.ws.File=logs/hpio-ws.log
• log4j.appender.ws.DatePattern='.'yyyy-MM-dd
• log4j.appender.ws.layout=org.apache.log4j.PatternLayout
• log4j.appender.ws.layout.ConversionPattern=%d [%-18t] %-5p %C.%M -
%m%n
• log4j.category.com.hp.hpio.nbapi.service=INFO, ws
Cannot install Operations Orchestration Studio. The following error is displayed: Studio version:
9.00 does not match Central version: 2.0. Setup will exit.
The correct version of Operations Orchestration Studio is installed on the CMS based on the OS
type (32-bit or 64-bit) during the installation of Insight Orchestration. However, the gear icon in the
Issue
Miscellaneous issues 109