1.If errors occur during discovery, an error message will display at the top of the screen below the discovery step where the errors occurred. If you receive an error message, enable Troubleshooting Mode by selecting the Enable Troubleshooting Mode check box located near the top of the page for each discovery step.

2.A red icon will display in the Problems column for each host for which a problem was detected. Clicking this icon for a particular host will cause a list of troubleshooting tips to display below the Enable Troubleshooting Mode check box. Use these tips to assist in the resolution of configuration problems for that host.

3.You can also enter Troubleshooting Mode by clicking the link located in the error message for one of the discovery steps. For example, if you are on discovery step 3, you can click the “Discovery->Setup in Troubleshooting mode” link located in the step 1 error message. Clicking this link will bring you to the step 1 page with Troubleshooting Mode enabled.

When Troubleshooting Mode is enabled during Discovery Data Collection, the following additional information is provided to assist in the identification of configuration issues:

•Host OS

•CIM Extension Version

•HBA (Driver Version)

•Multipathing

Unable to discover Emulex host bus adapters

The Emulex driver does not contain the required library that is required by HP Storage Essentials. You must install Emulex HBAnywhere software so that HP Storage Essentials can discover hosts configured with HBAnywhere and hbatest can detect the Emulex host bus adapter.

CIMOM Service Not Starting After Trying to Discover Sybase or SQL Server Applications

If your management server is running on Linux, you will not be able to discover Sybase or SQL Server applications. If you already added a Sybase or SQL Server entry to be managed in the Discovery setup page and performed a Get All Element Details operation, entries for the Sybase or SQL server will be added to the oracle listener configuration file. On the next system reboot, or on the next restart of the Oracle service, the Oracle listener will error out, and the CIMOM service will not start.

To correct the issue:

1.Edit ORA_HOME/network/admin/listener.ora and remove the SID_DESC text blocks containing the PROGRAM=hsodbc string.

where ORA_HOME is the Oracle home

For example: . /opt/oracle/product/9.2.0.4

If you have a SID_DESC block similar to the text block below, remove this entire block.

(SID_DESC =

(SID_NAME = SQLSERVERSID)

(ORACLE_HOME = /opt/oracle/product/9.2.0.4)

(PROGRAM = hsodbc)

HP Storage Essentials SRM 6.0 Installation Guide 397