This section
lists some frequently asked questions about DSU.
-
NOTE: Starting DSU 1.4, the
10th generation of PowerEdge servers are not supported. This is applicable
to the content in Linux repository and catalogs.
How can I select an
update in the given list?
Type the number displayed
against the update, to select the update. An asterisk (*) is displayed
corresponding to the update after it is selected.
How can I cancel an
update already selected in the given list?
It works like a
toggle button. For example, if update number 7 is already selected
(an asterisk (*) is displayed corresponding to the update after it
is selected), and now if you select 7 as an option, it gets cancelled.
After I select the
required updates, how to start the update process?
After you
selected the required updates, type
c option to start the update
procedure.
Can I select more than
one update?
Yes, you can select more than one update at a time.
You can provide update numbers one by one as an option to select multiple
updates.
Can I select all updates
at the same time?
Yes, you can select all updates at a time.
Select
a option and press enter, all the updates get selected.
Can I cancel all updates
at the same time?
Yes, you can cancel all updates at a time.
Select
q option and press enter, all updates get deselected.
Can I select multiple
updates at the same time using a single option in the command?
No, you cannot select multiple updates. However you can select multiple
updates by providing numbers one by one.
DSU Inventory displays
update for a component that is installed is newer than what is available.
DSU Linux Repository is refreshed on a monthly basis, at the next
refresh of the DSU Linux Repository the newer version will be carried.
I am using DSU on 10th
generation of PowerEdge Systems. What are the possible outcomes that
i may have to handle while using DSU with repository, catalog or RPM?
The following table describes the scenarios and the expected outcomes
if you use DSU on 10th generation of PowerEdge systems.
-
NOTE: The Dell’s PowerEdge
10G servers have reached end of support life. Version 16.12.01 is
the last version of repository or catalog with support for 10th generation
updates.
Table 1. Possible Outcomes for PowerEdge systems.
The following table describes the scenarios and
expected outcomes, if the user runs DSU on 10G system.
Scenarios
|
Outcomes
|
DSU on 10th generation of PowerEdge system pointing
to the newest Linux Repository (on linux.dell.com) and the Repository
no longer has 10G content.
|
Platform not supported message is displayed.
|
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.xml file that no longer has 10G content.
|
There may be two possible 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.
|
I see a message saying
that the DSU could not get the inventory. What should I be doing to
resolve the issue?
You have to uninstall or delete the inventory
collector from the DSU working folder and retry.
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?
Yes, using the script the repository is being created with the Linux bundles. As in mounted environment, DSU is being executed
which applies filters to remove the LC OS Driver Packs and the other files.
Which is the default directory to output the ISO?
Executing directory with ISO name as dsu_bootableimage_%Y%m%d_%H%M%S is the default directory to output the ISO.
Where to look for the log files while using the dsucreateiso command?
The log files are located in /var/log/ with the log filename as
dsucreateiso.log.
Does DSU fail to downgrade to a lower version (1.5.0) in Microsoft Windows ?
Yes, DSU fails to downgrade to a lower version (1.5.0) in Microsoft Windows.
Workaround is: Manually remove the latest version before installing 1.5.0. version.
DSU exits with an error message "inv.xml not found" while connecting to the remote system on Microsoft Windows 2016.
From the host a corrupted invcol was pushed to the remote, then the issue appears on the remote system.
Download the inventory collector and use option
--ic-location to provide the details to DSU.
How can I generate a separate log file for each remote system on host system.
Separate log file for individual connection can be provided using
LogFile attribute in the config file as shown below.
<RemoteSystem>
<System Address="100.100.138.12" LogFile="/home/dsu/system1.log"/>
<System Address="100.100.138.13" LogFile="/home/dsu/system2.log"/>
</RemoteSystem>
DSU exits with an error message on Ubuntu while loading libraries.
DSU exits with an error message:
" dsu : error while loading shared libraries: libssh2.so.1: cannot
open shared object file: No such file or directory."
. Install the dependencies (libssh2.so.1) required for executing remote feature of DSU.
Are there any limitations on the number of servers that can be updated at one time with the Remote attribute?
As long as the network has the bandwidth there are no limitations.
DSU does not auto-uninstall on SUSE Linux OS during Remote execution.
Following methods can be performed:
Method 1 :
ssh root@<IP Address> zypper remove dell-system-update Password will be asked.
Method 2:
sshpass -p 'password' ssh root@<IP Address> 'zypper remove dell-system-update'. This method requires
sshpass to be installed on the host system.
Redundant message displayed on Windows console while using remote option.
To avoid redundant messages the command prompt needs to be restarted. For example:
Number of systems complete: 5/5 100%
Number of systems complete: 4/5 80%
The system IP address on the DSU's Log file displayed is not correct.
On some cases the Virtual IP address is captured by DSU in place of OS IP, in such scenarios the IP address displayed will
not be correct.
On the remote systems running SUSE Linux 15 servers, the remote system is unable get connected after a restart.
This is due to the firewall which could be enabled after a restart.
Host System displays an error message as "unknown option provided in DSU" when the option
UseLatestDSU=FALSE mentioned in config file.
Set the value of attribute value as
TRUE. If the lesser version of DSU installed on target system all the functionality or the options for remote feature is not enabled
hence following message can be thrown in the case.
While using
--push-remote-updates option on systems running SUSE Linux operating systems , updates failure message is observed.
Reason for failure message is the
updates fails to download on the host system.
In such scenarios try using option
--source-type=REPOSITORY along
with
--source-location=<repo-location>.