HP Insight Dynamics 6.3 Release Notes

Clear browser cache after upgrade
After an upgrade to Insight Dynamics 6.3, or to a 6.3 update release, if your web browser cache
has not been cleared you may not be able to log into Insight Orchestration.
Suggested action
Clear your browser's cache (history) before launching Insight Orchestration after an upgrade.
Insight Orchestration service may not start automatically after system restart
The Insight Orchestration Windows service is occasionally unable to start, and displays the error
“Unable to retrieve HPIO's database password from mxpassword.” This error may occur when the
CMS is under high usage (often during services startup) in which the Systems Insight Manager
mxpassword command takes more than 60 seconds to respond.
Suggested action
Manually start the HP Insight Orchestration service after other services have completed startup.
Set retry parameters for BL620c G7 and BL680c G7 blades
Insight Orchestration may time out while waiting for the server to be recognized due to long server
post times, particularly when using the BL620c G7 or the BL680c G7.
Suggested action
To avoid this issue on any server:
1. Edit C:\Program Files\HP\Insight Orchestration\conf\hpio.properties
and set the retry.count.ares.pxe parameter to a value greater than 30.
2. Restart the HP Insight Orchestration service.
Inconsistent state during CMS crash recovery of Add Disk operation
If the Insight Dynamics CMS crashes during an Add Disk operation of a physical disk, the status
of the request is incorrectly displayed as Completed, and the logical server may remain inactive
when the request is resumed and completes successfully. In addition, after crash recovery, running
virtual services are shown with the status Off.
Suggested action 1
Activate the logical server using Insight Orchestration.
Suggested action 2
Restart the HP Insight Orchestration service. This resets the status of the virtual services to Up.
ioexec virtual machine provisioning fails during service creation when host name and
service name exceed character limits
If you use the ioexec command to create a new service, virtual machine provisioning failures can
occur if the server host name exceeds 13 characters, or the service name exceeds 16 characters.
Launching Telnet connection causes navigation error in IE 7 and IE 8
If you attempt to launch a Telnet connection to a deployed server from the Insight Orchestration
user interface, Internet Explorer opens a popup window that asks if you want to view only the
content that is delivered securely. If you click “Yes”, a navigation error page is displayed.
This issue occurs in Internet Explorer 7 and 8 only.
Suggested action
Click “No” in the popup window to launch Telnet.
HP Insight Orchestration 25