HP Storage Essentials V5.1 Installation Guide Second Edition (Linux Release) (T4283-96055, November 2006)

Storage Essentials 5.1 Installation Guide 53
Step 8 - Perform Discovery Data Collection/Get Details
Perform Discovery Data Collection/Get Details from HP SIM for all elements to repopulate the
database. Discovery Data Collection/Get Details is also required to repopulate information for
Brocade switches. Click Options > Storage Essentials > Discovery > Run Discovery Data
Collection. Then, click Get Details.
Important Information About Upgrading and Brocade Switches
As mentioned earlier, with new installations of build 5.1 of the management server, the default
Brocade provider is SMI-S. If you upgrade to build 5.1 from any build prior to 4.2 of the
management server your Brocade switches are discovered using the Brocade Fabric Access API.
To change the default discovery provider from Brocade Fabric Access API to Brocade SMI-S after an
upgrade follow the steps below:
1. Delete any previously discovered Brocade switches. See ”Step 7 - Remove and Rediscover
Certain Elements” on page 52 for details.
2. Change the Brocade provider setting. See ”About Brocade Discovery (Specifying Brocade
Discovery Using Fabric Access API or SMI-S)” on page 76 and specify the Brocade SMI-S
setting).
3. Restart the AppStorManager service.
IMPORTANT: Before performing any provisioning operations that involve a Brocade switch you
must perform Discovery Data Collection/Get Details for any subset of elements that includes the
Brocade switch. See ”Get Details or Discovery Data Collection” on page 136.
See ”Discovering Brocade Switches” on page 75 and ”About Brocade Discovery (Specifying
Brocade Discovery Using Fabric Access API or SMI-S)” on page 76 for important information.
Step 9 - Re-add Remote Sites in Global Reporter
All sites that provide global reports must be upgraded to this version of the management server.
Install this version of the management server on all remote sites, then complete the following steps
for each management server that is using Global Reporter.
1. You must modify the listener.ora file at each remote site, as described in the following steps. For
example, assume you have three remote sites. You must log onto each of these remote sites and
modify the listener.ora file at each remote site, as described in the following steps:
a. Log onto the remote site.
b. Stop the service for the management server running.
c. Stop the listener service for Oracle (OracleOraHome92TNSListener).
d. Open the following file in a text editor on the computer:
%ORA_HOME%\network\admin\listener.ora