Dell EMC OpenManage Enterprise Release Notes

1 Rev. 1 October 2021 Dell EMC OpenManage Enterprise ReleaseNotesDescribes the new features, changed features, resolved issues, known issues, and limitations in OpenManage Type: Major (MA)Topics: Revision history Product description New features Known issues Limitations Environment and system requirements Installation and upgrade considerations Where to get helpRevision historyThis section provides a description of document 1. Document Revision history Document RevisionDateDescription of changes01 October 2021 Initial Release in new templateProduct descriptionOpenManage Enterprise is a systems management and monitoring web application delivered as a virtual appliance. It provides acomprehensive view of the Dell EMC servers, chassis, storage, and network switches on the Enterprise network. OpenManageEnterprise's system management and monitoring is best suited for Enterprise LANs and is not recommended for usage overWANs.

2 For information about supported browsers, see the OpenManage Enterprise Support Matrix available on the 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 of the security features of OpenManage Enterprise are: Role-based access that limits access to console settings and device Scope based access control allows administrators to restrict the device groups that device managers can access andmanage.

3 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 featuresThe following table describes the features that are introduced in OpenManage Enterprise version nameFeature descriptionHTTPS supportAbility to configure the internal appliance share to furnish content throughHTTPS or CIFS (default).Windows 2022 supportDeployment of appliance on Windows Server 2022 is way to create and download a consolelog archive from the Graphical User Interface(GUI)You can now create a console log archive and then download it from theMonitor > Audit Logs > Troubleshoot submenu rather than the Text UserInterface (TUI) when the Field Service Debug (FSD) is issuesTable 2.

4 Known issues Issue IDFunctional areaDescriptionWorkaround/Resolution2108 58 Alert ManagementIf several alerts are received at once by thelead chassis, in a multi-chassis management (MCM)environment, then the display and processing of thosealerts in OpenManage Enteprise is ManagementFor the failed alert-policy-triggered IPMI tasks, thetask execution history on the Job Details page showsduplication of the error ManagementIf SNMPv3 destination(s) is/are already added asalert forwarding destination(s) in the appliance, thenin order to add and apply a new alert forwardingdestination address, the appliance prompts only thefirst time to re-enter of all the previously enteredSNMPv3 Authentication and Privacy passphrasesbefore of the applianceprompt, you must re-enter allthe previously entered SNMPv3 Authentication and Privacypassphrases every time theSNMP community string or portis edited on Application Settings >Alerts > SNMP Alert ManagementThe traps forwarded from one OpenManageEnterprise console to another OpenManage Enterpriseconsole are received as Miscellaneous category alertswith message "unknown trap ," if the TrapForwarding Format is set as "Original Format" in theformer ManagementThe 'From' address used for all email actions, suchas Reports, Update, Discovery and Alert Policies,is dependent on the SMTP server some SMTP server configurations.

5 The 'From'address is the Sender Email ID specified in theApplication settings (Application Settings > ConsolePreferences > Email Sender Settings > Sender Email2 Table 2. Known issues (continued)Issue IDFunctional areaDescriptionWorkaround/ResolutionID) and for others it is the username used for SMTP server authentication (Application Settings > Alerts> Email Configuration > SMTP Server NetworkAddress).160040 Alert ManagementThere is currently a discrepancy between the actualnumber of MIBs imported and the MIB count displayedon the Monitor > MIB ManagementEmails for alert policies don't work when the sameevent is generated twice within 2 minutes. Emailaction for alerts containing the same message ID andcontent are triggered every 2 minutes to avoid manyrepeated/redundant alert messages in the ManagementThe .CSV files, that record the deleted alerts fromthe Alert log, fail to capture the Device Name andthe Device IP details of the alerts received from theundiscovered ManagementIgnore alert policy created for warranty, firmwarecompliance, and configuration compliance alerts willbe ignored only if alerts are generated from the samedevice from which ignore policy was created.

6 In othercases, alerts will be received and not ManagementThe Severity status in the Alert log for the alertsreceived from the PowerVault ME4 storage arrays isbeing reported as Unknown by the appliance. Thisdefect is due to the unavailability of the precannedMIBs for the PowerVault ME4 storage arrays in theappliance ManagementWhen an already imported MIB is renamed and parsedthrough API the trap status is reported as 'Existing'instead of 'Imported'.121158 ApplianceDeploymentWhile programmatically deploying the OpenManageEnterprise from Linux shell, if the argumentprovided for --name= in the command line beginswith a "$" then the argument is ignored andappliance is deployed with the name --name= argument, whichbegins with "$" in the commandline must be enclosed in singlequotes, for example, --name='$OME-VM'.198702 Appliance SettingsManually setting the time to an earlier time on theVMware vSphere fails if periodic time synchronizationis enabled in the VM.

7 On VMware vSphere, changingthe appliance's time to an earlier time than the systemtime fails if the periodic time synchronization in theVM is set the appliance's time toan earlier time than the systemtime, disable the periodic timesynchronization in the VM, bylaunching the vSphere Client, goto Edit Settings > VM Options> VMware Tools > SynchronizeTime with Host and deselectthe checkbox Synchronize SettingPost addition of the disk space using the ConfigureAppliance Disk Size feature in the Text User Interface(TUI) , deletion or reduction of the appliance's consoleexpanded disk space is not remove a newly-added disk orto reverse the increase in size ofan existing disk, you must revertto prior VM snapshot that youare recommended to take as abackup before applying any diskconfiguration 2. Known issues (continued)Issue IDFunctional areaDescriptionWorkaround/Resolution1512 21 Appliance SettingThe Timezone and NTP Server Address fields addedto the Application Settings > Network > TimeConfiguration section will remain blank and will not bedisplayed for a few minutes if the entered NTP serverIP address is not UpgradeUpgrading of a PMP-installed OpenManage Enterpriseappliance to version might take longer.

8 Applianceupgrade time might be between 1 and 10 hoursdepending on the number of devices being monitoredby Power UpgradeUpgrade of the appliance may fail if initiated postdeletion of devices. If an upgrade of the applianceis initiated post deletion of devices, the Off-boardingtasks may fail or run endlessly resulting in upgradefailure and a console reboot with the previous workingstate of the the services from theText User Interface (TUI) page208040 Appliance UpgradeWhen upgrading an appliance that is supporting 8,000devices to , the Console Update Execution job'sstatus may be displayed as 'Failed' on the Jobs upgrading an appliance that is supporting 8,000devices to , the Console Update Execution job'sstatus may be displayed as 'Failed' on the Jobs Failed status of the Console Update Executiontask is seen if the appliance upgrade takes morethan 60 minutes. The 'Failed' status is due to a timeout of the Console Update Execution job and canbe ignored as this has no functional impact on theupgrade UpgradeConsole upgrade fails from version to , if there are a large number (more than 2,000)unreachable devices, in multiple discovery settings, inOpenManage Enterprise version This happensas the long runtime of Discovery task exceeds themaximum wait-time limit of 48 hours set for theinitiation of other post-upgrade prevent upgrade failure, insuch rare scenarios, you canmanually cancel the Discoverytask to allow the post-upgradetasks to initiate and UpgradePost deletion of 8K devices, Onboarding task doesnot trigger during next discovery cycle.

9 Post deletionof 8,000 devices from the appliance, the automaticonboarding task fails during the next discovery the services from theText User Interface (TUI) UpgradeThe Text User Interface (TUI) screen is not displayeduntil the 'Enter' key is pressed after updatingthe appliance to version on ESXi with largedeployments involving 8,000 or more UpgradeThe Console Update Execution job's status isdisplayed as 'Failed' on the Jobs page, if the applianceupgrade takes more than 60 minutes. The 'Failed'status is due to a time out of the Console UpdateExecution job and can be ignored as this has nofunctional impact on the upgrade UpgradeAddition of a new network interface in hypervisorsfails immediately after upgrading the OpenManageEnterprise from version to version ( > > > > ). An error message "Failedto reconfigure virtual machine to The attempted operation4 Table 2. Known issues (continued)Issue IDFunctional areaDescriptionWorkaround/Resolutioncann ot be performed in the currentstate (Powered on)" is UpgradeWhen updating local shares for a manual upgrade forversions without any installed plugins (such as ), the audit log displays warning entries suchas 'Unable to retrieve the source file of type PluginCatalog because the file does not exist' and 'Thestatus of downloading the Plugin Catalog is Failed'.

10 These error messages do not have any functionalimpact on the upgrade process and can be UpgradeConsole Upgrade from through NFS Share , console Upgrade through HTTPS (internalShare) fails when upgrading from versions and the online method forupdating, or use the HTTPS method. Ensure that the securitycertificates are signed by atrusted third-party certificateauthority while using the HTTPS method of UpgradeAfter upgrading to the latest version of OpenManageEnterprise, the existing job IDs are LogAn invalid audit log indicating 'console upgrade failure'is generated upon a successful upgrade of theappliance from version to version This auditlog can be to set Target iSCSI IQN on BIOS-iSCSI viareference server template deployment, as it failswith Invalid AttributeValue error. The defaultiSCSI Target IQN format of the iSCSI controllersof devices such as PowerVault ME4012 array andEquallogic PS array, is not accepted as a valid IQNformat for deployment with IDRAC version 'BIOS' attributes only the IP configuration of a discovered device ischanged during template deployment (from DHCPto Static or vice versa), the Boot to Network ISOoperation fails.