OpenManage Enterprise 4.0 Release Notes

PDF

Known Issues

Table 1. Known Issues for OpenManage Enterprise 4.0The table lists the known issues for OpenManage Enterprise 4.0.
Issue ID	Functional Area	Description	Workaround/Resolution
213931	Alert Management	Alerts that are forwarded from the MX7000 chassis 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
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 version 3.9.2 update files in the share before update.	Ensure you have OpenManage Enterprise version 3.9.2 update files in your network share 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 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.	N/A
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
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 created, the new identity pool will not show those identities as assigned.	N/A
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
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.
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
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: <Baseline Name>— is sometimes logged for these baselines on the Alerts page with any one random device in any of the firmware compliance baseline. Sometimes the firmware baseline is not associated with the device.	N/A
185312	Firmware/Driver Management	CDEV9000 non-compliance alert is logged for only one random device in the firmware baseline. When a firmware/driver baseline with many devices is checked for compliance, the warning alerts CDEV9000 on the Alerts page is logged for only one random non-compliant device from that baseline.	N/A
163175	Firmware/Driver Management	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.	N/A
159958	Firmware/Driver Management	Firmware catalog management using Dell.com or a local network path is limited to only the Enterprise Server catalog. Other catalogs such as ESXi_Catalog.xml.gz are not supported.	N/A
152092	Firmware/Driver Management	Appliance is unable to download the console upgrade from HTTP or HTTPS intranet share, when the intranet share address is blocked in proxy filtering.	If the upgrade download has a problem connecting through proxy, uncheck the proxy settings, and then download.
151332	Firmware/Driver Management	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.	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.
146564	Firmware/Driver Management	Firmware upgrade fails when iDRAC firmware versions older than 2.40.40.40 are upgraded directly to 2.63.60.61 with an error message Unable to verify Update Package signature. This failure happens as the firmware versions older than 2.40.40.40 cannot validate the latest SHA-256 digital signature of the Dell Update Packages.	First upgrade the older iDRAC firmware versions to 2.40.40.40 before attempting an upgrade to iDRAC firmware version 2.63.60.61.
136820	Firmware/Driver Management	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.	N/A
108218	Firmware/Driver Management	The Update Firmware button remains enabled even when there are no firmware catalogs available for upgrade or downgrade.	N/A
Not available	Firmware/Driver Management	The firmware or driver compliance status of network switches, modular IOAs, and Dell storage devices may show as "Compliant" (but unselectable) in the firmware/driver compliance reports even though update of these devices are not supported by the Dell catalog.	N/A
274271	Firmware/Driver Management	When an in-band firmware update with reboot required is performed on Windows servers, sometimes the post-upgrade inventory task fails. This happens due to the ongoing reboot operation during the inventory task.	Perform the inventory task manually once the device reboot has completed.
165191	Inventory	Incorrect inventory data after moving sled from lead to member chassis. For the Multi-Chassis Management (MCM) group, a Chassis Refresh Inventory task for the 'lead' chassis does not fully update the sled inventory. A Chassis Refresh Inventory task is triggered in the appliance when a sled is removed from the lead chassis and added to a member chassis.	To immediately update the sled inventory, trigger the refresh inventory of the sled manually. Otherwise, the sled inventory is refreshed during the automatic daily inventory collection.
160622	Inventory	Same inventory details can be present on two servers post migration, as the 'true' target-specific attributes are not reclaimed from the 'source' server as part of migration.	N/A
75653	Inventory	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
226626	Inventory	VxRail models in the View Details page may be tagged with an iDRAC IP instead of VxRail IP.	N/A
275838	Inventory	When a template is deployed by setting static IP, the post-deployment inventory refresh task updates the management url only for Redfish profile. The management url for WSMAN profile still points to old IP address. This results in 2 links of Launch IDRAC console one for each IP address.	Click the Launch IDRAC console with new IP address.
279193	Jobs	Using JobsService/Jobs to create JobName: Export Log jobs fail.	Use TechSupport Report (TSR) or diagnostic log API /api/JobService/Jobs with JobName: Diagnostic_Task to create a Diagnostic task.
Not available	Jobs	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.	N/A
254121	Migrate	After the Migrate Out process, the target OpenManage Enterprise appliance remains inaccessible and displays a Loading status for over12 hours. This issue occurs when the appliance moves from maintenance to the running state on the target appliance.	N/A
274292	Migrate	Unable to proceed with migrate out if the source primary NIC is in a disabled state.	Enable the primary NIC before performing the migrate out operation.
281230	Migrate	During the configuration of Step 2 in OpenManage Enterprise 3.10.x for migration, users with a proxy in their setup to connect to the internet may get the following error:Unable to perform the operation, because either the credentials are invalid or the provides IP value is not correct. This error occurs because the Proxy Exclusion list and the Ignore Certificate Validation options provided in Proxy Configuration are not being utilized. Therefore, the communication is routed through the proxy and the proxy server blocks the communication between local IP addresses.	Disable the Proxy Configuration and setup an offline network share of Plugins Catalog and other required files. Specify the path under Application Settings > Console and Plugins > Update Settings > Network Share > Local path. Refer to the Configuring a local network share for offline update section in the User Guide for more details.
161300	Multi-Chassis Management	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.	N/A
153980	Networking	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.	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.
148789	Networking	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.	N/A
102153	Networking	From the All Devices page, you cannot launch the iDRAC application interface with IPv6 addresses.	N/A
Not available	Networking	Template Deployment with iDRAC Management IP option "Set static IP for each device" fails with error message "connection lost" with IPV6 IP (Legacy(3.1)). It works with IPV4.	N/A
Not available	Networking	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.	N/A
Not available	Networking	When NIC teaming is enabled on MX7000 chassis along with VLAN configuration, deploying of VLAN from the OpenManage Enterprise console overwrites the NIC teaming configurations to 'No teaming'. The LACP or other teaming options would need to be reconfigured from MX7000.	N/A
282562	Plugin Management	On KVM deployments, plugins cannot be installed. The errors displayed are: This plugin does not meet the minimum requirements for installation. Appliance resources are not sufficient to either install or continue to run the <plugin name> efficiently: The OME VM is not configured with enough disk space to support this plugin. 400 GB of disk space must be allocated to the VM to support the appliance and all plugins (including this one). The VM has 0 GB allocated, 400GB is required for the appliance and all other installed plugins.	Ensure that both hard drive images associated with the appliance VM have Bus set to SATA.
254850	Reports	Appliances configured with a time zone other than Coordinated Universal Time (UTC) display the Schedule time in UTC, while appliances configured with a UTC time zone display the Schedule time properly, in local time.	Configure appliances with a UTC time zone.
230181	Reports	Device group does not get sorted into ascending or descending order on the Reports screen.	N/A
174851	Reports	The built-in Virtual Disk report contains duplicate or empty values if the virtual disks and physical disks do not have any associations and are used individually. This issue is not observed if the VDs an PDs are being used together.	It is recommended to use a custom report to get only the virtual disk data if the VDs and PDs are not associated.
133201	Reports	Export of large firmware compliance reports, containing more than 200,000 elements, fails and the appliance displays an Application timeout error.	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.
253473	Reports	Enclosure ID is not populated when listing server array disks on the UI.	N/A
210645	Scope-Based Access Control (SBAC)	Any scheduled tasks must be rescheduled by the new Device Manager after transfer of ownership. After a transfer of ownership is executed, the new Device Manager must reschedule any tasks, such as the tasks for firmware updates, deployment of templates, alerts policies that were previously scheduled by the former Device Manager.	N/A
197629	Scope-Based Access Control (SBAC)	Global search count is greater than the actual result count for scope-restricted device managers. When a 'scoped' device manager uses Global Search, the total search count exceeds the actual items displayed.	N/A
194142	Scope-Based Access Control (SBAC)	Alert policies and firmware baselines created by a device manager in 3.5 or earlier versions are only available to administrator users. Post upgrade of OpenManage Enterprise from version 3.5 or earlier versions, 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, these entities created by device managers prior to the upgrade would need to be recreated.	N/A
193698	Scope-Based Access Control (SBAC)	Ownership information for device managers (AD/LDAP and OIDC) is lost on appliance upgrade. Post upgrade of OpenManage Enterprise from version 3.5 or earlier versions, the AD/LDAP and OIDC (Ping Federate or Keycloak) device managers would need to recreate all the previous-version entities such as jobs, alert policies, configuration templates, configuration baselines, profiles, firmware baselines, firmware catalogs, and reports as these entities are only available to the administrators post upgrade.	N/A
193441	Scope-Based Access Control (SBAC)	Run Inventory on Group is unavailable for Device Manager users. For the Device Manager users, Run Inventory on Group option under Inventory on the All Devices page is unavailable.	N/A
192774	Scope-Based Access Control (SBAC)	After upgrade, device managers can perform VLAN operation on in-scope proxied MX7000 sleds even when the chassis is out of scope. VLAN operation on in-scope 'proxied' MX7000 sleds is allowed for a device manager, even if the MX7000 chassis is out of scope.	N/A
Not available	Security	OpenManage Enterprise could be impacted by the Linux TCP SACK vulnerability (CVE-2019-11477).	N/A
228238	User Management	Post deleting and re-creating a specific user, scheduled jobs that are created with the user may fail due to changes in the internal identification of the user.	Re-create the recurring task from the active user to avoid failure.
193717	User Management	If Ping Identity is used for OIDC provider, the appliance can only be used with Administrator role. With OIDC provider PingFederate, it is observed that all the OpenID client policies associated with the OpenManage Enterprise Client IDs are reset to the policy marked as 'Default' when the appliance console gets re-registered with the OIDC provider. Re-registration of the appliance console with OIDC provider happens in the event of an appliance upgrade, change in network configuration, or change in SSL certificate.	N/A
210771	Warranty Management	In a pure IPv6 setup, the appliance is unable to retrieve the warranty issues from the support site.	Consider enabling IPv4 for routing purpose before initiating Warranty jobs.
176493	Warranty Management	With the Japanese version of the appliance, it is observed that the PDF export of the Warranty page contains illegible characters.	To get the PDF export of the Warranty page without the illegible characters, use the following workaround: Export CSV report in Excel. Change the encoding type to UTF-8. Save it as PDF.