Resolution for the issue - iDRAC or CMC displays an “unknown” status after upgrading to the latest firmware version - Dell OpenManage Essentials - Systems Management - Dell Community
Systems Management Forums

Resolution for the issue - iDRAC or CMC displays an “unknown” status after upgrading to the latest firmware version

Systems Management

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

Resolution for the issue - iDRAC or CMC displays an “unknown” status after upgrading to the latest firmware version

  • Hi OME users,

    It has been observed that after upgrading to the latest firmware version (iDRAC >= 2.40.40.40, M1000e CMC >= 5.2, FX2 CMC >= 1.4, VRTX CMC >= 2.2), the iDRAC or CMC displays an “unknown” status.

    The latest firmware version supports TLS 1.1 as the default communication protocol. If the browser or operating system where OpenManage Essentials is installed, does not support TLS 1.1 protocol, then the device displays an “unknown” status.

    To resolve this issue, see “Step 2: Verifying Dell Management Consoles” in the following KB article: http://www.dell.com/Support/Article/us/en/19/SLN302365

     Note: Ensure the required registry updates are done either manually or using the “Easy Fix” described in the Microsoft support article - "Update to enable TLS 1.1 and TLS 1.2 as a default secure protocols in WinHTTP in Windows"

    Thanks,
    Vijay

  • I'm still having this issue after trying your fix above with IDRACs showing unknown and also the servers with 2.40.40.40 not updating the inventory properly. All of them are showing non-compliant though their IDRACs are up to date. My OME server is a Windows server 2012 R2 version 2.2.0.2056. Any help would be appreciated.

  • Same issue here, I've followed the original steps with no success.. All applicable iDRACs are updated but OME still shows them as non-compliant. OME version 2.2.0.2056. Any direction on how to fix this?

  • Hi,

    Windows Server 2012 R2 has by default TLS 1.1/1.2 enabled and you shall not be hitting the issue with OME installed on Windows Server 2012R2.

    Can you run the latest Troubleshooting tool shipped with OME 2.2 and perform ws-man test?

    That will give you some direction.

    Thanks,
    Vijay

  • This is what I get running the WS-Man test:

    Using TLS 1.0 for SSL/TLS handshake.
    Error: A complete request could not be sent to the remote server.
    Using TLS 1.1 for SSL/TLS handshake.
    UntrustedRoot: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.

    TLS 1.1 Handshake successful.

    The WS-Man target has TLS 1.1 enabled. If OME is unable to discover this device, install the required updates on the system where OME is installed. For more details, see “Enabling support for TLS 1.1 or 1.2” at delltechcenter.com/ome.


    Identify Failed. Could not connect

    Let me know if I can give you any additional information on this.

  • I am seeing similar issues with new servers running 2.40.40.40 for DRAC firmware:

    Protocols Selected are: WSMAN

    Using TLS 1.0 for SSL/TLS handshake.
    Error: A complete request could not be sent to the remote server.
    Using TLS 1.1 for SSL/TLS handshake.
    TLS 1.1 Handshake successful.

    The WS-Man target has TLS 1.1 enabled. If OME is unable to discover this device, install the required updates on the system where OME is installed. For more details, see “Enabling support for TLS 1.1 or 1.2” at delltechcenter.com/ome.

    Connected.
    WSMAN profiles found on the remote device are:
    1. Profile Registration
    2. Base Metrics
    3. Base Server and Physical Asset
    4. BIOS and Boot Management
    5. CPU
    6. Event Filter
    7. Fan
    8. Fiber Channel
    9. iDRAC Card
    10. Job Control
    11. LC Management
    12. License Management
    13. Memory
    14. OS Deployment
    15. PCI Device
    16. Persistent Storage
    17. Power State Management
    18. Power Supply
    19. Record Log
    20. Role Based Authorization
    21. Sensors
    22. Service Processor
    23. Simple Identity Management
    24. Simple NIC
    25. Simple RAID
    26. Software Inventory
    27. Software Update
    28. System Info
    29. Video
    30. SystemQuickSync
    31. USBDevice
    32. Physical Computer System View
    33. Command Line Protocol Service
    34. SM CLP Admin Domain
    35. SMASH Collections

  • Thanks Cameron for the details.

    As a next step, can you try running the below winrm commands replacing IP/credentials as required and see if it returns valid output.

    winrm e cimv2/root/dcim/DCIM_SystemView -u:user -p:password -r:https://a.b.c.d/wsman:443 -SkipCNcheck -SkipCAcheck -encoding:utf-8 -a:basic 

    If it gives valid output, then OME should not have any problem discovering the respective iDRAC.

    If it does not, then I would suggest to refer "How the DefaultSecureProtocols registry entry works"  in https://support.microsoft.com/en-us/kb/3140245 and ensure required registries are enabled.

    Regards
    Vijay

  • Thanks Vijay,

    I had previously installed the windows update from that link but I did not run the "easy fix" . After running that and rebooting OME server I am now able to fully see my dracs with 2.40.40.40 in OME.

    Thanks for your help!

  • Glad that your problem got solved.

    Thanks for taking time and updating this thread.

    Regards
    Vijay