OpenManage Suggestions for Improvements - Systems Management - Wiki - Systems Management - Dell Community
Wikis - Title

OpenManage Suggestions for Improvements

Systems Management

Systems Management
Dell Systems Management Solutions: Dell OpenManage, iDRAC, Repository Manager, Microsoft SCCM, Chassis Managment Controller, and more

Systems Management - Wiki

OpenManage Suggestions for Improvements

Systems Management - Wiki

This area is a collection point for any ideas you have on OpenManage product improvement. All of the OpenManage product marketing and product development teams have access to this area. Thanks for taking the time to submit your ideas.

Please start a new thread for each suggestion you have for improvement. Post each suggestion as a "new thread", don't post your new suggestion as a "reply" to an existing thread, create a new one.

You can also "vote" for the ideas by using the "Do you find this valuable?" buttons. Thanks for your feedback.

  • I would like to see disk speed (i.e. 10K, 15K) shown in the Dell DTK when running "raidcfg.exe pdisk controllerid=0"

    I know for SEAGATE disks the fourth from the last digit in the model is the speed but this is not true for all manufacturers.

    This is the output currently shown for one physical disk:

    ****** Physical Drive ******

      Vendor: DELL(tm)

       Model: ST9146803SS

    Protocol: SAS

       Media: HDD

    NegSpeed: 6144 Mbps

    CapSpeed: 6144 Mbps

    Certified: YES

    Supported: YES

    Location: 0:1:1

        Size: 139392 MB (136 GB)

       Avail: 0 MB

  • Please make it possible to change the default certificate encryption from a 56-bit key to something stronger, such as 128-bit or 256-bit by default, or allow us to change the certificate used in the web server from the command line.

  • The recent Red Hat kernel update associated with Red Hat 6.4 appears to have broken the latest Open Manager 7.2.0.  It looks like Red Hat moved their IPMI driver into the kernel (used to be a loaded module) which confuses the dataeng startup scripts.  Could you update the install or startup scripts to either detect this or perhaps provide an --option to work around this Red Hat change?