Users Guide
I see a message saying “Failed to parse cong le” with exit code 17. What should I do to troubleshoot and resolve the issue?
The cong le may not be lled correctly. Refer the conguration 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 le.
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 les such as LC OS Driver Packs, DSET and other
les?
Yes, using the script the repository is being created with the Linux bundles. As in mounted environment, DSU is being executed which
applies lters to remove the LC OS Driver Packs and the other les.
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 les while using the dsucreateiso command?
The log les are located in /var/log/ with the log lename as dsucreateiso.log.
How can I generate a separate log le for each remote system on host system.
Separate log le for individual connection can be provided using LogFile attribute in the cong le 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.
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 le displayed is not correct.
Frequently asked questions
37