Owner's Manual

Depending on the system configuration, this process may take several
minutes to complete. (138439)
* The figures and examples in the "Dell OpenManage Server Update
Utility User's Guide" are used as examples only and may not be
identical to the SUU GUI. (137294, 136624)
* When you verify the SUU return codes, use the operating system-
specific commands to view the exit codes. (137296)
For example:
Microsoft Windows: echo %ERRORLEVEL%
Red Hat Enterprise Linux: echo $?
######################################################################
KNOWN ISSUES
######################################################################
This section provides information about known issues with this release
of SUU.
* If your CERC ATA RAID controllers are configured with the H661
firmware, SUU cannot update the firmware to the latest version.
To update the firmware, use the "-force" option to manually apply
the DUP with the latest firmware version. (134775)
* When updating multiple, identical devices on the same system, SUU
applies the latest update to all instances of all devices. For
example, if your system is configured with three controllers
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)