Installation – HP Systems Insight Manager User Manual
Page 164
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 Systems Insight Manager with the type Server and subtype
as VMware ESX Host, Virtual Machine Host
•
The host is discovered correctly in Systems Insight Manager with the appropriate types and
subtypes. However, no guests are discovered. The Vman page shows the host, but no guests.
The virtual machine management 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 Systems Insight Manager 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
Data Collection..
Solution: Go to
. Note that the fix
above references /var/pegasus/vmware/install_queue/1 in the install queue. However,
the number might vary by installation.
-------------------------------------------------------------
I am unable to identify Windows XP targets through WBEM if Simple File Sharing is enabled.
Solution: Uncheck Simple File Sharing by navigating to Tools
→Folder Options→View or set the
security policy Network access: Sharing and security model for local accounts to Classic: Local users
authenticate as themselves.
Installation
HP-UX install/execution of partner plug-ins (for example, HP Insight Dynamics - VSE for Integrity)
might fail due to failed communication with Systems Insight Manager. Reviewing the install logs,
daemon service logs and command line command output of partner commands may show long
execution time with failed results describing a failure to connect to Systems Insight Manager or the
message java.net.NoRouteToHostException: No route to host (errno:242).
Local partner communication to Systems Insight Manager occurs using the ‘localhost’ hostname.
This should be set to the loopback IP address (usually 127.0.0.1). This is normally defined in the
/etc/hosts
file on the CMS. However, by default HP-UX systems will resolve hostnames through
DNS before looking at this file. If nslookup localhost does NOT resolve to the loopback IP
address, then you must change the lookup configuration. HP-UX or Linux systems use /etc/
164 Troubleshooting