DELL EMC System Update Version 1.9 User’s Guide September 2020 Rev.
Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your product. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. © 2020 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries.
Contents Chapter 1: Introduction to Dell System Update..............................................................................6 How does Dell System Update work...............................................................................................................................6 What is new in this release................................................................................................................................................6 Related Documents...........................
Category values .................................................................................................................................................................51 Category list........................................................................................................................................................................ 51 Upgrades only......................................................................................................................................
cJSON..................................................................................................................................................................................68 zlib.........................................................................................................................................................................................69 libcurl ..............................................................................................................................
1 Introduction to Dell System Update DELL EMC System Update (DSU) is a script optimized update deployment tool that is used to apply Dell EMC updates such as applications, firmware and drivers for Linux, and Microsoft Windows operating systems. Using DSU identify the available updates, select the relevant updates, and deploy the updates on a single system or multiple systems through operating systems or Integrated Dell Remote Access Controller (iDRAC) or iDRAC pass through.
2 Support Matrix This section lists the hardware, Operating Systems and PowerEdge Servers required for installing DSU. Topics: • • Supported hardware Supported Operating Systems Supported hardware DSU supports iDRAC7, iDRAC8 and iDRAC9 based Dell EMC PowerEdge servers. NOTE: To install through iDRAC on iDRAC9 based PowerEdge Servers, minimum version of iDRAC 3.30.30.30 and later is required NOTE: DSU 1.
Supported devices DSU supports iDRAC 7 and later version of Dell EMC PowerEdge Severs 8 Support Matrix
3 Installing DSU You can install DSU on Microsoft Windows Server and Linux Operating Systems through Dell Update Package (DUP). Topics: • • Installing DSU DUP on Linux operating systems Installing DSU DUP on Microsoft Windows Server Operating Systems on command prompt Installing DSU DUP on Linux operating systems Prerequisites ● ● ● ● ● ● ● Ensure Ensure Ensure Ensure Ensure Ensure Ensure that you have superuser or root user permissions.
Online method to install DSU on Red Hat Enterprise Linux operating system Prerequisites Ensure that the online repository is configured to linux.dell.com. About this task To install DSU on the supported Red Hat Enterprise Linux operating system through command prompt, perform the following steps: Steps 1. Download the latest Dell Update Package (DUP) from the support site. 2. Provide the superuser or root privileges for the folder where you have saved the DUP files. 3.
3. In command prompt, run the following command: ./SystemsManagement_Application_8CTK7_LN64_1.9.0_XA00.BIN Status of the installation is displayed with details such as release title, release date, description, and supported devices information. Next steps To verify if the installation is successful, run dsu -h and run dsu -v for Linux based Operating System on the command prompt with root privileges.
6. After a successful installation, the success page is displayed. Click OK. Next steps To verify if the installation is successful, run dsu /h and dsu -v for linux for /v for Windows on the command prompt or PowerShell with superuser or administrative privileges NOTE: The DSU file is saved in the following location by default: C:\Program Files\Dell\DELL EMC System Update 12 Installing DSU
4 DSU features Provides updates for BIOS, applications, firmware and driver for various devices to the end customer. The updates are provided to the customer by gathering and adding all the device and dependency details together by providing a consistent and easy to execute user interface. Also publishes inventory collector application for inventorying the updatable components and also the metadata about the updates in the form of catalogs and hosts repositories.
Table 1. Inventory Use cases Actions View inventory Mandatory Attributes --inventory Optional Attributes --component-type Syntax/Example Format: dsu --inventory Example: dsu --inventory dsu --inventory -component-type=BIOS Export inventory in JSON format --inventory --authentication --output --component-type --output-format Format: dsu --inventory -output= --outputformat=JSON Example: dsu --inventory -output=C:\Program files\Dell\Dell EMC System Update \dell_dup\inv.
Table 1. Inventory Use cases (continued) Actions View inventory when system is not connected to downloads.dell.com (offline) Mandatory Attributes --inventory --source-type --source-location Optional Attributes --component-type --authentication --catalog-location --ic-location Syntax/Example Format: dsu --inventory -sourcetype=repository -sourcelocation= Example: dsu --inventory -sourcetype=repository -sourcelocation=C:\Program files\Dell\Dell EMC SystemUpdate \ABC dsu --inventory -catalog-locat
Table 1. Inventory Use cases (continued) Actions Export inventory for single remote host server Mandatory Attributes --inventory Optional Attributes --component-type Syntax/Example Format: dsu --inventory -remote=username:pas sword@IPaddress -output= --outputformat=JSON --remote --output --output-format Example: dsu --inventory -remote=abc:abc_123@ 100.89.45.27 -output= C:\Dell \DELL EMC System Update\dell_dup \inv.json --outputformat=JSON dsu --inventory -remote=abc:abc_123@ 100.89.45.
Table 1. Inventory Use cases (continued) Actions Export inventory for multiple servers Mandatory Attributes --inventory Optional Attributes --component-type Syntax/Example Format: dsu --inventory -remote -config= output= --outputformat=JSON --remote --config --output Example: dsu --inventory -remote -config=C:\Dell \Dell EMC System Update\dell_dup \config.xml -output=C:\Dell \Dell EMC System Update\dell_dup \inv.
Table 1. Inventory Use cases (continued) Actions Export inventory Mandatory Attributes --inventory Optional Attributes --component-type Syntax/Example Format: dsu --inventory -remote=idracusernam e:idracpassword@iDR AC_IPaddress -rsystemtype=iDRAC -output= --outputformat=JSON --remote --rsystemtype --output --output-format Example: dsu --inventory -remote=abc:abc_123@ 100.88.66.100 -rsystemtype=iDRAC --output= C:\Program files \Dell\Dell EMC System Update \dell_dup\inv.
Table 1. Inventory Use cases (continued) Actions Mandatory Attributes Optional Attributes Syntax/Example 66.
Table 1.
Table 1. Inventory Use cases (continued) Actions View system inventory using an inventory file on host server(BasicAuth) Mandatory Attributes --inventory Optional Attributes --component-type Syntax/Example Format:: dsu --inventory -use-idracpassthrough -remote=idracusernam e:idracpassword -input-inventoryfile= --use-idracpassthrough --remote --input-inventoryfile Example: dsu --inventory -useidracpassthrough -remote=abc:abc_123 --input-inventoryfile=C:\Dell\DELL EMC System Update \dell
Table 2. Preview (continued) Action Mandatory Attributes Optional Attributes Syntax/Example Example: dsu --preview -remote=abc:abc_@128 .99.88.100 dsu --preview -remote=abc:abc_@128 .99.88.100 -component-type=BIOS Viewing preview using remote iDRAC --preview --component-type --remote --category --rsystemtype Format: dsu --preview -remote= -rsystemtype= Example: dsu --preview -remote=abc:abc_@128 .99.56.
Table 2. Preview (continued) Action View preview by importing inventory file Mandatory Attributes Optional Attributes --preview --remote --input-inventoryfile --config --authentication Syntax/Example Format: dsu --preview -input-inventoryfile=< path of the fileName> Example: dsu --preview -input-inventoryfile=C:\\users \progamdata \inventory.xml dsu --preview -input-inventoryfile=C:\\users \progamdata \inventory.
Table 2. Preview (continued) Action Mandatory Attributes Optional Attributes Syntax/Example Example: dsu --preview -sourcelocation=C:\Dell \Dell EMC System Update\Dell_dup \abc --sourcetype=REPOSITORY dsu --preview -sourcelocation=C:\Dell \Dell EMC System Update\Dell_dup \abc --sourcetype=REPOSITORY -authentication=Admi nistrator:password1 23 Compliance To view the compliance report of the system For more details on optional attributes and its usage, click the hyperlink that is provided in the below tab
Table 3. Compliance (continued) Action Viewing compliance using remote iDRAC Mandatory Attributes Optional Attributes --compliance --component-type --remote --category --rsystemtype --config Syntax/Example Format: dsu --compliance -remote= -rsystemtype= Example: dsu --compliance -remote=abc:abc_@128 .99.56.77 -rsystemtype=iDRAC dsu --compliance -remote=abc:abc_@128 .99.56.
Table 3. Compliance (continued) Action Mandatory Attributes Optional Attributes Syntax/Example \192.168.10.24\Shar e\inventory.xml dsu --compliance -catalog-loction=\ \192.168.10.24\Shar e\Catalog.gz -input-inventoryfile=\ \192.168.10.24\Shar e\inventory.
For more details on optional attributes and its usage, click the hyperlink that is provided in the below table. Table 4. Update on host server and single remote host server Actions Updating server using noninteractive method Mandatory Attributes Optional Attributes NA --non-interactive Syntax/Example Format: dsu --noninteractive Example: dsu --noninteractive Update single remote server from host server through operating systems.
Table 4. Update on host server and single remote host server (continued) Actions Mandatory Attributes Optional Attributes Syntax/Example Example: dsu --remote -config=C:\Dell \Dell EMC System Update\dell_dup \config.xml dsu --remote -config=C:\Dell \Dell EMC System Update\dell_dup \config.
Table 4.
Table 4. Update on host server and single remote host server (continued) Actions Mandatory Attributes Optional Attributes Syntax/Example remote=abc:abc_123@ 100.11.123.77 Applying updates for critical updates only --list-criticalupdates --remote Format: dsu --listcritical-updates --config Example: dsu --listcritical-updates dsu --listcritical-updates -config=C:\Dell \Dell EMC System Update\dell_dup \config.
Table 4. Update on host server and single remote host server (continued) Actions Mandatory Attributes Optional Attributes Syntax/Example Update\dell_dup \abc> --iclocation=
Table 4. Update on host server and single remote host server (continued) Actions Mandatory Attributes Optional Attributes Syntax/Example VH_WN64_10.1.18243. 8188_A04.EXE" dsu --updatelist= "Chipset_Driver_9V5 VH_WN64_10.1.18243. 8188_A04.EXE" -remote=abc:abc_123@ 100.19.88.77 Bootable ISO With Bootable ISO feature, user can perform the following use cases: 1. Interactive-mode 2.
Table 5. Bootable ISO (continued) Action Non-interactive mode Mandatory attributes --destination-type Optional attributes --authentication --config --destinationlocation --non-interactive Syntax/Example Format: dsu --destinationtype=ISO -config= -bootable-loglocation= -non-interactive Example: dsu --destinationtype=ISO --config=\ \100.98.20.21\DSU \config.xml-destinationlocation=\ \192.168.10.1\Share \ISO9660.
● Interactive: dsu --destination-type=ISO --destination-location=C:\OUTPUT.ISO ● Non-interactive: dsu --non-interactive --destination-type=ISO --destination-location=C:\output.iso -config=C:\config.
5 Network Share A shared resource, or network share, is a computer resource made available from one host to other host on a computer network . DSU supports SMB1 and SMB2 protocol. Choices: --authentication Network share allows user to specify the authentication parameters that are required for accessing the repository. If the authentication parameters are incorrect, then AUTHENTICATION_FAILURE is returned. To export inventory file using authentication option: --inventory --output=C:\Programfiles\Dell\Dell E
10. --dsu-win64-installer-location 11.
Exporting inventory of host server in JSON format To export inventory report of a host sever in JSON format to a network share Syntax: dsu /i --output= authentication=username:password --output-format=json -- Naming Convention The following section describes the format on how user can provide share location. For example: For windows: --catalog-location=\\100.96.12.21\folder\catalog.xml --authentication=abc:bca123 example: For Linux: --catalog-location=//100.96.12.
6 Index Catalog Index Catalog is also known as catalogs of catalog. To get host updates for inventory, Compliance and Update feature using Index Catalog for Enterprise Catalog.
Table 6.
Table 6. Index features (continued) Actions Attributes Optional Attributes Format/example sourcetype=REPOSITORY To get Host Server Updates through Offline method --cataloglocation --source-location --catalog --sourcetype=REPOSITORY --config --authentication Format: dsu --cataloglocation= --sourcelocation= -sourcetype=REPOSITORY Example: dsu --cataloglocation=/root/ user/IUC.xml or gz --sourcelocation=C:\Dell \Dell EMC System Update\dell_dup \abc --installerlocation -source
Table 6. Index features (continued) Actions To update remote host server through online method Attributes Optional Attributes --apply-upgrades --downgrades-only --sourcetype=REPOSITORY --equivalent-updates --catalog --remote --config Format/example Format: dsu --upgrades -sourcetype=REPOSITORY -catalog= -remote=username:p assword@IPAddress Example: dsu --upgrades -sourcetype=REPOSITORY --catalog= 46633c58-53b7-41a 9-9 b83-40491eebafd -remote=abc:abc@12 8.99.88.
Table 6.
Table 6. Index features (continued) Actions Attributes Optional Attributes Format/example Example: dsu --applyupgrades -sourcetype=REPOSITORY -catalog=46633c5853b7-41a9-9b83-40 491eebafd1 -remote=abc:abc@12 8.99.88.100 -sourcelocation=C:\Dell \Dell EMC System Update\dell_dup \abc --dsu-lin64installerlocation=/ home/dsu/SystemsManagement_Applic ation_7PMM2_LN64_ 1.9.0_A00.
7 Sample scripts using DSU Creating Bootable ISO using helper script To create linux-based bootable ISO, see the script at the location: https://linux.dell.com/repo/hardware/scripts/. Syntax to create bootable ISO: dsucreateiso[options] Creating bootable ISO Following options can be used while creating a bootable ISO: ● ● ● ● ● ● ● ● ● ● Destination path custom script. Location of the custom script. Location of the DELL boot plug-in. Apply action for the component. Location to create log file.
Display the location of Catalog file Provides either local or network location of repository or catalog. By default network would be enabled to download catalog and DUPs file. Syntax for displaying the location of catalog file: dsucreateiso -s SOURCELOCATION or dsucreateiso --source-location=SOURCELOCATION Location to create log file Creates a log file at the given location with the file name as dsucreateiso_%Y%m%d_%H%M%S.log. By default the log is located at /var/log/dsucreateiso.
Command to create Bootable ISO by the available repository dsucreateiso --source=/root --output=bootabledsu.iso Command to customize the working directory dsucreateiso --output=/root/bootabledsu.iso --workspace=/root/myworkspace Command to create Bootable ISO with offline network and local repository dsucreateiso --dellbootplugin=/root/dellbootplugin.tar.gz --source=/root -output=bootabledsu.
Using kickstart files Kickstart files can be used to create a Linux based Live-ISO image including DSU, using a bootable ISO creation utility, such as livecd-creator or any other bootable ISO creation utility that supports kickstart files. Command syntax to create Live-ISO image using kickstart files: livecd-creator --config= --fslabel= For more information, view https://linux.dell.
8 Dell System Update Options This section provides a detailed information on various DSU options.
DSU Help Displays the command-line options and help information. Command for Linux: dsu --help or dsu —h Command for Windows: dsu --help or dsu /h Utility version To get the DSU utility version. Command for Linux: dsu --version Command for Windows: dsu --version Non-interactive update Runs the update silently without user intervention. The -q option writes all the output to log files. The default behavior ignores new IC unless --download-ic option is specified.
Command for Linux: dsu --compliance Command for Windows: dsu --compliance Catalog location Path of catalog file used. File format supported: .xml, .gz and cab Command for Linux: dsu --catalog-location= Command for Windows: dsu --catalog-location= Catalog ID Allows user to select catalog from index catalog. To identify Enterprise ID from index catalog, download the index Catalog from downloads.dell.com/catalog/catalogIndex.xml. Extract the file and look for CatalogIndex.
Category values To get all the supported category values and display the corresponding acronym for the category name from the catalog. Command for Linux: dsu --get-categories Command for Windows: dsu --get-categories Category list To get all the upgradable components of the specified categories. Command for Linux: dsu --category= Command for Windows: dsu --category= Upgrades only Upgrades only option is considered while determining the applicable updates.
Command for Windows: dsu --update-list= Equivalent version updates To get the list of applicable components of the same versions for updating. For example, if the installed version of the component is same as the available version of the component in the catalog, below option is used. Command for Linux: dsu --apply-equivalents Command for Windows: dsu --apply-equivalents Inventory file path To provide the path of the inventory file.
Configuration file Configuration of the file path for DSU. All the configuration and options are specified using this option. Once this option is specified, the remaining options are ignored. NOTE: For the given config file, it performs schema check only if the schema file (config.xsd) is available at %programdata %\Dell\DellEMCSystemUpdate\dell_dup. To Download schema file, see http://downloads.dell.
Command for Linux: dsu --source-location= Command for Windows: dsu --source-location= Destination location To provide the path of the package created using the --destination-type and to be saved. NOTE: When using --destination-type=ISO, the ISO filename provided in --destination-location should adhere to ISO9660 file system standards. For more details, see main page of genisoimage.
Command for Linux: dsu --output-log-file=/root/dsu.log Command for Windows: dsu --output-log-file=C:\dsu.log List only critical updates To list critical component updates. The DSU selection views shall display Criticality of the updates along with update name. [ Urgent/Recommended/Optional] Dependent updates (only Hard) shall also be listed along with the updates. Command for Linux: dsu --list-critical-updates Command for Windows: dsu --list-critical-updates Log level Logging level of DSU.
DSU installer file location To install or update the DSU on remote systems which is required for remote updating. NOTE: If this option is not provided, then the DSU installer file present in the catalog are used. NOTE: The DSU version should be same version as the local system. Command for Linux: --dsu-lin64-installer-location= Command for Windows: --dsu-win64-installer-location= Restarting system To restart the system, automatically post updates.
Command for Linux: dsu --ignore-signature Command for Windows: dsu --ignore-signature Component Type Component type filter lists the updates that are required for the specified component type. The following are the five component type filters provided: 1. 2. 3. 4. 5. FRMW (Firmware) BIOS APAC (Application) APP (Application) DRVR (Drivers) NOTE: APP is used only for upgrading OMSA DUPs NOTE: For JSON supported files, APAC component is displayed as EAPP.
Command for Windows: dsu --remote NOTE: For the usage of remote option, root account only can be used. Sudo users cannot be used. The remote system must have default PermitRootLogin preenabled in /etc/ssh/sshd_config. NOTE: Remote option that is mentioned in the system prompt takes precedence over the config file options. Providing the credentials of the remote system To enable the remote system with the credentials provided along with the hostname.
● OAuth: Supports operating system to iDRAC passthrough connection without iDRAC credentials ● BasicAuth: Supports operating system to iDRAC passthrough connection with iDRAC credentials Command for Linux: dsu --use-idrac-passthrough Command for Windows: dsu --use-idrac-passthrough Input inventory Allows users to specify the inventory information in a file. DSU takes the information instead of inventorying for determining the applicable updates.
Command Syntax for Windows: dsu --output-format= Uninstall To uninstall the DSU from remote machine after performing DSU operation on remote Command Syntax for Linux: dsu --uninstall Command Syntax for Windows: dsu --uninstall Progress Progress command is used to get the update status of DSU on host and remote. NOTE: Run progress command in one minute interval. NOTE: When no instance of DSU is running on the system and --progress option is used, displays an output as No progress is available.
DSU Return Codes The return codes help you determine and analyze the results after the execution of DSU, see the codes described in the following table: Table 7. DSU Return Codes DSU Return Codes Number Return Codes Description of Return Codes 0 Success Any successful operation performed by DSU. 1 Failure Any failure in operation performed by DSU. 2 Insufficient Privileges DSU not executed using ROOT privilege.. 3 Invalid Log File Failure in opening a log file or invalid log location.
Table 7. DSU Return Codes (continued) DSU Return Codes 62 35 Remote Partial Failure Some remote systems has failure some maybe successful. 36 Remote Failure All the remote systems has failure. 40 Public Key Not Found The signature verification failed due to public keys are not imported on system.
9 Uninstalling DSU This chapter provides the steps to uninstall DSU DUP on Red Hat Enterprise Linux, CentOS, Ubuntu, SLES, windows through UI. Following are the prerequisites before uninstalling DSU DUP on any of the following Operating Systems. 1. Ensure to use working directory to store data. NOTE: While performing uninstallation, DSU deletes working directory. Following are the path for linux and windows: For Linux: /usr/libexec/dell_dup For windows: C:\ProgramData\Dell\DELL EMC System Update\dell_dup NO
Uninstalling DSU on Windows through UI About this task To uninstall DSU on Windows operating system through user interface (UI), perform the following steps: Steps 1. Launch the start menu and open Control Panel. 2. In Programs section, click Uninstall a program. 3. In the search bar search for Dell EMC System Update. 4. Select the program and click Uninstall. 5. In Programs and Features window, click Yes. 6. In User Account Control window, click Yes.
10 Troubleshooting DSU Inventory or compliance is displayed when Enterprise catalog provided instead of Index catalog along with catalog ID --catalog is not necessary to use when Enterprise location is given. To use --catalog, user must provide catalog ID. Provided Index catalog as an input to --catalog-location from the local or network share path. User can provide index catalog from local or share path using --source-type=REPOSITORY and --catalog= as an input to catalog location.
Description: When you try to access, file over SMB2 network share that is hosted on any windows operating system, the following error message is displayed intermittently Unable to access network location Work around: 1. Close all the open share connections. 2. Sign out and sign in to the machine to close the connection to the share network.
11 Appendix Topics: • • • • • • Xerces LibXML2 cJSON zlib libcurl Cygwin Xerces Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.
Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License.
SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. zlib zlib.
this free software. For both users' and authors' sake, the GPL requires that modified versions be marked as changed, so that their problems will not be attributed erroneously to authors of previous versions. Some devices are designed to deny users access to install or run modified versions of the software inside them, although the manufacturer can do so. This is fundamentally incompatible with the aim of protecting users' freedom to change the software.
1. Protecting Users' Legal Rights From Anti-Circumvention Law. No covered work shall be deemed part of an effective technological measure under any applicable law fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention of such measures.
of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work. A "User Product" is either (1) a "consumer product", which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling. In determining whether a product is a consumer product, doubtful cases shall be resolved in favor of coverage.
60 days after the cessation. Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice.
whom you convey the Program, the only way you could satisfy both those terms and this License would be to refrain entirely from conveying the Program. 1. Use with the GNU Affero General Public License. Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU Affero General Public License into a single combined work, and to convey the resulting work.
12 Frequently asked questions This section lists some frequently asked questions about DSU. The connection on remote machine using ssh on windows is lost during network driver installation DSU does not support ssh for windows. Unable to use the latest repository linux.dell.com with DSU 1.8 or earlier versions. User must upgrade to latest DSU version to use the latest repository. How can I select an update in the given list? Type the number displayed against the update, to select the update.
Table 8. Possible Outcomes for PowerEdge systems (continued) Scenarios Outcomes DSU 1.5 RPM (sourced from linux.dell.com) on a 10th generation of PowerEdge system pointing to the newest Linux Repository that no longer has 10G content. Platform not supported message is displayed. DSU 1.4 RPM on a 10th generation of PowerEdge system pointing to an older Linux Repository that still has 10G content. All commands work as usual. DSU 1.4 DUP (sourced from downloads.dell.com) pointing to catalog.
invcol_WF06C_WIN64_16.12.200.896_A00.exe" dateTime="2016-11-25T16:25:47Z" releaseDate="November 25, 2016" vendorVersion="16.12.200.896" dellVersion="A00" osCode="WIN64" /> ● LIN64: PAGE 78In case of USB-NIC already enabled status the interface settings then there are no actions carried out by DSU hence failure is observed. Solution: Change the state of USB-NIC in passthrough configuration to disable on iDRAC system and retry. [iDRAC Settings->Connectivity->OS to iDRAC Pass-through->State] Recommended to reset the iDRAC incase of connectivity failure. For more information see, Integrated Dell Remote Access Controller User's Guide at www.dell.com/iDRACmanuals.
DSU fails and displays an error message as "Invalid System ID" on re-branded systems. Update of SAS-RAID firmware and OS collector fails when multiple-updates scheduled via iDRAC or iDRAC Passthrough. In such scenarios update the failed components individually. Segmentation error is observed when the option rsystemtype or when --use-idrac-passthrough is mentioned in config file. In some scenarios segmentation fault is observed for multiple remote connection through iDRAC.
13 Sample When using an IC that has component type filter, it lists component types which are specified. When using an IC that does not have component type filter option, all the available server components are listed. Topics: • Sample options usage Sample options usage The following are some of the sample options with DSU: Sample Config file with Authentication Sequence and Remote System options To point to a repository hosted at https:///(for example, https://192.168.10.11/16.
# Sample Config file for Configuring repository and sequencing the order of updates using Config file
# Remote Windows OS to iDRAC Passthrough with basic Authentication PAGE 83# Linux Remote Hosts
Table 9. Config file options usage Element Options Usage Description Repository Type="OSNATIVE| REPOSITORY" When type is OSNATIVE, the command specific to the OS will be used to install updates.
Table 9. Config file options usage (continued) Element Options Usage Description ApplySequence -> Sequence -> Category Value OrderID There are two attributes which has to be mentioned for this feature: ● Value - Category value is to be provided. To get the category value use the option -get-categories ● OrderID - OrderID is positive integer value which will be used to apply the updates in an ascending order.
Command to perform firmware updates via iDRAC (Remote System) Inventory: dsu --source-type=REPOSITORY -i --remote="idracuser:idracpassword@iDRAC IP" -rsystemtype=iDRAC Preview: dsu --source-type=REPOSITORY --preview --remote="idracuser:idracpassword@iDRAC IP" -rsystemtype=iDRAC Update: dsu --source-type=REPOSITORY -u
Sample Config file to perform firmware update via operating system to iDRAC passthrough using Basic Authentication PAGE 87dsu --config="" --remote --category=BI -e --reboot The command restarts the remote systems specified in the config file if the update requires a restart of the system and will relaunch DSU to check the status of the same. Command to use push remote updates dsu --push-remote-updates --remote --config="" --category=BI To push all the required updates to the remote system from the system where DSU is running, runs the update and provides the status back.
Microsoft Windows Operating System: dsu --non-interactive --destination-type=ISO --destination-location= C:\output.iso –— config=C:\config.xml Command to create bootable interactive DSU ISO Linux Operating System: dsu --destination-type=ISO --destination-location=/root/home/output.iso Microsoft Windows Operating System: dsu --destination-type=ISO --destination-location= C:\output.
