Dell™ Update Packages for Linux Operating Systems User’s Guide
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. © 2009 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 . . . . . . . . . . . . . . . . . . 16 Update Packages Component and System Compatibility . . . . . . . Executing DUPs . . . . . . . . . . 16 . . . . . . . . . . . . . . . . . . 17 . . . . . . . . . . . 19 . . . . . . . . . . . . . . 22 Verifying the Digital Signature Compatibility Concerns . Effects of Applying the Updates on a Running System . . . . . . . . . . . . . . . . 24 .
4 Rebuilding Packages . Overview . . . . . . . . . . . . . . . . 39 . . . . . . . . . . . . . . . . . . . . . . . . 39 . . . . . . . . . . . . . . . . . . . 39 . . . . . . . . . . . . . . . . . . . . 39 Dell-Qualified Path Dell-Enabled Path Dynamic Kernel Support . . . . . . . . . . . . . . . . . Determining Whether Your Package Is Supported . . . . . . . . . . . . . . . . . . Setting Up a Test System for Rebuilding a Package . . . . Scenario . . . . . . . . . . . . . . 43 43 . . . . . . .
Kernel panic while running storage controller firmware update packages . . . . . . . 50 . . . . . . . . . . . . . 50 . . . . . . . . . . . . . . . . . . . . . . . . 50 Loss of functionality while renaming Linux DUPs . . . Messages DUP Message Logs . . . . . . . . . . . . . . . . . . . 61 Messages Log . . . . . . . . . . . . . . . . . . . 61 Messages Log File . . . . . . . . . . . . . . . . . Support Log File Example . 62 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 . . .
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.
before optionally continuing with the execution of the package. You can also use 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.
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.
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 the Dell Support website at support.dell.com, or visit the support site for your Linux operating system to download the latest drivers.
A successful update will return the exit code to either 0, 2 or 6. NOTE: For dependencies and information on running DUPs in the Dell-provided embedded Linux environment and in a customized embedded Linux environment and for information on the required files and tools, see the Dell OpenManage Deployment Toolkit User's Guide on the Dell Support website at support.dell.com. The required minimum kernel version is 2.6.9-42.
Before installing DUPs, read the information provided, both online and in the download package. Ensure that the updates you selected are both necessary and appropriate for your system. You may also need to complete some or all of the following steps: 1 Add executable privileges to the package filename. Type the following command: chmod +x packagename.bin 2 Verify that the package meets the prerequisites for performing an update.
Important Tips to Remember for Using DUPs • Prepare repair disks before you perform any updates. • Download the currently installed version of drivers, BIOS, and firmware so that you have a backup plan in case any issues arise. • Ensure that you have a backup of operating system files or system configuration files stored on a system other than the one you are updating. • Ensure that the updates are planned for and performed by the system administrator who knows which applications could be affected.
• The Dell OpenManage Deployment Toolkit (DTK) User's Guide on the Dell Support website at support.dell.com. The guide provides information on how to execute Linux DUPs in the Dell–provided or in the customized embedded Linux environment including the required dependencies. • The Dell OpenManage IT Assistant User’s Guide on the Dell Support website at support.dell.com or on the Dell Systems Management Tools and Documentation DVD.
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.
Executing DUPs You can run DUPs from the console in both interactive and non-interactive modes. 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.
Executing update... WARNING: DO NOT STOP THIS PROCESS WHILE BIOS UPDATE IS IN PROGRESS. STOPPING MAY CAUSE YOUR SYSTEM TO BECOME UNSTABLE! Update successful. 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.
Fixes / Enhancements: * Added support for version 2.8 of the onboard RAID controller (PERC3/Di) firmware. * Corrected issues affecting the Preboot Execution Environment (PXE). * Corrected problems which cause the system to power up at unexpected times. * Corrected problems with the Remote BIOS Update feature. * Corrected issues in BIOS USB Support. * Corrected issues in Embedded Server Management support.
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. You can download it by navigating to lists.us.dell.com and clicking the Dell Public GPG key link.
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 shown on the same web page as 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. For example, if a Linux DUP is named PE1850-BIOS-LX-A02.BIN, its signature filename is PE1850-BIOS-LX-A02.BIN.sign.
3 Validate the Dell public key, if you haven’t done so previously, by typing the following command: gpg --edit-key 23B66A9D At the command prompt, type the following commands: fpr sign Answer the validation questions. 4 Verify the PESC1425 BIOS package digital signature by running the following command: gpg --verify PESC1425-BIOS-LX-A01.bin.sign PESC1425-BIOS-LX-A01.
• The device associated with the DUP is present on your system. • The minimum required versions of related system software are running on your system. DUPs are designed with built-in error handling capabilities to ensure that the preceding requirements are validated. If the conditions are not met, no update occurs. DUPs also check for dependencies between BIOS and certain ESM packages. The application design allows you to create groups of DUPs and apply them to a wide range of systems.
Specifying the Order of Multiple Updates When applying multiple updates at the same time, be sure to use the order indicated in "Installation Order of DUPs." As previously noted in "System Reboot Required," you may defer rebooting the system until after running the last of multiple DUPs. Saving Console Output 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.
Updating Many Systems For large environments that consist of hundreds or perhaps thousands of systems, remote software distribution applications provide the best solution. Many of these tools can effectively leverage the DUP and provide the convenience of installing and updating a variety of software, such as operating systems and applications, in a heterogeneous environment. Network file shares also are an effective method of making DUP accessible in a distributed environment.
NOTE: DUPs for Linux can also be found in the repository on the Dell Server Updates DVD that contains the updated BIOS, and firmware components for Dell systems. The Dell OpenManage™ Server Update Utility (SUU) is an application for identifying and applying updates to your system. You can use SUU to update your Dell system or to view updates available for any system supported by SUU.
You can define a location to search for available updates from the following options: – the Dell File Transfer Protocol (FTP) server (ftp.dell.com). You can use a proxy server 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: See the Dell Unified Server Configurator User Guide available on the Dell Support website at support.dell.
Typical Usage Scenarios Scenario One—Retasking a System You are the system administrator for a large company. Your group requires an additional system to support a new financial analysis package, and you have access to a Dell system that is no longer in use, from another department within the company. Because the Dell system has an older operating system installed on it, you plan to upgrade the operating system before installing the new financial application.
5 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)
9 Create a simple script that executes the following packages one-by-one in this order: • ESM system firmware • BIOS Use the CLI -q option on each line in the script for these packages so that you can schedule the process by using the task manager. On each line of the file, you also include | tee -a /var/log/upgrade.log to check the results of the execution. Use the CLI -r option for the last line (BIOS) of the script.
4 Use the software distribution tool to create an update task that delivers the BIOS DUP to all the systems in the network. The update task is a script that invokes the BIOS DUP and uses the CLI -r -q > redirect_output.log options to ensure that the system is rebooted when necessary. Because this BIOS DUP executes only on a Dell system, you can plan on distributing this to all systems regardless of the system model type. The DUP does not affect other systems.
Using Dell Update Packages
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.
Exit Codes for CLI After running DUPs, the exit codes described in Table 3-2 are set. The exit codes help you determine and analyze the execution results after you run DUPs. 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.
Table 3-2. 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 server 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 3-2. Exit Codes (continued) Value Message Name Display Name Description 6 REBOOTING_SYSTEM Rebooting system The system is being rebooted. 7 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.
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 is 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, 30 delivering Update Packages to your systems, 24 Dell-enabled path, 39 C Catalog.
I R Important tips using Update Packages, 13 rebuilding a package Dell-enabled path, 39 Dell-qualified path, 39 determining whether your package is supported, 42 dynamic kernel support, 41 setting up a test system, 43 to add kernel support for multiple kernel versions, 46 K key, verify, 20, 22 M message logs for Update Packages, 61 rebuilding a package to add kernel support to a single system, 46 messages, 50 RPM, 38 N S non-interactive mode, 34 Server Administrator documentation, 13 O setting
T supported installation order of Update Packages, 12 supported order of installation, 24 system and user requirements, 11 troubleshooting, 50 unattended mode, 25 updating many systems, 25 verifying the digital signature, 19-22, 28 verifying the update, 25 troubleshooting known issues, 49 typical usage scenarios BIOS update for 200 systems, 30 Retasking a System, 28 U Update and Rollback in Unified Server Configurator Lifecycle Controller Enabled, 26 Update Options, 8 element update, 8 system update, 9 U
Index 72
