HP Systems Insight Manager 7.3 Update 1 User Guide

NOTE: This applies to both x86 and x86_64 if the user elects to install the XWindows support.
NOTE: These must be the 32-bit version even under x86_64 architecture as HP SUM and several
of the RPMs require 32-bit libraries installed.
NOTE: The versions below are needed as a minimum. Later versions of these can most likely be
used as well.
• libuuid-2.17.2-6.el6.i686.rpm
• freetype-2.3.11-5.el6.i686.rpm
• libSM-1.1.0-7.1.el6.i686.rpm
• libICE-1.0.6-1.el6.i686.rpm
• libXi-1.3-3.el6.i686.rpm
• libX11-1.3-2.el6.i686.rpm
• libXext-1.1-3.el6.i686.rpm
• libXcb-1.5-1.el6.i686.rpm
• libXau-1.0.5-1.el6.i686.rpm
• libXrender-0.9.5-1.el6.i686.rpm
• libXrandr-1.3.0-4.el6.i686.rpm
• libXfixes-4.0.4-1.el6.i686.rpm
• libXcursor-1.1.10-2.el6.i686.rpm
• fontconfig-2.8.0-3.el6.i686.rpm
• expat-2.0.1-9.1.el6.i686.rpm
• expect-5.44.1.15-2.el6.<arch>.rpm
• zlib-1.2.3-25.el6.i686.rpm
• libstdc++-4.4.4-13.el6.i686.rpm
• net-snmp-5.5-27.el6.<arch>.rpm
In addition, the build directory for RPMs built from source has changed depending on the name
of the user building them. Up through RHEL5, the directory had been /usr/src/redhat/RPMS/
<architecture>. Under RHEL6, the directory is /root/rpmbuild/RPMS/<architecture>
if the user is logged in as root and /$USER/home/rpmbuild/RPMS/<architecture> for
users other than root.
-------------------------------------------------------------
If you are receiving an HP Smart Update Manager Connection Error or Discovery Failed message
in the StdOut Task Results for Initial ProLiant Support Pack Install, SSH Install, or Configure or Repair
Agents, follow the following troubleshooting tips:
• Ensure your workstation does not have an existing connection to the admin/administrator
share on the target IP address. If it does, it prevents HP Smart Update Manager from connecting
to the remote server's share because Windows only allows one connection from a client to a
server's share. This can be checked 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. Use net use x:
\\fe80-0-0-0-a0b6-99c9-2f6c-5759. ipv6-literal.net\admin$
/u:administrator adminpassword for target IPv6 address servers. When the connection
is validated, ensure that it is deleted by entering net use x: /d at command prompt.
188 Troubleshooting