Owner's Manual

configured with firmware/driver versions 1.2, 1.3, and 1.4 and the repository version is 1.4, SUU
applies version 1.4 to all instances of all devices. (136620)
• When you run SUU using the "-p" option, SUU reports the current instance log location ("suu -p")
instead of the SUU instance log location ("suu -u") that is performing the update. (135925)
• SUU uses DUPs to update various system components. During a Red Hat Enterprise Linux update,
the DUPs create a "/var/lock/.spsetup" file using the Linux lockfile utility during the initial
execution procedure. Kernel panics or sudden reboots during DUP execution (reboots where
TERM signals are not sent to running processes or where running processes do not have time to
catch these signals) can generate a "/var/lock/.spsetup" lock file that cannot be deleted. SUU
reports the update as successful and prompts you to reboot the system. When you run SUU
again on the same system, the comparison reports no change in device status. If this
situation occurs and no update is in progress, remove "/var/lock/.spsetup" before running another
update on the system. (137287)
• If a NIC teaming application is installed on the system, SUU updates the NIC base driver only if
the driver is compatible with the teaming application. To verify driver compatibility, run DUP on
the system to update the driver and read the generated messages. (138648)
• Devices that are disabled in the operating system are not inventoried or updated by SUU. To
update or inventory these devices, enable the devices in the operating system and then re-
launch SUU. (142111)
• Do not use the RAC/iDRAC virtual media to run SUU remotely on a system. This procedure
breaks the virtual media connection, causing the SUU update procedure to fail. (144487)
• SUU fails if it is run from a pathname that contains special characters. For example, ",:,/,\,$, etc. It
is recommended to use a directory name without any special characters for running SUU. As an
example, a case where you can get directory name with special characters is:
In the SUSE Linux Enterprise Server operating system, when a USB DVD-ROM or USB disk is
attached, it may by default, mount to a directory name that contains special characters.
For example, /media/USB:1:2/ (42279)
• In Linux, if there is not enough space in the var partition or tmp folder, SUU displays the
following error message:
"Not enough space available in the /var or /tmp folder. Please ensure you have atleast 1.5GB."
Ensure that you have sufficient space in the var partition or tmp folder and restart SUU to start
the system inventory. (66118)
• In some cases where the latest Intel NIC driver (Intel PRO PCIE Gigabit Family of Adapters 9.5,
base driver version 9.6.31.0) is installed as part of Dell Systems Build and Update Utility (SBUU)
install, SUU may not be able to inventory the respective NIC. This may happen because SBUU
would not have installed the umbrella software. In these cases, install the umbrella with the
umbrella installer (available at dell.com/openmanagemanuals or in the SERVICE directory on the
Dell Systems Management Tools and Documentation DVD) to get the Intel NIC inventoried by
SUU (DF130363).
• When you try to execute SUU on a 64-bit RHEL operating system, it fails to execute since SUU is
a 32-bit application.
To work around this issue, manually install the following RPMs:
glibc.i686
compat-libstdc++.i686
libstdc++.i686
zlib.i686
libxml2.i686