Dell PowerEdge XE2420 iDRAC9 Version 4.00.129.00 Release Notes - Page 16

OpenAPI.YAML file.

Get Dell PowerEdge XE2420 PDF manuals and user guides View all Dell PowerEdge XE2420 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 16 highlights

• The Digitally sign communications option is disabled. • Permissions to access the folder/file are granted. • folder/file name does not have a space. • Share contains fewer files and folders. 43. While iDRAC is initializing, all communications with iDRAC may fail. For any service requests, wait until the initialization process is complete. 44. Performing Redfish Patch method on Read-Only property for PowerControl resource returns a status code 200. 45. In iDRAC, if there is no link that is detected in the selected iDRAC port then the iDRAC IP is displayed as 0.0.0.0. 46. While performing a firmware update on a system where the operating system is installed with GNOME GUI enabled, system may get into Suspend mode. To avoid the system from going into suspend mode, ensure that you change the power settings in the operating system. To change the power settings: a. Go to Settings, and select Power. b. For the option, "When the Power Button is pressed" select Power Off. 47. Firmware update on drives and backplanes through Windows DUP will reflect in iDRAC after. A cold boot. In Lifecycle logs, version change may be displayed repeatedly if cold reboot. Is not done. 48. FRU objects or properties for Network adapters that are embedded on the motherboard are not available through any of the iDRAC interfaces. 49. Lifecycle Controller supports ISO images with ISO-9660 format only. Other formats including combination with ISO-9660 are not recommended. 50. UserDefined delay AC Recovery Power Delay is slow with lower limit of 60, but some conditions might cause BMC ready to be later than this and hence may not work. So, it is advised that the UserDefined delay be set to 80 s or higher. Any values less than this may cause the operation to fail. 51. The iDRAC feature "Topology LLDP," is not supported on 1 GbE controllers and selects 10 GbE controllers (Intel X520, QLogic 578xx). 52. Mellanox network adapters that are used in PowerEdge MX740c and MX840c servers must be updated to version 14.23.10.20 or later, before updating the iDRAC firmware to version 4.00.00.00. 53. Install SEKM license before you update the iDRAC to SEKM supported version 4.00.00.00. If you install the SEKM license after updating the iDRAC to SEKM supported version, you have to reapply SEKM supported iDRAC firmware. 54. If you are configuring a Gemalto based KeySecure SEKM Server with iDRAC, and to get the redundancy feature functional, copy the certificates manually from primary Gemalto KeySecure cluster to secondary Gemalto SEKM KeySecure cluster. The redundance feature works after the iDRAC is set up for SSL certificate-based authentication. 55. Key sharing between multiple iDRACs is supported and can be configured on the SEKM server. Key sharing can be done if all the iDRACs are part of the same SEKM group and all keys are assigned to the same group with the right permissions. 56. When FCP is enabled, 'Default Password Warning' setting is disabled after the default user password is changed. 57. Firmware update from iDRAC versions earlier than version 3.30.30.30 is not supported (For example, updating iDRAC firmware from version 3.21.21.21 to version 4.00.00.00 is not supported). First update to version 3.30.30.30 or higher, and then initiate update to 4.00.00.00. 58. If system lockdown mode is enabled while a user is logged into LifeCycle Controller GUI, then lockdown mode will not be applicable on LifeCycle Controller. 59. Due to a DMTF tool limitation, the URIs for some OEM actions that are extensions to the DMTF schemas may not appear in the OpenAPI.YAML file. 60. The iDRAC Virtual Keyboard labeling is changed to upper case to align it with the physical keyboard layout. 61. Keyboard interactive authentication has been enabled on the iDRAC SSH Server to provide enhanced security. SSH clients now require both password authentication and keyboard interactive authentication to before logging in a user in to iDRAC. 62. If you see iSM0050 event in LC log, then ensure that you update the iDRAC Service Module (iSM) to version 3.4 or to a TLS-capable iSM. iSM without TLS capability is not supported on iDRAC firmware version 3.30.30.30 or later. 16 Important notes

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
•
The
Digitally sign communications
option is disabled.
•
Permissions to access the folder/file are granted.
•
folder/file name does not have a space.
•
Share contains fewer files and folders.
43.
While iDRAC is initializing, all communications with iDRAC may fail. For any service requests, wait until the initialization process is
complete.
44.
Performing Redfish Patch method on Read-Only property for PowerControl resource returns a status code 200.
45.
In iDRAC, if there is no link that is detected in the selected iDRAC port then the iDRAC IP is displayed as 0.0.0.0.
46.
While performing a firmware update on a system where the operating system is installed with GNOME GUI enabled, system may get
into Suspend mode. To avoid the system from going into suspend mode, ensure that you change the power settings in the operating
system. To change the power settings:
a.
Go to Settings, and select Power.
b.
For the option, “When the Power Button is pressed” select Power Off.
47.
Firmware update on drives and backplanes through Windows DUP will reflect in iDRAC after.
A cold boot. In Lifecycle logs, version change may be displayed repeatedly if cold reboot.
Is not done.
48.
FRU objects or properties for Network adapters that are embedded on the motherboard are not available through any of the iDRAC
interfaces.
49.
Lifecycle Controller supports ISO images with ISO-9660 format only. Other formats including combination with ISO-9660 are not
recommended.
50.
UserDefined delay AC Recovery Power Delay is slow with lower limit of 60, but some conditions might cause BMC ready to be later
than this and hence may not work. So, it is advised that the UserDefined delay be set to 80 s or higher. Any values less than this may
cause the operation to fail.
51.
The iDRAC feature “Topology LLDP,” is not supported on 1 GbE controllers and selects 10 GbE controllers (Intel X520, QLogic 578xx).
52.
Mellanox network adapters that are used in PowerEdge MX740c and MX840c servers must be updated to version 14.23.10.20 or later,
before updating the iDRAC firmware to version 4.00.00.00.
53.
Install SEKM license before you update the iDRAC to SEKM supported version 4.00.00.00. If you install the SEKM license after
updating the iDRAC to SEKM supported version, you have to reapply SEKM supported iDRAC firmware.
54.
If you are configuring a Gemalto based KeySecure SEKM Server with iDRAC, and to get the redundancy feature functional, copy the
certificates manually from primary Gemalto KeySecure cluster to secondary Gemalto SEKM KeySecure cluster. The redundance
feature works after the iDRAC is set up for SSL certificate-based authentication.
55.
Key sharing between multiple iDRACs is supported and can be configured on the SEKM server. Key sharing can be done if all the
iDRACs are part of the same SEKM group and all keys are assigned to the same group with the right permissions.
56.
When FCP is enabled, 'Default Password Warning' setting is disabled after the default user password is changed.
57.
Firmware update from iDRAC versions earlier than version 3.30.30.30 is not supported (For example, updating iDRAC firmware from
version 3.21.21.21 to version 4.00.00.00 is not supported). First update to version 3.30.30.30 or higher, and then initiate update to
4.00.00.00.
58.
If system lockdown mode is enabled while a user is logged into LifeCycle Controller GUI, then lockdown mode will not be applicable on
LifeCycle Controller.
59.
Due to a DMTF tool limitation, the URIs for some OEM actions that are extensions to the DMTF schemas may not appear in the
OpenAPI.YAML file.
60.
The iDRAC Virtual Keyboard labeling is changed to upper case to align it with the physical keyboard layout.
61.
Keyboard interactive authentication has been enabled on the iDRAC SSH Server to provide enhanced security. SSH clients now
require both password authentication and keyboard interactive authentication to before logging in a user in to iDRAC.
62.
If you see iSM0050 event in LC log, then ensure that you update the iDRAC Service Module (iSM) to version 3.4 or to a TLS-capable
iSM. iSM without TLS capability is not supported on iDRAC firmware version 3.30.30.30 or later.
16
Important notes