UNSOLVED

MK1024

updated

12 years ago

M

MK1024

1 Rookie

•

101 Posts

0

17809

August 20th, 2014 08:00

OME Wants to Install MD1000 Firmware A.04 Over and Over Again

We have a couple of MD1000 storage arrays.  OME sees these as having firmware version A.04.  It thinks the newest version is A04 (missing the period) and wants to install it.  This is causing OME to continually want to update the firmware and the associated systems are always labeled non-compliant.

  • MikeyB13

    33 Posts

    953

    0

    Posted August 20th, 2014 13:00

    We have the same issue. With our ML6000 it sometimes tells you an old firmware is newer than what you currently are running.
  • DELL-Rob C

    4 Apprentice

    •

    2843 Posts

    954

    0

    Posted August 20th, 2014 16:00

    Thanks for the post.  It looks like the MD1000 may be EOL and not in our support matrix.

    But, that said :)  I got word that it looks like we made a change in the upcoming version of OME to not do as strict of checking so it should be addressed.

    Thanks much,

    Rob

    www.delltechcenter.com/ome

  • DELL-Rob C

    4 Apprentice

    •

    2843 Posts

    954

    0

    Posted August 22nd, 2014 09:00

    Sure, sure, understand.

    I'll pass along the suggestion to ignore.  In this case, though EOL, we fixed it to do less strict string matching, so hoping we will be ok with this one.

    Best regards,

    Rob

  • MK1024

    1 Rookie

    •

    101 Posts

    954

    0

    Posted August 22nd, 2014 09:00

    Perhaps an option could be added to OME to allow an administrator to mark a specific update as ignored. 

    I'm glad to hear that the issue might be fixed in the next release of OME.  If that weren't the case, it would be disappointing to hear "It looks like the MD1000 may be EOL...so your are SOL." 

    A much more pleasing response would be "It looks like the MD1000 is EOL...so just mark the update as ignored."

  • MK1024

    1 Rookie

    •

    101 Posts

    954

    0

    Posted August 22nd, 2014 12:00

    Thanks.

  • MK1024

    1 Rookie

    •

    101 Posts

    954

    0

    Posted September 12th, 2014 06:00

    It looks like this problem has been fixed in OME 2.0.  The systems with the MD1000 devices are now showing as compliant.

  • DELL-Rob C

    4 Apprentice

    •

    2843 Posts

    954

    0

    Posted September 12th, 2014 14:00

    Ah great.  Thanks for posting an update.

    Regards,

    Rob

  • MK1024

    1 Rookie

    •

    101 Posts

    954

    0

    Posted December 22nd, 2014 07:00

    Just checking in to see if the option for ignoring selected updates has been given any serious consideration.  This would be really helpful for me.  Right now I have systems listed as non-compliant for the following reasons and I'd rather just ignore the associated DUPs.

    1. Firmware updates listed for Server 2003 servers even though the installer won't run on Server 2003.

    2. Driver update for a 32-bit Server 2008 system that is a 64-bit driver.  OME thinks the driver is newer because the 32-bit version number ends with .32 while the 64-bit driver ends with .64.  (64 > 32)

    3. OS Driver Packs that fail to install with "Secure Copy function Failed".  I'd like to ignore these because we aren't planning on using the lifecycle controller for OS installation on these systems any time soon.

  • 954

    0

    Posted December 22nd, 2014 10:00

    Hi,

    Thanks for the post. OME computes the non-compliance/compliance based on the active catalog source (which by default is dell online catalog). There is no option currently in OME to ignore specific DUPs for being considered in determining compliance/non-compliance.

    Having said this, there is a way where you can build your custom catalog using Dell Repository Manager (where you can select/ignore specific components) and select this Dell Repository Manager catalog as your catalog source in OME. Pl. look at this whitepaper which will provide more insights - http://en.community.dell.com/techcenter/extras/m/white_papers/20069223/download and keep us posted if it helps.

    Thanks,
    Vijay

  • MK1024

    1 Rookie

    •

    101 Posts

    248

    0

    Posted December 22nd, 2014 11:00

    Vijay,

    I know that OME currently doesn't allow specific DUPs to be ignored.  That's why I put in the feature request.

    Thanks for the suggestion, but building a custom repository sounds like a lot of work to work around logic errors and problematic DUPs. 

    Please just make sure that my feature request receives consideration.  Thanks.