Release Notes

￭ Delete the file keystore.db at <installed directory>\Dell\SysMgt\apache- tomcat\conf\
￭ Rename the file keystore.db.bak at <installed directory>\Dell\SysMgt\apache-
tomcat\conf\ to keystore.db
○ On systems running Linux:
￭ - Delete the keystore.db file at /opt/dell/srvadmin/lib64/openmanage/apache- tomcat/
conf
- Rename the keystore.db.bak at /opt/dell/srvadmin/lib64/openmanage/apache-tomcat/
conf to keystore.db
3. Start the Web server.
● BITS078118: On YX2X 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.
● JIT-60691: In SCOM – Server Management Pack (MP) for monitoring Physical and Team network interfaces XML files are
created due to the heavy usage of the Server Administrator CLI NIC command (omreport chassis nic -fmt xml).
● JIT-112708: Memory critical error not clearing from OMSA even after replacing the DIMM and clearing SEL logs.
If a dual-inline memory module (DIMM) generates errors, memory states of the DIMM’s are not automatically
cleared even after the failing DIMM in that slot is replaced. The command to clear the memory error is dcicfg
command=clearmemfailures. The binary dcicfg, needed to launch the command from a shell command, is included
in the OpenManage Server Administrator (OMSA) suite.
● JIT-148035: On Server Administrator, vFlash is not supported from YX5X generation of servers and above.
● JIT-148988: While logging to the Server Administrator GUI, the login may fail if the password contains the non-ASCII
characters for example: Euro symbol €.
● JIT-152343: In Remote Access page, Device Type will be displayed as iDRAC9 Express if iDRAC9 Datacenter license is
installed for iDRAC the Server Administrator does not recognize iDRAC9 Datacenter license.
● JIT-139048: The Command Log Size value if modified on Server Administrator Preferences page as Local user and then
logging into the same server via Server Administrator Managed System Login. The changes of the attribute are not reflected
in the Preferences page of Server Administrator Managed System Login.
Issues for Remote Access
NOTE:
The Remote Access Service is supported on YX1X 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.
10