Dell EMC OpenManage Enterprise Version 3.5 User's Guide October 2020 Rev.
Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your product. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. © 2017 - 2020 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries.
Contents Tables........................................................................................................................................... 9 Chapter 1: About Dell EMC OpenManage Enterprise.....................................................................10 New in this release............................................................................................................................................................. 11 Other information you may need..........................
Adding or editing devices in a Static child group.................................................................................................42 Rename child groups of Static or Query Dynamic groups.................................................................................42 Clone a Static or Query group..................................................................................................................................42 Add devices to a new group......................................
Deploy device deployment templates...........................................................................................................................65 Deploy IOA deployment templates................................................................................................................................66 Clone deployment templates..........................................................................................................................................
Alert policies........................................................................................................................................................................ 91 Automatic refresh of MX7000 chassis on insertion and removal sleds......................................................... 93 Create alert policies.................................................................................................................................................... 93 Enable alert policies.....
Stop an inventory job...................................................................................................................................................... 119 Delete an inventory job................................................................................................................................................... 119 Edit an inventory schedule job...................................................................................................................................
Disable OpenID Connect providers........................................................................................................................143 Security Certificates....................................................................................................................................................... 143 Generate and download the certificate signing request..................................................................................
Tables 1 Other information you may need........................................................................................................................... 11 2 Role-based user privileges in OpenManage Enterprise................................................................................... 14 3 OpenManage Enterprise User role types............................................................................................................15 4 Minimum recommended hardware...................
1 About Dell EMC OpenManage Enterprise OpenManage Enterprise is a systems management and monitoring web application delivered as a virtual appliance. It provides a comprehensive view of the Dell EMC servers, chassis, storage, and network switches on the enterprise network. 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.
● ● ● ● ● Manage the device warranty on page 121 Reports on page 123 Managing MIB files on page 128 Role-based OpenManage Enterprise user privileges on page 14 Directory services integration in OpenManage Enterprise on page 137 Topics: • • • • New in this release Other information you may need Contacting Dell EMC OpenManage Enterprise Advanced license New in this release ● ● ● ● Support for new plugins — SupportAssist Enterprise version 1.0 and Update Manager Plugin version 1.0.
Contacting Dell EMC NOTE: If you do not have an active internet connection, you can find contact information on your purchase invoice, packing slip, bill, or Dell EMC product catalog. Dell EMC provides several online and telephone-based support and service options. Availability varies by country and product, and some services may not be available in your area. To contact Dell EMC for sales, technical support, or customer service issues: 1. Go to Dell.com/support. 2. Select your support category. 3.
License-based features in OpenManage Enterprise The OpenManage Enterprise Advanced license is required to use the following features of OpenManage Enterprise: ● ● ● ● Server configuration deployment. Server configuration compliance baseline creation and remediation. Boot to ISO. Activate the available plugins, such as the Power Manager, to extend the capability of the appliance.
2 Security features in OpenManage Enterprise Some of the security features of OpenManage Enterprise are: ● ● ● ● ● User roles (Administrator, Device Manager, Viewer) with differing device management functionality. 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). Only browsers with 256-bit encryption are supported.
Table 2.
Table 3. OpenManage Enterprise User role types (continued) User with this role... Has the following user privileges ● Modify the roles of existing users ● Delete the users ● Change the user password Device Manager (DM) ● Run tasks, policies, and other actions on the devices assigned by the administrator. ● Cannot delete or modify any groups. NOTE: Users with Device Manager (DM) privileges cannot be assigned groups. Viewer ● Can only view information displayed on OpenManage Enterprise and run reports.
3 Install OpenManage Enterprise Dell EMC OpenManage Enterprise is provided as an appliance that you can install on a hypervisor and manage resources to minimize downtime. The virtual appliance can be configured from the application web console after initial network provisioning in the Text User Interface (TUI). For steps to view and update the console version, see Check and update the version of the OpenManage Enterprise and the available plugins on page 148.
Minimum system requirements for deploying OpenManage Enterprise Table 5. Minimum requirements Particulars Minimum requirements Supported hypervisors ● VMware vSphere versions: ○ vSphere ESXi 5.5 onwards ● Microsoft Hyper-V supported on: ○ Windows Server 2012 R2 onwards ● KVM supported on: ○ Red Hat Enterprise Linux 6.5 onwards Network Available virtual NIC which has access to the management networks of all the devices which is managed from OpenManage Enterprise.
9. On the Disk Format page, click Thick provision to pre-allocate physical storage space to VMs at the time a drive is created. 10. On the Ready to Complete page, review the options you selected on previous pages and click Finish to run the deployment job. A completion status window displays where you can track job progress. Deploy OpenManage Enterprise on Hyper-V 2012 R2 and earlier host NOTE: ● To perform any tasks on OpenManage Enterprise, you must have necessary user privileges.
Deploy OpenManage Enterprise on Hyper-V 2016 host NOTE: ● To perform any tasks on OpenManage Enterprise, you must have necessary user privileges. See Role-based OpenManage Enterprise user privileges on page 14 ● If a secondary adapter is added before powering on the appliance for the first time, the adapter will be configured with IPv4 and IPv6 disabled.
1. Download the openmanage_enterprise_vhd_format.zip file from the support site. Extract the file and then move or copy the enclosed VHD file into an appropriate location on your system where you want to store the OpenManage Enterprise virtual drive. 2. Start the Hyper-V Manager in the Windows Server 2019. The Windows Hyper-V should be displayed under the Hyper-V Manager. If not, right-click Hyper-V Manager, and then select Connect to Server. 3.
10. Navigate the file system and select the QCOW2 file that is downloaded in step 1, and then click Forward. 11. Assign 16 GB as the memory and select two processor cores, and then click Forward. 12. Assign the required disk space for the VM and click Forward. 13. Under Advanced options, ensure that the bridged host device network is selected and KVM is selected as the Virt Type. 14. Click Finish. OpenManage Enterprise appliance is now deployed by using the KVM.
This script modifies the openmanage_enterprise.x86_64-0.0.1.ovf file for deployment in accordance with the values set in the ovf_properties.config file. When the script finishes execution, a sample ovftool command is displayed. It contains tags such as , , , , and so on, that you must replace as per your deployment environment. These settings define the resources that are used on the target ESXi system and also the credentials and IP address of the target system.
4 Get started with OpenManage Enterprise Topics: • • • • • • Log in to OpenManage Enterprise Configure OpenManage Enterprise by using Text User Interface Configure OpenManage Enterprise Recommended scalability and performance settings for optimal usage of OpenManage Enterprise Supported protocols and ports in OpenManage Enterprise Use case links for the supported protocols and ports in OpenManage Enterprise Log in to OpenManage Enterprise When you boot the system for the first time from the Text User Inte
You can configure OpenManage Enterprise by using the TUI. The TUI screen has the following options: Table 7. Text User Interface options Options Descriptions Change the Admin Password Select Change the Admin Password screen to enter a new password and confirm the password. For the first time, you must change the password by using the TUI screen. Display Current Appliance Status Select Display Current Appliance Status to view the URL and the status of the appliance.
Table 7. Text User Interface options (continued) Options Descriptions This interface will have the routing priority if there is any ambiguity. The primary interface is also expected to be the 'public facing' interface which allows for corporate network/ internet connectivity. Different firewall rules are applied to the primary interface, which allow for tighter access control such as access restriction by IP range. NOTE: If multihoming is enabled, the appliance can be accessed from two networks.
Table 7. Text User Interface options (continued) Options Descriptions Change keyboard layout Select Change keyboard layout to change the keyboard layout if needed. Reboot the Appliance Select Reboot the Appliance to restart the appliance. NOTE: After running a command to restart the services, the TUI may display the following message: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 36s! [java:14439]. The soft lockup issue likely occurs as a result of the hypervisor being overloaded.
Recommended scalability and performance settings for optimal usage of OpenManage Enterprise The following table lists the performance parameters of the supported features in OpenManage Enterprise. To ensure an optimal performance of OpenManage Enterprise, Dell EMC recommends to run the tasks at the specified frequency on the maximum number of devices that are recommended per task. Table 8.
Table 9. OpenManage Enterprise Supported protocols and ports on management stations (continued) Port Number Protocol Port Type Maximum Encryption Level Source Direction Destination Usage 53 DNS UDP/TCP None OpenManage Enterprise appliance Out Management station ● For DNS queries. 68 / 546 (IPv6) DHCP UDP/TCP None OpenManage Enterprise appliance Out Management station ● Network configuration.
Table 9. OpenManage Enterprise Supported protocols and ports on management stations (continued) Port Number Protocol Port Type Maximum Encryption Level Source Direction Destination Usage ● Server-initiated discovery. 514 Syslog TCP None OpenManage Enterprise appliance Out Syslog server ● To send alert and audit log information to Syslog server. 3269 LDAPS TCP None OpenManage Enterprise appliance Out Management station ● AD/ LDAP login for Global Catalog.
Use case links for the supported protocols and ports in OpenManage Enterprise Table 11. Use case links for the supported protocols and ports in OpenManage Enterprise Use case URL Upgrade OpenManage Enterprise appliance https://downloads.dell.com/openmanage_enterprise/ Access device warranty https://apigtwb2c.us.dell.com/PROD/sbil/eapi/v5/assetentitlements Update catalogs https://downloads.dell.com/catalog/ Push new alert notifications using the OpenManage Mobile application https://openmanagecloud.
5 OpenManage Enterprise Graphical User Interface overview On the OpenManage Enterprise Graphical User Interface (GUI), you can use menu items, links, buttons, panes, dialog boxes, lists, tabs, filter boxes, and pages to navigate between pages and complete device management tasks. Features such as devices list, Donut charts, audit logs, OpenManage Enterprise settings, system alerts, and firmware/driver update are displayed at more than one place.
● G—The number of events generated in the alerts log. Also, based on your settings to whether or not view the unacknowledged alerts, the number of alerts in this section varies. By default, only the unacknowledged alerts are displayed. To hide or unhide the acknowledged alerts, see Customize the alert display on page 146. Deleting the alerts reduces the count. For information about symbols that are used to indicate severity statuses, see Device health statuses on page 37.
6 OpenManage Enterprise Home portal By clicking OpenManage Enterprise > Home, the Home page of OpenManage Enterprise is displayed. On the Home page: ● View the Dashboard to get a live snapshot about the health statuses of devices, and then take actions, where necessary. See Dashboard. ● View alerts under the critical and warning categories and resolve those. See Managing device alerts.
Click the name to view and configure device properties. See Viewing and configuring devices on page 48. To filter data, click Advanced Filters. Export data into Excel, CSV, HTML, or PDF format. See Export all or selected data on page 47. For more information about a Donut chart, see Donut chart on page 37 and Device health statuses on page 37. To view the summary of devices in a different device group monitored by OpenManage Enterprise, select from the Device Groups dropdown menu.
NOTE: An MX7000 chassis can be a lead, stand-alone, or member chassis. If an MX7000 chassis is a lead chassis and has a member chassis, the latter is discovered by using the IP of its lead chassis.
Donut chart You can view a Donut chart in different sections of your OpenManage Enterprise. The output displayed by the Donut chart is based on the items you select in a table. A Donut chart indicates multiple statuses in OpenManage Enterprise: ● The health status of devices: Displayed on the Dashboard page. Colors in the Donut chart split the ring proportionally to indicate the health of devices monitored by OpenManage Enterprise. Every device status is indicated by a color symbol.
7 Managing devices By clicking OpenManage Enterprise > Devices you can view the devices and device groups managed by OpenManage Enterprise. The System groups are default groups created by OpenManage Enterprise when shipped, and Custom groups are created by users such as administrators and device managers. You can create child groups under these two parent groups. For information about the parent-child rules, see Device Groups.
• • Start Management application iDRAC of a device Start the Virtual Console Organize devices into groups In a data center, for effective and quick device management, you can: ● Group the devices. For example, you can group devices based on functions, OSs, user profiles, location, jobs run, and then run queries to manage devices. ● Filter the device-related data while managing devices, updating firmware, discovering devices, and managing alert policies and reports.
● Static Groups: Manually created by the user by adding specific devices to a group. These groups change only when a user manually changes the devices in the group or a sub-group. The items in the group remain static until the parent group is edited or the child device is deleted. ● Query Group: Groups that are dynamically defined by matching user-specified criteria. Devices in the group change based on the result of devices that are discovered by using criteria.
Create or edit a Query device group NOTE: To perform any tasks on OpenManage Enterprise, you must have necessary user privileges. See Role-based OpenManage Enterprise user privileges on page 14. 1. Right-click Query Groups and then click Create New Query Group. Alternatively, click the + icon, select Query Group, and click Create in the Create Custom Group dialog box. For definitions about Static or Query (Dynamic) groups, see Organize devices into groups on page 35. 2.
3. Click Finish. A query criteria is generated and saved in the list of existing queries. An audit log entry is made and displayed in the Audit logs list. See Manage audit logs on page 99.
Add devices to a new group 1. In the working pane, select the check box corresponding to the device(s), click Add to Group , and then click Add to New Group. a. In the Add Devices to New Group Wizard dialog box, type or select data. For more information about groups, see Device Groups. b. To add more devices to the group, click Next. Else, go to step 5. 2. In the Group Member Selection dialog box, select more devices from the Add Devices list.
Related information Organize devices into groups on page 35 Exclude devices from OpenManage Enterprise NOTE: To perform any tasks on OpenManage Enterprise, you must have necessary user privileges. See Role-based OpenManage Enterprise user privileges on page 14. Devices are grouped for efficient handling of repeated tasks such as firmware update, discovery, and inventory generation.
b. Schedule Later: To specify a date and a time when the firmware and/or driver version must be updated. This mode is recommended if you do not want to disturb your current tasks. ● Under Server Options select one of the following reboot options : a. To reboot the server immediately after the firmware/driver update, choose Reboot server immediately and from the dropdown menu select one of the following options: i. Graceful Reboot without Forced Shutdown ii. Graceful Reboot with Forced Shutdown iii.
2. Select the check box corresponding to the device, and then click Refresh Inventory. The job is created and listed in the Jobs list and identified as New in the JOB STATUS column. The inventory of selected device(s) is collected and stored for future retrieval and analysis. For more information about viewing the refreshed inventory data, see Viewing and configuring devices on page 48. To download a device inventory, see Export the single device inventory on page 46.
NOTE: The working pane displays the Donut chart of the selected device group. By using the Donut chart, you can view the list of devices that belongs to other health statuses in that group. To view devices of other health status, click the corresponding color band on the Donut chart. The data in the table changes. For more information about using the Donut chart, see Donut chart.
NOTE: If you export data in the .csv format, you must have the administrator-level credentials to open the file. Viewing and configuring devices NOTE: In the Device list, click the device name or IP address to view device configuration data, and then edit device configuration as described in this section. By clicking OpenManage Enterprise > Devices > selecting a device in the device list > View Details, you can: ● View information about the health and power status, device IP, and Service Tag.
Device hardware information OpenManage Enterprise provides a built-in report about the components and their compliance with the firmware compliance baseline. Click OpenManage Enterprise > Monitor > Reports > Firmware Compliance per Component Report. Click Run. See Run reports on page 124. ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● Device Card Information—Information about cards used in the device. Installed Software—List of firmware and software installed on different components in the device.
run, the status of the job is indicated as Diagnostic Completed, and the Download link is displayed in the Recent Activity section. 5. To download the report, click the Download link, and then download the .TXT Diagnostics report file. ● Else, click Troubleshoot > Download Diagnostics Report, and then download the file. 6. In the Download RemoteDiagnostics Files dialog box, click the .TXT file link, and then download the report. 7. Click OK.
NOTE: The RACADM CLI tab is not displayed for the following servers because the corresponding task is not available in the device pack — MX740c, MX840c, and MX5016S. 3. In the Send Remote Command dialog box, type the command. Upto 100 commands can be entered with each command required to be on a new line. To display the results in the same dialog box, select the Open results after sending check box. NOTE: Enter an IPMI command in the following syntax: -I lanplus . To end the command enter 'Exit.
8 Manage the device firmware and drivers On the OpenManage Enterprise > Configuration > Firmware/Driver Compliance page, you can manage the firmware of all the 'managed' devices. You can also update the drivers of the 64-bit Windows-based devices. NOTE: ● To perform any tasks on OpenManage Enterprise, you must have the necessary user privileges. See Role-based OpenManage Enterprise user privileges on page 14. To manage these settings, you must have the OpenManage Enterprise administrator level credentials.
The summary of all the baselines is displayed in the working pane, and the compliance of a selected baseline is displayed in the right pane by using a Donut chart. A Donut chart and list of items in the baseline changes based on the baseline you select from the Baseline list. See Donut chart.
Add a catalog to the local network Catalog containing the firmware and drivers (64-bit Windows) can be downloaded using the Dell Repository Manager (DRM) and saved on a network share. 1. On the Catalog Management page, click Add. 2. In the Add Update Catalog dialog box: a. In the Name box, enter a catalog name. b. For the Catalog Source, select the option Network Path. The Share Type drop-down menu is displayed. c.
Related tasks Delete a catalog on page 55 SSL Certificate Information The catalog files for firmware and driver updates can be downloaded from the Dell support site, Dell EMC Repository Manager (Repository Manager), or a web site within your organization network. If you choose to download the catalog file from the web site within your organization network, you can accept or decline the SSL certificate. You can view details of the SSL certificate in the Certificate Information window.
2. To go back to the Firmware/Driver Compliance page, click Return to Firmware/Driver Compliance. NOTE: Catalogs cannot be deleted if linked to a baseline. Related information Add a catalog to the local network on page 54 Create a baseline A baseline is a set of devices or group of devices that are associated with that catalog. A baseline is created for compliance evaluation of the firmware and drivers for the devices in that baseline, against the versions specified in the catalog.
To delete the baselines: 1. Select the baseline(s) from the baselines listed on the Firmware/Driver Compliance page. 2. Click Delete and click Yes on the Confirmation prompt. The deleted baselines are removed from the Firmware/Driver Compliance page. Edit a baseline The baselines on the Configurations > Firmware/Driver Compliance page can be edited as follows: 1. Select a baseline, and then click Edit in the right pane. 2. Modify data as described in Creating the firmware baseline.
You can view the firmware and driver compliance of individual devices associated with a baseline and choose to either upgrade or downgrade the firmware and/or driver version on that device. To view the baseline compliance report: ● Select the check box corresponding to the baseline and click View Report in the right pane. On the Compliance Report page the list of devices associated with the baseline and their compliance level is displayed.
NOTE: ● The Reset iDRAC function is not supported for the devices under an MCM chassis that are in a 'Proxied' onboarding state and for updating only the drivers of the devices. For more information about onboarding states, see Onboarding devices on page 108. ● The firmware or driver compliance status of network switches, modular IOAs, and Dell storage devices is displayed as Unknown as these are not updatable using the Dell catalog.
● Reset iDRAC: Select to initiate a reboot of the iDRAC before the update job is initiated. NOTE: This function is not supported for updating the drivers. 5. Click Update. A firmware/driver update job is created to update the device's firmware and/or driver. You can view the status of the job on the Monitor > Jobs page.
9 Manage device deployment templates Device deployment template in OpenManage Enterprise allows you to set the configuration properties such as BIOS, boot, network properties, and so on of servers and chassis. The deployment template is a consolidation of system configuration settings referred to as attributes. The deployment template allows for multiple servers or chassis to be configured quickly and automatically without the risk of human error.
● Clone Reference Server: Enables you to clone the configuration of an existing server. ● Clone Reference Chassis: Enables you to clone the configuration of an existing chassis. ● Clone Reference IOA: Enables you to clone the configuration of an existing M I/O aggregator. NOTE: The attributes in the IOA template are uneditable. Only the name and description of an IOA template can be edited. c. Click Next. d.
2. In the working pane, click View Details. On the Template Details page, the deployment template name, description, the reference device from which the deployment template was created, and the last updated date by the OpenManage Enterprise user information is displayed. 3. Right-click an element to expand all or collapse all the child elements in the Configuration Details section to display all the attributes that are used for creating the deployment template.
of attribute dependencies, if you change the setting for whether or not a particular attribute gets deployed, it could cause unexpected results on the target device, or cause deployment to fail. Each group also has a check box to the left of its name. The icon in group check boxes has one of three values: i. Checked — Indicates that all of the attributes in the group are selected for deployment. ii. Hyphen — Indicates some (but not all) of the attributes are selected for deployment. iii.
1. Click IO Pool Assignment and from the Identity Pool list, select an identity pool for the deployment template. Click Next. 2. In the Bandwidth section, edit the Minimum Bandwidth (%) and the Maximum Bandwidth (%) of the associated NICs and click Next. NOTE: Bandwidth settings are only applicable to the partitioned NICs. 3. In the VLANs section (applicable only for the modular systems): a. Select an appropriate NIC Teaming option. b.
A graceful reboot of the server is attempted when the Do not forcefully reboot the host OS option is selected. If the reboot fails, you must rerun the template deployment task. c. Select the Use strict checking check box to match the VLANs with like characteristics. If unselected, only VLAN name and QoS are used for matching NOTE: This option is displayed only if the selected target devices are modular system sleds. d. Click Next. 3. If the target device is a server, in the Boot to Network ISO section: a.
Table 13. Supported cross template deployments (continued) IOA Deployment template mode Supported IOA template modes of target PMUX (Programmable MUX) PMUX, Standalone VLT VLT CAUTION: Ensure that only the appropriate devices are selected for deployment. After deploying a deployment template on a repurpose and bare-metal device, it might not be possible to revert the device to its original configuration. 1.
Create auto deployment targets NOTE: To perform any tasks on OpenManage Enterprise, you must have necessary user privileges. See Role-based OpenManage Enterprise user privileges on page 14 To create auto deployment targets : 1. Click OpenManage Enterprise > Configuration > Auto Deploy > Create The Auto Deploy Template wizard is displayed. 2. On the Template Information page, select the deployment template type (Server or Chassis). 3. From the Select Template drop-down menu, select an appropriate template.
Delete auto deployment targets NOTE: To perform any tasks on OpenManage Enterprise, you must have necessary user privileges. See Role-based OpenManage Enterprise user privileges on page 14 NOTE: If a template that is associated with auto deployment targets is deleted from the OpenManage Enterprise > Configuration > Templates page, the associated auto deploy entries would also get deleted irrespective of their current state. To remove the auto deployment targets from the Auto Deploy list. 1.
Create Identity Pool - Pool Information Identity pools are used for template-based deployment on servers to virtualize the network identity for the following: ● ● ● ● Ethernet iSCSI Fibre Channel over Ethernet (FCoE) Fibre Channel (FC) You can create a maximum of 5000 identity pools in each of these categories. The server deployment process fetches the next available identity from the pool and uses while providing a server from the template description.
● The virtual identities which are already assigned, will not be used for a new deployment unless these identities are cleared. Create identity pools You can create an identity pool that contains one or more virtual identity types. To create a pool of virtual identity types: 1. On the Configuration page, click Identity Pools. 2. Click Create. 3. In the Create Identity Pool dialog box, under Pool Information: a. Enter a unique name for the identity pool and an appropriate description. b. Click Next. 4.
Actions Previous Displays the FCoE tab. Finish Saves the changes and displays the Configuration page. Cancel Closes the Create Identity Pool wizard without saving the changes. Create Identity Pool - iSCSI You can configure the required number of iSCSI MAC addresses in the iSCSI tab. NOTE: The iSCSI attributes are applied only when the DHCP option for iSCSI Initiator is disabled in the source template.
NOTE: The IP Address Range, Gateway, Primary DNS Server, and Secondary DNS Server must be valid IPv4 addresses. Actions Previous Displays the Ethernet tab. Next Displays the FCoE tab. Finish Saves the changes and displays the Configuration page. Cancel Closes the Create Identity Pool wizard without saving the changes.
● AABB.CCDD.EEFF The maximum length of a MAC address is 50 characters. This option is displayed only if the Include ethernet virtual MAC addresses check box is selected. Number of virtual Select the number of virtual MAC identities. The identities can be 1 to 50. This option is displayed only if MAC Identities the Include ethernet virtual MAC addresses check box is selected. Actions Previous Displays the Pool Information tab. Next Displays the iSCSI tab.
You can select a network type only for MX7000 chassis. For more information about the network types, see Network types on page 75. 4. Click Finish. The network currently configured in your environment is now defined and resources can access the network. Network types NOTE: You can select a network type for MX7000 chassis only. Table 14. Network types Network types Description General Purpose (Bronze) Used for low priority data traffic.
a. Click Configuration > VLANs > Export and select Export All as CSV. 2. To download as a JSON file : a. Click Configuration > VLANs > Export and select Export All as JSON. Import network definitions The following options are available to import the network definitions: 1. Import VLAN definitions from a file To import VLAN definitions from a file: a. Click Configuration > VLANs. b. Click Import and select Import from File. c. Navigate to the file location and select an existing .json or .
10 Manage Profiles A 'Profile' is a specific instance of an existing deployment template that is customized with attributes unique to an individual device. Profiles can be created either implicitly during a template's deployment/auto-deployment or from the existing templates by the user. A Profile consists of target-specific attribute values along with the BootToISO choices, and iDRAC management IP details of the target device.
● ● ● ● ● ● ● ● View profile details. See, View Profile details on page 78 Edit profile attributes and settings. See, Edit a profile on page 79 Assign a profile to a device or service tag (through auto-deploy). See, Assign a Profile on page 79 Unassign a profile from a device or service tag. See, Unassign profiles on page 80 Redeploy profile changes to the associated target device. See, Redeploy profiles on page 81 Migrate profile from one target (device or service tag) to another. Delete profiles.
Profiles — view network To view the network bandwidth and VLAN allocations for the NIC ports associated to a profile: 1. Select a profile on the Configuration > Profiles page. 2. Click View > View Network to activate the View Network wizard. 3. The Bandwidth section displays the following bandwidth settings of the partitioned NICs: NIC identifier, Port, Partition, Min Bandwidth (%), and Max Bandwidth (%). Click Next 4.
b. The Details page displays the source template, profile name and description. Click Next. c. On the Target page: ● Click Select and from the list of devices, select a target device. NOTE: Devices that are already assigned a profile will be greyed out and not selectable in the target list. ● If a reboot is required after the deployment, select the Do not forcefully reboot the host OS if the graceful reboot fails check box. ● Click Next. d.
Redeploy profiles For the attribute changes of an already deployed profile to take affect on the associated target device, it must be redeployed. For modular devices, VLAN definitions can be configured during redeployment, however the strict checking to match the VLAN attributes is disabled. To redeploy profile(s): 1. On the Configuration > Profiles page, select the profile(s) that are 'Deployed' and/or 'Modified' ( deploy . ) and click Re- 2.
Delete Profiles The existing 'unassigned' profile(s) can be deleted from the Configuration > Profiles page: NOTE: ● An assigned or deployed profile can be deleted from the Profile portal only if it is unassigned. ● Deleting of an unassigned profile that had identities reserved, returns those identities to the Identity pool they came from. It is recommended to wait for 10 minutes to use these reclaimed identities for future reservations and deployments. To delete the unassigned profiles: 1.
11 Managing the device configuration compliance By selecting OpenManage Enterprise > Configuration > Configuration Compliance, you can create configurationcompliance baselines by using the built-in or user-created compliance templates. You can create a compliance template from an existing deployment template, reference device, or by importing from a file. To use this feature, you must have the Enterprise level license of OpenManage Enterprise and iDRAC for servers.
Manage compliance templates Use compliance template to create compliance baselines and then periodically check the configuration compliance status of devices that are associated with the baseline. See Managing the device configuration compliance on page 83. You can create compliance templates by using deployment template, reference device, importing from a file. See Manage compliance templates on page 84.
Create a compliance template from reference device To use the configuration properties of a device as a template for creating configuration baseline, the device must be already onboarded. See Onboarding devices on page 108. 1. Click Configuration > Configuration Compliance > Template Management > Create > From Reference Device. 2. In the Create Compliance Template dialog box, enter a name and description for the compliance template. 3.
● If there is a use case of frequent template edits, it is recommended that you associate a maximum of 100 devices per baseline for optimal performance. 1. On the Compliance Templates page, select the corresponding check box, and then click Edit. 2. On the Template Details page, the configuration properties of the compliance template is listed. 3. Expand the property you want to edit, and then enter or select data in the fields. a. To enable the property, select the check box, if not already enabled. 4.
collected. Also, on the Configuration Compliance page a progress bar indicating the progress of Inventory job appears alongside the respective baseline. Related information Managing the device configuration compliance on page 83 Remove a configuration compliance baseline on page 88 Edit a configuration compliance baseline You can edit the devices, name, and other properties associated with a configuration baseline.
To view the drifted attributes of a noncompliant target device, select the device and click View Report. The Compliance Report of the respective target device lists the attribute names with the expected and current values of the attributes. To remediate one or more noncompliant devices: 1. Select Configuration > Configuration Compliance. 2. From the list of configuration compliance baselines, select the corresponding check box, and then click View Report. 3.
12 Monitoring device alerts By clicking the OpenManage Enterprise menu, and selecting items under Alerts, you can: ● Monitor alerts by: ● ● ● ● ○ Acknowledge alerts on page 90 ○ Ignore alerts on page 90 ○ View archived alerts on page 91 and Download archived alerts on page 91 Create and manage alert policies. See Alert policies on page 91. View alert definitions. See Alert definitions on page 98. Hide and display acknowledged alerts. See Customize the alert display on page 146.
● SEVERITY indicates the severity of an alert. ● ACKNOWLEDGE displays a tick mark when an alert is viewed and acknowledged. The total number of alerts generated is also displayed in the header of OpenManage Enterprise. See OpenManage Enterprise Graphical User Interface overview on page 32. ● Click the hyper-linked device name under SOURCE NAME to view and configure device properties that generated the alert. See Viewing and configuring devices on page 48.
The alert is deleted. The total number of alerts displayed in the header row of OpenManage Enterprise is decremented. Related concepts View the alert logs on page 89 Related information Monitoring device alerts on page 89 View archived alerts At a time, a maximum of 50,000 alerts can be generated and viewed by using OpenManage Enterprise.
NOTE: Previous alert policies won't get implemented post upgrade until the Time Interval check box is enabled. See Edit alert policies on page 97. By clicking OpenManage Enterprise > Alerts > Alert Policies, you can: ● Automatically trigger actions based on the input from an alert. ● Send your alerts to email address, phone, SNMP traps, and perform device power control actions such as turning on or turning off a device when an alert of a predefined category is generated.
Related tasks Delete alert policies on page 98 Disable alert policies on page 97 Enable alert policies on page 97 Edit alert policies on page 97 Create alert policies on page 93 Automatic refresh of MX7000 chassis on insertion and removal sleds OpenManage Enterprise can almost instantly reflect the addition or removal of sleds after a standalone or a lead MX7000 chassis is discovered or onboarded.
3. In the Category section, the Built-in and the imported third-party MIBs are listed. By default, the categories are displayed but not applied. You can select the All check box to apply the alert policy to all the available categories or manually select the categories. To view sub-categories under each category, expand the category: a. Click Next. 4. In the Target section, add devices or groups. See Select target devices and device groups on page 104.
Forward audit logs to remote Syslog servers To monitor all the audit logs of OpenManage Enterprise from Syslog servers, you can create an alert policy. All the audit logs such as user login attempts, creation of alert policies, and running different jobs can be forwarded to Syslog servers. To create an alert policy to forward audit logs to Syslog servers: 1. Select Alerts > Alert Policies > Create. 2.
5. Select the Use SSL check box to secure your SMTP transaction. 6. Click Apply. 7. To reset the settings to default attributes, click Discard. To configure the SNMP alert forwarding configuration: 1. 2. 3. 4. 5. 6. 7. 8. Expand SNMP Alert Forwarding Configuration. Select the ENABLED check box to enable the respective SNMP traps to send alerts in case of predefined events. In the DESTINATION ADDRESS box, enter the IP address of the destination device that must receive the alert.
iii. Click Finish 3. To edit a remote command setting, select the command, and then click Edit. 4. To delete a remote command setting, select the command, and then click Delete. Enable alert policies You can enable an alert policy, only if disabled. Enable an alert policy while creating an alert policy by selecting the Enable Policy check box in the Name and Description section. See Create alert policies on page 93.
Delete alert policies To delete an alert policy, select the check box corresponding to the alert policy and click Delete. The alert policy is deleted and removed from the Alert Policies table. NOTE: You can delete multiple alert policies at a time by selecting the respective check boxes. To select or clear all the check boxes, select the check box in the header row next to ENABLED.
13 Manage audit logs Audit logs lists the actions that were performed on the devices monitored by OpenManage Enterprise. Log data help you or Dell EMC Support teams in troubleshooting and analysis. The audit log files can be exported to the CSV file format. See Export all or selected data on page 47. NOTE: To perform any tasks on OpenManage Enterprise, you must have necessary user privileges. See Role-based OpenManage Enterprise user privileges on page 14.
Forward audit logs to remote Syslog servers To monitor all the audit logs of OpenManage Enterprise from Syslog servers, you can create an alert policy. All the audit logs such as user login attempts, creation of alert policies, and running different jobs can be forwarded to Syslog servers. To create an alert policy to forward audit logs to Syslog servers: 1. Select Alerts > Alert Policies > Create. 2.
14 Using jobs for device control NOTE: To perform any tasks on OpenManage Enterprise, you must have necessary user privileges. See Role-based OpenManage Enterprise user privileges on page 14. NOTE: Each job type is limited to devices that: ● The user has permissions to access. ● Have the ability to complete the required action.
Table 20. Job status and description (continued) Job Status Description Completed with errors Job run was partially successful and was completed with errors. Failed Job run was unsuccessful. Stopped Job run was interrupted by the user. A job can belong to any one of the following types: Table 21. Job Types and description Job Type Description Health Checks the health status of the devices. See Device health statuses on page 37. Inventory Creates inventory report of the devices.
2. In the Blink Devices Wizard dialog box: a. In the Options section: i. In the Job Name box, enter a job name. ii. From the Blink LED Duration drop-down menu, select options to blink the LED for a set duration, turn on, or to turn off. iii. Click Next. b. In the Target section, select the target devices and click Next. See Select target devices and device groups on page 104. c. In the Schedule section, run the job immediately or schedule for a later point of time.
c. In the Arguments box, enter the command. Up to 100 commands can be typed with each command required to be on a new line. NOTE: The commands in the Arguments box are run one at a time. d. Click Next. A green tick mark next to Options indicates that the necessary data is provided. 3. In the Target section, select the target devices and click Next. See Select target devices and device groups on page 104. 4. In the Schedule section, run the job immediately or schedule for a later time.
15 Discovering devices for monitoring or management By clicking OpenManage Enterprise > Monitor > Discovery, you can discover devices in your data center environment to manage them, improve their usability, and improve resource availability for your business-critical operations. The Discovery page displays the number of devices discovered in task and information about the status of discovery job for that device. The job statuses are Queued, Completed, and Stopped.
• • • • • • • • • • • Globally excluding devices Specify discovery mode for creating Create customized device discovery Specify discovery mode for creating Create customized device discovery Specify discovery mode for creating Specify discovery mode for creating Create customized device discovery Create customized device discovery Specify discovery mode for creating Delete a device discovery job a server discovery job job protocol for servers –Additional settings for discovery protocols a chassis discover
NOTE: If there are any changes in the server IP address or SSL certificate, the server reinitiates contact with OpenManage Enterprise. 4. The Monitor > Server Initiated Discovery page lists the servers that establish contact with the console. Also, the servers whose credentials have been added in the console, but which are yet to initiate contact are also listed.
WARNING: A maximum of 8,000 devices can be managed by OpenManage Enterprise. Hence, do not specify large networks that have devices more than the maximum number of devices supported by OpenManage Enterprise. It may cause the system to abruptly stop responding. NOTE: When discovering a large number of devices, avoid creating multiple discovery jobs using individual IP address and instead use IP range of the devices. ● To discover devices by importing ranges from the .csv file.
● If administrator-level credentials are provided during discovery, the servers are onboarded (the device status is displayed as "managed" in the All Devices view). ● If lower privileged credentials are provided during discovery, the servers are not onboarded (the status is displayed as "monitored" in the All Devices view). ● If the console is also set as a trap receiver on the servers then their Onboarding status is indicated as "managed with alerts". ● Error: Indicates an issue in onboarding the device.
Protocol support matrix for discovering devices The following table provides information about the supported protocols for discovering devices. NOTE: The functionality of the supported protocols to discover, monitor, and manage the PowerEdge YX1X servers with iDRAC6 is limited. See Generic naming convention for Dell EMC PowerEdge servers on page 164 for more information. Table 22.
Edit a device discovery job You can edit only one device discovery job at a time. 1. Select the check box corresponding to the discovery job you want to edit, and then click Edit. 2. In the Create Discovery Job dialog box, edit the properties. For information about the tasks to be performed in this dialog box, see Creating device discovery job. Related information Discovering devices for monitoring or management on page 105 Run a device discovery job NOTE: You cannot rerun a job that is already running.
Globally excluding devices NOTE: To perform any tasks on OpenManage Enterprise, you must have necessary user privileges. See Role-based OpenManage Enterprise user privileges on page 14. NOTE: Currently, you cannot exclude a device by using its hostname, but exclude only by using its IP address or FQDN. When discovering device(s) from all the available devices, you can exclude certain device(s) from getting monitored by OpenManage Enterprise by doing the following: 1.
1. From the Device Type drop-down menu, select SERVER. 2. When prompted, select: ● Dell iDRAC: To discover by using iDRAC. ● Host OS: To discover by using an VMware ESXi, Microsoft Windows Hyper-V, or Linux operating system. ● Non-Dell Servers (via OOB): To discover third party servers by using IPMI. 3. Click OK. Based on your selection, the fields change under Settings. 4. Enter the IP address, host name, or IP range associated with the protocol in IP/Hostname/Range. 5.
NOTE: For sudo accounts to work, the server(s) /etc/sudoer file must be configured to use NOPASSWD. 4. To Discover using ESXi (VMware) a. In the Credentials section, enter User Name and Password. b. In the Connection Settings section: ● In the Retries box, enter the number of repeated attempts that must be made to discover a server. ● In the Timeout box, enter the time after which a job must stop running. ● Enter in the Port box to edit the port number. By default, 443 is used to connect to the device.
e. Select the Enable Certificate Authority (CA) check check box. 4. To discover IO modules, select the Discover IO Modules with chassis check box. NOTE: Applicable only for the CMC VRTX, M1000e, and FX2 chassis (models FN2210S, FN410T and FN410S). For the MX7000 chassis, the IO modules are automatically detected. NOTE: Only the IO Modules with Standalone, PMUX (Programmable MUX), VLT (Virtual Link Trunking) Modes are discoverable. Full switch and Stacked Modes will not be discovered. a.
Create customized device discovery job protocol HTTPS storage devices –Additional settings for discovery protocols In the Additional Settings dialog box: 1. Enter username and password of the PowerVault ME to be detected. 2. In the Connection Settings section: a. In the Retries box, enter the number of repeated attempts that must be made to discover a server. b. In the Timeout box, enter the time after which a job must stop running. c. Enter in the Port box to edit the port number.
Delete a device discovery job NOTE: A device can be deleted even when tasks are running on it. Task initiated on a device fails if the device is deleted before the completion. To delete a device discovery job: 1. Select the check box corresponding to the discovery job you want to delete, and then click Delete. 2. When prompted indicating if the job must be deleted, click YES. The discovery jobs are deleted and a message is displayed in the lower-right corner of the screen.
16 Managing device inventory NOTE: To perform any tasks on OpenManage Enterprise, you must have necessary user privileges. See Role-based OpenManage Enterprise user privileges on page 14. By clicking OpenManage Enterprise > Monitor > Inventory, you can generate a device inventory report to better manage your data center, reduce maintenance, maintain minimum stock, and reduce operational costs.
● Select the Collect configuration inventory check box to generate an inventory of the configuration compliance baseline. ● Select the Collect driver inventory check box to collect driver inventory information from the Windows server. Also, to install the Inventory Collector and Dell System Update on the Windows server if these components are not available on the server. NOTE: ● 'Collect driver inventory' applies only to devices discovered as 64-bit Windows servers.
Related information Managing device inventory on page 118 Edit an inventory schedule job 1. Click Edit. 2. In the Inventory Schedule dialog box, edit the inventory job name in Inventory Job Name. See Create an inventory job on page 118. The inventory schedule job is updated and displayed in the table.
17 Manage the device warranty NOTE: To perform any tasks on OpenManage Enterprise, you must have necessary user privileges. See Role-based OpenManage Enterprise user privileges on page 14. By clicking OpenManage Enterprise > Monitor > Warranty, you can view the warranty statuses of all the devices that are monitored by OpenManage Enterprise. You can also export selected or all data to an Excel sheet for the statistical and analytical purposes.
● Select the check box corresponding to the device. In the right pane, warranty status and other important details of the device such as the service level code, service provider, the warranty start date, the warranty end date, and so on are displayed. ● Expired warranties can be renewed by clicking Dell Warranty Renewal for Device, which redirects you to the Dell EMC support site allowing you to manage your device warranty.
18 Reports By clicking OpenManage Enterprise > Monitor > Reports, you can build customized reports to view device details at depth. Reports enables you to view data about the devices, jobs, alerts, and other elements of your data center. Reports are built-in, and user-defined. You can edit or delete only the user-defined reports. Definitions and criteria used for a built-in report cannot be edited or deleted. A preview about the report you select from the Reports list is displayed in the right pane.
Run reports NOTE: To perform any tasks on OpenManage Enterprise, you must have necessary user privileges. See Role-based OpenManage Enterprise user privileges on page 14. When you run a report, the first 20 rows are displayed and paginated results can be paged through. To view all the rows at one time, download the report. To edit this value, see Export all or selected data on page 47. Data displayed in the output cannot be sorted because it is defined in the query used to build a report.
Edit reports Only user-created reports can be edited. 1. Select the report and click Edit. 2. In the Report Definition dialog box, edit the settings. See Creating reports. 3. Click Save. The updated information is saved. An audit log entry is made whenever you generate, edit, delete, or copy a report definition. NOTE: While editing a customized-report, if the category is changed, the associated fields are also removed.
● Report definition must have at least one field and one category ● For reports having Device and Alert as categories, device name or device group must be one of the mandatory fields By default, Devices is selected as the category, and device name, device Service Tag, and device model columns are displayed in the working pane. If you select any other category while editing a report criteria, a message is displayed indicating that the default fields will be removed.
NOTE: When selected, the filters of an existing query criteria is copied only virtually to build a new query criteria. The default filters associated with an existing query criteria is not changed. The definition (filters) of a built-in query criteria is used as a starting point for building a customized query criteria. For example: 1. Query1 is a built-in query criteria that has the following predefined filter: Task Enabled=Yes. 2.
19 Managing MIB files NOTE: To perform any tasks on OpenManage Enterprise, you must have necessary user privileges. See Role-based OpenManage Enterprise user privileges on page 14. Third party tools in your data center may generate alerts that are vital for your operations. Such alerts are stored in the Management Information Base (MIB) files defined and understood by respective vendor tools.
● Only one MIB file can be imported at a time. 1. Click MIB > Import MIB. 2. In the Import MIB dialog box, in the Upload MIB Files section, click Choose File to select a MIB file. If the MIB has import statements that are resolved by external MIBs, a message is displayed. a. Click Resolve Types. Resolve the MIB types. See Remove MIB files on page 130. b. Click Finish. If the MIB file is Dell EMC owned, a message indicates that the MIB is shipped with the product and cannot be modified. 3. Click Next. 4.
Remove MIB files NOTE: You cannot remove a MIB file that has trap definitions used by any of the alert policies. See Alert policies on page 91. NOTE: Events that are received before removing a MIB will not be affected by the associated MIB removal. However, events generated after the removal will have unformatted traps. 1. In the MIB FILENAME column, expand the folder, and select the MIB files. 2. Click Remove MIB. 3. In the Remove MIB dialog box, select the check boxes of the MIBs to be removed. 4.
20 Managing OpenManage Enterprise appliance settings NOTE: To perform any tasks on OpenManage Enterprise, you must have necessary user privileges. See Role-based OpenManage Enterprise user privileges on page 14. NOTE: For information about supported browsers, see the OpenManage Enterprise Support Matrix available on the support site.
Configure OpenManage Enterprise network settings NOTE: To perform any tasks on OpenManage Enterprise, you must have necessary user privileges. See Role-based OpenManage Enterprise user privileges on page 14. 1. To only view the current network settings of all the active network connections of OpenManage Enterprise such as DNS domain name, FQDN, and IPv4 and IPv6 settings, expand Current Settings. 2.
NOTE: You cannot enable, disable, or delete the admin/system/root users. You can change the password by clicking Edit in the right pane. ● View details about the logged-in users, and then end (terminate) a user session. ● Manage Directory Services. ● Import and manage users from Active Directory. By default, the list of users is displayed under Users. The right pane displays the properties of a user name that you select in the working pane.
Table 26.
For more information, see Role-based OpenManage Enterprise user privileges on page 14. By default, the Enabled check box is selected to indicate that the user privileges currently being set up are enabled for a user. 3. Click Finish. A message is displayed that the user is successfully saved. A job is started to create a new user. After running the job, the new user is created and displayed in the list of users. Edit OpenManage Enterprise user properties 1.
Related references Disable OpenManage Enterprise users on page 135 Enable OpenManage Enterprise users on page 135 Related information Manage OpenManage Enterprise users on page 132 Import AD and LDAP groups NOTE: The users without Administrator rights cannot enable or disable the Active Directory (AD) and Lightweight Directory Access Protocol (LDAP) users. NOTE: Before importing AD groups in OpenManage Enterprise, you must include the user groups in a UNIVERSAL GROUP while configuring the AD. 1.
Related information Manage OpenManage Enterprise users on page 132 Directory services integration in OpenManage Enterprise Directory Services enables you to import directory groups from AD or LDAP for use on the console. OpenManage Enterprise supports integration of the following directory services: 1. 2. 3. 4. Windows Active Directory Windows AD/LDS OpenLDAP PHP LDAP Pre-requisites/supported attributes for LDAP Integration Table 27.
To use the Directory Services: ● Add a directory connection. See Add or edit Active Directory groups to be used with Directory Services on page 138. ● Import directory groups and map all users in the group to a specific role. See Import AD and LDAP groups on page 136. ● For DM users, edit the directory group to add the groups the DM can manage. See Add and edit OpenManage Enterprise users on page 134. Add or edit Active Directory groups to be used with Directory Services 1.
NOTE: To create an AD user group by using Directory Services, see Add or edit Active Directory groups to be used with Directory Services on page 138. a. Enter a desired name for the LDAP directory. b. Select the Domain Controller Lookup method: ● DNS: In the Method box, enter the domain name to query DNS for the domain controllers. ● Manual: In the Method box, enter the FQDN or the IP address of the domain controller.
Related information Managing OpenManage Enterprise appliance settings on page 131 Manage OpenManage Enterprise users on page 132 OpenManage Enterprise login using OpenID Connect providers OpenManage Enterprise 3.5 provides a new way to log in using OpenID Connect (OIDC) providers. OpenID Connect providers are the identity and user management software that allow users to securely access applications. Currently, OpenManage Enterprise provides support for PingFederate and Keycloak.
Add an OpenID Connect provider to OpenManage Enterprise Adding, enabling, and registering an OpenID Connect provider (Keycloak or PingFederate) allows for an authorized client login to OpenManage Enterprise. This generates a Client ID. To add an OpenID Connect provider to OpenManage Enterprise, go to the Application Settings > Users > OpenID Connect Providers page and do the following: NOTE: Only a maximum of four OpenID Connect provider clients can be added. 1.
Configure an OpenID Connect provider policy in Keycloak for rolebased access to OpenManage Enterprise To enable OpenManage Enterprise OpenID Connect login using Keycloak, you must first add and map a scope dxcua to the Client ID and define the user privileges as follows: NOTE: The Discovery URI specified in the OpenID Connect provider configuration wizard should have a valid endpoint of the provider listed. 1.
Enable OpenID Connect providers If an OpenID Connect provider's login was not enabled at the time when it was added to the appliance, then to activate the login you must 'enable' it in the appliance. On the Application Settings > Users > OpenID Connect providers page do the following: 1. Select the OpenID Connect provider(s). 2. Click Enable. Enabling the OpenID Connect providers in OpenManage Enterprise allows the authorized client access tokens to login to the appliance.
Assigning a webserver certificate to OpenManage Enterprise using the Microsoft Certificate Services 1. Generate and download the Certificate Signing Request (CSR) in OpenManage Enterprise. See Generate and download the certificate signing request on page 143 2. Open a web session to the certification server (https://x.x.x.x/certsrv) and click on the Request a certificate link . 3. On the Request a Certificate page, click on the submit an advanced certificate request link. 4.
Manage Console preferences NOTE: To perform any tasks on OpenManage Enterprise, you must have the necessary user privileges. See Role-based OpenManage Enterprise user privileges on page 14. By clicking OpenManage Enterprise > Application Settings > Console Preferences, you can set the default properties of the OpenManage Enterprise GUI. For example, default time after which a device health is automatically checked and updated on the dashboard, and preferred settings used for discovering a device.
● Automatic: To allow servers with iDRAC Firmware version 4.00.00.00, which are on the same network as the console, to be discovered automatically by the console. ● Manual: For the servers to be discovered by the user manually. ● Click Apply to save the changes or click Discard to reset the settings to the default attributes. 5.
Configure SMTP, SNMP, and Syslog alerts By clicking OpenManage Enterprise > Application Settings > Alerts, you can configure the email (SMTP) address that receives system alerts, SNMP alert forwarding destinations, and Syslog forwarding properties. To manage these settings, you must have the OpenManage Enterprise administrator level credentials. To configure and authenticate the SMTP server that manages the email communication between the users and OpenManage Enterprise: 1. Expand Email Configuration. 2.
5. By default, the SNMP port number for the incoming traps is 161. Edit to change the port number. 6. Click Apply. The SNMP credentials and settings are saved. 7. To reset the settings to default attributes, click Discard. NOTE: If SNMPv3 alert settings are configured before upgrading the appliance, you have to reconfigure the settings by providing the username, authentication passphrase, and privacy passphrase to continue receiving the alerts.
For more information see Update settings in OpenManage Enterprise on page 149 2. Download and install more plugins (extensions) such as the Power Manager plugin to enhance the functionality of the appliance. For more information about the installation of plugins, see plugin NOTE: The OpenManage Enterprise Advanced license is required for the plugins to be fully functional after installation.
Update OpenManage Enterprise Based on the update settings (Application Settings > Console and Extensions > Update Settings), your existing OpenManage Enterprise can be updated automatically or manually from the Dell.com site directly or from an already downloaded update package in the network share.
Update from Dell.com Your existing OpenManage Enterprise can be updated online, either automatically or manually, from Dell.com (https:// downloads.dell.com/openmanage_enterprise). Online update pre-requisites: ● Update settings Where to check for updates should be specified as Dell.com. For more information, refer Update settings in OpenManage Enterprise on page 149. ● You must ensure that the OpenManage Enterprise appliance can access Dell.com and the expected update.
● Ensure to take a VM snapshot of the console as a backup in case something unexpected occurs. (Allocate more downtime for this, if necessary). ● If the upgrade fails, the appliance would restart. It is recommended to revert the VM snapshot and upgrade again. ● Adding a second network interface should be done only after the completion of the post-console upgrade tasks. Attempt to add a second NIC while the post-upgrade task is in progress would be ineffective.
The details of the number of users logged in to OpenManage Enterprise, tasks in progress, and schedule jobs are displayed in the confirmation window. To confirm the installation, select I agree that I have captured the snapshot of the OpenManage Enterprise appliance prior to the upgrade option, and then click Confirm Install. The status of installation is displayed. Disable a plugin Disables all the functionality of the plugin on OpenManage Enterprise.
i. Script ii. RACADM iii. IPMI Tool d. If you select Script, do the following: i. ii. iii. iv. In the IP Address box, enter the IP address. Select the authentication method: Password or SSH Key. Enter the user name and password or the SSH Key. In the Command box, type the commands. ● Up to 100 commands can be typed with each command required to be on a new line. ● Token substitution in scripts is possible. See Token substitution in remote scripts and alert policy on page 161 v. Click Finish. e.
Enable or disable alert notifications for OpenManage Mobile By default, OpenManage Enterprise is configured to send alert notifications to the OpenManage Mobile application. However, alert notifications are sent from OpenManage Enterprise only when a OpenManage Mobile user adds OpenManage Enterprise to the OpenManage Mobile application. NOTE: The administrator rights are required for enabling or disabling alert notifications for OpenManage Mobile.
1. Click OpenManage Enterprise > Application Settings > Mobile. 2. Select the check box corresponding to the subscriber name and click Delete. 3. When prompted, click Yes.
View information about OpenManage Mobile subscribers After an OpenManage Mobile user successfully adds OpenManage Enterprise, the user is added to the Mobile Subscribers table in OpenManage Enterprise. To view information about the mobile subscribers, in OpenManage Enterprise, click Application Settings > Mobile. You can also export the information about mobile subscribers to a .CSV file by using the Export drop-down list.
Table 30. Troubleshooting OpenManage Mobile (continued) Problem Reason Resolution ● Verify if the network cables are connected. ● Verify the IP address and DNS server settings. ● Verify if the firewall is configured to allow outbound traffic. ● Verify if the ISP network is operating normally. Proxy settings are incorrect. Set proxy host, port, username, and password as required. Message Forwarding Service is temporarily unavailable. Wait for the service to become available.
21 Other references and field descriptions Definitions about some of the commonly displayed fields on the OpenManage Enterprise Graphical User Interface (GUI) are listed and defined in this chapter. Also, other information that is useful for further reference is described here.
NOTE: By default, the job scheduler clock is reset at 12:00 A.M. everyday. The cron format does not consider the job creation time while calculating the job frequency. For example, if a job is started at 10:00 A.M. to run after every 10 hours, the next time the job runs is at 08:00 P.M. However, the subsequent time is not 06:00 A.M. next day but 12:00 A.M. This is because the scheduler clock is reset at 12:00 A.M. everyday. Alert categories after EEMI relocation Table of EEMI relocations Table 31.
Table 31.
Unblock the FSD capability You can unblock the FSD capability through the TUI screen. 1. Navigate to the TUI main menu. 2. On the TUI screen, to use the FSD option, select Enable Field Service Debug (FSD) Mode. 3. To generate a new FSD unblock request, on the FSD Functions screen, select Unblock FSD Capabilities 4. To determine the duration of the debug capabilities being requested, select a start and end date. 5.
While the invoke command is run, OpenManage Enterprise can start an SSH daemon. The external SSH client can attach with OpenManage Enterprise for debugging purposes. Disable FSD After you invoke a debug capability on a console, it continues to operate until the console is restarted, or the debug capability is stopped. Else, the duration determined from the start and end date exceeds. 1. To stop the debug capabilities, on the FSD Functions screen, select Disable Debug Capabilities. 2.
NOTE: For the complete list of devices in the SC, MD, ME, and XC series, refer https://topics-cdn.dell.com/pdf/dellopenmanage-enterprise_compatibility-matrix2_en-us.pdf Generic naming convention for Dell EMC PowerEdge servers To cover a range of server models, the PowerEdge servers are now be referred to using the generic naming convention and not their generation. This topic explains how to identify the generation of a PowerEdge server that are referred to using the generic naming convention.
