Release Notes
• While viewing the current hardware inventory, some properties related to devices installed in PowerEdge VRTX system are not
displayed.
• LC can import and view an iDRAC license but cannot export or delete the iDRAC license. The iDRAC license can be deleted from
iDRAC GUI.
• The ISCSI offload attribute can be enabled only on two of the four available ports. If a card, which has this attribute enabled on two of
its ports, is replaced with another card that has the attribute enabled on the other two ports, an error occurs. The firmware does not
allow the attribute to be set because it is already set on the other two ports.
• In LC, not all the vendor FC cards are supported for VLAN configuration.
• LC displays two drive names for some CDs or DVDs, such as the ones containing operating systems.
• Network operations such as Update, Export, or Import may take more time than expected. The delay may occur because the source or
destination share is not reachable or does not exist, or due to other network issues.
• If the operating system (OS) selected for installation and the OS on the media used are different, LC displays a warning message.
However, while installing Windows OS, the warning message appears only when the bit count (x86 or x64) of the OS does not match.
For example, if Windows Server 2008 x64 is selected for installation and Windows Server 2008 x86 media is used, the warning is
displayed.
• LC does not support OS deployment on Dell Precision Workstation R7920.
• LC does not support SOCK4 proxy with credentials.
• LC GUI supports share names and file paths that are up to 256 characters long. However, the protocol you use may only allow shorter
values for these fields.
• Because of internal UEFI network stack protocol implementation, there may be a delay while opening the LC GUI Network Settings
page or while applying the network setting.
• The inventory displayed in LC GUI may not be the same as that of any iDRAC interfaces. To get the updated inventory, run the CSIOR,
wait for 2 minutes, reboot the host, and then check the inventory in LC GUI.
• Before performing any network operations, verify that the network is configured with the network cable connected. In some
scenarios, a warning message may not be displayed but the operation may fail. Following are some examples that may lead to failure:
• Static IP is configured without the network cable being connected.
• Network cable is disconnected.
• After a Re-purpose and Retire operation is performed.
• Network is configured with the network cable connected but the network card is replaced later.
• If you set a user with only SHA256 password, for example, through SCP, you cannot delete the user using the GUI. To delete such a
user, edit the user explicitly setting a password and then try to delete the user.
• Using WSMan, the attribute LCD.ChassisIdentifyDuration cannot be set to -1 (indefinite blink). To make the LED blink
indefinitely, use the IdentifyChassis command with IdentifyState=1.
• RACADM supports the underscore character (_) for iDRAC.SerialRedirection.QuitKey along with the existing symbols
shown in the integrated help.
• Using remote RACADM, if you use the racadm hwinventory export command to export the hardware inventory using an
incorrect CIFS share, an incorrect message is displayed: RAC930 : Unable to export the hwinventory. If the
issue persists, restart the iDRAC and then retry the operation after the iDRAC has finished
restarting.
• If iDRAC is in lock-down mode, and you run the racadm rollback command followed by the racadm resetcfg command, an
incorrect message is displayed: ERROR: A firmware update is currently in progress. Unable to reset the
RAC at this time. Reboot iDRAC to display the correct error message.
• In certain cases, in Group Manager Jobs view, the completion percentage for a job may be displayed incorrectly (>100%) for a job in
progress. This is a temporary condition and does not affect how Group Manager jobs are performed. When the job is completed,
Group Manager Jobs view displays Completed successfully or Completed with errors.
• In certain cases, Group Manager Jobs view may not show a detailed error message for a member iDRAC job. For more information
about the failure, review the job execution details in the Lifecycle Logs of the member iDRAC by using the GUI (Maintenance >
Lifecycle Log) or by using the RACADM command racadm lclog view.
• If there are no slots available to add a new user in iDRAC, the Group Manager Job for Add New User shows a failure with error
GMGR0047. Use the GUI (
iDRAC Settings > Users) to verify the number of iDRAC local users.
• If the user does not exist on a specific iDRAC, Group Manager Jobs for Change User Password and Delete User show a
failure with error GMGR0047. Use the GUI (iDRAC Settings > Users) to verify that the user exists.
• The Discovered Servers view of Group Manager may not show available iDRACs as available to onboard. Verify that the iDRACs are on
the same link local network and not separated by a router. If they are still not visible, reset the Group Manager's controlling iDRAC.
1. Open Group Manager on one of the member iDRACs.
2. In the search box, type the controlling system's Service Tag.
3. Double click the iDRAC that matches the search results and navigate to iDRAC Settings > Diagnostics.
4. Select Reset iDRAC.
When iDRAC fully restarts, Group Manager should see the new iDRAC.
Limitations
13