Release Notes

 OS Collector for Windows is not available in this ISO, it is available on Dell’s 12th and 13th

generation of PowerEdge servers 32-bit ISO. (BITS228497 & BITS228508)

 On Dell’s 13

generation of PowerEdge servers SEP (Backplane) firmware DUP {SWB# GWJRF}

does not work for system configurations having more than 8 HDD backplane systems

configurations.

 Hard drive update is not supported in HBA mode.

 Updates fail on Linux systems where OMSA is uninstalled.

Work around: Delete the directory srvadmin present in /opt/dell/ and then run SUU to update

system components.

 When you run the SATA hard disk update on Microsoft Windows 2012 Standard operating

system with 16GB configuration, the update is unsuccessful. (BITS053783)

 When you run the hard disk update (52P2Y) on Microsoft Windows 2012 operating system, it is

unsuccessful (BITS054325)

Refer the PSQN ID, ID:596787: Device Buffer error when running hard drive SATA DUP

under Microsoft Windows Server 2012 for BITS053783 and BITS054325.

 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 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