Dell OpenManage Server Update Utility Version 6.4 User's Guide
The following are some known issues with Dell OpenManage Server Update Utility (SUU).
If you manually try to run DUPs or the Inventory Collector on the VMWare ESX 4.1 managed node while the USB arbitration service is running, timeout occurs.
To fix the issue, stop the USB arbitration service and then run the DUPs or Inventory Collector.
To stop the USB arbitration service:
|
NOTE: If you require the usbarbitrator, enable it manually. To enable the usbarbitrator, run the chkconfig usbarbitrator on command. |
If you login to a system running on Microsoft Windows Small Business Server 2008 operating system, you are logged in as a regular user even though you have Administrator privileges.
|
NOTE: An in-built feature called User Account Control (UAC) automatically reduces the potential of security breaches for a system running on Windows operating system. |
Before you run SUU or DUPs on your system, change the security options in Group Policy Editor. To do so:
|
NOTE: Ensure that your system is a member of the domain. |
The Group Policy Editor window is displayed.
The Policy window is displayed.
If DUPs fail to run on a 64-bit Red Hat Enterprise Linux operating system, manually install the following RPMs:
|
NOTE: The RPMs are available on the RHEL 6 x64 media. |
If you use Microsoft Windows Server 2003 operating system, you require .Net Framework 2.0 to run Dell_PV_Utils_NASDUP.exe. If you do not have .Net Framework 2.0, the following error message may be displayed:
The application failed to initialize properly (0xc0000135). Click on OK to terminate the application.
SUU does not inventory or update devices that are disabled in the operating system, though these devices may be displayed in the Comparison Report. To update the disabled devices, make the appropriate changes in the operating system and restart SUU.
On Linux systems, libstdc++-libc6.2-2.so.5 and libstdc++-libc6.2-2.so.3 are required to run SUU. Your system will have these libraries if you have installed SUSE Linux Enterprise Server or current versions of Red Hat Enterprise Linux on your system. If your system does not have these libraries and you are running a supported version of Red Hat Enterprise Linux or SUSE Linux Enterprise Server on your system, install the compat-libstdc++ RPM from RedHat.com or from the Red Hat CD (for Red Hat customers), or the SUSE Linux Enterprise Server CD (for SUSE Linux customers).
SUU uses the Dell Update Packages (DUP) to update various system components. During a Linux update, the DUP creates the /var/lock/.spsetup file using the Linux lockfile utility. This file is created when one of the following conditions occur:
If one of these conditions occur, a /var/lock/.spsetup file is created rather than deleted, causing SUU to report a successful update and prompt the user to reboot the system. When you run SUU again and run the Comparison Report, the comparison procedure reports no change in device status.
If this situation occurs and you are not running an update, delete the /var/lock/.spsetup file before running another update.
When running SUU with the -p (progress) option, the SUU current instance log location is reported rather than the SUU update log location.
When updating multiple, identical devices on the same system, SUU applies the update to all instances of all devices. For example, if your system is configured with three controllers running firmware/driver versions 1.1, 1.2, and 1.3, and the repository contains version 1.2, the update applies firmware version 1.2 to all devices.
If you have multiple PowerEdge Expandable RAID Controller (PERC) cards installed on a system, you may need to run the SUU update more than once to update the firmware of all PERC cards. This procedure ensures that all PERC cards are updated if one or more cards failed to update during the initial SUU update.
PERC update packages may fail if other activities, such as a consistency check or background initialization (BGI) are running on the controller. Ensure that such activities are not in progress before running the update package.
SUU does not allow you to restart the system inventory in the same session if there is insufficient space in the var or tmp folder.
In Linux, if the space is not enough in the var or tmp folder, SUU displays the following error message:
Not enough space available in /var or /tmp folder. Please make sure you have atleast 100MB.
Ensure that you have sufficient space in the var or tmp folder and restart SUU to start the system inventory.
When you run SUU from a network location, JRE creates temporary files in the <%systemdrive%>:\Documents and Settings\<%user%>\Local Settings\Temp\hsperfdata_<%user%> directory in Microsoft Windows or in the /var folder in Linux. You need to manually delete these temporary files.
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.
Do not use the Virtual Media to run SUU remotely on a system. This procedure breaks the Virtual Media connection, causing the SUU update procedure to fail.
SUU fails if you run it from a directory that contains special characters such as ", :, /, \, $, and so on.
For example, when a USB DVD-ROM or USB disk is attached to the SUSE Linux Enterprise Server operating system, it may by default, mount to a directory name that contains special characters. For example, /media/USB:1:2/
It is recommended to use a directory name without any special characters while running SUU.
If you launch SUU when a Remote Access Controller (RAC) DUP package (RAC 4/P or RAC 4/i) is running, execution of the DUP package may fail. To resolve this issue, run SUU only after the RAC DUP package has completed execution.
The Dell Server Updates DVD was ejected from the DVD drive while SUU was running. SUU requires the DVD to be present during execution.
The Inventory Collector subcomponent of SUU requires the libstdc++-libc6.2-2.so.3 shared library to be installed on the system. Install the compat-libstdc++ RPM from RedHat.com or from the Red Hat CD if you are running a supported version of Red Hat Enterprise Linux on your system or from the SUSE Linux Enterprise Server CD if you are running SUSE Linux Enterprise Server on your system.
A part of the SUU update requires updating the backplane firmware. If the operating system queries the backplane during a flash update and the backplane does not respond, the operating system receives an indication that the device was removed unsafely. After the backplane firmware is updated, you may see a screen indicating that a new device was added.
To perform updates, you must be running SUU on a supported system and must have the correct user access privileges. For Microsoft Windows you must have administrator privileges and for Linux you must have root privileges. For a list of supported servers and operating systems, see the Dell Systems Software Support Matrix at support.dell.com/manuals.
SUU requires that Windows users have local administrator privileges. To obtain local administrator privileges, users must either belong to the local administrators group or use the local administrator account. On Linux systems, only root (user id 0) users can see the Comparison Report and perform updates.
Run a Prerequisites check and install the recommended items. See "Performing Prerequisites Check" for more information.
Running SUU and a separate DUP concurrently may cause unexpected behavior. SUU runs DUPs in the background. Therefore, you do not need to run the DUPs. Either run SUU or the DUP; do not run both at the same time.
To ensure that no other instance of SUU is running on the system:
On systems running Windows operating systems, open the Windows Task Manager, click the Applications tab, and find out if SUU is running.
On systems running Linux operating systems, open a terminal and type the ps -eaf | grep suu command to find out if SUU is running.
If SUU is running, close the application, and restart SUU.
If no other instance of SUU is running, then SUU may have encountered an abrupt shutdown for some reason. This results in the creation of lock files. To delete these lock files on systems running a Windows operating system, navigate to the <%systemdrive%>:\dell\suu directory and delete the suu.lck file.
To delete the lock files on systems running a Linux operating system, run the following commands:
chattr -i suu.lck
rm -f suu.lck
This removes the lock file from the log directory located at /var/log/dell/suu by default.
Sometimes, after updating Server Administrator using SUU, some of the Service Administrator services may not run. Restart your system and start Server Administrator.
For systems with a TCG 1.2 compliant Trusted Platform Module (TPM) chip, BIOS updates using SUU and DUPs fail if all of the following are true:
For details about the failure, see the log files at <%systemdrive%>:\dell\suu (on Microsoft Windows) and /var/log/dell/suu (on Linux systems).
To successfully update BIOS on such systems, perform the following steps:
While running SUU, ensure that the log directory specified at <%systemdrive%>:\dell\suu (on Windows operating systems) and /var/log/dell/suu (on Linux operating systems) contains at least 10MB of free space.
You can also specify a different directory to save the log files. See the SUU command line options for more details.