Dell EMC OpenManage Enterprise Version 3.6 Release Notes June 2021 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 - 2021 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.6 Release Notes................................................................................4 Release type and definition......................................................................................................................................... 4 What is supported...................................
1 Topics: • Dell EMC OpenManage Enterprise Version 3.6 Release Notes Dell EMC OpenManage Enterprise Version 3.6 Release Notes This document describes the new features, enhancements, known issues, and fixed issues in Dell EMC OpenManage Enterprise version 3.6. 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 ● Scope-based access control (SBAC) now allows a more efficient and secure management of the discovered devices. Administrators can now determine the device groups that the device managers are expected to manage. ● Seamless firmware updation on Multichassis Management (MCM) chassis with support for up to 20 chassis and their sleds. ● Ability to scan and expand appliance disk size on the Text User Interface (TUI) page.
Description: Post upgrade of OpenManage Enterprise to version 3.6, the alert policies from the previous appliance versions such as version 3.4 and version 3.5 are only assigned to the administrator users. Hence, the alert policies created by device managers prior to the upgrade would need to be recreated. [194142] Issue 3 Description: Post upgrade of OpenManage Enterprise to version 3.
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.
Issue 21 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. [91653] Issue 22 Description: If the onboarding state of the lead chassis and member chassis in an MCM group is in monitored state, the inventory task might fail if the MCM group is configured with more than 10 chassis.
Description: For the discovered network switches with firmware version 10.5, the firmware version is displayed as 'NA' on the Device Overview page. [192087] Issue 2 Description: Inventory collection and the firmware update on chassis storage sleds is not supported in OpenManage Enterprise if they are managed via chassis device management.
Description: The firmware update task using the HTTP and HTTPS local shares fails, if these local shares were configured using proxy settings and are not listed in the proxy exception list. [151332] Resolution: The HTTP and HTTPS local shares which are configured using the proxy settings, need to be listed in the proxy exception list before initiating any firmware update tasks using these shares. Issue 14 Description: Firmware upgrade fails when iDRAC firmware versions older than 2.40.40.
Description: Editing a Configuration template that is associated to a baseline which is either linked to a group of devices or a large number of devices (20 or more) might cause a timeout with error message ' An application request timed out. Please contact your support representative if the issue persists'. The changes however are saved to the template in spite of the timeout.
Description: Creation of a chassis template from a reference M1000e chassis which has Firmware versions 6.10 or later fails if SMBv1 is disabled in the appliance. [129049] Resolution: Enable SMBv1 in the appliance using Application Settings > Console preferences > SMB settings to create chassis templates from M1000e chassis with firmware versions 6.10 or later.
Description: For the discovered C9010 network switches, the Model field on the 'All Devices' and the 'Device Details' page is displayed as 'Unknown.' [188383] Issue 10 Description: When a C9010 network switch is rebooted or reloaded, the alerts received in the appliance are being categorized as Miscellaneous with message 'Unknown trap received with enterprise OID...
Resolution: To get the PDF export of the Warranty page without the illegible characters, use the following workaround: 1. Export CSV report in Excel. 2. Change the encoding type to UTF-8. 3. Save it as PDF. Issue 22 Description: When the appliance is configured to IPv6, it is unable to reach the targets like SMTP, syslog servers and share through FQDNs which is resolvable to both IPv4 and IPv6.
Description: Creation of templates using an MX7000 chassis that is configured to both IPv4 and IPv6 fails if the appliance is configured to use only IPv6. [167525] Resolution: Ensure that both the appliance and the MX7000 chassis are configured to use the same protocol(s). Issue 35 Description: The OpenManage Enterprise alert policies in de-branded MX7000 chassis are not deleted automatically when the chassis is off-boarded and the chassis data is purged in the appliance.
Issue 47 Description: While creating a customized device discovery job protocol for SNMP devices, the displayed default settings of 3 in the Retries box and 3 seconds in the Timeout box can be overlooked and should be customized as desired. [147416] Issue 48 Description: When updating local shares for a manual upgrade for versions without any installed plugins (such as 3.1 and 3.
Issue 60 Description: Certain SNMP alerts are undefined for the S4810 networking switch. [85016] Resolution: N/A Issue 61 Description: An unknown Error message occasionally displayed in the SNMP alert console. [84894] Resolution: Ignore or click Dismiss. Issue 62 Description: In the SNMP alert console, some alerts from OMSA correctly show the Message ID field, while others show N/A.
Resolution: After updating the appliance, edit the alert policy and select the target devices or device groups to receive the group-specific alerts. Issue 74 Description: After you update the appliance from OpenManage Enterprise-Tech Release, the Syslog server messages do not retain the standard format of _. The alerts are displayed as "EEMI@123_[id]":Alert_Message.
Description: A "Connection to server failed" error is displayed by the failed Power Action Tasks. Power Action tasks fail when they encounter servers where no power state change is required. This error message, though misleading, does not mean that the appliance is unable to establish contact with the server.
Table 2. Minimum system requirements (continued) Particulars Minimum requirements Network Available virtual NIC which has access to the management networks of all the devices which is managed from OpenManage Enterprise. Supported browsers ● ● ● ● User interface HTML 5, JS based Internet Explorer (64-bit) 11 and later Mozilla Firefox 52 and later Google Chrome 58 and later Microsoft Edge version 41.
2. Select your support category. 3. Verify your country or region in the Choose a Country/Region drop-down list at the bottom of page. 4. Select the appropriate service or support link based on your need.
