service. To determine the Logon account for the DataProtector CRS service, go to Control Panel > Administrative Tools > Services, select the DataProtector CRS service, access its Properties page, and select the Logon tab. To determine the Logon account for the AppStorWin32Agent service, go to Control Panel > Administrative Tools > Services, select the AppStorWin32Agent service, access its Properties page, and select the Logon tab.
•If you change the password of a host after you discover it, stop and restart the CIM extension running on the host, and change the host password in the WBEM Settings section of the System Protocol Settings page.
•If you update the system protocol settings for a host in HP SIM, the updated information is sent to HP Storage Essentials when an identification step occurs in HP SIM.
•If your license lets you discover UNIX and/or Linux hosts, the Test button for discovery reports SUCCESS from any UNIX and/or Linux hosts on which the management server can detect a CIM extension. The CIM extension must be running. The management server reports “SUCCESS” even if your license restricts you from discovering certain types of hosts. For example, assume your license lets you discover Solaris hosts but not AIX hosts. If you click the Test button, the management server reports “SUCCESS” for the AIX hosts. You will not be able to discover the AIX hosts. The IP address is not discoverable, because of the license limitation.
•If you want to receive status reports about Discovery Data Collection, see ”Configuring
•Depending on your license, you may not be able to access Backup Manager, File System Viewer and/or monitor certain applications may not be available. See the List of Features to determine if you have access to Backup Manager, File System Viewer and/or are able to monitor the other applications. The List of Features is accessible from the Documentation Center (Help > Documentation Center in Storage Essentials). To learn more about File System Viewer, see the File Servers Guide, which is also available from the Documentation Center.
•If you are unable to discover a UNIX host because of DNS or routing issues, see ”Unable to Discover a UNIX Host Because of DNS or Routing Issues” on page 718.
•Discovery Data Collection can hang if obtaining information from an AIX host where SAN storage was previously available is no longer visible to the operating system. You may need to reboot the management server to resolve this issue.
•When discovering a Linux host from the management server, the operating system/server type is not available.
•If you started a CIM extension on a Sun Solaris host by using the cim.extension.parameters config file or with the ./start
./start
•If you try to discover a Solaris host with multiple IP address, the management server picks only one IP address for discovery.
•You can configure the management server to obtain information about your backup manager hosts at a set interval. See the topic, “Scheduling Backup Collection for Backup Managers” in the User Guide for more information about collectors.
84 Discovering Applications, Backup Hosts and Hosts