Users Guide

Scenarios Outcomes
• If the DUP doesn’t support 10G platform, then DSU is not
installed.
• If DUP supports 10G platform, DSU is installed. When dsu
command is invoked Platform not supported message is
displayed.
I am running DSU 1.4 DUP and pointing at a legacy catalog.xml
that has 10G content.
There may be two possible outcome:
• If the DUP doesn’t support 10G platform, then DSU is not
installed.
• If DUP supports 10G platform, DSU is installed. dsu command
works as usual.
On Ubuntu operating system, I see a message “genisoimage: command not found. Please install genisoimage to create
bootable iso”. What am I supposed to do?
To troubleshoot the issue, execute the following command: sudo apt-get install genisoimage. By executing the command,
you are installing the genisoimage to generate the ISO.
On Linux operating system, I see a message “mkisofs: command not found. Please install mkisofs to create bootable iso”.
What am I supposed to do?
To troubleshoot the issue, execute the following command: yum install mkisofs on RHEL operating systems and zypper
install mkisofs on SLES operating systems.
On Microsoft Windows operating system, when I execute the command “dsu”, I see a message “dsu is not recognized as an
internal or external command, operable program or batch file”. What am I supposed to do?
To troubleshoot the issue, you must add the dsu install path to environmental variable by executing following command with administrator
privileges: setx PATH=%PATH%;C:\Dell\Dell System Update.
There are few components that are listed when I execute the command dsu —i or dsu /i. However, I am not able to view
these components in the comparison report. Why do I see the difference?
Though the components are listed after executing the command, there may be no updates available for certain components in the catalog.
You may view the components in the comparison report if an update is available for that particular component in the catalog.
I get a warning message saying “Inventory collector returned with partial failure”. How do I get more information about the
potential issue?
Check the IC log to get more information regarding the failure. You can find the log file in C:\ProgramData\Dell\UpdatePackage
\log on Microsoft Windows operating systems and /var/log/dell/ on Linux operating systems.
I see a message saying “Failed to parse config file” with exit code 17. What should I do to troubleshoot and resolve the
issue?
The config file may not be filled correctly. Refer the configuration schema information in the dsuconfig.xml section in Using DSU
bootable ISO topic.
I see a message “unable to get the inventory collector path from catalog”. What should I do to troubleshoot and resolve the
issue?
For more information on the inventory collector path, check the catalog file.
Sample inventory collector data from catalog.xml:
• WIN64: <InventoryComponent schemaVersion="2.0" releaseID="WF06C"
hashMD5="0dbe6b18f0ebf247ea317c51c7257ff4" path="FOLDER04054889M/1/
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: <InventoryComponent schemaVersion="2.0" releaseID="WF06C"
hashMD5="2778b35ac99d4fb7a6c09aa04d095ca6" path="FOLDER04054886M/1/
invcol_WF06C_LN64_16.12.200.896_A00" dateTime="2016-11-25T16:25:47Z" releaseDate="November
25, 2016" vendorVersion="16.12.200.896" dellVersion="A00" osCode="LIN64" />
When we create a bootable ISO using the ./dsucreateiso script, does it include files such as LC OS Driver Packs, DSET and
other files?
Frequently asked questions
53