HP Integrity Superdome 2 8/16 HP Smart Update Manager 5.0 User Guide - Page 72

HP SUM found new hardware message

Get HP Integrity Superdome 2 8/16 PDF manuals and user guides View all HP Integrity Superdome 2 8/16 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 72 highlights

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 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, 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/.rpm) and then copy it back into the HP SUM repository. HP 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. For example, if you select the component HP NC Series Mellanox 10GBE Driver for Linux on the Select Items to be Installed screen, it appears as hp-minx-en-1.4.3.1-1.src.rpm and on the Installation Results screen, it appears as hp-minx-en-kmp-default-1.4.3.1_2.6.27.19_5-1.x86_64.rpm. Troubleshooting 72

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
Troubleshooting 72
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 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, 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/<driver>.rpm) and then copy it back into the HP SUM repository. HP
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.
For example, if you select the component
HP NC Series Mellanox 10GBE Driver for Linux
on the
Select Items to be Installed screen, it appears as
hp-minx-en-1.4.3.1-1.src.rpm
and on the
Installation Results screen, it appears as
hp-minx-en-kmp-default-1.4.3.1_2.6.27.19_5-1.x86_64.rpm.