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.
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?
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
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.
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.
Hi we have some similar issues with ESXi hosts and updating to latest firmware.
We have discovered ESXi hosts by WSMAN and iDRAC and the Servers all reported under RAC and ESXi groups in OME all ok.
So we set about updating the firmware using OME - packages all downloaded ok and started to update.
However the task does not complete successfully - runs firmware updates but never reports back and times out. We have checked and in fact the firmware did update on the hosts we chose - iDRAC, BIOS, LifeCycle, OS Driver and UEFI Diags - so the iDRAC shows versions are updated.
However the inventory despite being updated shows previous versions of the firmware in OME. Also RAC in OME reports as off and we can no longer access the iDRAC via IE - 'this page cannot be displayed' yet before the updates we could access via IE. Now have to use Firefox and add exception to access the iDRAC.
We experienced the same issue when updating another host using OME - so it seems the update of the iDRAC means it can no longer communicate back to OME.
we have the same problem with new installation OpenManageEssentials_2_3_A00 on W2012R2. I can see R630 (ESXi 6.0U3 with OMSA 8.5.0-2372) or R320 (ESXi 6.5 with OMSA 8.5.0-2372) from OME server:
If I run WSMAN test in Troubleshooting Tool with both Skip CA & CN Check enabled I get full info:
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
Otherwise I get an error:
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. RemoteCertificateNameMismatch 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
Is it certificate problem? Both servers are discovered, inventoried and statused in OME but stay unknown and Device Type Unclassified with Device Summary and NIC Information only.
ITguy2471
5 Posts
10432
0
Posted November 2nd, 2016 15:00
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.