•The latest build of the software requires you to upgrade some of your CIM Extensions. Please refer to “About Upgrading Your CIM Extensions” (in the Deploying and Managing CIM Extensions chapter) for details.

•The installation will fail if there is insufficient temporary space. You must have at least 2 GB in the /tmp directory.

•After you upgrade the software, you are required to run HP SIM Discoveryand do Discovery Data Collection on all new and existing managed elements. This allows the software to gather any new data that is associated with the new features available in the latest release.

•Windows hosts using SecurePath – SecurePath information is not retrieved from legacy CIM extensions.

•After you upgrade, you need to rediscover backup details. Make note of your Backup Manager hosts. Refer to Backup Managerfor a list of Backup Manager hosts.

•The following elements are not supported even though they were supported in Service Pack 4, Build 5.1 of the management server:

•Cisco switches with firmware versions earlier than 3.1.x for switches discovered through SMI-S. You need to upgrade to version 3.2.(2c) if you want to discover the Cisco switches through SMI-S.

•Brocade SMI-A versions prior to 120.6.0a. You need to upgrade to at least version 120.6.0a.

•You should try to complete the upgrade and its subsequent steps in one session, which may take several hours, depending on your network configuration.

•It is necessary to perform Discovery Data Collection after you upgrade to repopulate the database.

•Upgrade and start the Windows proxy service first and then the management server.

•Some upgrade-related steps are required after the upgrade, as indicated later in this section.

•Any customizations to your CIMOMConfig.xml will not be preserved, because the file format has changed. The old file will be saved for reference. The customizations in the old CIMOMConfig.xml file must be manually merged into the file shipped with 6.0 and you must restart the CMS before the customizations are applied to the updated CMS. Depending upon the customizations, starting the CMS using the default CIMOMConfig.xml file can have varying impacts.

•If end-users change the port number of some of the discovery groups and then start the CMS using the default config file, the discovery groups may not start up since the default ports may be in use.

•If end-users modify the repository location and start the CMS using the default config file, the system fails to locate the discovered elements in the new repository created in the default location. If this happens, reapply the customizations to the new CMS or end-users will have problems running discovery or collecting data.

•Users who wish to continue gathering backup data from their backup manager hosts must update the CIM extensions on those hosts. The procedure for upgrading the CIM extension on a backup managing host is the same as for any host.

HP Storage Essentials SRM 6.0 Installation Guide 93