Dell EMC OpenManage Enterprise Version 3.5 Release Notes October 2020 Rev.
Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your product. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. © 2017 - 2020 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries.
Contents Chapter 1: .................................................................................................................................... 4 Dell EMC OpenManage Enterprise Version 3.5 Release Notes................................................................................4 Release type and definition......................................................................................................................................... 4 What is supported...................................
1 Topics: • Dell EMC OpenManage Enterprise Version 3.5 Release Notes Dell EMC OpenManage Enterprise Version 3.5 Release Notes This document describes the new features, enhancements, known issues, and fixed issues in Dell EMC OpenManage Enterprise version 3.5. Release type and definition Dell EMC OpenManage Enterprise OpenManage Enterprise is a systems management and monitoring web application delivered as a virtual appliance.
New in this release ● ● ● ● Support for new plugins — SupportAssist Enterprise version 1.0 and Update Manager Plugin version 1.0. Support for PowerEdge XE7420 and PowerEdge XE7440 sleds. Discovery supports IPv6 ranges. OME appliance upgrade feature — success or failure of upgrade to OME 3.5+ is indicated by a banner. If the upgrade fails, the appliance state prior to upgrade is restored. ● Support for appliance login using OpenID Connect providers Keycloak and PingFederate.
Issue 3 Description: For the discovered HP servers, the devices' Hardware Logs are not displayed as the third party library used by the appliance is unable to extract the hardware logs for HP iLO servers. [170550] Issue 4 Description: For the discovered HP servers, the 'Power Supply' details are not displayed under the subsystem health section on the device's Overview page. This detail is missing as the third party API that is used to gather sensor health details, doesn't provide the 'Power Supply' data.
Resolution: To immediately update the sled inventory, trigger the refresh inventory of the sled manually. Otherwise, the sled inventory will be refreshed during the automatic daily inventory collection. Issue 17 Description: All the existing firmware compliance tasks will refresh automatically post device discovery. [146981] Issue 18 Description: The management IP on the Device Details page of the discovered VxRail devices does not match the management IP displayed on the All Devices page.
Firmware and driver updates Issue 1 Description: In-band driver updates are only supported on Windows with OpenSSH. Driver updates on third party SSH hosted on Windows, such as the CygwinSSH, are not supported. [157887] Issue 2 Description: For the family of network adapter drivers, the operating system installed version, as seen in the Device Manager, differs from the version available in the online catalog.
Issue 12 Description: A job for firmware rollback on the PowerEdge MX7000 sleds, though allowed in the appliance, would fail. This happens because the firmware rollback is not supported on the MX series sleds discovered as part of MX7000 chassis discovery or in proxied state. [136820] Issue 13 Description: When updating MX7000 chassis in the MCM mode, always make sure that the lead chassis is updated as the final step after updating all the member chassis.
Description: If a chassis template is deployed with a new static IP address on the FX2, VRTX, and M1000e chassis, then these devices need to be re-discovered with the new IP for managing the device. Issue 12 Description: The deployment task of an MX7000 chassis fails if proxy authentication is enabled in the configuration template with error: 'Unable to complete the request because the input value for Password is missing or an invalid value is entered'.
Description: The built-in Virtual Disk report contains duplicate or empty values if the virtual disks and physical disks don't have any associations and are used individually. This issue is not observed if the VDs an PDs are being used together. [174851] Resolution: It is recommended to use a custom report to get only the virtual disk data if the VDs and PDs are not associated.
Resolution: The complete inventory is updated by running sled inventory manually/scheduled. Issue 17 Description: If a pending scheduled deployment task for a profile is deleted, any identities that were reserved to the profile are freed back to pool. [167265] Issue 18 Description: For sleds that are discovered as part of the MX discovery and are in a fully managed mode, any static IP changes on the sleds through the proxy mode (chassis), are not updated in the OpenManage Enterprise console.
Description: Addition of a new network interface in hypervisors fails immediately after upgrading the OpenManage Enterprise from version 1.0 to version 3.3.1 (1.0>3.0>3.1>3.2>3.3.1). An error message "Failed to reconfigure virtual machine Config-7 1.0 to 3.3.1. The attempted operation cannot be performed in the current state (Powered on)" is displayed. [146752] Resolution: Power off the virtual machine, add a new network interface, and then power on the virtual machine if the upgrade workflow is 1.0>3.0>3.
Description: Not all scheduled jobs are displayed in the Recent Tasks list. [86488] Resolution: Go to the Jobs page to view the latest and complete list of jobs. Issue 43 Description: Discovery operation fails by using IPMI commands on the CISCO server if a KG key is used. [78545] Resolution: KG key is not supported for this device discovery. Issue 44 Description: When a device is turned off, the console takes a few moments to display the updated health status.
Description: From the All Devices page, you cannot launch the iDRAC application interface with IPv6 addresses. [102153] Issue 57 Description: When PCIe cards are mapped to the FX2/FX2s chassis, migration of identities is not supported on the sleds in the same FX2s chassis since the FQDDs differ. Issue 58 Description: Console Upgrade from 3.0 through NFS Share fails. Also, console Upgrade through HTTPS (internal Share) fails when upgrading from versions 3.0 and 3.1.
Issue 70 Description: The .CSV files, that record the deleted alerts from the Alert log, fail to capture the Device Name and the Device IP details of the alerts received from the undiscovered devices.[132915] Issue 71 Description: Export of large firmware compliance reports, containing more than 200,000 elements, fails and the appliance displays an Application timeout error.
Minimum system requirements for deploying OpenManage Enterprise version 3.5 Table 2. Minimum system requirements Particulars Minimum requirements Supported hypervisors ● VMware vSphere versions: ○ vSphere ESXi 5.5 Onwards ● Microsoft Hyper-V supported on: ○ Windows Server 2012 R2 Onwards ● KVM supported on: ○ Red Hat Enterprise Linux 6.5 Onwards Network Available virtual NIC which has access to the management networks of all the devices which is managed from OpenManage Enterprise.
Table 3. PowerEdge servers naming convention and examples (continued) YX3X servers YX4X systems PowerEdge T130 PowerEdge R540 Contacting Dell NOTE: If you do not have an active internet connection, you can find contact information on your purchase invoice, packing slip, bill, or Dell product catalog. Dell provides several online and telephone-based support and service options. Availability varies by country and product, and some services may not be available in your area.
