HP Insight Dynamics 6.2 Release Notes

1. Make sure that the Integrity service was successfully provisioned (the Integrity service is running).
2. Discover the Integrity blade where the Integrity service is running using its IP address from
Systems Insight Manager. The Integrity node's identification information should contain the
UUID and UUID (logical). You can discover the blade in either of the following ways:
a. Use the Systems Insight Manager menu selection Options→Discovery..., or
b. Use the Systems Insight Manager command: mxnode -a <ip-address> -w
where <ip-address> is the IP address that was assigned to the Integrity blade after
provisioning.
Add the root login of the Integrity blade using the Systems Insight Manager menu selection
Options→Security→Credentials→ Credentials....
3. To set up an SSH connection between the CMS and the Integrity blade, enter the command:
mxagentconfig -a -n <ip-address> -u <username> -p <root password>
Suggested action
If you did not perform the preceding steps before you started a delete request for the Integrity
service, the automatic delete service will not succeed completely. In that case, you must clean up
the logical server associated with the Integrity blade and manually erase the disk.
1. Power on the server blade. (The blade was powered off when delete service completed or
failed.)
2. Perform steps 2 and 3 above, if you did not do so before starting the delete request.
3. To erase the disk, enter the following command from the CMS:
mxexec -t "Ignite Erase Disks" -n <ip-address>
Customizations to the blade_models.properties file are not saved after upgrade
During an upgrade, the blade_models.properties file from an earlier release is replaced
by a new file for the 6.2 release. If you made any modifications or customizations to the
blade_models.properties file, your changes are lost.
The blade_models.properties file is used to declare any new server models to be managed
in Insight Orchestration. For example, if you modified this file to add rack mount server models so
that physical provisioning can be performed using ESA, you will no longer be able to provision
to those systems after an upgrade.
Suggested action
Before an upgrade to Insight Dynamics 6.2, save a copy of the C:\Program Files\HP\Insight
Orchestration\conf\blade_models.properties file to a location that is not under the
\Program Files\HP\Insight Orchestration or \Program Files\HP\Virtual
Server Environment directory trees, or note any changes made to the file. After the upgrade,
edit the new blade_models.properties file to add back in any custom entries made to the
previous version’s file.
Clear browser cache after upgrade
After an upgrade to Insight Dynamics 6.2, or to a 6.2 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.
Virtual machine deployment on Microsoft Hyper-V with High Availability does not create
an HA VM
If an Insight Orchestration template is configured to manually deploy a Hyper-V virtual machine
or use SA jobs to deploy a non-linked clone Hyper-V virtual machine with High Availability (HA)
selected, the provisioning operation completes and reports success. However, the virtual machine
22 Issues and suggested actions