Release Notes

- Rename the keystore.db.bak at /opt/dell/srvadmin/lib64/openmanage/apache-tomcat/conf to
keystore.db
3. Start the Web server.
• BITS078118: On 12th generation of PowerEdge servers with specific versions of iDRAC, you cannot set the platform event alert
actions (reboot, shut down, and so on) through Server Administrator. Set the alert actions for the events through iDRAC GUI.
• BITS144583: On Mozilla Firefox 21 or later, the Quit browser option does not work after logging out from Server Administrator. To
close the browser or tab, you must manually close the Firefox browser tab.
• BITS177670: On Chrome 38 or later, the Quit browser option does not work after logging out from Server Administrator. To close
the browser or tab, you must manually close the Firefox browser tab.
• On PowerEdge T430, C4130, and R220 II, with PERC S130 configuration and no backplane, Storage Management displays a mock
backplane which does not support the blink/unblink operation for disks available on this configuration.
• BITS256932: The default factory IP for an IDRAC is “192.168.0.120” or “192.168.0.*”, which indicates that the iDRAC IP is not
configured by the user. However, if you choose to configure the default factory IP (static or DHCP) as your iDRAC IP, then the “Not
Configured” value for “iDRAC Network Settings” displayed on the OMSA “System Summary” page can be ignored. Note: On rack and
tower systems, the default factory IP for iDRAC is “192.168.0.120”. On modular systems, the default factory IP range for iDRAC is
“192.168.0.*”, where “*” can be any value from 0 to 255.
• 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.
11