HP Integrity Superdome 2 8/16 HP Smart Update Manager 5.3 User Guide - Page 69

HP Integrity Superdome 2 8/16 Manual

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 69 highlights

The user-specified reboot message does not appear when using a Japanese character set on a Linux operating system Solution: None. You can specify a message to appear before the system shuts down during a reboot operation. If you are using a Japanese character set and running on a Japanese version of a Linux operating system, the message does not appear properly. Automatic reboot does not occur when using the user-specified reboot message with a Japanese character set on Windows You can specify a message to appear before the system shuts down during a reboot operation. When using a Japanese character set and running on a Japanese version of Windows, the message causes the reboot not to occur automatically. Solution: For a successful reboot, you must click Exit. When the message is entered using CLI, the reboot message looks corrupted because the Japanese character set is not supported in CLI. HP SUM stalls when run in a directory path that contains multi-bye characters Solution: Do not run HP SUM in directories containing multi-byte characters in the path name. Microsoft Windows displays a Found new hardware message During the discovery progress, HP SUM might display the following message: Found New Hardware. This message appears because one of the self-discovery components is loading a new driver and Windows discovers it as a new piece of hardware. Solution: Ignore the message and continue. Non-matching systems error reported when building source Linux RPMs or installing Linux RPMs built from source If HP SUM reports non-matching systems errors when trying to build source Linux RPMs or installing Linux RPMs built from source, 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 6.0 and RHEL 6.1 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. Solution: Use one of the following 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 you to deploy it anywhere you choose. Linux component version discrepancy for source RPMs You might observe differences in the RPM component name that might appear to be a version mismatch for the component on the Select Item to be Installed and Installation Results screens. 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 Operation issues 69

  • 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
The user-specified reboot message does not appear when using a Japanese character
set on a Linux operating system
Solution:
None.
You can specify a message to appear before the system shuts down during a reboot operation. If
you are using a Japanese character set and running on a Japanese version of a Linux operating
system, the message does not appear properly.
Automatic reboot does not occur when using the user-specified reboot message with
a Japanese character set on Windows
You can specify a message to appear before the system shuts down during a reboot operation.
When using a Japanese character set and running on a Japanese version of Windows, the message
causes the reboot not to occur automatically.
Solution:
For a successful reboot, you must click
Exit
. When the message is entered using CLI, the
reboot message looks corrupted because the Japanese character set is not supported in CLI.
HP SUM stalls when run in a directory path that contains multi-bye characters
Solution:
Do not run HP SUM in directories containing multi-byte characters in the path name.
Microsoft Windows displays a
Found new hardware
message
During the discovery progress, HP SUM might display the following message:
Found New
Hardware.
This message appears because one of the self-discovery components is loading a
new driver and Windows discovers it as a new piece of hardware.
Solution:
Ignore the message and continue.
Non-matching systems error reported when building source Linux RPMs or installing
Linux RPMs built from source
If HP SUM reports non-matching systems errors when trying to build source Linux RPMs or installing
Linux RPMs built from source, 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 6.0 and RHEL
6.1 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.
Solution:
Use one of the following 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 you to deploy it anywhere you
choose.
Linux component version discrepancy for source RPMs
You might observe differences in the RPM component name that might appear to be a version
mismatch for the component on the Select Item to be Installed and Installation Results screens. 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
Operation issues
69