Release Notes

• BITS265922 - The DSM SA Connection will fail to start if Java Runtime Engine 1.8.0 or newer is installed and specified as the
“System JRE” in Preferences of the Server Administrator web GUI. OMSA 8.3 and older is currently not compatible with Java
1.8 or newer. To recover to the default Bundled JRE setting so that the web service starts again, enter the following command
line: omconfig preferences webserver attribute=setjre jreversion=bundled
• BITS260330/BITS260451 — Restart the data manager service, after Intel NIC driver update or NVIDIA graphics driver update
is performed
Issues for Remote Access
NOTE: The Remote Access Service is supported on 11th generation of PowerEdge servers only. The following
subsections list the currently known issues regarding implementation and operation of your RAC and the Remote Access
Service in Server Administrator.
Issues of Server Administrator on all Operating Systems
• The Server Administrator user interface and commands related to local authentication enable are not applicable for RAC
firmware 3.20. The Active Directory authentication feature replaces the local operating system authentication feature in this
version of firmware. Due to this change, the following commands return errors:
– racadm localauthenable
– omconfig rac authentication
• Due to fluctuations in the watchdog timer, the Last Crash Screen may not be captured when the Automatic System Recovery
is set to a value of less than 30 seconds. To ensure the correct functioning of the Last Crash Screen feature, set the System
Reset Timer to at least 30 seconds.
• DF132894: The cfgDNSServer1 and cfgDNSServer2 properties of group cfgLanNetworking may be set to identical values while
swapping addresses. Some performance may be lost temporarily during the swapping. The cfgLanNetworking group is
configured using theracadm config command.
• The remote access controller uses FTP protocol to perform some of the Server Administrator commands. If a firewall is installed
in the system, it may cause these commands to fail.
The following Server Administrator CLI commands use FTP protocol to communicate with the RAC:
– omconfig rac uploadcert
– omconfig rac generatecert
The following racadm commands use FTP protocol to communicate with the RAC:
– racadm sslcertupload
– racadm sslcsrgen
– racadm fwupdate
• If the RAC configuration is reset to factory defaults using the racadm racresetcfg command, the RAC configuration tab in
Server Administrator does not reflect the reset configuration settings until the system reboots. Also, the RAC configuration
page in Server Administrator cannot be used to make any configuration changes until the system reboots.
• The RAC does not support local RAC user IDs with special characters. When adding a local RAC user, use only alphanumeric
characters for the user name.
• While the RAC is being reset, the Instrumentation Service cannot read sensor data for certain systems. As a result, the voltage,
temperature, and other probes may not be visible on the Server Administrator home page until the RAC has completed
resetting.
• The RAC may not send traps when your system is locked up. To enable traps to be sent when the system is locked, configure
the watchdog timer using the Server Administrator GUI. On the GUI, click the "Properties" tab and ensure that Auto Recovery
is selected. The default value of theAction On Hung Operating System Detection setting is None.None indicates that
detection will not be performed.
• RAC firmware 2.0 and later does not support passwords with special characters (non- alphanumeric) only for RAC user IDs
logging in using the Web-based interface (with Local RAC Authentication). You cannot log on to RAC, if you created RAC user
IDs using previous versions of the firmware or using Server Administrator that is running version 2.0 firmware on the managed
system.
Use one of these methods to correct this issue:
11