Manualshelf

Release Notes

ManualsBrandsDell ManualsActive System ManageriDRAC6 for Monolithic Servers Version 2.90
123456789
iDRAC6 v2.90.04 7
Issue 10
Description
When the Certificate Authority (CA) is enabled, the Domain Controller (DC) is specified as FQDN and Global Catalog
(GC) as IP address, the authentication using Test Settings fails and normal login succeeds. The expected behavior is
the authentication using Test Settings must succeed by using DC FQDN.
Resolution
Specify the FQDN for GC.
Versions/Systems affected
All iDRAC6 supported Dell PowerEdge systems.
Issue 11
Description
SSH server takes more time to establish a connection from putty client.
Resolution
For improving the performance, change the order of the key exchange algorithm in Putty SSH configuration:
1. Open Putty.
2. Expand SSH tab.
3. Click Kex.
4. Change the order in the Algorithm selection policy window.
5. Connect to the SSH server. The connection is established.
Versions/Systems affected
All iDRAC6 supported Dell PowerEdge systems.
Issue 12
Description
In a system with Microsoft Windows Server 2012 R2 and Dell OpenManage 7.4, the operating system name may not
appear on the iDRAC6 web interface and RACADM. This is an intermittent issue.
Resolution
View the operating system name from the Dell OpenManage Server Administrator installed on the host system.
Versions/Systems affected
All iDRAC6 supported Dell PowerEdge systems.
Issue 13
Description
After updating Lifecycle Controller using the Remote Enablement (RE) Services, the Lifecycle Controller version is
not updated in the System Summary page in the iDRAC web interface.
Resolution
Reboot iDRAC to view the updated Lifecycle Controller version.
Versions/Systems affected
All iDRAC6 supported Dell PowerEdge systems.
Issue 14
Description
The remote host supports IPMI v2.0. The Intelligent Platform Management Interface (IPMI) protocol is affected by
an information disclosure vulnerability due to the support of RMCP+ Authenticated Key-Exchange Protocol (RAKP)
authentication. A remote attacker can obtain password hash information for valid user accounts via the HMAC from
a RAKP message 2 response from a BMC.