unable to update

Question

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

DELL-Chris H · Answer

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.

Dell-Martin S · Answer

Hi,### **Configuring OME to Use NATted Public IP for iDRAC Firmware Updates**   When OpenManage Enterprise (OME) initiates a firmware update, it instructs iDRAC to connect back to OME on **port 445 (SMB)** to download the firmware. However, if OME provides iDRAC with its **private IP** (which isn’t reachable from the internet), the update fails.   To resolve this, you need to ensure OME communicates its **NATted public IP** to iDRAC instead of the private one. Below are the steps to configure this properly.   --- ## **Solution: Force OME to Use Public IP for iDRAC Communication**   ### **1. Verify NAT & Firewall Rules**  - Ensure **port 445 (SMB)** is forwarded from the public IP to OME’s private IP.  - Confirm iDRAC can reach the public IP (e.g., via `ping` or `telnet` to port 445).   ### **2. Configure OME to Advertise Its Public IP**  #### **Option 1: Update OME Network Settings**  1. Log in to **OME Web UI** → **Application Settings** → **Network Configuration**.  2. If available, set the **'External Address'** or **'NAT Address'** to the public IP.  3. Save and restart OME services if required.   #### **Option 2: Use DNS Resolution**  - Ensure OME’s hostname resolves to the **public IP** when queried by iDRAC.  - Configure iDRAC’s DNS settings to use a resolver that correctly maps OME’s hostname.   #### **Option 3: Manually Specify OME’s Public IP in Discovery**  1. In OME, go to **Devices** → **Discovery**.  2. Edit the discovery job and specify the **public IP/hostname** in the **'OME Server Address'** field.   ### **3. Configure iDRAC for NAT Communication**  1. Log in to **iDRAC Web UI** → **iDRAC Settings** → **Network**.  2. Ensure **DNS settings** are correct (if using hostnames).  3. If available, configure **NAT/proxy settings** to use the public IP for outgoing connections.   ### **4. Test the Firmware Update**  - Initiate a firmware update from OME.  - Check **iDRAC logs** (**Logs** → **System Event Log**) to confirm it connects to the **public IP**.  - If it still fails, manually push firmware via:    - **iDRAC Web UI** → **Maintenance** → **Firmware Update** → Enter OME’s **public IP/hostname**.   --- ## **AResources**  - [Dell OME Documentation](https://www.dell.com/support/manuals/)  - [iDRAC Network Configuration Guide](https://www.dell.com/support/kbdoc/en-us/000177212/)  - [OME Troubleshooting NAT Issues](https://www.dell.com/community/OpenManage-Enterprise/bd-p/OpenManageEnterprise)   If the issue persists, consider updating **OME/iDRAC firmware** or contacting **Dell Software Support via Hotline**. Let me know if you need further assistance!

btiiss · Answer

@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?

DELL-Erman O · Answer

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:

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

btiiss · Answer

okay thanks u can u please show me how i can increase timeout is it from idrac or OME TUI cuz i couldnt find the info

DELL-Erman O · Answer

If you're on an older version, updating the iDRAC firmware itself might help prevent future timeouts.

or in OME

Go to: Configuration > Firmware
Create or select a baseline
Click: Update Firmware
In the Schedule Update window, choose:
- Update Now
- Stage for next reboot
- Schedule Later — this lets you pick a specific time/date, which can help avoid peak network load or maintenance windows

Git: Yapılandırma> Ürün Yazılımı Bir temel oluşturun veya seçin Tıklayın: Ürün Yazılımını Güncelle Program Güncelleme penceresinde şunu seçin: Şimdi Güncelle Bir sonraki yeniden başlatma için sahne Daha sonra programlayın -

btiiss · Answer

another qst related to how we fixed the problem:

"First, OME connects to the Dell servers, and then the Dell servers connect back to OME on port 445 to copy or retrieve the firmware image for upgrades. The issue is that OME asks iDRAC to connect using the private IP which is not reachable from the internet. We need OME to instruct iDRAC to connect through the NATted public IP instead. How can we configure OME so that iDRAC uses the NATted IP instead of the private one?"

Dell OpenManage Enterprise

unable to update

Was this post helpful?