HP Systems Insight Manager - Manual (Page 136)

by entering net use at a command prompt. If there is an existing share to the target IP address,
\admin$
share, delete it and try the installation again.
•
Ensure that the target IP address server’s admin$ share is accessible. Validate the target server can be
accessed by entering net use x: \\<ip_address_or_dns_name>\admin$ for the target server’s
IP address or DNS name. When the connection is validated, ensure that it is deleted by entering net
use x: /d
at command prompt.
•
Ensure the user ID being used to connect to the target IP address server is part of the administrator’s
group. If it is not, HP Smart Update Manager blocks installation to the target.
•
Ensure WMI is enabled and running on all Windows target servers.
•
For Linux, ensure the SSH port is not blocked.
•
In some rare cases, external storage enclosures can cause HP Smart Update Manager to report a
discovery failure. To resolve this problem, disconnect the external storage until the firmware updates
are completed.
•
For Linux, ensure that the target server can be contacted through SSH and that the scp command is
available to securely send files to the target server.
•
Ensure the firewall ports on any routers in the network as documented in the Enabling ports in the HP
Smart Update Manager documentation.
•
The Symantec End Point Protection product (SEP) blocks HP Smart Update Manager ability to
communicate with remote targets if the Network Threat Analysis feature is enabled. Disable this feature
while HP Smart Update Manager is in use on the workstation.
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 Systems Insight
Manager. 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 iLO2 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 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
136 Troubleshooting