HP Insight Management 7.3 Installation and Upgrade Release Notes

◦ C:\Program Files\HP\Virtual Server Environment\conf\lsa\
lsaclient.properties
◦ C:\Program Files\HP\Virtual Server Environment\conf\lsa\vc\
vcController.properties
◦ C:\Program Files\HP\Virtual Server Environment\conf\lsa\vmm\
vmmController.properties
◦ C:\Program Files\HP\Virtual Server Environment\conf\lsa\storage\
storageController.properties
After the upgrade has completed, but before the services are restarted or the CMS is rebooted,
edit the new properties files and add any custom entries made to the previous version of the
file.
• Upgrading HP Matrix infrastructure orchestration requires a manual step to upgrade Operations
Orchestration. This step is documented in the HP Insight Management 7.3 Installation and
Configuration Guide.
• During an upgrade of Insight Control server migration, an uninstallation window appears.
Suggested action: This window is an expected part of the upgrade process and it appears
only for a moment. Do not manually close this window.
• When upgrading from SPM 1.x to 2.x, if the unmanaged volumes do not have serial numbers
defined in the original version, the arrays do not show up in the new SPM catalog. This is
caused by a problem with the generated unmanaged array XML file.
Suggested Action: Prior to upgrading SPM 1.x to SPM 2.x, edit all unmanaged volumes to
include a serial number. (This must be a unique value.) If the upgrade was performed prior
to performing this action, your SPM 2.x catalog will have to be edited to fill in the missing
field. Contact Matrix support for assistance.
• Any upgrades from SPM 1.x to SPM 2.x requires SPM to be able to access the storage arrays
during the upgrade process. If any of the arrays is down or is offline, or if the connection
information is not correct, then any 1.x managed arrays will be converted to unmanaged
arrays in 2.x version. This is important because the upgrade process works by analyzing the
older catalog, importing the appropriate array resources into the new SPM catalog, and
mapping the older catalog resources onto the new resources. If SPM 2.x cannot communicate
with the array, then it is not possible to perform the import step.
NOTE: The connection mechanism for EVA arrays has changed between SPM 1.x and SPM
2.x. In both the cases, the management host, user name, and password should be the same,
however, SPM 1.x uses ESA to communicate with the EVA array, and the connection
information includes the access port. SPM 2.x communicates directly with HP P6000 Command
View Software running on the management host, using the HP P6000 Command View Software
port (usually 2372 or 2374). If HP P6000 Command View Software is configured to use a
different port, SPM will be unable to connect with the array during the upgrade process. If
you have reconfigured HP P6000 Command View Software, you must change back the
configuration to use the default port during the upgrade process. This allows the upgrade
process to communicate with the array and import the appropriate resources. The user can
force the upgrade SPM by running spmadmin /forcev1upgrade command. After the
upgrade process is complete, you can reconfigure HP P6000 Command View Software to
your preferred port and reconfigure the array’s connection information within SPM 2.x, if
necessary.
• In some cases, the existing SPM 1.x services become non-comformant after upgrading to SPM
2.x. In some of these cases, it is possible to clean up these by bringing up the Matrix Operating
Upgrading Insight Management 17