Owner's Manual

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.
12G and 13G 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.
BIOS
• A BIOS update requires enough free physical memory to load the entire BIOS image into the
physical memory. If there is insufficient free physical memory available on the system to load the
BIOS image, the Dell Update Package for BIOS may fail. In this instance, you may attempt
running the Dell Update Package immediately after reboot or after adding more memory. If this
does not resolve the issue, update the BIOS using the Diskette method.
• If the above memory limitation occurs on VMware ESX Server, the problem is because the
console operating system available memory is only 272 MB by default. Increase the console
operating system memory to 800 MB temporarily and perform the firmware update. During ESX
Server boot up, perform the following steps to increase the available memory:
1. While booting, press "e" on the VMware ESX line (Grub option display screen).
2. Press "e" again on the 'uppermem=' line and edit uppermem=819200.
3. Press "Enter".
4. Press "e" on the kernel line (below the uppermem line).
i. Edit the kernel line with mem=800M and press “Enter”.
5. Press "b" to boot with these options.
6. Perform the firmware update.
• BIOS update may issue the following kernel messages on the console and in "/var/log/messages":
dcd***: disagrees about the version of symbol struct_module
dcd***: Unknown symbol get_user_size