Release Notes
When you try to execute DUPs on a 64-bit RHEL operating system, it fails to execute since DUP 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
While executing some DUP's on 11G servers and When virtual media is in attached mode, a window with
name SECUPD will popup and close automatically. Due to this there will be no functionality impact on DUP.
This behaviour is observed across all RHEL OS flavours.
Linux CLI Options
For options beginning with '--', abbrevations are also supported.
Power Supply Unit (PSU) Dell Update Packages (DUPs)
After a Successful Power Supply firmware update, the system turns off, for up to 5 to 10 minutes, and reboots
automatically. If you perform a cold boot (AC Power cycle) during the firmware update, the system does not boot.
Unified Server Configurator (USC) Dell Update Packages (DUPs)
Lifecycle controller updates require system services to be enabled.
For the first time, before you attempt to run Driver Package Diagnostics DUPs, execute the USC DUP.
Before running DUPs, ensure that there are no external devices mounted to /media or /tmp.
If the operating system is installed from "Operating System Deployment", select "Reboot and Exit" in the USC
environment before booting to the operating system. This closes the USC session which is held for 18 hours. If you
do not want to enter the USC and select "Reboot and Exit", but want to execute the DUPs within 18 hours, unplug
the power supply of the system, wait for 10 seconds, and then power on the system.
Due to the USB arbitration services of VMWare ESX 4.1, the USB devices appear invisible to the Hypervisor. So,
when DUPs or the Inventory Collector runs on the Managed Node, the partitions exposed as USB devices are not
shown, and it reaches the timeout after 15 to 20 minutes. This timeout occurs in the following cases:
If you run DUPs or Inventory Collector on VMware ESX 4.1, the partitions exposed as USB devices are not visible
due to the USB arbitration service of VMware ESX 4.1 and timeout occurs. The timeout occurs in the following
instances:
When you start “DSM SA Shared Service” on the VMware ESX 4.1 managed node, it runs Inventory Collector. To
work around this issue, uninstall Server Administrator or wait until the Inventory Collector completes execution
before attempting to stop the “DSM SA Shared Service”.
When you manually try to run DUPs or the Inventory Collector on the VMware ESX 4.1 managed node while USB
arbitration service is running. To fix the issue, stop the USB arbitration service and run the DUPs or the Inventory
Collector.
To stop the USB arbitration service:
1. Use the “ps aux|grep usb” to check if the USB arbitration service is running.
2. Use the “chkconfig usbarbitrator off” command to prevent the USB arbitration service from starting during
boot.
3. After you stop the usbarbitrator, reboot the server to allow the DUPs and/or the Inventory collector to run.
Note: If you require the usbarbitrator, enable it manually. To enable the usbarbitrator, run the command - chkconfig
usbarbitrator on.
12 G BIOS
BIOS updates require system services/Lifecycle controller to be enabled.
If the operating system is installed from "Operating System Deployment", select "Reboot and Exit" in the USC
environment before booting to the operating system. This closes the USC session which is held for 18 hours. If you
do not want to enter the USC and select "Reboot and Exit", but want to execute the DUPs within 18 hours, unplug
the power supply of the system, wait for 10 seconds, and then power on the system.
BIOS DUP will use LC to update BIOS. BIOS DUP will stage the BIOS firmware to maser partition and create a
SSIB update task, which is executed by the SSM manager on reboot. The update task in the SSIB is a call to update
wrapper in LC which has BIOS update logic.