Dell EMC OpenManage Enterprise Version 3.4 Release Notes

Others

Issue 1

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. [153980]

Resolution: When the features that use FQDN fail, it is recommended to check the interface and use the corresponding IP. For instance, if the primary network is enabled with only IPv6, and the FQDN expected to work on primary interface fails, user can use IPv6 address in the place of FQDN as a workaround. This applies for secondary interface as well.

Issue 2

Description: Creating a report with chassis table columns and device table columns using a query with an 'or' will not generate a report with expected result. [154713]

Issue 3

Description: When a Lead chassis retires and a backup chassis becomes the new lead on OpenManage Enterprise, the refresh inventory marks the original backup chassis and its associated devices to be invisible and not shown in the UI. [161300]

Resolution: Discover the new Lead on OpenManage Enterprise.

Issue 4

Description: "Virtual identity by usage report" does not display the identity state as "Used" when the virtual identities were assigned to a device from an external source. The current reports do not support the "Used" status, and instead display them as either 'Reserved' or 'Assigned'. [160507]

Issue 5

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.

Issue 6

Description: If a Configuration Inventory task finds external identities that fall in an existing identity pool and that identity pool is later deleted and a new one with the same or overlapping identities is created, the new identity pool will not show those identities as assigned. [160888]

Issue 7

Description: OpenManage Enterprise appliance does not prevent unauthorized shell access by an end user with FSD enabled. The GRUB bootloader allows root level shell access during boot. [162922]

Issue 8

Description: Complete inventory is not collected when a sled is removed and reinserted in the chassis. [165192]

Resolution: The complete inventory is updated by running sled inventory manually/scheduled.

Issue 9

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 10

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. [167259]

Resolution: Re-discover the chassis to update the appliance with the new IP details of the sleds.

Issue 11

Description: Inventory refresh fails to update the chassis name change(s) in OpenManage Enterprise. [167923]

Issue 12

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 13

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. [166435]

Issue 14

Description: For the YX3X servers, few of the Subsystem Health section details, available on the individual device's Overview page, such as the Storage, Temperature, and License details are displayed as 'No Data available,' even when their health status is 'OK.' [155425]

Issue 15

Description: The 'From' address used for all email actions, such as Reports, Update, Discovery and Alert Policies, is dependent on the SMTP server configuration. For some SMTP server configurations, the 'From' address is the Sender Email ID specified in the Application settings (Application Settings > Console Preferences > Email Sender Settings > Sender Email ID) and for others it is the username used for SMTP server authentication (Application Settings > Alerts > Email Configuration > SMTP Server Network Address). [164204]

Issue 16

Description: There is currently a discrepancy between the actual number of MIBs imported and the MIB count displayed on the Monitor > MIB page. [160040]

Issue 17

Description: When NIC teaming is enabled on MX7000 chassis along with VLAN configuration, deploying of VLAN from the OpenManage Enterprise console will overwrite the NIC teaming configurations to 'No teaming'. The LACP or other teaming options would need to be reconfigured from MX7000.

Issue 18

Description: Appliance is unable to download the console upgrade from HTTP or HTTPS intranet share, when the intranet share address is blocked in proxy filtering. [152092]

Resolution: If the upgrade download has a problem connecting through proxy, uncheck the proxy settings and then download.

Issue 19

Description: Profile creation, editing and assigning requires the Boot to network ISO password has to be re-entered. [161247]

Issue 20

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. [148789]

Issue 21

Description: The Timezone and NTP Server Address fields added to the Application Settings > Network > Time Configuration section will remain blank and will not be displayed for a few minutes if the entered NTP server IP address is not reachable. [151221]

Issue 22

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.1>3.2>3.3.1.

Issue 23

Description: Chassis health status shown in the chassis UI and the OMEnterprise console does not match. This happens because the chassis UI shows the chassis controller's health, whereas the OMEnterprise shows the overall health of the chassis. Hence, it is recommended to check the component-related health status for M1000e, FX2s and VRTX chassis. [85977]

Issue 24

Description: Emails for alert policies don't work when the same event is generated twice within 2 minutes. Email action for alerts containing the same message ID and content are triggered every 2 minutes to avoid many repeated/redundant alert messages in the inbox.[148407]

Issue 25

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 26

Description: When updating local shares for a manual upgrade for versions without any installed extensions/plugins (such as 3.1 and 3.2), the audit log displays warning entries such as 'Unable to retrieve the source file of type Extension Catalog because the file does not exist' and 'The status of downloading the Extension Catalog is Failed'. These error messages do not have any functional impact on the upgrade process and can be ignored. [144379]

Issue 27

Description: Clicking Check Update on OpenManage Enterprise version 3.2, where PowerManager extension is not installed, an error CGEN1003- Unable to complete the operation because an empty payload is not allowed for this request is displayed.

Resolution: This error can be ignored as it is for information purpose only. There is no functional impact of this error and the user can go ahead with the upgrade.

Issue 28

Description: OpenManage Enterprise could be impacted by the Linux TCP SACK vulnerability (CVE-2019-11477).

Resolution: OpenManage Enterprise includes CentOS kernel patches for the TCP SACK Panic issues and carries the updated kernel-3.10.0-957.21.3.el7.x86_64.rpm including fixes for the CVE-2019-11477 vulnerability.

Issue 29

Description: Post console update Time interval should be enabled manually in alert policy as it is disabled by default.

Issue 30

Description: Alert policies have been recategorized since OpenManage Enterprise version 3.3.1. The alert policies from appliance versions before 3.3.1 need to be recreated after the appliance upgrade.

Issue 31

Description: A query group with switch and device power state together is not working as expected. [86481]

Resolution: Exclude switch power state while creating a query group.

Issue 32

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 33

Description: The target IP address is incorrectly listed in the task history of an alert policy that is created by running a remote script. [86424]

Resolution: N/A

Issue 34

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 35

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 36

Description: When a device is turned off, the console takes a few moments to display the updated health status. [86146]

Resolution: Refresh the browser, or wait for a few moments.

Issue 37

Description: An individual Chassis Management Controller (CMC) health may not be correctly displayed in the device drill-down operation. [85977]

Resolution: Always consider the CMC rollup health status.

Issue 38

Description: Certain SNMP alerts are undefined for the S4810 networking switch. [85016]

Resolution: N/A

Issue 39

Description: An unknown Error message occasionally displayed in the SNMP alert console. [84894]

Resolution: Ignore or click Dismiss.

Issue 40

Description: In the SNMP alert console, some alerts from OMSA correctly show the Message ID field, while others show N/A. [83579]

Resolution: N/A

Issue 41

Description: Discovery of an HP server by using IPMI command may not reflect the correct rollup health status. [85153]

Resolution: View the lower-level sensor health data.

Issue 42

Description: In the Execution Details section, data must be manually sorted in the table every time after moving to a new page. [81207]

Resolution: Sort information of a single page at a time.

Issue 43

Description: Currently, the health status including PSU and temperature data is not displayed for the storage devices. [99821]

Resolution: N/A

Issue 44

Description: : The rollback feature is not supported on the MX7000 chassis. Also, the rollback operation fails on the M1000e, FX2, and FX2s chassis. [110239]

Resolution: For M1000e, FX2, and FX2s chassis, create and associate a new baseline with the necessary firmware version to roll back.

Issue 45

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. [106369]

Issue 46

Description: Invalid host names are displayed under the Source Name column and are also available for selection in some of the OpenManage Enterprise tasks. [68214]

Issue 47

Description: Authentication by one-way and two-way trusts of AD users is not supported by the appliance.

Issue 48

Description: From the All Devices page, you cannot launch the iDRAC application interface with IPv6 addresses. [102153]

Issue 49

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 50

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. [114683]

Resolution: Use the online method for updating, or use the HTTPS method. Ensure that the security certificates are signed by a trusted third-party certificate authority while using the HTTPS method of update.

Issue 51

Description: The selected target devices or device groups while creating an alert policy in OpenManage Enterprise-Tech Release are cleared when the appliance is updated. [115698]

Resolution: After updating the appliance, edit the alert policy and select the target devices or device groups to receive the group-specific alerts.

Issue 52

Description: After you update the appliance from OpenManage Enterprise-Tech Release, the Syslog server messages do not retain the standard format of <timestamp><hostname>_<Alert_Message>. The alerts are displayed as "EEMI@123_[id]":Alert_Message. [115699]

Issue 53

Description: Few alerts from the PowerEdge R240, R340, T140, T340, and R740xd2 servers are received with unknown severity in the OpenManage Enterprise appliance. [112404]

Issue 54

Description: While programmatically deploying the OpenManage Enterprise from Linux shell, if the argument provided for --name= in the command line begins with a "$" then the argument is ignored and appliance is deployed with the name OPENMANAGE ENTERPRISE. [121158]

Resolution: The --name= argument, which begins with "$" in the command line must be enclosed in single quotes, for example, --name= '$OME-VM'.

Issue 55

Description: The Severity status in the Alert log for the alerts received from the PowerVault ME4 storage arrays is being reported as Unknown by the appliance. This defect is due to the unavailability of the precanned MIBs for the PowerVault ME4 storage arrays in the appliance console. [122657]

Issue 56

Description: After the console is upgraded, there is a delay of approximately 15 minutes in the initiation of the Post Upgrade task by the appliance. [130142]

Issue 57

Description: When an already imported MIB is renamed and parsed through API the trap status is reported as 'Existing' instead of 'Imported.'[111854]

Issue 58

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 59

Description: SSH Private key can be applied while adding a remote script in the Script Execution page. [129366]

Issue 60

Description: The Schedule advanced filter in the Monitor > Discovery page incorrectly displays even those discovery jobs which have completed their initial scheduled run. [128842]

Issue 61

Description: All the AD/LDAP groups imported from the OpenManage Enterprise versions before version 3.2, such as the version 3.1 and version 3.0, should be deleted and re-imported.

Issue 62

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 63

Description: Export of large firmware compliance reports, containing more than 200,000 elements, fails and the appliance displays an Application timeout error. [133201]

Resolution: When exporting large firmware compliance reports, the following workarounds can be employed :

• Allocate more memory to the appliance while installing.
• Before exporting large reports, ensure that other jobs are not running.
• Use the Firmware Compliance per Component or the Firmware Compliance per Device Report instead of exporting.
• Use filters to derive a smaller result set before exporting.

Issue 64

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. [136816]

Issue 65

Description: The Monitor > Jobs > View Detail Execution History page incorrectly displays Could not set alert destination on the target under Messages, even for the successfully-completed jobs created for setting of trap destinations for the MX7000 chassis.

Issue 66

Description: Deleting a device from the All Devices page would fail if there are active jobs involving the device.

Resolution: Before deleting a device from the All Devices page, ensure there are no jobs in the 'running' status involving the device.