Trademarks used in this text: Dell™, the Dell logo, Dell Boomi™, Dell Precision™ , OptiPlex™, Latitude™, PowerEdge™, PowerVault™,
PowerConnect™, OpenManage™, EqualLogic™, Compellent™, KACE™, FlexAddress™, Force10™ and Vostro™ are trademarks of Dell
Inc. Intel®, Pentium®, Xeon®, Core® and Celeron® are registered trademarks of Intel Corporation in the U.S. and other countries. AMD
is a registered trademark and AMD Opteron™, AMD Phenom™ and AMD Sempron™ are trademarks of Advanced Micro Devices, Inc.
Microsoft®, Windows®, Windows Server®, Internet Explorer®, MS-DOS®, Windows Vista® and Active Directory® are either trademarks
or registered trademarks of Microsoft Corporation in the United States and/or other countries. Red Hat® and Red Hat
Enterprise Linux® are registered trademarks of Red Hat, Inc. in the United States and/or other countries. Novell® and SUSE® are
registered trademarks of Novell Inc. in the United States and other countries. Oracle® is a registered trademark of Oracle Corporation
and/or its affiliates. Citrix®, Xen®, XenServer® and XenMotion® are either registered trademarks or trademarks of Citrix Systems, Inc. in
the United States and/or other countries. VMware
trademarks of VMware, Inc. in the United States or other countries.
Corporation.
2012 - 12
®
,
Virtual SMP
®
®
,
vMotion
®
is a registered trademark of International Business Machines
IBM
,
vCenter
®
and
vSphere
®
are registered trademarks or
®
®
Rev. A00
Contents
Notes, Cautions, and Warnings...................................................................................................2
What’s New in This Release.....................................................................................................................................7
Before You Begin......................................................................................................................................................7
Linux Prerequisites and Features...........................................................................................................................10
Dell-Qualified and Dell-Enabled Packages......................................................................................................10
Windows Prerequisites and Features....................................................................................................................10
Installation Order of DUPs......................................................................................................................................11
Important Tips to Remember for Using DUPs.........................................................................................................11
Other Documents You May Need...........................................................................................................................12
2 Using Dell Update Packages...................................................................................................13
Updating Packages Component and System Compatibility....................................................................................13
Executing DUPs in Linux Environment....................................................................................................................13
Verifying the Digital Signature.........................................................................................................................14
Executing DUPs in the Windows Environment.......................................................................................................14
Verifying the Digital Signature on Windows....................................................................................................15
Effects of Applying the Updates on a Running System..........................................................................................15
System Reboot Required..................................................................................................................................15
Saving Console Output for Linux......................................................................................................................16
Delivering DUPs to the Systems.............................................................................................................................16
Updating Many Systems..................................................................................................................................16
Stand-alone Systems and Firewalls.................................................................................................................16
Confirming the Update............................................................................................................................................16
3 Performing BIOS And Firmware Updates Using Dell Linux Online Repository...............19
Setting Up/Bootstrapping the Repository...............................................................................................................19
Creating a Local Mirror....................................................................................................................................19
Updating BIOS and Firmware.................................................................................................................................20
Updating BIOS and Firmware Using CLI..........................................................................................................20
Updating BIOS and Firmware Using GUI..........................................................................................................20
4 Update and Rollback in Lifecycle Controller Enabled Server............................................23
Update in Lifecycle Controller................................................................................................................................23
Rollback in Lifecycle Controller..............................................................................................................................23
5 Command Line Interface Reference......................................................................................25
Linux CLI Options....................................................................................................................................................25
Windows CLI Options..............................................................................................................................................26
Exit Codes for CLI....................................................................................................................................................28
6 Linux Troubleshooting..............................................................................................................31
Known Issues..........................................................................................................................................................31
Diagnostic Tasks Will Not Run While a DUP Reboot is Pending.....................................................................31
Abnormal Termination of a DUP.......................................................................................................................31
Error While Loading Shared Libraries..............................................................................................................31
Insufficient Free Physical Memory to Load the BIOS Image...........................................................................31
Kernel Panic While Running Storage Controller Firmware Update Packages................................................32
Loss of Functionality While Renaming Linux DUPs..........................................................................................32
7 Windows Troubleshooting.......................................................................................................41
Known Issues..........................................................................................................................................................41
Inventory Failure on Microsoft Windows Operating System...........................................................................41
9 Trusted Platform Module and BitLocker Support................................................................47
10 Microsoft Windows Server 2008 User Account Control...................................................49
UAC Restrictions When Running DUPs remotely...................................................................................................50
6
1
Getting Started
A Dell Update Package (DUP) is a self-contained executable in a standard package format that updates a single
software element on the system.
DUPs are available for the following software components:
•System BIOS
•System firmware, also known as the Embedded Systems Management (ESM) firmware
•Network firmware and drivers
•Remote Access Controller (RAC) firmware
•RAID controller firmware and device drivers
•SWRAID 3.0 (S110) Driver
Using DUPs, you can update a wide range of system components simultaneously and apply scripts to similar sets of Dell
systems to bring the system components to the same version levels.
You can use DUPs to:
•Apply an individual update to a system by using an interactive command line interface (CLI).
•Install device drivers in interactive and non-interactive modes.
•Execute multiple updates on the 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 systems.
What’s New in This Release
•Added new HDD support for this release like:
– Hitachi Mars K firmware M2D4
– Hitachi Cobra E firmware N2B4
– Toshiba Mustang firmware DCAA
– Toshiba AL12SX firmware DB04
– Toshiba AL12SE firmware DA09
– Western Digital Sirius firmware D1S4
•Updating Dell Servers by integrating Dell Update Package with Microsoft Windows Server 2012 Cluster Aware
Update. For more information see http://en.community.dell.com/techcenter/extras/m/white_papers/
20217029.aspx
Before You Begin
Before you install and use DUPs, ensure that:
•The system and operating system is supported by DUPs. See Supported Operating Systems for more
information.
7
•You have Administrator privileges.
Downloading DUPs
You can download DUPs from support.dell.com .
NOTE: DUPs are also available in the repository folder in the Dell OpenManage Server Update Utility DVD, along
with the Catalog.xml (that contains information about both Windows and Linux DUPs) and
DellSoftwareBundleReport.html files.
To download DUPs from support.dell.com:
1. Log on to support.dell.com and select Support for Enterprise IT.
2. Select Drivers and Downloads.
3. Enter the service tag or choose your product model.
NOTE: In case you enter the service tag, there is no need choose the product family, line etc.
4. Select the product family and product line.
5. Select the operating system, language, category, and the update importance.
Lists of applicable updates are displayed.
6. Click Download.
7. To complete downloading the file, follow the instructions on the screen.
NOTE: You can also download a different file format from the File Title column by selecting a file format for the DUP
and clicking it. In case you want to download more than one file type, you must do it one at a time.
NOTE: You can also download a DUP or group of DUPs using Dell Repository Manager. See the DRM users guide
for more information.
Feature Overview
This section provides a brief description of the Dell Update Package (DUP) supported features.
DUP Support for PCIe-SSD firmware and driver
Dell PowerEdge Express Flash Peripheral Component Interconnect Express (PCIe) Solid State Device (SSD) is a high
performance storage device designed for solutions requiring low latency, high input output operations per second
(IOPS), and enterprise class storage reliability and serviceability. The Dell PowerEdge Express Flash PCIe SSD is based
on Single Level Cell (SLC) NAND flash technology with a high-speed PCIe 2.0 compliant interface. The high-speed PCIe
2.0 compliant interface helps improve the performance for I/O bound solutions.
NOTE: Firmware update for PCIe-SSD device is not supported on RHEL5_x64 and SLES10_x64 bit operating
systems.
HDD DUP support behind S110
HDD that supported online FW updates could be updated when connected to a H200, H300, SAS5, SAS6, PERC5, PERC6,
H7xx and H8xx servers. With the new feature, the HDD that supports online FW updates can also be updated when
connected to a S110.
8
Supported Operating Systems
For Windows
•Microsoft Windows Server 2012 Standard, Enterprise, Datacenter and Foundation x64 Editions
•Microsoft Windows Server 2008 SP2 Standard, Enterprise, and Datacenter x86 Editions
•Microsoft Windows Server 2008 SP2 Standard, Enterprise, and Datacenter x64 Editions
•Microsoft Windows Server 2008 R2 Standard, Enterprise, and Datacenter x64 Editions with SP1
•Microsoft Windows Server 2008 R2 SP1 HPC Edition
•Microsoft Windows Server 2008 R2 Standard, Enterprise, and Datacenter x64 Editions with SP2
•Microsoft Windows Server 2008 Core Standard, Enterprise, and Datacenter Editions (x64) with SP2
•Microsoft Windows Essential Business Server 2008 Standard and Premium Editions (x64) with SP1
•Microsoft Windows Small Business Server 2011 Standard and Premium Editions
•Microsoft Windows Storage Server 2008 R2 Express, Workgroup, Standard, and Enterprise Editions
•Microsoft Windows Small Business Server 2011 Essentials
•Microsoft Windows Storage Server 2008 Basic, Workgroup, Standard, and Enterprise Editions
•Microsoft Hyper-V R2 and Windows Server 2008 with Hyper-V role R2
For Linux
•Red Hat Enterprise Linux 5.8 x86
•Red Hat Enterprise Linux 5.8 x86_64
•Red Hat Enterprise Linux 6.3 server (64-bit)
•SUSE Linux Enterprise Server 10 SP4 x86_64
•SUSE Linux Enterprise Server 11 SP2 x86_64
•VMware ESX Server version 4.1 Update 3
•Citrix Xen Server 6.1
Installing Device Drivers
DUPs update BIOS, firmware, drivers, and applications. If a device driver is not present in the system, DUPs allow you to
do a fresh installation of the driver. You can install the driver provided 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. Installation results are logged in the DUP Message Logs.
Non-Interactive Mode
When a fresh installation is applicable, executing DUPs with the /s switch installs the driver.
For example, packagename.exe /s and packagename.exe /s /r does a fresh installation of driver DUPs.
NOTE: Not all driver DUPs support fresh installation. See the
Operating Systems readme
file for the list of drivers that do not support fresh installation.
Dell Update Packages for Microsoft Windows
9
Linux Prerequisites and Features
This section lists all the prerequisites and features for Linux Operating System.
Dell-Qualified and Dell-Enabled Packages
Before installing DUPs, read the information provided online and in the download package. Ensure that the updates you
selected are both necessary and appropriate for the 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, type the
following command: ./packagename.bin -c
•Utilize one of the following methodologies for performing the updates. The first method is called the Single
update method. In this method, Run the DUP from the command line in interactive mode to perform the update.
The other method is called the 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 the system. If you are prompted
during installation to obtain the latest drivers, see dell.com/support/manuals. or download the latest drivers from the
Linux support site.
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
OpenManage Deployment Toolkit User's Guide
NOTE: The required minimum kernel version is 2.6.9-42.
at dell.com/support/manuals. .
Dell
Windows Prerequisites and Features
Before installing DUPs, read the information provided online and in the download package. Ensure that the updates you
selected are necessary and appropriate for the system. You may also need to complete some or all of the following
steps:
NOTE: Run the DUP Check option on the target system to ensure that the system meets the prerequisites for
performing an update.To run the check from the CLI, type the following command:
packagename.exe /c /s
To run the check from the GUI, perform the following steps:
1. Double-click the .exe file for the DUP you downloaded.
2. 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
older version prior to DUP 7.2 framework the log file is %SystemDrive%\dell\updatepackage\log
and the path for DUP 7.2 framework onwards the log file are :
Windows2003 : %SystemDrive%\Documents and Settings\All Users\Application Data\Dell\UpdatePackage\log
Windows 2008 and 2012 : %SystemDrive%\Program Data\Dell\UpdatePackage\log .
3. Determine that the target system meets compatibility requirements.
10
4. For more information, see the Dell OpenManage Legacy Compatibility Guide, the Dell Systems Software Support
Matrix, and Other Documents You May Need.
5. Create a directory structure for performing the updates.
6. Determine a methodology for performing the updates. The first method is called as Single update method. In this
method, Run the DUP from the command line in interactive mode to perform the update. The other method is called
as Script method. Use this method if you want to run one or more updates from a script in non-interactive mode.
NOTE: DUPs for Windows can also be found in the repository on the Dell OpenManage Server Update Utility DVD
that contains the updated BIOS, drivers, and firmware components for Dell systems.
Installation Order of DUPs
If you are installing multiple DUPs, install the updates that require a reboot at the end. For recommended installation
order see the following table.
Table 1. Update Packages: Recommended Installation Order
Installation OrderSystem Software Components
1Device driver
2Device firmware
3ESM firmware
4LifeCycle Controller
5BIOS
NOTE: If you have updated the BIOS, Power supply FW, PERC FW, SAS expander FW, PCIeSSD FW, Intel, QLogic
and Broadcom FW the changes to the components take effect only after you reboot the system.
NOTE: To ensure a single reboot, you must install the ESM firmware update before the BIOS 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
of any issues.
•Make sure that you have a backup of operating system files or system configuration files stored on a system
other than the one you are updating.
•Make sure 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.
•Make sure 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.
11
Other Documents You May Need
To access other documents go to dell.com/support/manuals and select the product or use the direct link on the
Systems Management Tools and Documentation DVD
•Dell OpenManage
NOTE: You do not need to install Dell OpenManage Server Administrator on the system to run DUPs.
•
Dell OpenManage Server Update Utility User's Guide
Man page for DKMS from linux.dell.com/dkms/manpage.html
Legacy Compatibility Guide
.
Dell
Contacting Dell
NOTE: If you do not have an active Internet connection, you can find contact information on your purchase invoice,
packing slip, bill, or Dell product catalog.
Dell provides several online and telephone-based support and service options. Availability varies by country and
product, and some services may not be available in your area. To contact Dell for sales, technical support, or customer
service issues:
1.Visit www.dell.com/support.
2.Select your support category.
3.Verify your country or region in the Choose a Country/Region drop-down menu at the top of page.
4.Select the appropriate service or support link based on your need.
12
2
Using Dell Update Packages
Dell provides a number of aids to help you determine whether or not the system requires an update. You can download
DUP from dell.com/support/manuals. For more information, see Downloading DUPs .
NOTE: DUPs currently does not support every device type. DUPs will be available on additional devices in future
releases.
Updating Packages Component and System Compatibility
You can run the DUP and read the summary information. This information is provided to help you determine whether the
update is appropriate for the system and specific environment.
Executing DUPs in Linux Environment
You can run DUPs from the console in two modes:
•interactive
•non‑interactive
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.
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
the package in its simplest form by typing ./packagename.bin from the working directory, where packagename is the
model and component‑specific 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.
ssh
. Once a package has been delivered to the target system, administrators can execute
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. the 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.
13
Verifying the Digital Signature
A digital signature is used to authenticate the identity of the signer of an Update Package and to certify that the original
content is unchanged. Digital signature of DUPs gives you a more reliable and trustful method of authentication.
Verifying the digital signature ensures that the original Update Package was received correctly and that the content has
not been modified since it was signed.
NOTE: This is applicable for both Windows and Linux Environment.
Verifying the Digital Signature on Linux
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.
2.Import the public key to the gpg trust database by running the following command: gpg --import <Public Key
Filename>
NOTE: You must have a private key to complete the process.
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) <linux‑security@dell.com> Primary key fingerprint: 4172 E2CE 955A 1776 A5E6 1BB7 CA77 951D
23B6 6A9D
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.
c) While still in the key editor, type sign.
d) Answer the list of trust-validation questions that appears and create a passphrase to use as the secret key. You
must import and validate the public key only once.
4.Obtain the Linux DUP and its associated signature file from dell.com/support/manuals/downloads.
. If the fingerprint of the imported key is the same as the key owner's, you have a correct copy of the
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.
5.Verify the DUP using the following command: gpg --verify <
Update Package filename
>
Linux Update Package signature filename
> <
Linux
Executing DUPs in the Windows Environment
To run DUPs from the interactive graphical user interface (GUI), perform the following steps. This procedure applies to
all Update Packages.
1.Execute the DUP by double-clicking the filename from within Windows Explorer.
2.Read the update information displayed in the DUP window.
3.Check the DUP inventory report for Package version and Installed Versions of component.
4.Click Install to install the DUP.
5.Reboot the system, if necessary.
To execute DUPs from the command line interface (CLI), see Command Line Interface Reference.
14
Verifying the Digital Signature on Windows
To verify the Update Package’s digital signature, perform the following steps:
1.Start Windows Explorer and locate the Update Package whose digital signature you want to verify.
2.Right-click the filename.
3.Click Properties in the pop-up menu.
4.In the Properties window, click the Digital Signatures tab. If this tab is not displayed, the Update Package is not
signed.
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.
NOTE: 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.
Compatibility Concerns
DUPs are designed to confirm that all prerequisites are satisfied before applying the update to the 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 the target system.
•The DUP to be applied in the command is compatible with the operating system running on the system.
•The device associated with the DUP is present on the system.
•The minimum required versions of related system software are running on the 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.
Additionally, if you only want to verify that a given package can be applied to the system, you can invoke the package by
using the following CLI command:
./Packagename.bin ‑c for Linux
packagename.exe /c /s for Windows
This command executes the dependency rules within the DUP, issues any warnings, exits without applying the update to
the system, and writes the results to the console. You can also use the DUP to set an exit code to perform decisions
within the scripts.
Effects of Applying the Updates on a Running System
This section describes all the 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.
15
Loading...
+ 35 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.