Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

Server Administrator 8.5 Release Notes

PDF

Issues of Server Administrator on All Supported Operating Systems

  • BITS107804: On PowerEdge R210 II and T110 II servers, clearing the Shutdown OS First check box and performing a reboot using the ‘Reboot’ option does not reboot the servers. After performing these steps if you refresh the Page, the options on the Remote Shutdown page are not displayed.
  • On Dell PowerEdge T110 II systems, the following Server Administrator BIOS settings are not consistent with the F2 BIOS setup settings:
    • Watchdog timer: Server Administrator displays the option as disabled, but F2 BIOS allows to change the setting.
    • Embedded Video Controller: Server Administrator provides options to enable or disable, but in F2 BIOS the option is grayed out.
    • TPM Security: Server Administrator does not allow to change the settings, but F2 BIOS allows to change the settings.
    • System Profile State: Server Administrator does not allow to make changes, but F2 BIOS allows to make the changes.
    • Memory Testing: Server Administrator does not support this feature, but F2 BIOS supports this feature.
    • SRIOV option: Server Administrator does not display this information, but F2 BIOS displays this feature.
  • Due to non-availability of resources, inventory collector may terminate unexpectedly and restart. If this occurs, the folder C:\Temp\invcol may be left as an artifact. The presence of this folder does not affect the functionality of the inventory collection. The folder can be deleted if required.
  • After installing Server Administrator from the command prompt, typing an omreport or mconfig command from the same prompt can cause an error. Open a new command prompt window and type commands.
  • If the command log page in the Server Administrator GUI displays an error message indicating that the XML is malformed, you must clear the command log from the CLI using the omconfig system cmdlog action=clear command
  • After a Reset to Defaults operation of the Integrated Remote Access Controller, the first user configuration, operation fails if it is a single-user configuration item (such as enabling or disabling a user or changing user name). Always change a combination of two-user configuration items (such as enabling or disabling a user and changing user name) concurrently during your first configuration operation.
  • While typing the command omreport system version -outc <filename>, ensure that you specify an absolute path name for the output file; else, the output file is empty. For example, c:\out.txt.
  • Typing omreport system esmlog/alertlog/cmdlog -fmt tbl command on the CLI can result in XML parsing errors if the size of the log is large. Use the GUI or the omreport system esmlog/alertlog/cmdlog CLI command to view the contents of the log.
  • For complex omconfig CLI commands that contain multiple set commands in one command line, the CLI may report a success status for the command even if a part of the command failed. To avoid this issue, run only one command per command line. The current settings can be confirmed by performing the corresponding omreport command.
  • Some complex omconfig CLI commands that contain multiple set operations have been modified to avoid the above problem. While running a CLI command if the message, Error! Illegal combination of parameters is displayed, modify your command into several simpler commands. Each command should change only one setting.
  • When running Server Administrator on a system with a traditional Chinese operating system, the application pages are displayed in simplified Chinese. To view the Server Administrator pages in English, go to your browser language preference page and change the language to English.
  • Log files saved from Server Administrator are saved in zip format. It is recommended that you open this zip file using WinZip. Windows Server 2003 or Windows XP embedded Compressed (zipped) Folder utility is not recommended.
  • After configuring BIOS settings on certain systems, a second reboot may be required for the Server Administrator to display the updated BIOS settings properly.
  • If you import an invalid root certificate into Server Administrator, using Preferences > General Settings > Web Server > X.509 Certificate , and try to log on to the application after restarting the Web server, a blank page is displayed. To fix this issue, restore your original keystore.db file before importing a valid root certificate. To restore the keystore.db file, use both the basic operating system commands and the Server Administrator Command Line Instrumentation (CLI).

    Perform the following steps from your operating system command line:
    1. Type: omconfig system webserver action=stop
    2. Locate the keystore.db.bak file. The default path is C:\program files\dell\SysMgt\apache-tomcat\conf.

    3. Copy keystore.db.bak to keystore.dbkeystore.db.

    4. Type: omconfig system webserver action=start

  • A temperature drop below a minimum failure threshold does not cause a system reset even if this alert action is set.
  • Clicking the Back and Refresh buttons on the browser may not display the correct page regarding the Server Administrator component tree, tabs, tab menus, or help, as Server Administrator has been designed with limited functionality to reduce overhead. Full feature capabilities of the Web browser such as Back, Refresh, and Open in New Window may not be supported.
  • Selecting the boot sequence under the BIOS Setup tab does not re-enable boot devices that have been disabled in the System Setup Program, earlier.
  • The links on the Server Administrator home page may not work after repeated random clicking. To resolve this issue, refresh the browser by pressing <F5> or click the browser Refresh button.
  • All unsecured HTTP requests to Server Administrator receive an invalid response. Server Administrator runs only one instance of the Web server, which is secure. Make all connections through https://<ip address>: <port number> . Any http://<ip address>: <port number> request for connection with the server receives an invalid response.
  • If the web browser used with Server Administrator does not display a page or perform an action, make sure that the browser is in online mode. To go online, perform the following:
    • In Internet Explorer, on the menu bar, click File and clear the Work Offline option. When Work Offline is selected, a check mark is displayed to the left of the option on the File menu.
  • If Internet Explorer prompts you to Work Offline, Connect, or Try Again, always select Connect or Try Again. Do not select Work Offline.
  • In Internet Explorer, on the menu bar, click File and clear the Work Offline option. When Work Offline is selected, a check mark is displayed to the left of the option on the File menu.
  • If Internet Explorer prompts you to Work Offline, Connect, or Try Again, always select Connect or Try Again. Do not select Work Offline.
  • While setting dates in the Asset Information section of the Server Administrator home page, the current time is appended to the date. While setting dates with the CLI, the appended time is noon.
  • On some systems, temperature probe values and settings are only supported for whole degrees, not tenths of a degree. On those systems, setting a fractional value for the minimum warning temperature threshold results in the set value being rounded off to the next whole number value. This behavior may cause the minimum warning threshold to have the same value as the minimum failure threshold.
  • If you close the browser using the Close button on the browser or log off from the operating system, the Server Administrator session is not terminated. This session is listed in the Session Management page until the session time out occurs, or DSM SA connection service is restarted, or the operating system is rebooted.
  • If you change the operating system Time Zone to a new time zone, Server Administrator session management does not display the time in the new time zone specified. Restart Server Administrator to display the accurate time for the time zone in the Session Management page.
  • DF78425: The Server Administrator Auto Recovery feature may execute the configured action before the time interval when the system is under heavy stress.

    The Auto Recovery feature can be set to execute an action (For example, system reboot) to recover a hung system. Since the Auto Recovery timer is now an application-level timer instead of a kernel-level timer, heavy resource stress on the system may result in an inaccurate measurement of a short keep alive interval (less than 120 seconds), and the configured action may be triggered. The issue is more prevalent in systems that have only one CPU with hyper-threading unsupported/disabled or systems that are subjected to persistent stressful conditions such as, resource depletion and CPU running at 100% usage with significantly more threads than normal usage.

    The Auto Recovery feature is not enabled by default. If the Auto Recovery feature has been enabled, increase the System Reset Timer value to at least 120 seconds.

  • Using the Internet Explorer browser, if you install Server Administrator on a system that includes an underscore in its host name, you must use the IP address of the target system in the browser URL to launch Server Administrator, as Host names with underscores are not supported. For example, (assuming Server Administrator is listening on port 1311): https://192.168.2.3:1311.

    For more information, see the following article on the: Microsoft website http://support.microsoft.com/kb/312461

  • DF152755: The Server Administrator GUI does not respond when the alerts log has many events. If the Alert Log contains several entries and if you try to navigate to another page, the Server Administrator GUI may take about 30 seconds to display the content.
  • DF172125: Power monitoring probes are displayed on certain systems that do not support power monitoring. On certain systems that do not support power monitoring, Server Administrator reports the two platform event filters related to a power monitoring as System Power Probe Warning and System Power Probe Failure. These two filters are not supported on these systems. That is, you can view and configure these filters, but no action is taken.
  • DF185770: Primary User Telephone Number does not accept symbols. On Server Administrator, under Asset Information > System Information > Primary User Telephone Number configuration allows only alphanumeric characters.
  • The selection of default option for the front panel LCD in Server Administrator displays the Model Name whereas the default is a Service Tag on the physical LCD.
  • If Server Administrator does not respond or is locked to your selections on the component tree, perform the following steps:
    1. Click Preferences. The Preferences page appears.
    2. Click Server Administrator. The items on the front page may respond to your click.
  • DF277439: Persistence of Configuration and Log File Changes in VMware ESXi On systems running the VMware ESXi operating system, the file system is ramdisk. Modifications made to the files within the file system are generally not persistent across reboots, with the exception of designated configuration and log files. These files are updated to the disk periodically and on system shutdown. If the system is reset without a graceful shutdown before the updated to the designated configuration are made and before log files are updated to the disk, the changes are lost.

    The following is an example of the effect of this behavior:

    • On certain systems, the first time that the thresholds for a probe are changed after Server Administrator is installed; the current threshold values for that probe are saved as the default threshold values by writing the values to a configuration file. When Set to Default is performed after the first change of the thresholds, Server Administrator sets the threshold values to the values that were saved in the configuration file as the default. If the system running the VMware ESXi operating system is reset without a graceful shutdown before the changes to the configuration file are updated to the disk, the user- defined thresholds become the default thresholds.
  • DF315853: Some Server Administrator CLI commands, function properly only when run from the elevated console window. It is recommended that you use the elevated console for running the CLI.
  • Due to some limitations, you cannot log on simultaneously to multiple browser instances/tabs using SSO login, as only one session remains active while the other sessions expire.
  • DF489034: Intel TXT configuration fails due to Virtualization technology dependency.
  • If the current Virtualization Technology attribute setting is Disabled (Virtualization Technology is part of the Processor Settings group on the BIOS setup page); the Intel TXT attribute configuration fails on the Server Administrator user interface ( System > Main System Chassis > BIOS > Setup > System Security ). To resolve this issue, configure Virtualization technology setting to Enabled and reconfigure the Intel TXT attribute, if it is configurable.
  • DF549057: When an operating system is installed through USC, the BIOS attributes in Server Administrator are displayed as read-only. You can edit the BIOS attributes 18 hours after the operating system installation.

    Workaround: To enable editing of the Server Administrator BIOS attributes, launch Lifecycle Controller while booting.

  • DF552204: On Mozilla Firefox browsers (versions 10, 11 and 12), Server Administrator fails to launch if IPv6 address is used.

    This is a known issue. For more information, see https://bugzilla.mozilla.org/show_bug.cgi?id=633001.

  • BITS040169: In case of Boot/HDD/UEFI sequence, if they are read-only, then toggle buttons (+ and -) and submit button are not visible. On the BIOS setup page, dependencies may exist between the various attributes for Bios settings. Setting an attribute value may change the state of the dependent attributes to non-editable or editable. For example, changing the Boot Mode to UEFI from the Boot Settings page does not allow you to configure the Boot or Hard-Disk Drive Sequence in the BIOS Boot Settings page. When the page is non-editable, the toggle buttons on the page allows toggling the order of the boot sequence. However, settings cannot be configured since Apply button will not available to submit the settings.
  • BITS050574: On 11th generation and 12th generation of PowerEdge servers running the Linux OS, the omreport system summary command displays RAC Command Interface as 7.1.0. "RAC Command Interface" is a DRAC4 RPM and its version is 7.1. It is installed as a dependent package for iDRAC6 and iDRAC7 Command Interface packages.
  • If a new certificate imported to Server Administrator is not active after restarting the Web server, restore the previous certificate. To restore the previous certificate, do the following:
    1. Stop the Web server.
    2. Perform one of the following as applicable:
      • On systems running Windows:
        • 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:
        • For 32-bit OS
          • Delete the keystore.db file at /opt/dell/srvadmin/lib/openmanage/apache- tomcat/conf
          • Rename the keystore.db.bak at /opt/dell/srvadmin/lib/openmanage/apache- tomcat/conf to keystore.db

        • For 64-bit OS
          • 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 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.
  • JIT-25314: The alert log is not generated in Server Administrator, when the Power Supply Unit (PSU) is inserted in the server without connecting a power cable for that PSU. However, corresponding log is generated in ESM or Hardware logs.
  • JIT-22805: Server Administrator does not recommend the upgrade to major versions of JRE. For more details, see the release notes of Server Administrator (packaged with Server Administrator application) or at dell.com/openmanagemanuals.
  • JIT-31814: OpenManage Server Administrator Cannot show the SNMP test trap destination addresses, when admin configured through domain policy.
  • JIT-36610/JIT-36599: In OpenManage Server Administrator slots page, the Dell “HBA330 Adapter” PERC card will be enumerated as “12GB/s HBA internal” and Dell “HBA330 Mini” PERC card will be enumerated as “SAS3008 PCI-Express Fusion-MPT SAS-3

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\