Start a Conversation

Solved!

Go to Solution

1 Rookie

 • 

17 Posts

104

May 14th, 2025 12:16

unable to update

im trying to update my firmware from OME: Version 3.10.0 (Build 169) and im receiving this error:

Unable to update the firmware because communication with Chassis Management Controller (CMC) or Management Module (MM) took more time than the specified duration.

PS: port 443 is open both ways

Moderator

 • 

9.4K Posts

May 14th, 2025 16:32

Btiiss,

 

It sounds like you're encountering a timeout issue during the firmware update process. Would you confirm the specific update it fails at? I would also try these steps to see if any resolve this issue:

 

First off I would check network connectivity:

Ensure that there are no network issues between the OpenManage Enterprise (OME) appliance and the Chassis Management Controller (CMC) or Management Module (MM). I see that you stated port 443 are open, but can you verify that it isn't being blocked by any firewall rules.

 

You can try increasing the timeout settings in OME to allow more time for the firmware update process. This can sometimes resolve issues where the update process is taking longer than expected.

 

Update OME and CMC/MM Firmware:

Ensure that both the OME appliance and the CMC/MM firmware are up to date. Sometimes, compatibility issues between different firmware versions can cause update failures. Check for the latest firmware versions on Dell's support site and apply any available updates.

 

If the issue persists, consider using a local repository for the firmware updates. This can help reduce the time taken to download and apply updates, as the files will be accessed from a local network share rather than over the internet. You can create a local repository using Dell Repository Manager (DRM) and configure OME to use this repository 1.

Review the job logs in OME for any specific error messages or codes that can provide more insight into why the update is failing. This information can be useful for further troubleshooting or when contacting Dell support.

 

Sometimes, restarting the OME services can help resolve communication issues. You can do this by logging into the OME appliance and restarting the relevant services.

 

Let me know if this helps and what you see. 

 

1 Rookie

 • 

17 Posts

August 4th, 2025 13:36

@DELL-Chris H ​ hello thanks for ur replay, this is the error msg i get: 

Messages:
Running
Verifying if the device Service Tag is valid.
The device Service Tag is valid.
Starting communication with the device.
Update allowed in target, System Lockdown status = DISABLED
Checking Remote LC Services availability
Remote LC Services are ready now
Attempting to initiate/stage payload instance: DCIM:INSTALLED#802__ServiceModule.Embedded.1
Initiated Status check for Job ID : JID_543154780581
Job state for JID_543154780581 is Failed
Unable to update the firmware because communication with Chassis Management Controller (CMC) or Management Module (MM) took more time than the specified duration.
Task Failed. Completed With Errors.
can u advise how to check whats the exacte issue is, cuz i checked with security and they say that the firewall isnt blocking the request on the way out but thay cant even see it on the outside of the firewall on the way back?

Moderator

 • 

2.8K Posts

August 4th, 2025 14:31

Hi, 

sounds like you're hitting a timeout when trying to update firmware via Remote LC Services.
Even if outbound traffic isn’t blocked, the return traffic from the CMC/MM might be getting lost due to:

  • Network latency or dropped packets
  • Firewall/NAT issues (like stateful inspection or missing inbound port rules)
  • Outdated LC or CMC firmware
  • Timeout settings being too short for the job

Here are a few things you can check:

  1. Ports – Make sure required ports (e.g., TCP 443, 22, 5900) are open both ways.
  2. Firmware versions – Confirm LC and CMC are up to date.
  3. Network trace – Use Wireshark or tcpdump to see if return traffic is getting blocked or dropped.
  4. Timeout config – If possible, increase the timeout duration.
  5. LC job logs – Check detailed logs in Lifecycle Controller or iDRAC for more clues.

(edited)

No Events found!

Top