HP ProLiant BL465c Server Blade - Manual (Page 36)

Troubleshooting HP SUM in IPv6 Red Hat and Novell SUSE-based Linux environments
•
Verify that you can establish an SSH connection to the remote target server using the credentials
within HP SUM by issuing the following command at a console prompt:
ssh <ipv6 address>
SSh 2101:db8:0:1::9
You must enter the root password for the target Linux server at the console to complete the
IPv6 connection.
•
Validate that you can ping the remote target server. In Linux, you need to use the ping6
command to ping IPv6 addresses: ping6 <ipv6 address>.
•
Ensure you can ping the IPv6 loopback address: ping6 ::1.
•
Use the DNS hostname instead of IPv6 address to ensure the address is correct.
•
Use ipconfig to validate you have IPv6 addresses assigned to your NICs. For more
information about troubleshooting your configuration, see the Linux IPv6 How-To at
http://
www.linux.com/learn/docs/ldp/592-linuxipv6-howto .
•
For more information about setting up and troubleshooting IPv6 networks, see Getting Around
IPv6 by Carla Schroder at
http://www.enterprisenetworkingplanet.com/netsp/article.php/
3634596 .
•
Move back to an IPv4 network address to ensure HP SUM properly finds the remote target
server without any issues.
•
You can copy HP SUM to the target servers and execute using the local installation method.
Windows found new hardware message
During the discovery progress, Windows might display the following pop-up message:
Found New Hardware.
This message appears because one of the self-discovery components is loading a new driver and
the Windows operating systems discovers it as a new piece of hardware.
Non-matching systems error reported when building source Linux RPMs or
installing Linux RPMs built from source
If HP SUM reports non-matching systems error when trying to build source Linux RPMs or installing
Linux RPMs built from source, then the operating system on the target server does not match the
operating system from which you are running HP SUM in one of the following ways:
•
The distribution of the operating system does not match. For example, Red Hat Enterprise Linux
4.7 and 4.8 would be a mismatch.
•
The architecture of the two operating systems does not match. For example, one server might
be running an operating system with x86 architecture and the other with x86_64 architecture.
•
The kernel version running on the two systems does not match.
Resolution options are:
◦ Run HP SUM on the target server itself instead of remotely deploying HP SUM.
◦ Build the driver RPM locally and take the resulting RPM file from the standard location
(for example, /usr/src/redhat/RPMS/i686/.rpm) and then copy it back
into the HP SUM repository. HP SUM picks up the pre-built RPM and enables you to
deploy it anywhere you choose.
36 Troubleshooting