FAQ

Firmware update scenarios in OMIMSSC
Failure of creation of update source
When the Domain Name System (DNS) network configuration of the Appliance is changed, creation of HTTP or FTP type of update
source fails.
As a workaround, restart the Appliance, and then create the update source of type HTTP or FTP.
Failure to connect to FTP using system default
update source
After setting up and configuring, upgrading, or migrating OMIMSSC when you try to access the FTP site using the default update source
Dell Online Catalog it may fail if proxy credentials are required.
As a workaround, to access the FTP site using Dell Online Catalog as an update source, edit the update source to add the proxy
credentials.
Failure of test connection for local update source
After proving the details of a local update source, the test connection may fail as the required files may be not accessible.
As a workaround, ensure that catalog.gz file is present in the following folder structure.
For local HTTP update source: http:\\IP address\catalog\catalog.gz
For local FTP update source: ftp:\\IP address\catalog\catalog.gz
For local DRM update source: \\IP address\\catalog\<catalogfile>.gz
Failure to create DRM update source
Creating DRM update source on management server running on Windows 10 Operating System (OS) may fail, displaying the following
error message: Failed to reach location of update source. Please try again with correct location
and/or credentials.
Refer the dlciappliance_main log in OMIMSSC Admin portal, if the error message displayed is: Unix command failed
SmbException: com.dell.pg.tetris.business.samba.smbclient.SmbException: session setup failed:
NT_STATUS_IO_TIMEOUTwhere EnableSMB1Protocol = false.
As a workaround, see to the following KB article: support.microsoft.com/en-us/help/4034314
Failure to create repository during firmware
update
Creation of a repository may fail during a firmware update because of incorrect credentials provided while creating an update source, or
update source is not reachable by OMIMSSC Appliance.
As a workaround, ensure that the update source is reachable from where the OMIMSSC Appliance is hosted, and provide the correct
credentials while creating an update source.
8
16 Firmware update scenarios in OMIMSSC