Dell Update Packages Version 6.2 User Manual

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.

____________________

Reproduction of these materials in any manner whatsoever without the written permission of Dell Inc. is strictly forbidden.

Trademarks used in this text: Dell, the DELL logo, and OpenManage are trademarks of Dell Inc.; Microsoft and Windows are either trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries; Intel is a registered trademark of Intel Corporation in the United States and other countries; Red Hat and Red Hat Enterprise Linux are registered trademarks of Red Hat, Inc. in the United States and other countries; SUSE is a registered trademark of Novell, Inc. in the United States and other countries; VMware and ESX Server are registered trademarks or trademarks of VMware, Inc. in the United States and/or other jurisdictions; Citrix and XenServer are either trademarks or registered trademarks of Citrix Systems, Inc. in the United States and/or other countries.

Other trademarks and trade names may be used in this document to refer to either the entities claiming the marks and names or their products. Dell Inc. disclaims any proprietary interest in trademarks and trade names other than its own.

December 2009

Contents

1 Getting Started With Dell

Update Packages . . . . . . . . . . . . . . . . . . . 9

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Server Update Utility and DUPs

Update Options

Supported Operating Systems . . . . . . . . . . . . . . 11

OpenIPMI Requirements

Using DUPs in the DTK Pre-Operating System Environment

Dell-Qualified and Dell-Enabled Packages

Before You Begin . . . . . . . . . . . . . . . . . . . . 13

How to Obtain DUPs from the Dell Support Website

Installation Order of DUPs

Important Tips to Remember for

Using DUPs . . . . . . . . . . . . . . . . . . . . . 15

Other Documents You May Need . . . . . . . . . . . . 15

Obtaining Technical Assistance

. . . . . . . . . . . . . . . . . . . 10

. . . . . . . . . . . . . . . . . . . 12

. . . . . . . . . . . . . . . . . . 13

. . . . . . . . . . . . . 10

. . . . . . . . . . . . . . . . . 11

. . . . . . . 13

. . . . . . . . . . . . . 14

. . . . . . . . . . . . 16

2 Using Dell Update Packages . . . . . . . . . . 17

Before You Begin . . . . . . . . . . . . . . . . . . . . 17

Contents 3

Develop Your System Update Plan . . . . . . . . . 17

Acquiring DUPs

. . . . . . . . . . . . . . . . . . . 18

Update Packages Component and

System Compatibility

Executing DUPs

. . . . . . . . . . . . . . . . 18

. . . . . . . . . . . . . . . . . . . 19

Verifying the Digital Signature . . . . . . . . . . . 21

Compatibility Concerns

. . . . . . . . . . . . . . . 23

Effects of Applying the Updates on a

Running System . . . . . . . . . . . . . . . . . . . 24

Delivering DUPs to Your Systems

Updating Many Systems

. . . . . . . . . . 25

. . . . . . . . . . . . . . 26

Confirming the Update . . . . . . . . . . . . . . . 26

Typical Usage Scenarios. . . . . . . . . . . . . . . . . 27

Scenario One—Retasking a System

. . . . . . . . 27

Scenario Two — BIOS Update for

200 Systems . . . . . . . . . . . . . . . . . . . . . 29

3 Performing BIOS and Firmware

Updates Using Dell Linux

Online Repository . . . . . . . . . . . . . . . . . . 31

4 Contents

Overview . . . . . . . . . . . . . . . . . . . . . . . . . 31

Setting Up/Bootstrapping the Repository

Creating a Local Mirror

Installing Firmware-tools

. . . . . . . . . . . . . . . 32

. . . . . . . . . . . . . . . . 33

. . . . . . . . 32

Downloading Applicable Firmware . . . . . . . . . . . 33

Inventory Installed Firmware

Updating BIOS and Firmware

Updating BIOS and Firmware Using CLI

. . . . . . . . . . . . . . 34

. . . . . . 34

Updating BIOS and Firmware Using

Graphical User Interface (GUI) . . . . . . . . . . . 36

Automatically Update Firmware

Viewing Log Information

. . . . . . . . . . . . 37

. . . . . . . . . . . . . . . . 37

4 Update and Rollback in Unified

Server Configurator - Lifecycle

Controller Enabled . . . . . . . . . . . . . . . . . 39

Update in USC LCE . . . . . . . . . . . . . . . . . . . . 39

Rollback in USC LCE

. . . . . . . . . . . . . . . . . . . 40

5 Command Line Interface Reference . . . . 41

Using the CLI . . . . . . . . . . . . . . . . . . . . . . . 41

CLI Options

Exit Codes for CLI

. . . . . . . . . . . . . . . . . . . . . 41

. . . . . . . . . . . . . . . . . . . . 44

6 Rebuilding Packages . . . . . . . . . . . . . . . . 47

Overview . . . . . . . . . . . . . . . . . . . . . . . . . 47

Dell-Qualified Path . . . . . . . . . . . . . . . . . . . 47

Dell-Enabled Path

Dynamic Kernel Support

. . . . . . . . . . . . . . . . . . . . 47

. . . . . . . . . . . . . . . . . 49

Determining Whether Your Package Is Supported

. . . . . . . . . . . . . . . . . . . . . . . 50

Setting Up a Test System for Rebuilding a Package

. . . . . . . . . . . . . . . . . . 51

Contents 5

Scenario. . . . . . . . . . . . . . . . . . . . . . . 51

Prerequisites for the Test System

. . . . . . . . . . . . 52

Rebuilding a Package to Add Kernel Support to a Single System

. . . . . . . . . . . . . . . 54

Rebuilding the Package to Add Kernel Support for Multiple Kernel Versions

Scenario

. . . . . . . . . . . . . . . . . . . . . . . 55

. . . . . . . . . . 54

Deploying Custom Packages Across the Environment

. . . . . . . . . . . . . . 56

7 Troubleshooting . . . . . . . . . . . . . . . . . . . 57

Known Issues . . . . . . . . . . . . . . . . . . . . . . 57

Diagnostic Tasks will not run while a DUP reboot is pending

Abnormal termination of a DUP. . . . . . . . . . . 57

Error while loading shared libraries

Insufficient free physical memory to

load the BIOS image . . . . . . . . . . . . . . . . 57

Kernel panic while running storage controller firmware update packages

Loss of functionality while renaming

Linux DUPs . . . . . . . . . . . . . . . . . . . . . 58

Yum and Up2date repository management software caches incorrect repository

metadata . . . . . . . . . . . . . . . . . . . . . . 58

Use Dell Linux Repository with yum and

Red Hat Enterprise Linux version 4 . . . . . . . . . 58

. . . . . . . . . . . . . . . 57

. . . . . . . . 57

. . . . . . . 58

6 Contents

Messages . . . . . . . . . . . . . . . . . . . . . . . . 59

DUP Message Logs

Messages Log

Messages Log File

. . . . . . . . . . . . . . . . . . . 69

. . . . . . . . . . . . . . . . . 70

Support Log File Example. . . . . . . . . . . . . . 70

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Contents 7

8 Contents

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.

By using DUPs, you can perform the following functions:

• Apply an individual update to a system by using an interactive command line interface (CLI)

• Execute multiple updates for your system by using a script comprised of non

interactive commands that you write using the CLI feature

• Leverage your operating system’s scheduling and software distribution utilities to apply updates remotely to any number of servers

Each DUP (Dell Update Package) is designed to update a single software component on your system. This product feature allows you to select and apply the updates that you want for your system, minimizing the resources required to transport the DUP across your network.

DUPs improve your ability to update your systems effectively. For example, each DUP contains pertinent information about when Dell issued the package, which systems the DUP is designed to support, and what functional enhancements are contained in the update or which problems were fixed.

Each DUP contains the execution logic to verify that the update will work on your system. When using DUPs, you are not required to use any Dell OpenManage™ software applications, and you do not have to create alternative media. Each DUP also carries a digital signature to ensure reliable and trusted authentication. See "Verifying the Digital Signature" for more information.

You can use DUPs interactively, which is ideal for applying a limited number of updates. When you execute a package interactively, it first displays a scrollable view of the package release notes. You may view these notes

Getting Started With Dell Update Packages 9

before optionally continuing with the execution of the package. You can also use DUPs in non 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.

-interactive mode to facilitate rapid deployment for an

Server Update Utility and DUPs

Dell OpenManage Server Update Utility (SUU) is a DVD–based application that is used to identify and apply the latest updates to your system. It is a Graphical User Interface (GUI) and a Command Line Interface (CLI) based application. SUU compares the versions of components currently installed on your system with the update components packaged on the Dell Server Updates DVD and then displays a comparison report of the versions and provides the option of updating the components. You can use SUU to update your system or view the updates available for any system listed in the repository. The Dell Server Updates DVD is available as part of the Dell OpenManage subscription service kit.

Linux DUPs can be downloaded from the Dell Support site at

support.dell.com. They are also available in the repository on the Dell Server Updates DVD. The repository folder in the Dell Server Updates DVD

contains Windows and Linux DUPs, Catalog.xml (that contains information about both Windows and Linux DUPs), and the DellSoftwareBundleReport.html. SUU uses DUPs to update the system components.

Update Options

You can update your system components using any one of the following two options:

•

Element Update

(element) to a specific version. Use DUP to perform element updates.

•

System Update

that you use SUU to automatically:

– inventory the Dell firmware and drivers on that system

10 Getting Started With Dell Update Packages

–To update an

–To update all elements on your system. Dell recommends

individual

system software component

– compare the installed configuration with the content on the

Server Updates

– 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.dell.com/manuals, for information on how SUU identifies and applies updates to your entire system.

Figure 1-1 helps you choose between SUU and DUPs when performing updates.

Figure 1-1. Choosing between SUU and DUPs

DVD

Dell

Supported Operating Systems

For a complete list of supported systems and operating systems, see the Dell Systems Software Support Matrix available on the Dell Support website at support.dell.com/manuals. The Dell Systems Software Support Matrix has information about the various Dell systems, the operating systems supported by these systems, and the Dell OpenManage™ components that can be installed on these systems.

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.

Getting Started With Dell Update Packages 11

Using DUPs in the DTK Pre-Operating System Environment

The Dell OpenManage Deployment Toolkit (DTK) includes utilities, sample scripts, and other tools for configuring and deploying Dell systems. DTK is released in two versions: the Linux version is distributed as an Embedded Linux

-based ISO, and the Windows

(Windows PE) version is distributed as a package of Dell with instructions on how to integrate with a standard Windows PE image. Booting the CD created from the ISO image creates a To ol k it folder which contains subdirectories with the necessary files to perform deployment tasks.

NOTE: Currently, DUPs are supported only in the DTK embedded Linux

environment.

The bootable DTK embedded Linux environment is required for bare-metal (or pre-operating system) DUP execution and is bootable from many types of media and does not require the local disk. It allows users to use Linux DUPs for change management.

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

Preinstallation Environment

-provided content

./packagename -q -r

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/manuals. The required minimum kernel version is 2.6.9-42.

12 Getting Started With Dell Update Packages

Dell-Qualified and Dell-Enabled Packages

A DUP can be applied as a Linux operating system DUP for a system in one of the following ways:

• The DUP that you are applying See "Dell-Qualified Path" for more information.

• The DUP that you are applying can be kernels and operating systems in your environment. See "Dell-Enabled Path" for more information.

matches

the Dell-qualified operating systems.

enabled

to work with the running

Before You Begin

DUPs support Dell systems running the operating systems listed in the

Overview" section.

that has root (administrator) privileges.

How to Obtain DUPs from the Dell Support Website

Log on to

Click

Drivers and Downloads.

Enter your service tag or choose your product model.

Select your product family and product line.

Select your operating system, language, category, and the update importance. A list of applicable updates are displayed.

Click

Download Now

You can also download a different file format from the column labeled

File Title

If you want to download more than one file type, you must do so one at atime.

To complete the download of your file, follow the directions on the screen.

You must be able to log on to the system with an account

support.dell.com

. Select a file format for your DUP and single-click its filename.

Getting Started With Dell Update Packages 13

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:

Add executable privileges to the package filename. Type the following command:

chmod +x packagename.bin

Verify that the package meets the prerequisites for performing an update.

To perform the check from the CLI, type the following command at the command line prompt:

./packagename.bin -c

Determine a methodology 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 have a requirement for running one or more updates from a script on one or more systems in non-interactive mode.

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

3ESM firmware

4BIOS

NOTE: If you have updated the BIOS, the changes to the BIOS do not take effect

until you reboot your system.

NOTE: To ensure a single reboot, you must install the ESM firmware update before

the BIOS update.

14 Getting Started With Dell Update Packages

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.

• Before updating all systems, perform the upgrade on one nonessential system to test the update.

• Do not run other applications while executing DUPs.

• Do not shut down the system while an update is in progress.

• Ensure that the system reboots without power interruption after performing a BIOS update.

• Do not close any terminal console windows used for performing the DUP CLI execution, while DUP executions are in progress.

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 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 Help" in your system's

16 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 smooth operation.

Before you apply any update to your system, you may want to carefully plan your update strategy, based on the conditions that are necessitating the update. Many reasons may exist for making the decision to update your Dell system, such as:

• Correcting a security concern

• Correcting a problem on your system, based on a recommendation from Dell support personnel

• Updating a system software component to a minimum level required by an application

• Gaining access to a new feature or improved performance

• Updating all system components as part of your company's periodic maintenance process

Each of the preceding update situations entails different levels of urgency, but all require a certain level of planning to ensure a successful update with minimal disruption to your applications and users. The following subsections help you develop the system update strategy that best fits your needs, your company's policies and procedures, and the tools available to you.

Develop Your System Update Plan

You may want to update your system for many reasons, as mentioned in the preceding section. This update requirement may be planned or unplanned.

Using Dell Update Packages 17

Planned updates occur as a part of your regular cycle of maintaining your systems with up-to-date BIOS, firmware, and drivers. Most IT organizations establish a regular schedule for performing the updates that are integrated with the planned maintenance functions. The frequency of these updates varies from company to company; however, it is common for companies to adopt quarterly or semi-annual update schedules. Irregular but planned updates may occur when a system is retasked with a new application or when the operating system is upgraded or changed. When you have scheduled planned outage or downtime for your system, consider upgrading the system software components.

Unplanned updates typically occur as a result of applying a critical upgrade to your system to avoid data loss, service interruption, or security threats. You may, for example, be advised to apply an update in response to a call you have placed to a Dell support professional. Although the urgency of applying such an update is greater than a planned update, you know that you must apply careful thought and consideration to ensure a successful update with minimal disruption to your users. The key to success is always having a well-planned strategy for all update scenarios.

Acquiring DUPs

Dell provides a number of aids to help you determine whether or not your system requires an update. You can locate the DUP for your system on the Dell Support website at support.dell.com. For instructions, see "How to Obtain DUPs from the Dell Support Website."

Update Packages Component and System Compatibility

After you locate your DUP, read the summary information to determine whether or not you should download the update and apply it to your system. You can run the DUP and read the summary information by using the command line interface option --version. For more information on the

--version option, see "Command Line Interface Reference." This information is provided to help you determine whether the update is appropriate for your system and your specific environment.

18 Using Dell Update Packages

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.

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. Once a package has been delivered to the target system, administrators can execute the package in its simplest form by typing ./packagename.bin from the working directory, where packagename is the model and component name of the package. This syntax assumes that the .bin file has the appropriate permissions set and that a user account with root privileges executes the update. Once underway, the DUP will echo its progress and status to the console (stdout) and log its activity to /var/log/messages.

The following example shows the command for applying a BIOS DUP to a Dell system in interactive mode:

chmod +x ./PE1650-BIOS-LX-A10.bin ./PE1650-BIOS-LX-A10.bin

The DUP application writes the following messages to the screen. Interactive mode requires Y/N responses to continue with update and reboot.

Collecting inventory... Running validation... BIOS The version of this Update Package is newer than the currently installed version. Software application name: BIOS Package version: A10 Installed version: A9 Continue: Y/N? Y Y entered; update was forced by user 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.

-specific

Using Dell Update Packages 19

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:

Dell Server System BIOS, A10

Release Date:

November 21, 2003

Release ID:

R60452

Supported System(s):

PowerEdge 1650

Prerequisite(s):

BIOS A05

Description:

PowerEdge 1650, BIOS, A10

Supported Device(s):

Server System BIOS

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.

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.

In the following command example, the command applies a BIOS DUP without any user confirmation, forces the execution in the case of a downgrade from a more recent BIOS version, and reboots the system after the DUP is applied. This command is executed provided the DUP satisfies all the system and version requirements.

./PE2850-ESM_FRMW_LX_R92394.bin -q -f -r

For more information on the command line interface (CLI), see "Command Line Interface Reference."

20 Using Dell Update Packages

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:

Get the Dell Linux public GnuPG key, if you do not already have it. You can download it by navigating to

Dell Public GPG key

Import the public key to your gpg trust database by running the following

link.

command:

gpg --import <Public Key Filename>

NOTE: You must have your private key to complete the process.

To avoid a distrusted-key warning, validate the public key by its fingerprint before you use it.

Type the following command:

gpg --edit-key 23B66A9D

Within the GPG key editor, type appears:

pub 1024D/23B66A9D 2001-04-16 Dell, Inc. (Product Group) <linux-security@dell.com> Primary key fingerprint: 4172 E2CE 955A 1776 A5E6 1BB7 CA77 951D 23B6 6A9D

lists.us.dell.com

fpr

. The following message

and clicking the

If the fingerprint of your imported key is the same as the key owner's, you have a correct copy of the key. You can verify the key's owner in person, over the phone, or by any other means that guarantees that you are communicating with the key's true owner.

While still in the key editor, type

Answer the list of trust-validation questions that appears and create

sign

a passphrase to use as your secret key.

You must import and validate the public key only once.

Using Dell Update Packages 21

Obtain the Linux DUP and its associated signature file from the Dell Support website at

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. To download the files, right-click the download link and use the "Save Target As..." file option.

Verif y th e DUP:

support.dell.com/support/downloads

gpg --verify <Linux Update Package signature filename> <Linux Update Package filename>

The following example illustrates the steps that you follow to verify a 1425SC BIOS DUP:

Download the following two files from

support.dell.com

• PESC1425-BIOS-LX-A01.bin.sign

• PESC1425-BIOS-LX-A01.bin

Import the public key by running the following command line:

gpg --import <linux-security-publickey.txt>

The following output message appears:

gpg: key 23B66A9D: "Dell Computer Corporation (Linux Systems Group) <linuxsecurity@dell.com>" not changed gpg: Total number processed: 1 gpg: unchanged: 1

22 Using Dell Update Packages

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.

Verify the PESC1425 BIOS package digital signature by running the following command:

gpg --verify PESC1425-BIOS-LX-A01.bin.sign PESC1425-BIOS-LX-A01.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) <linuxsecurity@dell.com>"

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. Each DUP checks to ensure the following:

• The logged-on user has root privileges.

• The DUP to be applied in the command is compatible with your target system.

• The DUP to be applied in the command is compatible with the operating system running on your system.

Using Dell Update Packages 23

+ 53 hidden pages

Dell Update Packages Version 6.2 User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Getting Started With Dell Update Packages

Overview

Server Update Utility and DUPs

Update Options

Supported Operating Systems

OpenIPMI Requirements

Using DUPs in the DTK Pre-Operating System Environment

Dell-Qualified and Dell-Enabled Packages

Before You Begin

How to Obtain DUPs from the Dell Support Website

Installation Order of DUPs

Important Tips to Remember for Using DUPs

Other Documents You May Need

Obtaining Technical Assistance

Using Dell Update Packages

Before You Begin

Develop Your System Update Plan

Acquiring DUPs

Update Packages Component and System Compatibility

Executing DUPs

Verifying the Digital Signature

Compatibility Concerns