Cannot upgrade firmware on the servers in any way CIFS(v2) or HTTPS

Hello,

you dont need to export the ceritificate, the error is about network or protocol issue, not certificate.

Try to check update job log in OME. Does it fail on the download or the push of the firmware update?

Try to check proxy configuration. 
Can you try to manually update the server throught the iDRAC?

Which port are you using?

Thanks

With the CIFS (v2) share, when I push firmware update from OME, then on IDRAC side in Job Queue I have successive statuses:

1."New"

2."Downloading" which take minute or so with information like e.g. "RED110: Downloading the FOLDER13542637M_1_iDRAC-with-Lifecycle-Controller_Firmware_K2KHC_WN64_7.20.70.50_A00.EXE update package."

3.RED016: Mount of remote share failed.

Logs from the OME side is:

Proxy is disabled on the OME.

Yes, from IDRAC I can manually install updates without any problems.

Hello,

 

HTTPS (RED137) and CIFS v2 (RED016):

 

• HTTPS (RED137): OME uses its internal HTTPS share for firmware delivery. If iDRAC cannot establish a secure connection, it’s usually due to:
• Certificate trust mismatch (iDRAC does not trust OME’s self-signed certificate).
• DNS or IP resolution issues.
• CIFS v2 (RED016): Indicates the remote share mount failed, often because:
• SMBv2 is disabled on the OME appliance.
• Incorrect credentials or share permissions.
• Network name resolution issues.

 

Resolution steps:

1. For HTTPS Method
• Yes, you need to export OME’s HTTPS certificate and import it into each iDRAC if you enforce certificate validation.
• Alternatively, disable certificate validation in OME firmware update settings (less secure).
• Steps:
• In OME: Application Settings → Certificates → Export HTTPS certificate.
• In iDRAC: Configuration → iDRAC Settings → Network/Security → Import Trusted Certificate.
2. For CIFS v2 Method
• Ensure SMBv2 is enabled on OME appliance.
• Verify share path and credentials.
• Test connectivity from OME to the share using: *```bash mount -t cifs //\ /mnt
3. DNS and IP
• Confirm iDRAC resolves OME FQDN correctly (ping from iDRAC SSH if enabled).
• If DNS fails, use IP in OME settings.
4. Firewall/Ports
• HTTPS requires port 443 open between iDRAC and OME.
• CIFS requires ports 445 and 139.

 

 

 

I'm adding in some reference material that may help:

 

OpenManage Enterprise: How to Perform Firmware Updates

https://www.dell.com/support/kbdoc/en-au/000183965/how-to-create-perfom-firmware-updates-using-openmanage-enterprise

 

Dell OpenManage Enterprise 4.5 User's Guide

https://dl.dell.com/content/manual71515353-dell-openmanage-enterprise-4-5-user-s-guide.pdf?language=en-us

 

For the HTTPS method:

I exported the OME certificate from the browser login screen and saved it as ome.cer. Unfortunately, there is no option to export the certificate in the location you specified in OME certificates.

Then, on the IDRAC side, there is no option to import the certificate, only to import the CA certificate, which does not apply to us.

So I imported the certificate manually into IDRAC and restarted it:

racadm -r idrac_ip -u root -p idrac_password sslcertupload -t 2 -f C:\ome.cer

But after repeating the installation via HTTPS, I get the same error (RED137).

Hello, 

in this case I suggest to call in our technical support in order to check and analyse the issue and find a resolution.

Thanks

For the CIFSv2 methow what I found:

test ports open to OME, from the server that is on the same network (ip addressing) like OME server:

PS C:\Users\Administrator> Test-NetConnection -ComputerName <ome_ip> -Port 445          

WARNING: TCP connect to (<ome_ip> : 445) failed                                                                                                       

PS C:\Users\Administrator> Test-NetConnection -ComputerName <ome_ip> -Port 139
WARNING: TCP connect to (<ome_ip> : 139) failed

How can I check if ports are open on the OME server, is there any SSH, CLI access to it?

No, OME doesn’t allow SSH or direct CLI access. To check if ports are open, you need to test from another machine.

Key ports for firmware updates: 443 (HTTPS), 445 (CIFS), and sometimes 80