UNSOLVED

GBains

updated

6 years ago

G

GBains

3 Posts

0

875

February 5th, 2021 07:00

DOME 3.5.0 (Build 60) - FW Updates and revision numbers

All,

Is anyone having a problem with the inventories updating incorrectly with the appropriate revision numbers?

For example, I have a PowerEdge R740xd whose BIOS was updated from 2.9.4 to 2.10.0. On checking the inventory after a refresh, it still states it's running 2.9.4. On logging into the iDrac, it states it's running 2.9.4 BUT on boot from viewing the console, it shows as 2.10.0.

As a result, the machine shows up as being non-compliant and does not disappear from the list.

  • DELL-Chris H

    7 Practitioner

    •

    9682 Posts

    •

    48046 Points

    580

    0

    Posted February 5th, 2021 12:00

    GBains,

     

    To me it sounds like iDrac Inventory is the issue, not OME, but let me confirm a couple things. 

     

    Is it only happening to the one server, if so does running 

    racadm systemerase lcdata resolve the issue?

     

    If it is multiple servers, is there any similarities between the servers, like generation, network, etc?

    Lastly, is the system(s) up to date on BIOS and iDrac?

     

    Let me know.

     

     

    DELL-Chris H

    Social Media and Communities Professional

    Dell Technologies | Enterprise Support Services

    #IWork4Dell

    Did I answer your query? Please click on ‘Mark as Accepted Answer’. ‘Thumbs up’ the posts you like!

  • justin gray

    2 Intern

    •

    143 Posts

    •

    2 Points

    539

    0

    Posted February 12th, 2021 13:00

    I discovered the same issue today after several BIOS updates. The only way I could correct it was on each device:

    1. Reset iDRAC (Device > Overview > Troubleshoot > Rest iDRAC)
    2. Then Refresh Inventory (Device > Overview > Refresh Inventory)

    Once that was done on each device, I went back to their Baseline and clicked 'Check Compliance'.

    I had a similar issue where Firmware was showing downgrade because it flagged a non-existent device with firmware version = 'NA'. The same process above resolved that, as well.

    HTH