Dell OpenManage Server Administrator Version 11.0.1.x Release Notes

PDF

Limitations

Table 1. Limitations in OpenManage Server Administrator 11.0.1.xThe following are the limitations of OpenManage Server Administrator:
Functional Area	Limitation
User privileges	The iDRAC user privileges and attributes have changed. Therefore, you see a difference in Server Administrator and iDRAC user privileges and attributes. For more information about iDRAC user privileges and attributes, see the latest iDRAC User's Guide.
Server Administrator	On PowerEdge 13^th generation or later servers with supported iDRAC versions, you can set the Platform Event Destination as IPv4 or IPv6.
Server Administrator	If you belong to an Active Directory group that is part of another group, appropriate privileges are not granted on the Server Administrator UI. Launch Server Administrator using the desktop icon when Single Sign-On (SSO) is enabled.
Server Administrator	On Server Administrator, the following behaviors are observed for CPU that supports the High-Bandwidth Memory (HBM) interface. For more information about HBM, see iDRAC UI. Server Administrator UI does not display information about HBM. The Total of Memory Array(s) option on the Memory page displays information about regular memory and HBM. Server Administrator does not log the alerts for HBM on the Alert Log page. When you run the omreport system alertlog command, the alerts for HBM are not displayed in the CLI.
Server Administrator	When you install the firmware of the enclosure backplane, the firmware version is displayed incorrectly on the Enclosure on Controller <Controller name> page. Workaround—Wait for a maximum duration of 24 hours or restart the Data Manager service.
Server Administrator	When High-Bandwidth Memory (HBM) errors are detected in the CPU, the Server Administrator does not log the HBM alerts in the Alert Log page. The alerts are also not displayed in the CLI when you run the omreport system alertlog command.
Instrumentation Service	On PowerEdge servers, when conflicting BIOS settings exist while configuring BIOS setup options through Server Administrator, the update attempt may fail at system reboot. Also, none of the BIOS setup options may be updated. For example, the conflict prevents the BIOS configuration updates (at system reboot) when you configure the following simultaneously: Embedded SAT controller to RAID Boot Mode to UEFI. UEFI does not support the RAID option.
Instrumentation Service	On certain systems, user-defined thresholds set under Server Administrator become the default thresholds after uninstalling Server Administrator. When you change the threshold value of a probe on certain systems and then uninstall Server Administrator, the changed threshold value becomes the default threshold value.
Instrumentation Service	When you modify the warning threshold settings, the values are stored in the firmware as discrete integer values and scaled for display. If the modified value is not a discrete integer, it may change when saved.
Instrumentation Service	Fan redundancy can have the following states: Fully Redundant—The sensors display this status when all the fan-in systems are present and are in a nonfailed state. Redundancy Lost—The sensors display this status whenever any system fan fails or is removed from the chassis. If a system with memory redundancy enabled enters a Redundancy Lost state, it may not be clear which memory module caused it. If you cannot determine which DIMM to replace, see the Switch to spare memory detected log entry in the ESM system log to find the unsuccessful memory module.
Instrumentation Service	If you run Server Administrator when the system is in OS Install Mode, it may report the memory incorrectly. To avoid this issue, you must disable the OS Install Mode before running the application.
Instrumentation Service	Server Administrator does not enumerate the CMC USB ports that are attached to a Blade server.
Instrumentation Service	Except for AC power cable traps, SNMP traps for server instrumentation are not generated when the state of the device sensor changes from unknown to normal.
Instrumentation service	On systems running VMware ESXi operating systems, NIC cards using native drives display limited information about Server Administrator. Also, the TOE status of a network controller is not available. Redundancy Status is displayed as Not Applicable even when NIC cards are teamed, and NIC teaming status may not display in the Server Administrator network section. It is due to the operating system limitation and has no functional impact to the system. The Server Administrator only discovers the physical NIC and displays the IP addresses. The operating system fully controls it, and not the hypervisor. As a result, the IP address value is displayed as Unknown for virtual machines.
Instrumentation service	On certain systems that do not support power monitoring, Server Administrator reports the two platform event filters related to power monitoring as System Power Probe Warning and System Power Probe Failure. On the systems, when these filters are not supported, you can view and configure these filters, but no action can be taken.
Restart of Instrumentation Service	When the Server Administrator is installed on the VMware ESXi operating system, wait for a minimum duration of five minutes before subsequent restart of CIM services.
Installation and Management	When you restart VMware ESXi operating systems without backing up the configuration, the following behaviors are observed: The following error message is displayed when you access the Server Administrator UI: Connection time out. To resolve this error, do the following: To enable openwsman service, run the following command in the ESXi Shell: esxcli system wbem set -W true. To open openwsman service, run the following command in the ESXi Shell: /etc/init.d/wsman start. The alerts that are logged in a duration of one hour may not be displayed on the Alert Log page. Workaround—Ensure to run the /sbin/auto_backup.sh command to back up the configuration in the state.tgz file and then restart the VMware ESXi operating systems. For more information, see the VMWare.
Installation and Management	The following message is displayed in the Prerequisite checker screen: An error occurred while attempting to execute a Visual Basic Script. Confirm that Visual Basic files are installed correctly. This error occurs when the prerequisite checker uses the vbtest.vbs Visual Basic [VB] script to verify the installation environment and fails for some reason. The possible causes and its workaround are: Incorrect security settings on supported web browser Workaround: Ensure that Active Scripting is enabled. Go to Control Panel > Internet Options > Security > Custom Level > Scripting > Active Scripting and click Enable. Ensure that Scripting of Java Applets is enabled. Go to Control Panel > Internet Options > Security > Custom Level > Scripting > Scripting of Java Applets and click Enable. Windows Scripting Host (WSH) has disabled the running of VB scripts. Workaround: By default, WSH is installed during the operating system installation. WSH can be configured to prevent the execution of .VBS scripts. On the desktop, right click My Computer and click Open . Go to Tools > Folder Options > File Types. Identify files with an VBS extension and verify that the File Type is set to VBS Script File. If the file is not set as a VBS Script File, click Change and select Microsoft Windows Based Script Host as the application to run the script. The WSH version may be wrong, corrupted, or is not installed. Workaround: By default, WSH is installed during the operating system installation. The Scrrun.dll file may not be registered. Workaround: Register it manually by running the below command: regsvr32 Scrrun.dll
Installation and Management	After Unattended Installation is complete, a new console window is opened to run CLI commands. It is not possible to run the CLI commands on the same console window after the Server Administrator is installed. Workaround: Open a new console window to run the CLI commands.
Installation and Management	Tracking ID: 332601—On the Microsoft Windows Server operating system, the listener creation link on the Prerequisite Checker screen does not work. Workaround: Create the HTTPS-listener using winrm command-line utility. For more information, see Dell OpenManage Installation Guide.
Installation and Management	Server Administrator uses OpenIPMI device driver which conflicts with the Intel IMB device driver. Workaround Uninstall the IMB driver before installing Server Administrator.
Installation and Management	On a Linux operating systems with nautilus file manager—Gnome Desktop Environment—launching Server Administrator using, the desktop icon displays a window Untrusted application launcher. Workaround: The behavior is because of a vulnerability fix mentioned in CVE-2017-14604. It occurs only when the Server Administrator is launched for the first time by using the desktop icon. Click Trust and Launch to proceed with launching Server Administrator.
Installation and Management	As per PCR-732, systems with Linux operating system, RPMs, and web packs are signed with the RSA or SHA512 algorithm.
Installation and Management	On Red Hat Enterprise Linux Server operating systems, installing or removing Server Administrator SELinux policy(srvadmin-selinux), when Server Administrator services are running causes the services to restart.
Storage Management	Unable to perform the SNMP walk operation after you install Server Administrator or restart OpenManage services. Workaround—Wait for a minimum duration of five minutes after you install Server Administrator or restart OpenManage services to perform SNMP walk operation.
Storage Management	In servers where either BOSS-S1 or BOSS-S2 controllers are attached, the VDR58, PDR57, PDR64, and PDR51 alert messages contain NULL. NULL can be a block number, part number, physical disk ID, virtual disk ID, or controller ID for respective alerts. For traditional alerts 2282, 2307, and 2350, the alert messages contain %1 or %2.
Storage Management	On systems running VMware ESXi operating systems, the Device Name for all virtual disks are displayed as Not Available.
Storage Management	In the alert message, if the controller name is not displayed, check the controller information page for mapping the controller ID and controller name.
Storage Management	Part Number, Serial Number, Product ID, Vendor ID, Firmware Revision, Sub-vendor ID, and Model Number values may not enumerate for drives in a Failed state.
Storage Management	The polling interval is set to five minutes to determine the changes that are made on an enclosure that is connected to HBA 11 and later. It takes approximately six minutes to generate an enclosure event report and update its properties. However, an event is not recorded when the following is done: When a change is made to the enclosure environment status. Reverted to the previous status within predefined five minutes. For example, if a fan is removed but installed back within five minutes, and then an event is not recorded for this purpose.
Storage Management	When storage enclosures are heavily populated, Storage Management responds slowly.
Storage Management	When the System Lockdown Mode is enabled in the iDRAC UI, the configuration task updates are displayed within a minimum duration of one hour in the following: Storage Management UI CLI The configuration task updates may be displayed more than the expected time based on the system performance. Restart the Server Administrator service to view the configuration task updates immediately.
Storage Management	Storage Management does not support software RAID controllers on PowerEdge R7625, R7615, R6625, and R6615 servers. Install the OpenManage Server Administrator 11.0.0.1 patch to support the PERC S160 software RAID controller on PowerEdge R7625, R7615, R6625, and R6615 servers.
Storage Management	When Self-Encrypting Drive (SED) is attached to BOSS-N1 controllers, then the state of the unconfigured physical disk is displayed as Unknown on the Physical Devices on BOSS-N1 page. Workaround—To view the state of the physical disks, do the following: Log in to the iDRAC UI using your login credentials. On the iDRAC UI, click Storage > Physical Disks. The Physical Disks page is displayed. Also, when the SED attached to the BOSS-N1 controller is in Ready state, then the severity state of the physical disk is displayed as Unknown on the Health page. Workaround—Not available.