Dell EMC OpenManage Enterprise Version 3.6.2 Release Notes July 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.2 Release Notes............................................................................ 4 Release type and definition......................................................................................................................................... 4 What is supported....................................
1 Topics: • Dell EMC OpenManage Enterprise Version 3.6.2 Release Notes Dell EMC OpenManage Enterprise Version 3.6.2 Release Notes This document describes the new features, enhancements, known issues, and fixed issues in Dell EMC OpenManage Enterprise version 3.6.2 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 update on Multi-Chassis 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.
Issue 3 Description: Fixed the post upgrade issue with delay in the display of the Job Target window when Select Devices is clicked. [201904] Issue 4 Description: Fixed the post upgrade issue of not being able to create a 'child' group with the same name as the 'parent' group on the All Devices page. [201690] Issue 5 Description: Fixed the upgrade failure to version 3.6 from version 3.5 appliances in which an RPM patch was installed due to a custom web certificate issue.
Discovery and inventory Issue 1 Description: When the Administrator password is reset on any discovered chassis (MX7000, M1000e, VRTX,and FX2), there is a disconnection of the chassis with the appliance for 600 seconds. During this interval, the Health State of the chassis on the All Devices page is displayed as 'Disconnected' and the tasks initiated on the chassis and sleds fail.
Issue 14 Description: The Guest information for the discovered Hyper-V 2012 R2 servers is not available on the device's Hardware page. [159535] Issue 15 Description: The correlation of Windows Hyper-V post MX7000 chassis CCD, fails to give the Guest VM information under Device details page. [167935] Resolution: The sled discovery need to be done out of the MX7000 chassis and managed separately to view the guest details.
Issue 28 Description: In order to support discovery with domain credentials, OpenManage Enterprise 3.2 and later uses SSH instead of WSMAN. Hence, all the Windows and Hyper-V devices discovered prior to updating the appliance have to be deleted and re-discovered using their SSH credentials.
Issue 8 Description: PERC H730P controller driver is not listed in the Firmware/Driver compliance report as it is currently not included in the online firmware/driver catalog. However, as this driver is a part of the Windows' server inventory, it is listed in the Inventory report of the windows devices.
Description: The Firmware Update task fails on the MCM member chassis with error message 'Syncing data with passive MM Task Failed. Completed With Errors'. [169333] Configuration management Issue 1 Description: For the MX7000 chassis managed with OpenManage Enterprise - Modular versions 1.31.00 or earlier, the remediation task (Make Devices Compliant MX7000) fails with an error message — "error while applying Setting: Users| Directoriesnull|null Required fields are missing (UserName or Password).
Issue 13 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 14 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: On VMware vSphere, changing the appliance's time to an earlier time than the system time fails if the periodic time synchronization in the VM is enabled. [198702] Resolution: To set the appliance's time to an earlier time than the system time, disable the periodic time synchronization in the VM, by launching the vSphere Client, go to Edit Settings > VM Options > VMware Tools > Synchronize Time with Host and deselect the checkbox Synchronize time periodically.
Resolution: To prevent upgrade failure, in such rare scenarios, you can manually cancel the Discovery task to allow the post-upgrade tasks to initiate and finish normally. Issue 14 Description: An invalid audit log indicating 'console upgrade failure' is generated upon a successful upgrade of the appliance from version 3.4 to version 3.5. This audit log can be ignored.
Description: The rack physical groups with long names consisting of more than 150 characters with no spaces, the appliance wizards experiences an 'overflow'. [164157] Resolution: Limit the number of characters used to create names.
Resolution: If the upgrade download has a problem connecting through proxy, uncheck the proxy settings and then download. Issue 39 Description: Profile creation, editing and assigning requires the Boot to network ISO password has to be re-entered. [161247] Issue 40 Description: After a fresh install or an upgrade to OpenManage Enterprise and configuration of network interface to DHCP, any prior static IP settings will not be retained.
Resolution: Exclude switch power state while creating a query group. Issue 52 Description: The management IP is incorrectly indicated if the server is discovered by using both the IPv4 and IPv6 addresses. [86196] Resolution: Manually start the iDRAC Graphical User Interface (GUI). Issue 53 Description: The target IP address is incorrectly listed in the task history of an alert policy that is created by running a remote script.
Resolution: For M1000e, FX2, and FX2s chassis, create and associate a new baseline with the necessary firmware version to roll back. Issue 65 Description: Currently, the alerts are not received by OpenManage Enterprise if the alerts are associated with the devices' IP address. However, alerts are successfully received when associated with the device Service Tag.
Description: Ignore alert policy created for warranty, firmware compliance, and configuration compliance alerts will be ignored only if alerts are generated from the same device from which ignore policy was created. In other cases, alerts will be received and not ignored. [124596] Issue 79 Description: SSH Private key can be applied while adding a remote script in the Script Execution page.
Table 1. Minimum recommended hardware Minimum recommended hardware Large deployments Small deployments Number of devices that can be managed by the appliance Up to 8000 1000 RAM 32 GB 16 GB Processors 8 cores total 4 cores total Hard drive 400 GB 400 GB Minimum system requirements for deploying OpenManage Enterprise version 3.6.2 Table 2. Minimum system requirements Particulars Minimum requirements Supported hypervisors ● VMware vSphere versions: ○ vSphere ESXi 5.
● The letter X (digit) denotes the make of the processor. Table 3. PowerEdge servers naming convention and examples YX3X servers YX4X systems PowerEdge M630 PowerEdge M640 PowerEdge M830 PowerEdge R440 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.
