Hp sum found new hardware message – HP ProLiant Support Pack User Manual
Page 97
Troubleshooting 97
•
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
•
For more information about setting up and troubleshooting IPv6 networks, see Getting Around IPv6
by Carla Schroder
•
Move back to an IPv4 network address to ensure HP Smart Update Manager properly finds the
remote target server without any issues.
•
HP Smart Update Manager can always be copied to the target servers and executed using the local
installation method.
HP SUM found new hardware message
During the discovery progress, HP SUM 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.
Similar pop-up messages might occur with Windows® 2008 operating systems when the Allow Non-
bundle version option on the Select Bundle Filter screen is selected.
Non-matching systems error reported when building
source RPMs or installing RPMs built from source
If HP SUM reports non-matching systems error when trying to build source RPMs or installing 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, RHEL 4.7 and RHEL 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:
1.
Run HP SUM on the target server itself instead of remotely deploying HP SUM.
2.
Build the driver RPM locally and take the resulting RPM file from the standard location (for example,
/usr/src/redhat/RPMS/i686/
SUM will pick up the pre-built RPM and enable the user to deploy it anywhere they choose.
Linux component version discrepancy for Source
RPMs
You might observe differences in the RPM component name which might appear to be a version mismatch
for the component on the Select Item to be Installed screen and the Installation Results screen. This is
caused by the RPM build phase. The resulting component is actually the same version. The RPM build
adds information, so it is technically the same component.