Owner's Manual
file:///T|/htdocs/SOFTWARE/smdup/dup65/EN/readme/lin/lin_read.txt[10/23/2012 10:39:00 AM]
racadm config -g cfgRacVirtual -o cfgLCDriveEnable 0
* When you run USC-related DUPs with Citrix(R) Xenserver(TM) 5.6.0-x,
you need to set the virtual media in iDRAC to Detach. If you set the
virtual media to Attach, the following error message is displayed:
"Inventory Failure: Secure Copy Failure - The Secure copy function
has failed"
For BIOS updates, the following message is displayed:
"doDepCheck failed"
For other USC access related DUPs (PSU, NIC, SAS, PERC, BackPlane),
the update is successful but the following error message may be
displayed:
"… mount: block device /dev/secmasupd-SECUPD is write-protected …
/bin/cp: cannot create regular file …"
* 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
----------------------------------------------------------------------
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: