DELL EMC OpenManage Enterprise 4.0 Release

OpenManage Enterprise 4.0 Release Notes
Describes the new features, resolved issues, known issues, limitations and installation requirements for this major version of OpenManage Enterprise, and all released minor versions to date.

Release Type: Major (MA)
Topics:

• Revision history
• Product description
• New features
• Resolved issues
• Known Issues
• Limitations
• Environment and system requirements
• Installation and upgrade considerations
• Where to get help

Revision history
Table 1. Document revision history

• Revision Date Description
• A00 October 2023 Initial release

Product description

OpenManage Enterprise is a systems management and monitoring web application delivered as a virtual appliance. It provides a comprehensive view of the Dell servers, chassis, storage, and network switches on the enterprise network. OpenManage Enterprise’s system management and monitoring is best suited for enterprise LANs and is not recommended for usage over WANs. For information about supported browsers, see the OpenManage Enterprise Support Matrix available on the support site.

With OpenManage Enterprise, a web-based one‑to‑many systems management application, users can:

• Discover devices in a data center environment.
• View hardware inventory and monitor health of devices.
• View and manage alerts received by the appliance and configure alert policies.
• Monitor firmware/driver versions and Manage firmware/driver updates on devices with firmware baselines.
• Manage remote tasks (such as power control) on devices.
• Manage configuration settings across devices using deployment templates.
• Manage virtual identity settings across devices using intelligent identity pools.
• Detect and remediate configuration deviations across devices using configuration baselines.
• Retrieve and monitor warranty information for devices.
• Group devices into static or dynamic groups.
• Create and manage OpenManage Enterprise users. Some of the security features of OpenManage Enterprise are:
• Role-based access that limits access to console settings and device actions.
• Scope-based access control allows administrators to restrict the device groups that device managers can access and manage.
• Hardened appliance with Security-Enhanced Linux (SELinux) and an internal firewall.
• Encryption of sensitive data in an internal database.
• Use of encrypted communication outside the appliance (HTTPs).
• Create and enforce firmware and configuration-related policies.
• Provision for configuring and updating the bare-metal servers.

New features

The new features introduced in this major version of OpenManage Enterprise.

Table 2. New features in OpenManage Enterprise 4.0

Stream backup data seamlessly from a source appliance to a target appliance.

●    This feature only supports migrations from OpenManage Enterprise 3.10.x to OpenManage Enterprise. 4.0.

Initial onboarding| Default plug-in (CloudIQ and Service Plug-ins) installation.| ●    Services and CloudIQ plug-ins are automatically installed when you download and install OpenManage Enterprise.

●    You can also defer default plug-in installation during appliance setup and install them later.

Device management| ●    With the ‘Internal iDRAC credential management’ option, OpenManage Enterprise can now create a set of encrypted credentials (service account) to access iDRAC, along with an option to rotate them automatically at regular intervals.

●    With the CyberArk Integration option, OpenManage Enterprise provides support for customers who use the CyberArk identity security platform. OpenManage Enterprise can now access iDRAC passwords from the CyberArk vault.

| The iDRAC Password Management feature allows supported iDRACs to be managed by password management solutions either internally (if enabled) or externally using CyberArk integration to perform various device management operations.
Appliance communication| Redfish support.| Redfish protocol support for onboarding, offboarding, template, and profile management.
Security enhancements| Removed support for SMB1.| SMB1 is no longer supported on built-in appliance shares:

●    SMB1 support is removed.

●    Only SMB2 is supported for CIFS, enhancing security for the appliance share.

TLS1.3 and cipher suite support.| Enhanced security with TLS1.3 and cipher suite support.
Secure boot.| Pre-boot environment is now protected by ensuring that only trusted software is allowed to run during appliance startup.
RSA SecurID configuration for local multifactor authentication.| Administrators can select which appliance users, including other administrators, require multifactor authentication to log in to the appliance.

Table 2. New features in OpenManage Enterprise 4.0 (continued)

OpenManage Enterprise is now based on common operating system SLES 15 SP4.

Resolved issues
The resolved issues in this major version of OpenManage Enterprise, and all released minor versions to date.

Table 3. Resolved issues in OpenManage Enterprise 4.0

response

of the InventoryDetails(deviceLicense) API: /api/DeviceService/Devices(Id)/ InventoryDetails(deviceLicense).

245496| User Management| Deleting a Directory user type (i.e., a directory group), deletes users in the group that have created system objects but not users that have not created system objects.
246672| Alert Management| After a user with administrator privileges that creates alert policies that trigger remote scripts is deleted, triggering the user’s alert policies will cause remote script execution to fail.
249716| Backup and Restore| If an alert policy with All Categories and All Devices is configured to forward SNMP events or generate emails, internal alerts will be forwarded and/or generate emails even when the appliance is in maintenance state.
251941| Backup and Restore| When an appliance is in maintenance state, all open user sessions are not automatically removed from the Application Settings

Users > Users > User Sessions screen.
250093| Backup and Restore| When the network share location is not accessible or the user has entered the wrong credentials, the backup can fail with an unclear error message.
251950| Configuration Management| When importing a configuration compliance template with the same name as an existing template, an unknown error is displayed and the reason for the error is unclear.
256776| Reports| If a report and firmware baseline are created with the same name, the baseline will show as failed and the report will not show any data.
251191| Inventory| When a chassis has two controllers in shared mode (PERC 8 and 9), and a virtual disk is created on any one of the controllers, in the Devices > Hardware > Storage Controller screen the virtual disk information is displayed under both controllers.
250738| Firmware/Driver Management| After restoring an appliance, Windows OS driver updates from an NFS share may fail in IPv6 environments.
239379| User Console| When a UPS is discovered via IPv6, clicking the IP in the device screen header does not load the remote console.
228360| Discovery| Switches discovered via network device discovery using SNMP may no longer be listed in the All Devices screen when discovering the same switches using chassis discovery with Discover IO modules with chassis enabled.
246824| Firmware/Driver Management| When targeting SAS drive updates against Chassis Management Controller 3.41 only a single disk is updated.
258993| CloudIQ Plugin| Changes made to group names while Secure Remote Services (SRS) are down do not reflect on the portal when restored.
260337| CloudIQ Plugin| Firmware update tasks that require a reboot incorrectly show as completed on the appliance when they have failed on iDRAC.
261080| Diagnostics| Remote diagnostics jobs initiated from the appliance goes into Scheduled or Failed state on target iDRAC servers.
260084| Discovery| NGM chassis discovered by AD users with Compute Manager, Fabric Manager, Storage Manager and Viewer roles are listed as Managed instead of Monitored.

Table 3. Resolved issues in OpenManage Enterprise 4.0 (continued)

console upgrade.
260065| Plugin Management| Installing certain third party plugins triggers an error: Couldn’t complete request because of following error CGEN6038 – Unable to complete the action because the value entered for id is invalid.
263138| Plugin Management| Plugin uninstallation fails when the plugin is in Registered state with the message Error occured while initiating a task to perform the required action.
260457| Upgrade| The Notify Me option is deselected automatically during console upgrades.
267936| Firmware/Driver Management| The Reboot option is enabled when a firmware update is performed with multiple advanced filters.

Known Issues

Table 4. Known Issues for OpenManage Enterprise 4.0

having firmware version 1.40.00 are received in the Alert Log page with message ‘Unknown trap received’.| Alerts are classified properly after version

1.40.00 MIB is uploaded.

190690| Alert Management| If SNMPv3 destination(s) is/are already added as alert forwarding destination(s) in the appliance, then in order to add and apply a new alert forwarding destination address, the appliance prompts only the first time to reenter of all the previously entered SNMPv3 Authentication and Privacy passphrases before proceeding.| Regardless of the appliance prompt, you must reenter all the previously entered SNMPv3 Authentication and Privacy passphrases every time the SNMP community string or port is edited on Application Settings > Alerts > SNMP Alert Forwarding Configuration.
164204| Alert Management| The ‘From’ address used for all email actions, such as Reports, Update, Discovery and Alert Policies, depends 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 that is used for SMTP server authentication (Application

Settings > Alerts > Email Configuration > SMTP Server Network Address).

| N/A
160040| Alert Management| There is a discrepancy between the actual number of MIBs imported and the MIB count that is displayed on the Monitor > MIB page.| N/A
148407| Alert Management| Emails for alert policies do not 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.| N/A
132915| Alert Management| The CSV files that record deleted alerts from the Alert log fail to capture the Device Name and the Device IP details of the alerts that are received from the undiscovered devices.| N/A
Issue ID| Functional Area| Description| Workaround/Resolution
---|---|---|---
124596| Alert Management| Ignore alert policy created for warranty, firmware compliance, and configuration compliance alerts are ignored only if alerts are generated from

the same device from which ignore policy was created. In other cases, alerts are received and not ignored.

| N/A
122657| Alert Management| The Severity status in the Alert log for the

alerts that are 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.

| N/A
111854| Alert Management| When an already imported MIB is renamed and parsed through API the trap status is reported as ‘Existing’ instead of ‘Imported’.| N/A
249177| Alert Management| MX sled removal alert triggers associated device to be deleted from the appliance which causes any associate profile and IO identities to also be removed.| Prior to any sled removal, set up an alert policy to ignore message ID CDEV6134 and CDEV6133.
121158| Appliance Deployment| While programmatically deploying the OpenManage Enterprise from Linux shell, if the argument provided for –name= in the command line begins with a “$” and then the argument is ignored, and appliance is deployed with the name OPENMANAGE ENTERPRISE.| The –name= argument, which begins with “$” in the command line must be enclosed in single quotes, for example, –name= ‘$OME-VM’.
218979| Appliance Deployment| Templates that are created from a reference device may contain a discovery password. When deployed on target devices, this can cause communication failure.| There are two ways to overcome this issue:

●    After deployment, rediscover the device with the new credentials.

●    Export the SCP from reference the iDRAC without password hash values and import it to OpenManage Enterprise. Optionally, set the password value by editing the attributes and deploying it.

192976| Appliance Setting| Post addition of the disk space using the Configure Appliance Disk Size feature in the Text User Interface (TUI) , deletion or reduction of the appliance’s console expanded disk space is not supported.| To remove a newly added disk or to reverse the increase in size of an existing disk, you must revert to prior VM snapshot that you are recommended to take as a backup before applying any disk configuration changes.
151221| Appliance Setting| 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.

| N/A
198702| Appliance Settings| Manually setting the time to an earlier time on the VMware vSphere fails if periodic time

synchronization is enabled in the VM. 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.

| 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.
254840| Appliance Upgrade| When updating OpenManage Enterprise to version 3.10 or later from an offline share, update fails if you don’t have OpenManage Enterprise| Ensure you have OpenManage Enterprise version 3.9.2 update files in your network share
Issue ID| Functional Area| Description| Workaround/Resolution
---|---|---|---
 |  | version 3.9.2 update files in the share before update.| before updating OpenManage Enterprise to version 3.10 or later using the offline method.
253760| Appliance Upgrade| When multiple metric collecting plugins are installed before updating OpenManage Enterprise to version 3.10 or later, the update may fail, the plugins may not be available in the Plugins menu, or the interface may get stuck in the Services starting up state.| Update OpenManage Enterprise to version

3.9.2 before updating to version 3.10.

220679| Appliance Upgrade| Upgrade of a ‘scaled’ appliance may fail due to insufficient provisioning of hard drive space that is required for the data backup from large number of devices and additional plugins.| If the storage utilization in the Resource Utilization home screen widget is more than 33%, it is recommended to add twice the size of current hard disk size using the Configure Appliance Disk Size option in the Text

User Interface (TUI). For example, consider expanding the available HD space to 300 GB if the initial allocation is 100 GB.

209000| Appliance Upgrade| Upgrade of the appliance may fail if initiated post deletion of devices. If an upgrade of the appliance is initiated post deletion of devices, the Off-boarding tasks may fail, or run endlessly resulting in upgrade failure and a console reboot with the previous working state of the appliance.| Restart the services from the Text User Interface (TUI) page.
208040| Appliance Upgrade| When upgrading an appliance that is supporting 8,000 devices to v3.8, the Console Update Execution job’s status may be displayed as ‘Failed’ on the Jobs page. When upgrading an appliance that is supporting 8,000 devices to v3.8, the Console Update Execution job’s status may be displayed as ‘Failed’ on the Jobs page. This Failed status of the Console Update Execution task is seen if the appliance upgrade takes more than 60 minutes. The ‘Failed’ status is due to a time out

of the Console Update Execution job and can be ignored as this has no functional impact on the upgrade process.

| N/A
200458| Appliance Upgrade| Post deletion of 8K devices, Onboarding task does not trigger during next discovery cycle. Post deletion of 8,000 devices from the appliance, the automatic onboarding task fails during the next discovery cycle.| Restart the services from the Text User Interface (TUI) page.
173206| Appliance Upgrade| The Text User Interface (TUI) screen is not displayed until the ‘Enter’ key is pressed after updating the appliance to version 3.4.1 on ESXi with large deployments involving 8,000 or more devices.| N/A
170688| Appliance Upgrade| The Console Update Execution job’s status is displayed as ‘Failed’ on the Jobs page, if the appliance upgrade takes more than 60 minutes. The ‘Failed’ status is due to a time out of the Console Update Execution job and can be ignored as this has no functional impact on the upgrade process.| N/A
146752| Appliance Upgrade| Addition of a new network interface in hypervisors fails immediately after upgrading the OpenManage Enterprise from version 1.0| N/A
Issue ID| Functional Area| Description| Workaround/Resolution
---|---|---|---
 |  | 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.

|
144379| Appliance Upgrade| When updating local shares for a manual upgrade for versions without any installed plugins (such as 3.1 and 3.2), the audit log displays warning entries such as ‘Unable to retrieve the source

file of type Plugin Catalog because the file does not exist’, and ‘The status of downloading the Plugin Catalog is Failed’. These error messages do not have any functional impact on the upgrade process and can be ignored.

| N/A
114683| Appliance Upgrade| 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.| 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.
278556| Appliance Upgrade| When you uninstall a OMEVV plug-in from a migrated appliance, it triggers a reboot operation. However, the appliance may fail to reboot, as both the Monitor Service and Database Service may become inactive.| Perform another reboot on the appliance from the ESXi to make the appliance functional.
173311| Audit Log| 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.| N/A
253921| Backup and Restore| In rare cases, the first time a backup, restore or migrate is initiated, the message Error

while getting the appliance state is displayed.

| Ignore this message.
Not available| Backup and Restore| If the Share Type is NFS and the Destination Path contains letters in any language other than English, the backup or restore process fails.| Only use English letters in the destination path when using NFS.
219404| Chassis Grouping| License details and capability for telemetry are unavailable for member chassis.| N/A
132601| Configuration Deployment| Unable to set Target iSCSI IQN on BIOS-iSCSI via reference server template deployment, as it fails with Invalid AttributeValue error. The default iSCSI Target IQN format of the iSCSI controllers of devices such as PowerVault ME4012 array and EqualLogic PS array, is not accepted as a valid IQN format for deployment with IDRAC version 3.34.34.34.| Select ‘BIOS’ attributes only for deployment.
113576| Configuration Deployment| If the IP configuration of a discovered device is changed during template deployment (from DHCP to Static or vice versa), the Boot to Network ISO operation fails. This happens as the appliance is unable to ping the target post template deployment.| N/A
Issue ID| Functional Area| Description| Workaround/Resolution
---|---|---|---
108779| Configuration Deployment| 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’.

| N/A
Not available| Configuration Deployment| If a chassis template is deployed with a new static IP address on the FX2, and VRTX chassis, and then these devices need to be rediscovered with the new IP for managing the device.| N/A
Not available| Configuration Deployment| The directory service details in an MX7000 chassis are overwritten after the device configuration template is deployed.| N/A
Not available| Configuration Deployment| After a chassis is removed from the MCM

group, you must rediscover the lead, and member chassis to create and deploy a configuration template.

| N/A
Not available| Configuration Deployment| Template Deployment with iDRAC Management IP option “Set as DHCP” fails, and the task has to be tracked from iDRAC for final status.| N/A
253324| Configuration Deployment| Deploying templates that modify the static management IP can cause the All Devices screen to list two management URLs for the iDRAC: the original IP and the IP deployed by the template.| Use the newly configured IP to access the iDRAC virtual console.
273437| Configuration Deployment| Template deployment fails for RAID Initialization Operation (RAIDinitOperation) if performed on a non RAID server.| Click Edit > Next > RAID > Virtual Disk

and change the default value of Initialization Operation from FAST to NONE or unselect the Initialization Operation when the target server doesn’t have RAID.

175692| Configuration Management| Profile redeployment on FX2, and VRTX chassis with edited VLAN configuration (tagged and untagged values), clears only those VLAN values which were set during the initial deployment of the profile. The other VLAN values on the ports that were not set during the initial deployment of the profile are not cleared during redeployment.| N/A
174576| Configuration Management| If only VLANs are assigned to a target device during profile deployment, and then these VLANs are not reclaimed from the device when the profile is migrated to a new device. This behavior is not seen if other identities were assigned along with VLAN definitions during the profile deployment.| N/A
174360| Configuration Management| If only VLANs are assigned to a target device during profile deployment, and then these VLANs are not reclaimed by the appliance when the profile is unassigned from the device. This behavior is not seen if other identities were assigned along with VLAN definitions during the profile deployment.| N/A
160888| Configuration Management| 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

| N/A
Issue ID| Functional Area| Description| Workaround/Resolution
---|---|---|---
 |  | created, the new identity pool will not show those identities as assigned.|
255669| Configuration Management| When profile migration fails, the MAC Address State for all associated identities is displayed as Assigned, and the Management IP is shown as the target IP.| ●    Ensure that the source and target devices are accessible and then retry migrate profile.

●    Unassign the profiles by clicking Configuration > Profiles > Unassign > Force Reclaim Identities > Finish to associate the identities back to profile and to deploy to other devices.

105156| Configuration Management| The changed VLAN name and IDs are not updated on the target MX7000 chassis after a stateless deployment task is run.| N/A
98511| Configuration Management| The Reclaim Identities and Profile Migration features are not supported for Emulex OneConnect Cards.| N/A
116913| Device Grouping| Servers that are reconfigured as VxRAIL do not automatically group under HCI upon refreshing the inventory.| After a server is reconfigured as a VxRAIL, rediscover the device in the Discovery page. After rediscovery, the device is correctly grouped under HCI.
86481| Device Grouping| A query group with switch and device power state together is not working as expected.| Exclude switch power state while creating a query group.
212646| Device Management| For the servers discovered using read-only user credentials, the Launch Virtual Console button on the device’s Overview page remains enabled. Clicking the button displays an error- ‘Error launching Virtual Console: An unknown error has occurred. Try again’.| N/A
198434| Device Management| Chassis Health State shows as disconnected for 10 minutes after the chassis administrator password is reset. When the Administrator password is reset on any discovered chassis (MX7000, 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 that are initiated on the chassis and sleds fail.

| N/A
173061| Device Management| The IPMI CLI command -I lanplus shell does not end automatically and the jobs that are associated with such tasks would appear as ‘In Progress’ for a prolonged time on the Jobs page.| N/A
170550| Device Management| Unable to retrieve hardware logs for HPE servers. For the discovered HP servers, the devices’ Hardware Logs are not displayed as the third- party library that is used by the appliance is unable to extract the hardware logs for HP iLO servers.| N/A
102887| Device Management| If the IP setting is not configured on the discovered PowerEdge MX740C and PowerEdge MX840C, the Boot to Network ISO operation is not run during the template deployment.| N/A
Issue ID| Functional Area| Description| Workaround/Resolution
---|---|---|---
91653| Device Management| Mismatch in device management IP for VxRail devices on Device Details and All Devices pages. 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.| N/A
Not available| Device Management| The iDRAC virtual console management launch point is unavailable in the All Devices page for sleds with a ‘Proxied’ onboarding state.| N/A
99821| Device Monitoring| The health status including PSU and temperature data is not displayed for the storage devices.| N/A
198421| Device Monitoring| Connection State of ESXi servers that are disconnected due to authentication failure are shown as ‘Disconnected’. For the

authentication-related disconnected ESXi servers, the Connection State on the All Devices

page is displayed as ‘Disconnected’ instead of ‘Disconnected (Authentication failure)’.

| N/A
192087| Device Monitoring| For the discovered network switches with firmware version 10.5, the firmware version is displayed as ‘NA’ on the Device Overview page.| N/A
181229| Device Monitoring| MAC address not displayed for the discovered Windows servers. For the discovered Windows servers using Open SSH, the MAC address is not displayed on the device’s Hardware > Device Management Info page.| N/A
180572| Device Monitoring| Duplicate entries displayed for third-party devices when discovered using multiple protocols. For third-party devices such as the HPE Proliant servers, you might see duplicate entries if they are discovered using multiple protocols. This duplication can be corrected by deleting the entries and rediscovering the device(s) using only the IPMI protocol.| N/A
171103| Device Monitoring| For Ubuntu devices, the OS Version under operating system information (from iDRAC/ISM) on the Device Overview page is not displayed.| N/A
159535| Device Monitoring| The Guest information for the discovered Hyper- V 2012 R2 servers is not available on the device’s Hardware page.| N/A
157824| Device Monitoring| 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.| N/A
155425| Device Monitoring| For the 13G 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’.| N/A
153611| Device Monitoring| Description: Configuration > VLANs page does not update automatically after importing VLAN definitions from file or from chassis.| Refresh the Configuration > VLANs page or navigate to another page and return to view the newly imported VLAN definitions.
Issue ID| Functional Area| Description| Workaround/Resolution
---|---|---|---
152154| Device Monitoring| The Managed State of the previously ‘Monitored’ MX7000 chassis and sleds, on the All Devices page, is incorrectly displayed as ‘Managed’ post their rediscovery using the same lower privilege local or AD/LDAP credentials (Viewer or Device Manager) as before.| N/A
99821| Device Monitoring| The health status including PSU and temperature data is not displayed for the storage devices.| N/A
85977| Device Monitoring| An individual Chassis Management Controller (CMC) health may not be correctly displayed in the device drill-down operation.| Always consider the CMC rollup health status.
85977| Device Monitoring| Chassis health status that is shown in the chassis UI and the OpenManage Enterprise. console does not match. This happens because the chassis UI shows the chassis controller’s health, whereas the OpenManage Enterprise. shows the overall health of the chassis. Hence, it is recommended to check the component-related health status for FX2s and VRTX chassis.| N/A
85153| Device Monitoring| HPE servers display incorrect power supply data. 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, does not provide the ‘Power Supply’ data.

| N/A
85153| Device Monitoring| Discovery of an HP server by using IPMI command may not reflect the correct rollup health status.| View the lower-level sensor health data.
75653| Device Monitoring| HPE servers do not display certain FRU fields. For the discovered HP servers, the following field- replaceable unit (FRU) details are not displayed under the device’s Hardware page: Memory FRU details, BIOS – Part number and version, BMC controller – Part number.| N/A
Not available| Device Monitoring| The All Devices page shows health status of the discovered YX1X servers with iDRAC firmware version 1.98 or later as unknown.| N/A
178692| Discovery| Few invalid IP range formats are not being validated when creating a Discovery job. While discovering devices, a few invalid IP and IP- range formats are not being rejected by the Create Discovery Job wizard, resulting in ‘failed’ Discovery jobs.| N/A
158088| Discovery| Unclear error message on failure of Windows server discovery using SSH. Discovery of Windows server(s) using non-admin credentials fails with an error message Unable to connect to the device over SSH because a connection error occurred. This must be interpreted instead as ‘Unable to perform the requested

action because the device management endpoint authentication over SSH failed’.

| N/A
Issue ID| Functional Area| Description| Workaround/Resolution
---|---|---|---
147416| Discovery| 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.| N/A
249730| Discovery| The Management IP of non-Dell servers discovered via Redfish is not displayed on the device details Overview screen.| Click the IP displayed on the device screen header.
263682| Discovery| If a target iDRAC is slow to respond or there are network delays, the console will generate CDEV6131 alerts in the event of a device connection failure.| By default the value of WS-MAN Service Check Timeout. is set to 1 second with

a hardcoded number of retries. It is recommended to increase the timeout value higher than the default to avoid connection failures.

255237| Firmware/ Driver Management| Windows driver update may fail for managed Windows servers with a Dell System Update (DSU) version later than 1.9.2.1.| Uninstall Dell System Update (DSU) on the Windows server, and run an inventory job to install the DSU with the Collect inventory option checked.
209750| Firmware/ Driver Management| If an MX7000 chassis firmware is downgraded then the associated job’s status and details must be checked on the respective MX7000 as they are not available in OpenManage Enterprise.| N/A
209728| Firmware/ Driver Management| Baseline Version field in the Compliance report using local firmware catalogs shows as ‘Update file not in catalog.’ For the firmware catalogs generated using DRM versions lower than 3.3.2 and hosted on network shares with Windows 2019 and above, the Baseline Version field in the Compliance report using such catalog shows as ‘Update file not in catalog’.| For local network shares using Windows 2019 and later, catalogs must be generated using Dell Repository Manager (DRM) version 3.3.2 and later.
208758| Firmware/ Driver Management| OpenManage Enterprise supports UI internationalization, however, it is recommended that the functional content such as the file names and catalog content are entered only

in English. Firmware compliance catalog with Japanese catalog file name in the path fails

the connectivity test and fails to create catalog across CIFS , NFS , HTTP, and HTTPS shares.

| N/A
185315| Firmware/ Driver Management| Firmware compliance on multiple baselines logs CDEV9000 alerts for a single device with non- associated firmware compliance baseline. When firmware compliance check is executed for multiple firmware baselines simultaneously, the warning alert —CDEV9000 – This device and several others has become non-compliant after running compliance task: