Dell Update Packages Version 6.
Notes and Cautions NOTE: A NOTE indicates important information that helps you make better use of your computer. CAUTION: A CAUTION indicates potential damage to hardware or loss of data if instructions are not followed. ____________________ Information in this document is subject to change without notice. © 2012 Dell Inc. All rights reserved. Reproduction of these materials in any manner whatsoever without the written permission of Dell Inc. is strictly forbidden.
Contents 1 Getting Started With Dell Update Packages 7 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 . . . . . . . . . . . . . . . . . . . . . 8 What’s New in This Release. Before You Begin 7 Downloading DUPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 . . . . . . . . . . . . . . . . . . 9 Fresh Installation of Device Drivers . Interactive Mode . 8 Non–Interactive Mode . . . . . . . . . . . . . . . .
2 Using Dell Update Packages . Acquiring DUPs 15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Updating Packages Component and System Compatibility 15 Executing DUPs in Linux Environment Verifying the Digital Signature . . . . . . . . . 15 . . . . . . . . . . . 17 . . . . 18 . . . . . . . . . . . 18 . . . . . . . . . . . . . . . . . 19 Executing DUPs in the Windows Environment: .
4 Update and Rollback in Unified Server Configurator - Lifecycle Controller Enabled 29 Update in USC LCE . . . . . . . . . . . . . . . . . . . . Rollback in USC LCE . 5 Command Line Interface Reference Linux CLI Options Exit Codes for CLI 31 . . . . . . . . . . . . . . . . . . . . 31 . . . . . . . . . . . . . . . . . . 34 . . . . . . . . . . . . . . . . . . . . 37 Linux Troubleshooting . Known Issues 30 . . . . Windows CLI Options 6 . . . . . . . . . . . . . . . . . . 29 . . . . . . . .
DUP Message Logs . . . . . . . . . . . . . . . . . . . 54 Messages Log . . . . . . . . . . . . . . . . . . . 54 Messages Log File 7 . . . . . . . . . . . . . . . . . Windows Troubleshooting and FAQs . Known Issues . . . . . . . . . . . . . . . . . . . . . . . . 55 57 57 Inventory Failure on Microsoft Windows Operating System 57 Messages . . . . . . . . . . . . . . . . . . . . . . . . 58 . . . . . . . . . . . . . . 61 DUP Message Logs . . . . . . . . . . . . . . . . . . .
1 Getting Started With Dell Update Packages Overview A Dell Update Package (DUP) is a self-contained executable in a standard package format that updates a single software element on the system.
• Support for XenServer 5.6 FP1 • Support for Windows 2008 R2 x64 SP1 • Support for Windows Small Business Server 2011 Before You Begin Before you install and use DUPs, ensure that: • Your system and operating system is supported by DUPs. • You are able to log on to the system with an account that has Administrator privileges. Downloading DUPs You can download DUPs for Windows and Linux operating systems from support.dell.com.
Fresh Installation of Device Drivers DUPs update BIOS, firmware, drivers, and applications. If a device driver is not present in your system, DUPs allow you to do a fresh installation of the driver. You can install the driver if the supported hardware is present. Interactive Mode In interactive mode, if a fresh installation is applicable, DUP displays a message to install the driver along with the version of the package. Click Yes to install the package.
3 Determine one of the following methodologies for performing the updates: • Single update method: Run the DUP from the command line in interactive mode to perform the update. • Script method: Use this method if you want to run one or more updates from a script in non-interactive mode. OpenIPMI Requirements Certain DUPs may require the latest OpenIPMI Linux device drivers to be installed on your system. If you are prompted during installation to obtain the latest drivers, see support.dell.
b Read the information about the update in the GUI’s scrolling text window. You can view the log results after running the check option from either the CLI or the GUI. The default path for the log file is C:\dell\updatepackage\log. 2 Determine that the target system meets compatibility requirements. For more information, see the Dell OpenManage Legacy Compatibility Guide, the Dell Systems Software Support Matrix, and "Other Documents You May Need" on page 13.
Installation Order of DUPs If you are installing multiple DUPs, install the updates that require a reboot at the end. Table 1-1 provides the recommended installation order. Table 1-1. Update Packages: Recommended Installation Order Installation Order System Software Components 1 Device driver 2 Device firmware 3 ESM firmware 4 BIOS NOTE: If you have updated the BIOS, the changes to the BIOS take effect only after you reboot your system.
Other Documents You May Need To access other documents you may need, go to support.dell.com/manuals and select your product or use the direct link on the Dell Systems Management Tools and Documentation DVD. • Dell OpenManage Legacy Compatibility Guide NOTE: You do not need to install Dell OpenManage Server Administrator on your system to run DUPs.
Getting Started With Dell Update Packages
Using Dell Update Packages 2 Acquiring DUPs NOTE: DUPs currently do not support every device type. DUPs will be available on additional devices in future releases. NOTE: You can download Windows DUPs from support.dell.com. For more information, see "Downloading DUPs" on page 8. DUPs are also available in the repository on the Dell Server Updates DVD. Dell provides a number of aids to help you determine whether or not your system requires an update.
Interactive Mode In the interactive mode, you issue a command, and the interface prompts you for permission to continue executing the command. When you execute a package interactively, it first displays a scrollable view of the release notes for the package. You may view these notes before continuing with the execution of the package. The DUP may be executed from a local console attached to the target system or from an administrator’s workstation by using a remote shell, such as ssh.
Verifying the Digital Signature A digital signature is used to authenticate the identity of the signer of a file and to certify that the original content of the file has not been modified since it was signed. If you do not already have it installed on your system, you must install the Gnu Privacy Guard (GPG) to verify a Linux DUP digital signature. To use the standard verification procedure, perform the following steps: 1 Get the Dell Linux public GnuPG key, if you do not already have it.
4 Obtain the Linux DUP and its associated signature file from the Dell Support website at support.dell.com/support/downloads. NOTE: Each Linux DUP has a separate signature file, which is displayed along with the DUP. You need both the DUP and its associated signature file for verification. By default, the signature file is named the same as the DUP filename with a .sign extension.
3 Click Properties in the pop-up menu. 4 In the Properties window, click the Digital Signatures tab. NOTE: If this tab is not displayed, the Update Package is not signed. 5 Select the signature from the signature list, and click Details. NOTE: The signature is not verified until you click Details. The Digital Signature Details window appears. 6 Read the digital signature information to verify that the digital signature is OK. 7 Click OK to close the window.
This command executes the dependency rules within the DUP, issues any warnings, exits without applying the update to your system, and writes the results to the console. You can also use the DUP to set an exit code to perform decisions within your scripts. Effects of Applying the Updates on a Running System System Reboot Required Certain packages, such as those that update the system BIOS, require a reboot for the new software to take effect.
Saving Console Output for Linux As the DUPs are executed, messages are printed to the console. To redirect console output, use the following syntax with interactive commands: ./packagename.bin | tee -a logname.log The | tee specifies the output from the DUP to be sent to both the console and to a log file. The -a switch ensures that output is appended to a file, protecting any previous log file output from being overwritten.
Stand-alone Systems and Firewalls For systems that are not connected to the Internet or that have firewalls which block user downloads, you need to download your DUP from support.dell.com by using a system that does have access to the Internet, such as your desktop or portable computer. You can make DUP available to your system by copying them onto removable media that your system supports.
Performing BIOS and Firmware Updates Using Dell Linux Online Repository 3 You can update your system to the latest version or to a specific version of the BIOS and firmware available in the Dell Linux online repository. The updates are available in the RPM Package Manager (RPM) format. RPM is a standard package format for software updates specific to Linux operating systems.
Setting Up/Bootstrapping the Repository To setup/bootstrap the Dell Linux online repository, run the following command at the command prompt: wget -q -O http://linux.dell.com/repo/hardware/latest/bootstrap. cgi | bash The system is configured to access the Dell Linux online repository using supported repository management software. The Dell GPG keys and libsmbios (BIOS library) are also installed.
Downloading Applicable Firmware Depending on the repository management software you are using, run one of the following commands to download applicable firmware: • For yum: yum install $(bootstrap_firmware) • For up2date: up2date --solvedeps=$(bootstrap_firmware -u) • For rug: rug install $( bootstrap_firmware | xargs -n1 -r rug --terse wp | cut -d'|' -f3 | grep -v "No matches" | sort | uniq ) • For zypper: zypper install $(bootstrap_firmware) Bootstrap firmware is a process where the latest BIOS/Fi
Updating BIOS and Firmware Using CLI Run the following command to inventory the system and scan the repository for new versions of components: update_firmware This command provides information about the existing versions of components on your system and the list of component versions that are available to be installed.
• If your system component version is higher than the version available in the repository, you can downgrade your system components to the versions in the repository. In the Inventory and Update Firmware dialog box, select the required components to downgrade and click Allow Downgrade. • If you need to re-install the component versions, select the required components and click Allow Reflash.
Performing BIOS and Firmware Updates
Update and Rollback in Unified Server Configurator - Lifecycle Controller Enabled 4 Dell Unified Server Configurator - Lifecycle Controller Enabled (USC LCE) is an embedded configuration utility that enables systems and storage management tasks from an embedded environment throughout the system’s life cycle. Residing on an embedded flash memory card, USC - LCE is similar to a BIOS utility in that it can be started during the boot sequence and can function independently of an installed operating system.
You can define a location to search for available updates from the following options: • The Dell File Transfer Protocol (FTP) system (ftp.dell.com). You can use a proxy system to access ftp.dell.com. • A USB device. When accessing updates from a local USB device, the USB device must be plugged in before selecting the Platform Update option in USC LCE. NOTE: For more information on updating the platform, see the Dell Unified Server Configurator User Guide available on the Dell Support website at support.
5 Command Line Interface Reference You can display information about CLI options by typing the DUP name and either -h or --help at a command line prompt. The console displays all of the command line options and provides help for each choice. Linux CLI Options Table 5-1 provides a list of the CLI options for Linux, a description of each option, and the command syntax. Table 5-1.
Table 5-1. Linux CLI Options: Usage (continued) CLI Option CLI Task Description -f Force a downgrade or update to ./packagename.bin an older version. -q -f The -q option is required when using the -f option. Force option Command Syntax NOTE: Before downgrading the software to a previous version, see the documentation for the previous version. --list List package contents option -q Run command in non-interactive mode -r Reboot option Display all files that are contained in the DUP. ./packagename.
Table 5-1. Linux CLI Options: Usage (continued) CLI Option CLI Task Description Command Syntax Display the version, fixes, ./packagename.bin enhancements, and release -v Display version option date; lists systems to which the ./packagename.bin DUP can be applied. -v,--version NOTE: This option exits after --version Extract all files contained in the DUP to the path you specify. If the directory specified in the path does not exist, it is created. ./packagename.
Windows CLI Options Table 5-2 provides a list of the CLI options for Windows, a description of each option, and the command syntax. NOTE: DUPs for Microsoft Windows operating systems cannot display output at the command line because they are Windows GUI applications. All output information is written to a log file. See "DUP Message Logs" on page 54 for information on log files. Table 5-2.
Table 5-2. Windows CLI Options: Usage (continued) CLI Option CLI Task Description /f Allows downgrade of the software to a packagename.exe /s previous (older) version. /f /l=c:\pkg.log Force option Command Syntax The /s option is required with this option. Options /e and /c are not valid with this option. NOTE: Before downgrading the software to a previous version, see the documentation for the previous version.
Table 5-2. Windows CLI Options: Usage (continued) CLI Option CLI Task Description /s Executes the update silently without packagename.exe /s user intervention. When /s is not speci- /l=c:\pkg.log fied, the DUP is launched in GUI (interactive) mode. Silent option Command Syntax The /s option is required when using the /e, /f, /c, /l, and /u options. NOTE: Using the /s option causes all output to be written to log files.
Exit Codes for CLI Exit codes help you determine and analyze the execution results after you run DUPs. After running DUPs, set the exit codes described in Table 5-3. Table 5-3. Exit Codes Value Message Name Display Name Description 0 SUCCESSFUL Success The update was successful. 1 UNSUCCESSFUL (FAILURE) Unsuccessful An error occurred during the update process; the update was not successful. 2 REBOOT_REQUIRED Reboot required You must restart the system to apply the updates.
Table 5-3. Exit Codes (continued) Value Message Name Display Name Description 4 DEP_HARD_ERROR Hard dependency error The required prerequisite software was not found on your system. The update was unsuccessful because the system did not meet BIOS, driver, or firmware prerequisites for the update to be applied, or because no supported device was found on the target system.
Table 5-3. Exit Codes (continued) Value Message Name Display Name Description 6 REBOOTING_SYSTEM Rebooting system The system is being rebooted. 9 RPM_VERIFY_FAILED RPM The Linux DUP framework uses verification has RPM verification to ensure the failed security of all DUP dependent Linux utilities. If security is compromised, the framework displays a message and an RPM Verify Legend, and then exits with exit code 9. RPM produces output only if there is a verification failure.
Command Line Interface Reference
Linux Troubleshooting 6 Known Issues The issues listed below are known issues and corrective actions for Dell Update Packages (DUPs) for Linux operating systems. Also see the corresponding Readme for Linux at support.dell.com/manuals. Diagnostic Tasks Will Not Run While a DUP Reboot is Pending It is recommended that you complete any pending updates with a reboot prior to running diagnostic tasks.
Kernel Panic While Running Storage Controller Firmware Update Packages Linux systems running one or more applications that interact with SCSI devices in certain ways are known to cause a kernel panic situation. Therefore, it is recommended that you stop Dell OpenManage Server Administrator and Dell OpenManage Server Administrator Storage Management Service before running storage controller firmware DUPs.
DUPs Fail on 64-bit Red Hat Enterprise Linux Operating System If DUPs fail to run on a 64-bit Red Hat Enterprise Linux operating system, manually install the following RPMs: • compat-libstdc++-33.i686 • libstdc++-4.4.4-5.el6.i686 • libxml2.i686 NOTE: The RPMs are available on the RHEL 6 x64 media. DUP Update of Firmware Might Fail While Running in the UEFI Mode When RHEL6 or SLES11 is installed and booted in a UEFI environment, flashing firmware via DUP might fail after DUP reboots the system.
Messages Table 6-1 provides descriptions and solutions to messages that you may receive when running DUPs. Table 6-1. Messages Message Description/Solution This Update Package is not compatible with your system Your system: System(s) supported by this package: Select a compatible DUP, and try the update again. This Update Package cannot be executed under the current operating system. DUPs support Linux operating systems and kernels supported by the -rebuild option.
Table 6-1. Messages Message Description/Solution The version of this Update Package is newer than the currently installed version. Software application name: Package version: Installed version: This message confirms the version of the currently installed software before the update is performed. The version of this Update Package is older than the currently installed version.
Table 6-1. Messages Message Description/Solution In order to assist in the Download and install the minimum , you can required OpenIPMI driver from download and install a version support.dell.com. of the OpenIPMI driver that meets the minimum version requirement from support.dell.com. The minimum version required is . This Update Package requires a newer version of the OpenIPMI driver than is currently installed on the system, which is version .
Table 6-1. Messages Message Description/Solution Kernel source for the running kernel is installed, but the currently installed OpenIPMI driver RPM was installed without the kernel source for the running kernel. In order to install OpenIPMI driver modules for the running kernel that meet the minimum version requirement, use DKMS (see man page for dkms) to install and build OpenIPMI driver modules for the running kernel.
Table 6-1. Messages Message Description/Solution Rebuilding package to support kernel version "kernel.x". This process may take several minutes to complete... The DUP application is rebuilding the package to support a different kernel version. No specific kernel version specified! Building support for current kernel... Unable to determine current system kernel. The DUP application attempts to rebuild the package. Cannot create directory /extract directory.
Table 6-1. Messages Message Description/Solution Rebuilding Package Failed Error creating driver support directory. The package could not be rebuilt because the support directory could not be created. Rebuilding Package Failed Error copying kernel modules. The package could not be rebuilt because the kernel modules could not be copied. Rebuilding Package Failed Error re-creating archive. The package could not be rebuilt because the archive could not be recreated.
Table 6-1. Messages Message Description/Solution Rebuilding Package Failed Packages cannot be rebuilt on a system Server Administrator device that has the HAPI device driver driver (HAPI) is already installed. installed on the system. Package can be rebuilt only on a system that does not have Server Administrator device driver (HAPI) installed. Unable to Install Dell The package cannot install the HAPI Instrumentation Driver (HAPI). driver.
Table 6-1. Messages Message Description/Solution packagename.bin: Rebuilding Package Failed - Error recreating archive. Ensure that enough space is available in the /tmp directory. packagename.bin: Rebuilding Package Failed - Uninstall of driver was unsuccessful. The driver could not be uninstalled. packagename.bin: Rebuilding Package Failed - Error creating files. Ensure that enough space is available in the /tmp directory. Package has been rebuilt successfully. Output package: packagename.
Table 6-1. Messages Message Description/Solution The installed operating system version is not supported by this Update Package. To customize this package, see "Rebuilding Packages" in the Update Package User’s Guide. In no event shall Dell Inc. be held liable for any direct, indirect, incidental, special, or consequential damages suffered during or after package customization and execution.
Table 6-1. Messages Message Description/Solution Execution operation exceeded specified timeout Execution update operations have time-out limits as defined in the package. Time-out durations are in seconds. If an operation times out, the remainder of the package update is cancelled. /var/lock directory must exist. Create this system directory to ensure that package updates do not execute concurrently. Unable to build a device Select a compatible DUP and try again.
Table 6-1. Messages Message Description/Solution The Linux DUP framework uses the Linux utility, less, to display the release (--version). notes relevant to the specific firmware Press 'q' to continue with DUP or driver release managed by the DUP. execution (dup dup execution).
• DUP type • DUP version • Framework version of the DUP • Version that was previously installed on the system • Version that the command is trying to apply to the system • Exit code that results from execution of the command • Whether a reboot was performed NOTE: The support log files are intended for use by Dell support personnel. Dell encourages you to redirect the DUP output to a file of your choice.
Linux Troubleshooting
Windows Troubleshooting and FAQs 7 Known Issues The issues listed below are known issues and corrective actions for Dell Update Packages (DUPs) for Windows operating systems. Also see the corresponding Readme for Windows at support.dell.com/manuals. Inventory Failure on Microsoft Windows Operating System NOTE: This issue is applicable to systems running Windows operating system version 2008 and higher.
Messages Table 7-1 provides descriptions and solutions to messages that you may receive when running DUPs. Also see the corresponding Readme for Microsoft Windows at support.dell.com/manuals. Table 7-1. Update Packages Message Information Message Description/Solution This Update Package is not compatible with your system. Your system: Select a compatible DUP, and try the update again. This Update Package is not Select a compatible DUP, and try the compatible with your update again.
Table 7-1. Update Packages Message Information (continued) Message Description/Solution Your system exceeds the maximum operating system version supported by this Update Package. The DUP you selected cannot be installed because your system exceeded the maximum operating system version supported by the DUP. Install the appropriate version or select another DUP, and try the update again. This Update Package is not compatible with any of the devices detected in your system.
Table 7-1. Update Packages Message Information (continued) Message Description/Solution The version of this Update Package is older than the currently installed version. Software application name: Package version: Installed version: The DUP you selected cannot be installed because a newer version of the software already exists on the system. To install the older version: (Using the Interactive mode) Click Yes when prompted to continue with the installation.
Table 7-1. Update Packages Message Information (continued) Message Description/Solution This Update Package is not installed. Software application name: Package version: In interactive mode, if a fresh install is applicable, you are presented with a choice to install or not. The package version is also displayed.
DUPs are not available for all devices. Dell will continue to make additional DUPs available for more devices in future releases. See the readme.txt file for a list of devices currently supported by DUPs. Question: I'm using a software distribution tool to deploy my applications or operating system updates to my remote servers. Can I use DUPs with this tool to remotely update my servers? Answer: DUPs are designed to work with most software distribution tools.
Question: I recently updated the BIOS on my system and now I would like to go back to the previous version. Can I do this with DUP? Answer: Yes. Download the DUP for the previous version of your system BIOS from support.dell.com and install it. If a DUP is not available, use one of the other formats on support.dell.com. Question: Why does the DUP for the system BIOS require a reboot? Answer: The BIOS update is applied only after you reboot your system. I'd like to apply several updates to my system at once.
Question: How will I know when there are new DUPs available for my systems? Answer: You can check support.dell.com for updates or register for the File Watch Service at dell.com to receive automatic notification for upgrades to your system. Question: Why do BIOS and firmware updates fail to re-apply (update to the same version), even when using the force (/f) option in CLI mode? Answer: Re-installation of BIOS or firmware DUPs wastes valuable company time and resources. It accomplishes nothing.
DUP Message Logs Logging occurs when you run a command for a DUP. The logs maintain information about all update activities. DUPs write to the Messages log. If you install the same package more than once on the same system, the log is appended. Messages Log Messages log files reside in the following default location: C:\Users\\AppData\Local\Dell\UpdatePackage\Log NOTE: User needs to have administrative privilege to see the log files.
Windows Troubleshooting and FAQs
A Trusted Platform Module (TPM) and BitLocker Support A TPM is a secure microcontroller with cryptographic capabilities designed to provide basic security-related functions involving encryption keys. It is installed on the motherboard of your system, and communicates with the rest of the system using a hardware bus. You can establish ownership of your system and its TPM through BIOS setup commands.
BitLocker is designed for systems that have a compatible TPM microchip and BIOS. A compatible TPM is defined as a version 1.2 TPM. A compatible BIOS supports the TPM and the Static Root of Trust Measurement. BitLocker seals the master encryption key in the TPM and only allows the key to be released when code measurements have not changed from a previous secure boot. It forces you to provide a recovery key to continue boot if any measurements have changed.
B Microsoft Windows Server 2008 User Account Control In previous versions of Windows, user accounts were often members of the local Administrators group and had access to administrator privileges. Members of the local Administrators group could install, update, and run software since an Administrator account has system-wide access. When a user was added to the local Administrators group, that user was automatically granted every Windows privilege.
UAC prompts users in the Domain Administrators group (except the Administrator account) to click Continue, if they need to elevate privileges, or to click Cancel when performing functions that may entail a security risk. With UAC, users have to upgrade to an Administrator account before running DUPs. NOTE: Since the user experience is configurable with the Security Policy Manager snap-in (secpol.msc) and with Group Policy, there are multiple UAC user experiences.
• Disabling UAC for all users on remote machines (not a recommended option). • Not upgrading to Administrator account on remote machines. NOTE: Only two accounts (the Local Administrator Account and the Local System Account) are not protected by UAC. All other users including accounts with local administrator rights or domain administrator rights have UAC enabled by default. Even though UAC can be disabled by updating the local or domain security policy, it is not recommended.
Microsoft Windows Server 2008 User Account Control
Index B /l=, 35 /r, 35 /s, 36 /u=, 36 Check, 34 Extract, 34 Force, 35 Help, 34 Log, 35 Reboot, 35 Silent, 36 Unicode Log, 36 BIOS and Firmware Updates, 23 BitLocker, 67 Boostrapping repository, 24 C CLI -c, 19, 31 Check, 31 exit codes, 37 --extract, 33 -f, 22, 32, 45 Force, 32 --h, 31 -h, 31 non-interactive mode, 32 -q, 22, 32 -r, 32 reboot, 32 rebuild, 32 -v, 33 --version, 33 CLI options /?, 34 /c, 34 /c /s, 62 /e=, 34 /f, 35, 60 /h, 34 conditions that may require update, 15 D delivering Update Packag
F P Firmware-tools, 23 Platform Configuration Registers, 67 frequently asked questions, 61 H HAPI, 50 Help option, 31 I Important tips using Update Packages, 12 public key, verify, 17 R RPM, 39 RPM format, 23 S Server Administrator documentation, 13 signature, verify, 17 K key, verify, 17 specifying order of multiple updates, 20 standalone systems and firewalls, 22 M message logs for Update Packages, 54, 65 messages, 58 N non-interactive mode, 32 strategy for running Update Packages, 10 system
Trusted Platform Module, 67 U Update and Rollback in Unified Server Configurator Lifecycle Controller Enabled, 22, 29 Update Options, 8 using Update Packages important tips, 12 V verify digital signature, 17 public key, 17 update, 22 Update Packages acquiring, 15 applying on a running system, 20 before you begin, 15, 29 CLI commands, 19 delivering to your systems, 21 executing, 15 information provided about updates, 9-10 message information, 58 message logs, 61 messages, 22 resolving compatibility conce
Index 76
