Dell™ Update Packages for Linux Operating Systems User’s Guide w w w. d e l l . c o m | s u p p o r t . d e l l .
Notes and Notices NOTE: A NOTE indicates important information that helps you make better use of your computer. NOTICE: A NOTICE indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. ____________________ Information in this document is subject to change without notice. © 2003–2008 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 . . . . . . . . . . . . . . . . . . Overview . . . . . . . 7 . . . . . . . . . . . . . . . . . . . . . . . . . 7 Server Update Utility and DUPs . Update Options . . . . . . . . . . . . . . 8 . . . . . . . . . . . . . . . . . . . 8 Supported Operating Systems . OpenIPMI Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using DUPs in the DTK Pre-Operating System Environment . . . . . . . . . . . . . . . . . . .
2 Using Dell Update Packages . Before You Begin . . . . . . . . . 17 . . . . . . . . . . . . . . . . . . . . 17 . . . . . . . . . 17 . . . . . . . . . . . . . . . . . . 18 Develop Your System Update Plan Acquiring DUPs . Update Packages Component and System Compatibility . . . . . . . Executing DUPs . . . . . . . . . 18 . . . . . . . . . . . . . . . . . . 18 . . . . . . . . . . . 21 . . . . . . . . . . . . . . 24 Verifying the Digital Signature Compatibility Concerns .
Dell-Enabled Path . . . . . . . . . . . . . . . . . . . . Dynamic Kernel Support . . . . . . . . . . . . . . . . Determining Whether Your Package Is Supported . . . . . . . . . . . . . . . . . . . . . . . Setting Up a Test System for Rebuilding a Package . . . . . . . . . . . . . . . . Scenario . . . . . . . . . . . . . . . . . . . . . . 41 . . . . . . . . . . . . . . . . . . . . . . Rebuilding the Package to Add Kernel Support for Multiple Kernel Versions . 42 44 . . . . . . . . . 44 . . .
Messages . . . . . . . . . . . . . . . . . . . . . . . . 48 DUP Message Logs . . . . . . . . . . . . . . . . . . . 59 Messages Log . . . . . . . . . . . . . . . . . . . 59 Messages Log File . . . . . . . . . . . . . . . . . Support Log File Example . . . . . . . . . . . . . 59 60 Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Index 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Getting Started With Dell Update Packages Overview Dell™ Update Packages (DUPs) allow administrators to update a wide range of system components simultaneously and apply scripts to similar sets of Dell systems, to bring system software components up to the same version levels.
DUPs in non-interactive mode to facilitate rapid deployment for an experienced user, to accommodate large environments with multiple systems, or to process multiple updates per system. This guide is designed to familiarize you with Linux DUPs so that you can begin applying them to simplify the system software maintenance on your Dell systems. The "Using Dell Update Packages" section of this guide provides several sample scenarios for using DUPs.
System Update–To update all elements on your system. Dell recommends that you use SUU to automatically: • inventory the Dell firmware and drivers on that system • compare the installed configuration with the content on the Dell Server Updates DVD • report on discrepancies and recommend updates, including any prerequisites that may impact the update sequence • update and (if needed) reboot the system NOTE: See the Server Update Utility User's Guide available on the Dell Support website at support.
• SUSE Linux Enterprise Server 10 SP2 (x86_64) • VMware® ESX Server™ version 3.0.3 Update 1 and version 3.5 Update 2 • Citrix® XenServer version 5.0 Dell Edition NOTE: For the latest information about the various systems and operating systems that DUPs are supported on, see the Dell Systems Software Support Matrix. This guide is available on the Dell Support website at support.dell.com or on the Dell Systems Management Tools and Documentation DVD.
Users can boot to the system under the DTK embedded Linux Environment and execute the package from either a network drive, a USB device supporting Linux file systems, or a CD drive, with the following options: Interactive Mode: ./packagename Non-Interactive Mode: ./packagename -q or ./packagename -q -r A successful update will return the exit code to either 0, 2 or 6.
How to Obtain DUPs from the Dell Support Website 1 Log on to support.dell.com. 2 Click Drivers and Downloads. 3 Enter your service tag or choose your product model. 4 Select your product family and product line. 5 Select your operating system, language, category, and the update importance. A list of applicable updates are displayed. 6 Click Download Now. 7 You can also download a different file format from the column labeled File Title. Select a file format for your DUP and single-click its filename.
Installation Order of DUPs If you are installing multiple DUPs, install the updates that require a reboot at the end. Dell recommends the installation order as described in Table 1-1. Table 1-1. Update Packages: Recommended Installation Order Installation Order System Software Components 1 Linux device driver 2 Device firmware 3 ESM firmware 4 BIOS NOTE: If you have updated the BIOS, the changes to the BIOS do not take effect until you reboot your system.
Other Documents You Might Need • The Dell OpenManage Server Administrator Compatibility Guide under Dell OpenManage Server Administrator on the Dell Support website at support.dell.com, or on the Dell Systems Management Tools and Documentation DVD that came with your system. The guide summarizes all systems management releases that precede the current release date. NOTE: DUPs do not require the Dell OpenManage Server Administrator to be installed on your system.
Obtaining Technical Assistance If at any time you do not understand a procedure described in this guide, or if your product does not perform as expected, different types of help are available. For more information see "Getting Help" in your system's Installation and Troubleshooting Guide or the Hardware Owner’s Manual. Additionally, Dell Enterprise Training and Certification is available; see www.dell.com/training for more information. This service might not be offered in all locations.
Getting Started With Dell Update Packages
Using Dell Update Packages Before You Begin This section is designed to help you get the most out of Dell™ Update Packages (DUPs). Updating the system software on your Dell systems should be a key element of your company's overall change management policies and procedures. Maintaining the system software on your Dell systems helps ensure trouble-free operation.
Planned updates occur as a part of your regular cycle of maintaining your systems with up-to-date BIOS, firmware, and drivers. Many IT organizations establish a regular schedule for performing the updates, which are integrated with the planned maintenance functions. The frequency of these updates varies from company to company; however, it is not uncommon for companies to adopt quarterly or semiannual update schedules.
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 server or from an administrator’s workstation by using a remote shell, such as ssh.
Would you like to reboot your system now? N The system should be restarted for the update to take effect. Version Information One of the most informative commands uses the --version option. An actual example that retrieves extensive version information for a DUP is as follows: [root@localhost 1027]# ./PE1650-BIOS-LX-A10.bin -version Dell Update Package 2.x Copyright (c) 2003-2004 Dell Inc. All rights reserved.
Non-Interactive Mode Non-interactive mode is essential when executing a script for applying DUPs to multiple systems. When applying DUPs to multiple systems, you cannot answer yes or no during script execution. Your script specifies -q for non-interactive mode; often script writers add -f for force and -r for reboot if a reboot is required for the type of update being performed.
3 To avoid a distrusted-key warning, validate the public key by its fingerprint before you use it. a Type the following command: gpg --edit-key 23B66A9D b Within the GPG key editor, type fpr. The following message appears: pub 1024D/23B66A9D 2001-04-16 Dell, Inc. (Product Group) Primary key fingerprint: 4172 E2CE 955A 1776 A5E6 1BB7 CA77 951D 23B6 6A9D If the fingerprint of your imported key is the same as the key owner's, you have a correct copy of the key.
The following example illustrates the steps that you follow to verify a 1425SC BIOS DUP: 1 Download the following two files from support.dell.com: • PESC1425-BIOS-LX-A01.bin.sign • PESC1425-BIOS-LX-A01.bin 2 Import the public key by running the following command line: gpg --import The following output message appears: gpg: key 23B66A9D: "Dell Computer Corporation (Linux Systems Group)
NOTE: If you have not validated the key as shown in step 3, you will receive additional messages: gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: 4172 E2CE 955A 1776 A5E6 1BB7 CA77 951D 23B6 6A9D Compatibility Concerns DUPs are designed to confirm that all prerequisites are satisfied before applying the update to your system.
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. After you apply an update that requires a reboot, you must restart the system to complete the update. You have the option of choosing to defer the reboot until another time as long as you do not turn off the system.
The following are two example commands that redirect output to a log file: ./PE2600-BIOS-LX-A01.bin | tee -a /var/bioslogs.log ./PE2600-BIOS-LX-A01.bin -q | tee -a /var/bioslogs.log If you run these commands in the order shown above, the first command directs its interactive mode output to be appended to the log file. The second command directs its non-interactive mode output to be appended to the end of the same log file.
Confirming the Update To ensure that DUPs were applied to your system, review the console output that was generated during execution. See "Troubleshooting" for detailed information about the messages. If you want to revert to a previous (older) version of the software after updating to a newer version, you must download the appropriate DUP from support.dell.com and install it. To install the previous version from a script, use -q (unattended) mode.
To prepare the system to run the company's new financial software, perform the following general steps: 1 Use the Dell Systems Management Tools and Documentation DVD that came with the Dell system to install the most current version of the Red Hat® Enterprise Linux® AS operating system. 2 Log on to support.dell.com, select Drivers and Downloads and enter the Dell hardware service tag for the Dell system. Otherwise, you can also select the Model.
7 Verify the PE2850 BIOS package digital signature by running the following command: gpg --verify PE2850-BIOS-LX-A02.bin.sign PE2850BIOS-LX-A02.bin The following output message appears: gpg: Signature made Thu 14 Apr 2005 04:25:37 AM IST using DSA key ID 23B66A9D gpg: Good signature from "Dell Computer Corporation (Linux Systems Group)
manage these systems, you have invested in a software distribution tool that allows you to schedule remote software installation and updates. You also have a planned 4-hour service window each weekend when you can perform any maintenance functions necessary on the company’s systems. To roll out the BIOS update to the company’s Dell systems, you perform the following general steps: 1 Log on to support.dell.com, select Drivers and Downloads and enter the Dell hardware service tag for the Dell system.
Command Line Interface Reference Using the CLI This section provides information for using the command line interface (CLI) for Dell™ Update Packages (DUPs). CLI Options You can display information about CLI options by typing the DUP name and either -h or --help at a command line prompt. For example, type the following command to get a help screen about the CLI options: ./packagename.bin -h or --help The console displays all of the command line options and provides help for each choice.
Table 3-1. CLI Options: Usage (continued) CLI Option CLI Task Description -c Determine if the update can be ./packagename.bin applied to the target system. -c Check option -f Force option Command Syntax Force a downgrade or update to ./packagename.bin an older version. -q -f The -q option is required when using the -f option. NOTE: Before downgrading the software to a previous version, see the documentation for the previous version.
Table 3-1. CLI Options: Usage (continued) CLI Option CLI Task Description --rebuild Automatically rebuild a DUP to ./packagename.bin support Linux operating system --rebuild kernels in addition to the supported kernels. Rebuild option Command Syntax See "Rebuilding Packages." 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.
Table 3-2. 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. 3 DEP_SOFT_ERROR Soft dependency error Some possible explanations are: • You attempted to update to the same version of the software.
Table 3-2. Exit Codes (continued) Value Message Name Display Name Description 5 Qualification error The DUP is not applicable to the system. Some possible explanations are: QUAL_HARD_ERROR • The operating system is not supported by the DUP. • The system is not supported by the DUP. • The DUP is not compatible with the devices found in your system. A QUAL_HARD_ERROR cannot be suppressed by using the /f switch. 6 REBOOTING_SYSTEM Rebooting system The system is being rebooted.
Table 3-2. Exit Codes (continued) Value Message Name 7 Display Name Description 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. The format of the output is: .
Rebuilding Packages Overview When you download a Dell™ Update Package (DUP) from the Dell Support website at support.dell.com, you want to apply it to a specific target system.
The Dell-enabled path allows you to customize a DUP by using the --rebuild option. The prerequisites for using the --rebuild option are described in "Setting Up a Test System for Rebuilding a Package." The Dell-enabled path is described by the flow diagram in Figure 4-1. Figure 4-1. Dell-Enabled Path for Rebuilding Packages Dell Supported OS? N Use the --rebuild option to customize the package packagename.
4 The DUP checks to make sure that the kernel, for the package you are trying to apply to your target system, is supported. If the kernel is not supported, you must follow the "Dynamic Kernel Support" procedures and other procedures found later in this section to build a customized package. NOTE: It is recommended that the --rebuild option be executed on a test system having the same configuration.
Determining Whether Your Package Is Supported Rebuilding a supported kernel does not require any prerequisites. In this case, the standard DUP is used and the rebuild process completes successfully. Rebuilding an unsupported kernel requires prerequisites. See "Prerequisites for the Test System." DUP execute on a given target system and can determine if the running kernel is supported by the package you are trying to apply to your system.
Setting Up a Test System for Rebuilding a Package Dell recommends using a test system that has the same running kernel as the kernel that will be running on the system in the production environment. Scenario The following scenario covers the major steps that you would follow in determining that your downloaded package does not support the running kernel on the Dell system to which you were trying to apply the package.
6 Apply the rebuilt package to a test system to ensure that the package applies without errors. For example, type the following command: ./PE2850--ESM_FRMW_LX_R92394.bin--CUSTOM If package execution results in errors, correct the errors and rebuild and reapply the package until you get satisfactory results. 7 Distribute the rebuilt package to all 200 of the target systems. You can write a script to apply the package to all systems.
5 Dell OpenManage™ Server Administrator is not installed on the test system: Ensure that the Server Administrator is not installed on the test system. You cannot rebuild a package on a system that has Server Administrator installed. NOTE: It does not matter whether Server Administrator is installed on the production systems to which the rebuilt packages are to be distributed and applied. Server Administrator cannot be present on the system where the packages are rebuilt.
Rebuilding a Package to Add Kernel Support to a Single System The following command rebuilds the package for the currently running version of the kernel. ./packagename.bin --rebuild Depending on your system configuration, the rebuild takes between a few seconds and a few minutes to complete. DUPs display any error messages encountered while executing the rebuild command. The /tmp directory requires 6 MB or more to execute the --rebuild command.
The package can be built on one test system that supports kernel version (a). The output from the rebuilt package for kernel (a) can be copied to another system that is running kernel (b). The package can be rebuilt on the test system running kernel (b), and then copied to the system running kernel (c). The package can be rebuilt on test system c and the resulting output package will have a package that contains support for kernel versions (a), (b), and (c).
Deploying Custom Packages Across the Environment These modified custom packages rebuilt for a custom environment can be deployed across the network. The execution behavior of the rebuilt packages will not be modified. DUPs would still check for compatibility of the package with the system to which it is being applied, and for all other prerequisites that must be met for successful package execution as discussed in the "Using Dell Update Packages" and "Command Line Interface Reference" sections.
Troubleshooting Known Issues The following are known issues and corrective actions for Dell™ Update Packages (DUPs) for Linux operating systems: 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. Abnormal termination of a DUP When a DUP stop abruptly due to a power outage or abnormal termination, perform the following steps: 1 Remove the lock file.
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.
Table 5-1. Update Packages Message Information (continued) Message Description/Solution This Update Package is not compatible with any of the devices detected in your system. Select a compatible DUP for the device(s) you want to update, and try again. The prerequisite software version for this update was not found. Software application name: Current version: Required version: The DUP you selected cannot be installed because a prerequisite requirement was not met.
Table 5-1. Update Packages Message Information (continued) Message Description/Solution The version of this Update Package is the same as the currently installed version. Software application name: Package version: Installed version: The DUP you selected cannot be installed because the same version of the software already exists on the system. (Using the interactive mode) Type Y or N when prompted to continue. (Using the CLI) Specify the -f option.
Table 5-1. Update Packages Message Information (continued) Message Description/Solution Kernel source for the running kernel is not installed, and the currently installed OpenIPMI driver RPM was installed without the kernel source for the running kernel.
Table 5-1. Update Packages Message Information (continued) Message Description/Solution You must reboot the system for If you shut down or power off the the update to take effect. system after performing an update, you will lose the update. After performing a BIOS update, do not power off the system. Reboot the system for the update to take effect. An Update Package is already running. Wait until it is complete before proceeding with another update. You can run only one DUP at a time.
Table 5-1. Update Packages Message Information (continued) Message Description/Solution Cannot create temporary file "filename" The package cannot create the temporary file for a technical reason, such as lack of disk space, permissions, or a pre-existing file. Unable to create Temp Files. Please ensure that there is enough space in the tmp folder. The package cannot create the temporary file for a technical reason, such as lack of disk space, permissions, or a pre-existing file.
Table 5-1. Update Packages Message Information (continued) Message Description/Solution Rebuilding Package Failed Uninstallation of driver was unsuccessful. The package could not be rebuilt because the driver could not be uninstalled. Package has been rebuilt successfully. The package rebuild was successful. Rebuilding Package Failed Ensure that the directory from which Error creating output package. the package rebuild option is being executed is writable.
Table 5-1. Update Packages Message Information (continued) Message Description/Solution Rebuilding Package Failed RPM Installation failed with error code= Provides the RPM error code that prevented the package from being rebuilt. packagename.bin: Rebuilding Package failed - Unable to extract package contents. Ensure that there is enough space in the /tmp directory. packagename.bin: Rebuilding Package - Kernel is already supported by this package.
Table 5-1. Update Packages Message Information (continued) Message Description/Solution Package has been rebuilt successfully. Output package: packagename.bin:--CUSTOM. Package is ready for distribution and execution on production systems with the same running kernel as the system on which it was rebuilt. Package has been rebuilt successfully. Package is ready for distribution and execution on production systems with the same running kernel as the system on which it was rebuilt. packagename.
Table 5-1. Update Packages Message Information (continued) Message Description/Solution The running kernel is not supported. See "Rebuilding Packages" in the Update Package User’s Guide. See the "Rebuilding Packages" section. You may be able to customize your package to support the kernel you are running. 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 5-1. Update Packages Message Information (continued) Message Description/Solution Unable to build a device Select a compatible DUP and try again. driver for the running kernel because it is not supported on your system. The Intel IMB driver is currently loaded. Please unload the driver before executing. Warning: The shell less command is not available. When viewing Release Notes, press space to continue viewing notes, q to continue DUP processing.
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.
Sep 10 00:14:54 localhost spsetup.bin[8088]: Package Release ID=R54734 Package Description=Dell ESM Firmware, A22 Previous version=1.63 New Version=1.63 Support Log path= /var/log/dell/updatepackage/log/support/R54734.log Exit code = 2 (Reboot required) Sep 19 17:27:05 7708sk1 spsetup.bin[7835]: Package Release ID=R57025 Package Description=Dell ESM Firmware, A24 Support Log path= /var/log/dell/updatepackage/log/support/R57025.
Running validation... BIOS Application: BIOS Previous version: A19 New version: A21 The version of this Update Package is newer than the currently installed version. Software application name: BIOS Package version: A21 Installed version: A19 Executing update... WARNING: DO NOT STOP THIS PROCESS OR INSTALL OTHER DELL PRODUCTS WHILE UPDATE IS IN PROGRESS. THESE ACTIONS MAY CAUSE YOUR SYSTEM TO BECOME UNSTABLE! The system should be restarted for the update to take effect.
... ...
Glossary The following list defines or identifies technical terms, abbreviations, and acronyms used in this guide. BIOS Acronym for basic input/output system. Your system's BIOS contains programs stored on a flash memory chip. The BIOS controls the following: • Communications between the microprocessor and peripheral devices, such as the keyboard and the video adapter • Miscellaneous functions, such as system messages CLI Abbreviation for command line interface.
DTK Acronym for Dell OpenManage Deployment Toolkit. DTK includes a set of utilities for configuring and deploying Dell systems and is designed for users who need to build scripted installations to deploy large numbers of servers in a reliable fashion without having to dramatically change their current deployment processes.
GNU Privacy Guard The GNU Privacy Guard (GnuPG or GPG) is a free software replacement for the PGP suite of cryptographic software, released under the GNU General Public License. interactive mode The method by which you can install DUPs interactively through the CLI.
pre-operating system environment A shell environment used to configure system hardware before a major operating system, such as Microsoft Windows or Linux, is installed. rebuild The --rebuild option is a process that modifies a DUP so that the package can support operating systems and/or running kernels for Linux operating systems beyond those that were supported and tested for the original DUP that you downloaded from support.dell.com.
Index B D BIOS update for 200 systems usage scenario, 29 delivering Update Packages to your systems, 26 Dell-enabled path, 37 C Catalog.
I determining whether your package is supported, 40 dynamic kernel support, 39 setting up a test system, 41 to add kernel support for multiple kernel versions, 44 Important tips using Update Packages, 13 K key, verify, 22, 24 rebuilding a package to add kernel support to a single system, 44 M retasking a system usage scenario, 27 message logs for Update Packages, 59 messages, 48 RPM, 36 S Server Administrator documentation, 14 N non-interactive mode, 32 setting up a test system for rebuilding a p
T system and user requirements, 11 troubleshooting, 48 typical usage scenarios, 27 unattended mode, 27 updating many systems, 26 verifying the digital signature, 21-24, 28 verifying the update, 27 troubleshooting known issues, 47 typical usage scenarios BIOS update for 200 systems, 29 retasking a system, 27 typical usage scenarios for using Update Packages, 27 U Update Options, 8 element update, 8 system update, 9 Update Packages acquiring, 18 applying on a running system, 25 before you begin, 17 CLI com
Index 70
