Release Notes

Dell - Internal Use - Confidential
 When updating multiple, identical devices on the same system, SUU applies the latest update to all instances of all devices.
For example, if the system is configured with three controllers configured with firmware or 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 track these signals) can generate a "/var/lock/.spsetup" lock file that cannot be deleted. SUU reports the update as
successful and prompts to reboot the system. When you run SUU again on the same system, the comparison report displays
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 only the NIC base driver, 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 remotely run SUU on a system. This procedure ends the virtual media
connection, resulting in an unsuccessful SUU update.(144487)
 SUU update is unsuccessful if SUU is run from a pathname that contains special characters such as,",:,/,\,$, and so on. It is
recommended to use a directory name without any special characters for running SUU. For example, when a USB DVD-
ROM or USB disk is attached, to a system running SUSE Linux Enterprise Server operating system, mounts it to a directory
name that contains special characters.
For example, /media/USB:1:2/ (42279)
 In Linux, if there is no 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 reboot 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 happens because SBUU would not have installed the umbrella software. In these cases, install the
umbrella with the umbrella installer (available at dell.com/support or in the SERVICE directory in the Dell Systems
Management Tools and Documentation DVD).(DF130363)
 Defect DF452489 - Export comparison report, in the file Dialogbox mouse movements are sluggish.
To work around the issue, add the following line:
"*.multiClickTime: 500"
to the file ~/.Xdefaults and run
xrdb -merge ~/.Xdefaults
 Defect DF497677 - If an update fails while updating multiple devices of same type, the comparison report shows that the