Users Guide

Single remote iDRAC with non-default port fails to get the inventory, preview or update command information.

Recommendation: It supports only by providing the non-default port details in a Config file.

Sample config file:

<DSUConfig xmlns="DSUConfiguration>"

</AuthenticationSequence>

</System>>

</RemoteSystem>

</DSUConfig>

DSU fails to connect to the remote host system using ActiveDirectory credentials.

If the ActiveDirectory crendentials contains suffixes with dot, the DSU fails to connect. Only single-label DNS names are supported that

do not contain a suffix such as .com, .corp, .net, .org or companyname.

If using a multi-domain user. For example: If the user has provided "subdomain.domain.com\username", Dell recommends to provide the

username as subdomain\username.

DSU fails to connect to remote host system with local administrator user when the host was added to the ActiveDirectory.

Recommended to use ActiveDirectory user instead of local Administrator user.

DSU fails to connect to the remote iDRAC using USB-NIC pass through option using ActiveDirectory credentials.

For the remote system to connect through iDRAC USB-NIC pass through option, use only iDRAC user Administrator account.

Remote update fails from windows to windows when network is very slow

Remote update fails from when network speed is slow, and displays an error message. Dell recommends to avoid this issue ensure the

network connection is suitable to run the update and re-try the operations.

DSU update fails for few components when update is pushed via iDRAC or via operating system to iDRAC passthrough.

When updates are pushed via iDRAC or OS to iDRAC passthrough, the update fails when the job is in-progress or scheduled or fails in

case of restart is required.

Work around: Clear the iDRAC job queue to avoid this error.

Invalid System ID on RHEL 7.6 when executed on Re-branded systems.

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.

Recommendation: If the issue persists, user has to re-try the command.

Firmware updates via iDRAC or iDRAC passthrough with a non-admin user displays an error as 0 Updates Succeeded.

Reason for this error might be with insufficient privileges, refer DSU log file to confirm same. Perform the update using iDRAC user with

Administrator privileges.

DSU functionality fails for the system when the iDRAC was configured with non-default HTTPS port using iDRAC USB-NIC

passthrough

Change the iDRAC HTTPS port to default (443) and retry the updates.

DSU installed system environmental variable "PATH" is not getting cleared during uninstallation

When DSU is used in remote scenarios, DSU installed system environmental variable "PATH" is not getting cleared during uninstallation. If

multiple remote sessions are used for the same machine the entry created by DSU will get accumulated due to this.

Workaround : Delete multiple entries of DSU path.

Incorrect network Firmware name displayed for iDRAC and iDRAC-pass-through with preview with iDRAC version

3.36.36.36

Frequently asked questions