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 . . . . . . . . . . . . . . 9 . . . . . . . . . . . . . . . . . . . . . . . . . 9 . . . . . . . . . . . . 10 . . . . . . . . . . . . . . . . . . 10 Server Update Utility and DUPs . Update Options . Supported Operating Systems . OpenIPMI Requirements . . . . . . . . . . . . . . 11 . . . . . . . . . . . . . . . . 11 Using DUPs in the DTK Pre-Operating System Environment . . . . . . . . . . . . . . . . . . . . . . . . .
Develop Your System Update Plan Acquiring DUPs . . . . . . . . . . 17 . . . . . . . . . . . . . . . . . . 18 Update Packages Component and System Compatibility Executing DUPs . . . . . . . . . . . . . . . . . 18 . . . . . . . . . . . . . . . . . . 19 . . . . . . . . . . . 21 . . . . . . . . . . . . . . 23 Verifying the Digital Signature Compatibility Concerns . Effects of Applying the Updates on a Running System . . . . . . . . . . . . Delivering DUPs to Your Systems .
Updating BIOS and Firmware Using Graphical User Interface (GUI) . . . . . . . . . . . 36 . . . . . . . . . . . . 37 . . . . . . . . . . . . . . . . 37 Automatically Update Firmware Viewing Log Information 4 Update and Rollback in Unified Server Configurator - Lifecycle Controller Enabled . . . . . . . . . . Update in USC LCE . . . . . . . . 39 . . . . . . . . . . . . . . . . . . . 39 Rollback in USC LCE . 5 Command Line Interface Reference Using the CLI . 41 . . . . . . . . . . . . . . . .
Scenario. . . . . . . . . . . . . . . . . . . . . . . Prerequisites for the Test System . . . . . . . . . . . . Rebuilding a Package to Add Kernel Support to a Single System . . . . . . . . . . . . . . . Rebuilding the Package to Add Kernel Support for Multiple Kernel Versions . Scenario. 54 55 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Diagnostic Tasks will not run while a DUP reboot is pending . . . . . . . .
Support Log File Example . Index . . . . . . . . . . . . . 70 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents
1 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.
– 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.dell.com/manuals, for information on how SUU identifies and applies updates to your entire system.
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® Preinstallation Environment (Windows PE) version is distributed as a package of Dell-provided content with instructions on how to integrate with a standard Windows PE image.
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 matches the Dell-qualified operating systems. See "Dell-Qualified Path" for more information. • The DUP that you are applying can be enabled to work with the running kernels and operating systems in your environment. See "Dell-Enabled Path" for more information.
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 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 has information about installing, configuring, and using IT Assistant.
Using Dell Update Packages 2 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.
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.
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.
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.
Verifying the Digital Signature A digital signature is used to authenticate the identity of the signer of a file and to certify that the original content of the file has not been modified since it was signed. If you do not already have it installed on your system, you must install the Gnu Privacy Guard (GPG) to verify a Linux DUP digital signature. To use the standard verification procedure, perform the following steps: 1 Get the Dell Linux public GnuPG key, if you do not already have it.
4 Obtain the Linux DUP and its associated signature file from the Dell Support website at support.dell.com/support/downloads. NOTE: Each Linux DUP has a separate signature file, which is 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.
4 Start to verify the signature of the packages by first downloading the following two files from support.dell.com: • PE2850-BIOS-LX-A20.bin.sign • PE2850-BIOS-LX-A20.bin 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: a ESM system firmware b 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.
Performing BIOS and Firmware Updates Using Dell Linux Online Repository 3 Overview You can update your system to the latest version or to a specific version of the BIOS and firmware available in the Dell Linux online repository. The updates are available in the RPM Package Manager (RPM) format. RPM is a standard package format for software updates specific to Linux operating systems.
The steps to update BIOS and firmware for your system are: 1 Setup/bootstrap the repository 2 Install firmware-tools 3 Download applicable firmware 4 Update BIOS and firmware The commands to setup, install, and update RPM-based BIOS and firmware for yum, up2date, rug, and zipper are provided in this section. Setting Up/Bootstrapping the Repository To setup/bootstrap the Dell Linux online repository, run the following command at the command prompt: wget -q -O http://linux.dell.
Installing Firmware-tools Depending on the repository management software you are using, run one of the following commands to install firmware-tools: For yum: yum install dell_ft_install For up2date: up2date -i dell_ft_install For rug: rug install dell_ft_install For zypper: zypper install dell_ft_install Downloading Applicable Firmware Depending on the repository management software you are using, run one of the following commands to download applicable firmware: For yum: yum install $(bootstrap_firmware)
Inventory Installed Firmware You can also inventory your system for the list of existing versions of BIOS and firmware using the following command: inventory_firmware Here is a sample output: [root@localhost ~]# inventory_firmware Wait while we inventory system: System inventory: BIOS = a07 Primary Backplane = 1.00 System BIOS for PowerEdge 2850 = A07 PowerEdge Expandable RAID Controller 4e/Di Firmware = 5b2d PERC 5/E Adapter Controller 0 Firmware = 5.2.2-0076 BMC = 1.
Available: dell_dup_componentid_03967 - 1.00 Did not find a newer package to install that meets all installation checks. Checking System BIOS for PowerEdge 2850 - A07 Did not find a newer package to install that meets all installation checks. Checking PowerEdge Expandable RAID Controller 4e/Di Firmware - 5b2d Available: pci_firmware(ven_0x1028_dev_0x0013_subven_0x1028_subdev_0x016d) 5b2d Did not find a newer package to install that meets all installation checks.
5b2d Available: pci_firmware(ven_0x1028_dev_0x0013_subven_0x1028_subdev_0x016d) - Did not find a newer package to install that meets all installation checks. Checking PERC 5/E Adapter Controller 0 Firmware - 5.2.1-0066 Available: pci_firmware(ven_0x1028_dev_0x0015_subven_0x1028_subdev_0x1f01) 5.2.2-0076 Found Update: pci_firmware(ven_0x1028_dev_0x0015_subven_0x1028_subdev_0x1f01) - 5.2.2-0076 Checking BMC - 1.83 Available: dell_dup_componentid_05814 - 1.
You can also perform the following: • If your system component version is higher than the version available in the repository, you can downgrade your system components to the versions in the repository. In the Inventory and Update Firmware dialog box, select the required components to downgrade and click Allow Downgrade. • If you need to re-install the component versions, select the required components and click Allow Reflash.
Performing BIOS and Firmware Updates Using Dell Linux Online Repository
Update and Rollback in Unified Server Configurator - Lifecycle Controller Enabled 4 Dell Unified Server Configurator - Lifecycle Controller Enabled (USC LCE) is an embedded configuration utility that enables systems and storage management tasks from an embedded environment throughout the system’s life cycle. Residing on an embedded flash memory card, USC - LCE is similar to a BIOS utility in that it can be started during the boot sequence and can function independently of an installed operating system.
NOTE: For more information on updating the platform, see the Dell Unified Server Configurator User Guide available on the Dell Support website at support.dell.com/manuals After you select the updates you want to apply, USC - LCE downloads and applies the updates. If you decide to update any device in USC - LCE, the update package of the corresponding device is downloaded. After successfully downloading, verifying, and extracting the DUPs, the corresponding devices are updated.
5 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 5-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 5-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 5-2 are set. The exit codes help you determine and analyze the execution results after you run DUPs. Table 5-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 5-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 5-2. Exit Codes (continued) Value Message Name Display Name Description 6 REBOOTING_SYSTEM Rebooting system The system is being rebooted. 9 RPM_VERIFY_FAILED RPM The Linux DUP framework uses verification has RPM verification to ensure the failed security of all DUP dependent Linux utilities. If security is compromised, the framework displays a message and an RPM Verify Legend, and then exits with exit code 9. RPM produces output only if there is a verification failure.
6 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 6-1. Figure 6-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.
7 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.
Messages Table 7-1 provides descriptions and solutions to messages that you may receive when running DUPs. Table 7-1. Update Packages Message Information Message Description/Solution This Update Package is not compatible with your system Your system: System(s) supported by this package: Select a compatible DUP, and try the update again. This Update Package cannot be executed under the current operating system.
Table 7-1. Update Packages Message Information (continued) Message Description/Solution The version of this Update Package is newer than the currently installed version. Software application name: Package version: Installed version: This message confirms the version of the currently installed software before the update is performed. The version of this Update Package is older than the currently installed version.
Table 7-1. Update Packages Message Information (continued) Message Description/Solution In order to assist in the Download and install the minimum , you can required OpenIPMI driver from the download and install a version Dell Support website. of the OpenIPMI driver that meets the minimum version requirement from the Dell Support website at support.dell.com. The minimum version required is .
Table 7-1. Update Packages Message Information (continued) Message Description/Solution Kernel source for the running kernel is installed, but the currently installed OpenIPMI driver RPM was installed without the kernel source for the running kernel. In order to install OpenIPMI driver modules for the running kernel that meet the minimum version requirement, use DKMS (see man page for dkms) to install and build OpenIPMI driver modules for the running kernel.
Table 7-1. Update Packages Message Information (continued) Message Description/Solution Rebuilding package to support kernel version "kernel.x". This process may take several minutes to complete... The DUP application is rebuilding the package to support a different kernel version. No specific kernel version specified! Building support for current kernel... Unable to determine current system kernel. The DUP application attempts to rebuild the package.
Table 7-1. Update Packages Message Information (continued) Message Description/Solution Rebuilding Package Failed Error creating driver support directory. The package could not be rebuilt because the support directory could not be created. Rebuilding Package Failed Error copying kernel modules. The package could not be rebuilt because the kernel modules could not be copied. Rebuilding Package Failed Error re-creating archive.
Table 7-1. Update Packages Message Information (continued) Message Description/Solution Rebuilding Package Failed Packages cannot be rebuilt on a system Server Administrator device that has the HAPI device driver driver (HAPI) is already installed. installed on the system. Package can be rebuilt only on a system that does not have Server Administrator device driver (HAPI) installed. Unable to Install Dell The package cannot install the HAPI Instrumentation Driver (HAPI). driver.
Table 7-1. Update Packages Message Information (continued) Message Description/Solution packagename.bin: Rebuilding Package Failed - Error recreating archive. Ensure that enough space is available in the /tmp directory. packagename.bin: Rebuilding Package Failed - Uninstall of driver was unsuccessful. The driver could not be uninstalled. packagename.bin: Rebuilding Package Failed - Error creating files. Ensure that enough space is available in the /tmp directory.
Table 7-1. Update Packages Message Information (continued) Message Description/Solution The installed operating system version is not supported by this Update Package. To customize this package, see "Rebuilding Packages" in the Update Package User’s Guide. In no event shall Dell Inc. be held liable for any direct, indirect, incidental, special, or consequential damages suffered during or after package customization and execution.
Table 7-1. Update Packages Message Information (continued) Message Description/Solution Attempt to update BIOS or Re-application of BIOS or firmware firmware to the same version. DUP serves no purpose. Update was unnecessary and not applied. Inventory operation exceeded specified timeout. Inventory operations have time-out limits as defined in the package’s PIEConfig.xml file. Time-out durations are in seconds. If an operation times out, the remainder of the package update is cancelled.
Table 7-1. Update Packages Message Information (continued) Message Description/Solution The Linux DUP framework uses the Linux utility, less, to display the release (--version). notes relevant to the specific firmware Press 'q' to continue with DUP or driver release managed by the DUP. execution (dup dup execution).
• DUP type • DUP version • Framework version of the DUP • Version that was previously installed on the system • Version that the command is trying to apply to the system • Exit code that results from execution of the command • Whether a reboot was performed NOTE: The support log files are intended for use by Dell support personnel. Dell encourages you to redirect the DUP output to a file of your choice.
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.
Troubleshooting
Index B D BIOS and Firmware Updates, 31 delivering Update Packages to your systems, 25 BIOS update for 200 systems usage scenario, 29 Boostrapping repository, 32 C Catalog.
H R HAPI, 65 rebuilding a package Dell-enabled path, 47 Dell-qualified path, 47 determining whether your package is supported, 50 dynamic kernel support, 49 setting up a test system, 51 to add kernel support for multiple kernel versions, 54 Help option, 41 I Important tips using Update Packages, 15 K key, verify, 21, 23 rebuilding a package to add kernel support to a single system, 54 RPM, 46 RPM format, 31 M message logs for Update Packages, 69 messages, 59 S Server Administrator documentation, 15
T system and user requirements, 13 troubleshooting, 59 unattended mode, 26 updating many systems, 26 verifying the digital signature, 21-23, 28 verifying the update, 26 troubleshooting known issues, 57 typical usage scenarios BIOS update for 200 systems, 29 Retasking a System, 27 updating many systems, 26 U Update and Rollback in Unified Server Configurator Lifecycle Controller Enabled, 27, 39 Update Options, 10 element update, 10 system update, 10 Update Packages acquiring, 18 applying on a running sys
Index
