HP Systems Insight Manager - Manual (Page 190)

Identification
The new SSH identification method cannot be used to form associations between DL100 series
systems; such as the DL160 G5 and DL180 G5 and their management processors. There is an
incompatibility between the system UUID presented by the system and the UUID presented by the
BMC (management processor) firmware.
-------------------------------------------------------------
To get basic hardware data, such as model, serial number, and UUID, from non-HP x86 servers
running VMware ESX Server or Linux, you must configure the root user as the Sign-in credential in
HP SIM. This is because the Privilege Elevation feature is not used for identification of servers and
running dmidecode requires the root privilege. In addition, to identify the VMware ESX server as
the VMware ESX Host subtype, the WBEM cimserver on the ESX host must be up and working
correctly. There are many ways to set these credentials:
•
Global sign-in credentials (Options
→Security→Credentials→Global Credentials)
•
System Sign-in credentials (Options
→Security→Credentials→System Credentials)
•
Discovery task Sign-in credentials (Options
→Discovery→Edit→Credentials)
-------------------------------------------------------------
For ProLiant iLO2's to be properly identified with WS-MAN functionality, the iLO 2 credentials
must be the first credentials specified in either the discovery credential list or the global credential
list when discovery is run. Otherwise, system credentials can be set directly for the system after it
is discovered.
-------------------------------------------------------------
Unable to identify ESX 3.x classic servers to have the appropriate system types and subtypes, or
no virtual machines can be discovered from the ESX 3.x hosts.
Symptoms:
•
The host is not identified correctly in HP SIM with the type Server and subtype as VMware
ESX Host, Virtual Machine Host
•
The host is discovered correctly in HP SIM with the appropriate types and subtypes. However,
no guests are discovered. The Vman page shows the host, but no guests. The virt property
page is the one place on the CMS that does show the guests.
•
On the ESX host, when attempting to start the WBEM server, the following error is given:
# service pegasus start
Processing /var/pegasus/vmware/install_queue/1 [FAILED]
ERROR: See log - /var/pegasus/vmware/install_queue/1.log
•
When running HP SIM discovery, the following information appears:
Running WBEM rules based identification.
Cannot get ComputerSystem WBEM/WMI data from the system
[WBEM] System identified as WBEM instrumented but no usable
WBEM credentials available. Check configuration and rerun
Identification. Root Cause: Identification failed to generate
relevant WBEM credentials for target system.
Corrective Action: Check network and configuration of target
system. Check the following pages to ensure appropriate WBEM
credentials and port number data are provided: Global Protocol
Settings, System Protocol Settings. Rerun Identification and
190 Troubleshooting