Dell EMC OpenManage Enterprise Version 3.3.
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 - 2019 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries.
Contents 1 About Dell EMC OpenManage Enterprise........................................................................................ 9 New in this release............................................................................................................................................................... 10 Other information you may need....................................................................................................................................... 10 Contacting Dell EMC....
Create or edit a Query device group...........................................................................................................................38 Adding or editing devices in a Static child group.......................................................................................................40 Rename child groups of Static or Query Dynamic groups....................................................................................... 40 Clone a Static or Query group.......................
Edit a chassis template....................................................................................................................................................... 60 Edit IOA template................................................................................................................................................................ 60 Edit network properties..................................................................................................................................
Alert policies......................................................................................................................................................................... 79 Create alert policies.......................................................................................................................................................80 Enable alert policies.................................................................................................................................
16 Manage the device warranty..................................................................................................... 104 View and renew device warranty.....................................................................................................................................104 17 Reports...................................................................................................................................106 Run reports......................................................
Install an Extension.......................................................................................................................................................129 Disable an extension.................................................................................................................................................... 129 Uninstall an extension..............................................................................................................................................
1 About Dell EMC OpenManage Enterprise OpenManage Enterprise is a systems management and monitoring application that provides a comprehensive view of the Dell EMC servers, chassis, storage, and network switches on the enterprise network. With OpenManage Enterprise, a web-based and one‑to‑many systems management application, you can: • • • • • • • • • • • Discover and manage devices in a data center environment. Create and manage OpenManage Enterprise users. Group and manage devices.
• • • • • Manage the device warranty Reports Managing MIB files Role-based OpenManage Enterprise user privileges Directory services integration in OpenManage Enterprise Topics: • • • • New in this release Other information you may need Contacting Dell EMC OpenManage Enterprise Advanced license New in this release • • • • • Support for multihoming with the ability to work with multiple-segmented networks New Secure API to collect device warranty Support for YX5X servers (See Generic naming convention fo
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.
• • • 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. NOTE: To access features of the OpenManage Enterprise such as the Virtual Console Support function, which depends on the iDRAC, you would need the iDRAC enterprise license. For more details, see the iDRAC documentation available on the support site.
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).
OpenManage Enterprise features User levels for accessing OpenManage Enterprise Admin Device Manager Viewer Manage jobs Y Y N Create monitoring policies Y Y N Deploy operating system Y Y N Power control Y Y N Manage reports Y Y N Refresh inventory Y Y N Set up the OpenManage Enterprise appliance Y N N Manage discovery Y N N Manage groups Y N N Set up security Y N N Manage traps Y N N Select targets for autodeployment Y N N Related tasks Deploy and manage Op
User with this role... Has the following user privileges Viewer • • • Can only view information displayed on OpenManage Enterprise and run reports. By default, has read-only access to the console and all groups. Cannot run tasks or create and manage policies. NOTE: • If a Viewer or DM is changed to an Administrator, they get the full Administrator privileges. If a Viewer is changed to a DM, the Viewer gets the privileges of a DM.
3 Deploy and manage OpenManage Enterprise Dell EMC OpenManage Enterprise is provided as an appliance that you can deploy 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 extensions.
Minimum system requirements for deploying OpenManange 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.
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.
• 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. Upon login to the TUI, and after accepting the EULA and changing the admin password, the adapter will show up as DISABLED and must be configured by the user. • Upon an install or an upgrade to OpenManage Enterprise version 3.3.
4. Click Next on the initial Before You Begin page. 5. On the Specify Name and Location page • • provide the Virtual machine name. (Optional) Select the Store the virtual machine in a different location check box to activate the Location field, and then browse and navigate to capture a folder location where the VM would be stored. NOTE: If the check box is not selected, the VM is stored in the default folder. 6. Click Next 7. On the Specify Generation page, select Generation 1 and click Next.
OpenManage Enterprise appliance is now deployed by using the KVM. To get started with OpenManage Enterprise, see Log in to OpenManage Enterprise. Deploy OpenManage Enterprise programmatically OpenManage Enterprise can be deployed programmatically (using a script) on VMWare ESXi version 6.5 or later. NOTE: Programmatic/scripted deployment is only supported using the primary interface.
NOTE: The ovftool command must be run with the --X:injectOvfEnv and --powerOn flags because they are required for programmatic deployment. After the ovftool command is run, the manifest validates and the deployment begins.
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
• • Choose Network Adapter menu lists all the available network adapters. Clicking on a network adapter will display its current settings. Set Networking Parameters • Choose Network Adapter menu lists all the available networks adapters. Clicking on a network adapter allows you to reconfigure its network parameters and apply the changes to the appropriate interface. NOTE: • By default, only IPv4 is enabled on primary network interface with a private static IP in the appliance.
• To configure IPv6, ensure that it is already configured by a vCenter server. • In an IPv6 environment, when a Router Advertisement is configured for stateless configuration of multiple IPv6 IPs on a port, iDRAC supports a maximum of 16 IPs addresses. In such a case, OpenManage Enterprise displays only the last discovered IP and uses that IP as the out-of-band interface to iDRAC. • By default, the last discovered IP of a device is used by OpenManage Enterprise for performing all operations.
Tasks Recommended frequency of running the tasks Tasks whether precanned? Inventory OpenManage Enterprise provides a precanned task that automatically refreshes inventory once a day. Yes. You can disable this feature. Devices that are monitored by OpenManage Enterprise. Warranty OpenManage Enterprise Yes. You can disable this feature. Devices that are monitored by provides a precanned task that OpenManage Enterprise. automatically refreshes warranty once a day.
Port Number Protocol Port Type Maximum Source Encryption Level Direction Destination Usage firmware DUPs, and FSD process. OpenManage Enterprise appliance Out CIFS share To import firmware catalogs from CIFS share. 162* SNMP UDP None Management station In/Out OpenManage Enterprise appliance Event reception through SNMP. The direction is 'outgoing' only if using the Trap forward policy.
Port Number Protocol Port Type Maximum Source Encryption Level Direction Destination Usage 69 TFTP UDP None In Management station For updating CMC firmware CMC * Port can be configured up to 499 excluding the port numbers that are already allocated. NOTE: In an IPv6 environment, you must enable IPv6 and disable IPv4 in the OpenManage Enterprise appliance to ensure all the features work as expected. Use case links for the supported protocols and ports in OpenManage Enterprise Table 10.
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 update are displayed at more than one place.
• • • • • acknowledged alerts, see Customize the alert display. Deleting the alerts reduces the count. For information about symbols that are used to indicate severity statuses, see Device health statuses. Click a severity symbol to view all events in that severity category on the Alerts page. To view all the events, click All events. See Managing device alerts. H—Total number of device warranties in Critical (expired) and in Warning (expiring soon) statuses. See Managing device warranty.
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.
Viewing and configuring devices. To filter data, click Advanced Filters. Export data into Excel, CSV, HTML, or PDF format. See Export all or selected data. For more information about a Donut chart, see Donut chart and Device health statuses. To view the summary of devices in a different device group monitored by OpenManage Enterprise, select from the Device Groups drop-down menu.
Manage the device compliance baseline by using the OpenManage Enterprise dashboard On the OpenManage Enterprise dashboard page, in the Widgets section, the Configuration section displays the number of configuration compliance baselines that do not comply with the properties of the template it is compared against. To view a list of configuration compliance baselines that drift from the template properties, click Configuration.
• • • Servers: Dell iDRAC servers, Linux servers, Non-Dell servers, OEM servers, and Windows servers Storage Devices: Dell Compellent storage Arrays, PowerVault MD storage arrays, and PowerVault ME storage arrays Discovery Groups: Groups that map to the range of a discovery task. Cannot be edited or deleted because the group is controlled by the discovery job where the include/exclude condition is applied. See Discovering devices for monitoring or management.
NOTE: The compliance level of the selected device in indicated by a Donut chart. When more than one device is associated with a baseline, the status of a device with the least compliance level to the baseline is indicated as the compliance level of that baseline.
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.
• 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. For example, a query is run to discover servers that are assigned to the Finance department. However, the Query Groups have a flat structure without any hierarchy. NOTE: Static and Query groups: • Cannot have more than one parent group. Meaning, a group cannot be added as a sub-group under its parent group.
4. In the Query Criteria Selection dialog box, from the Select existing query to copy drop-down menu, select a query, and then select the other filter criteria. See Select a query criteria. 5. Click Finish. The query group is created and listed in line with the parent group in the left pane. NOTE: You cannot add devices directly under Query Groups. You must create child Query groups, and then add devices under the child groups. To edit a Query group: a.
Adding or editing devices in a Static child group By using the Static child groups, you can classify your servers based on their use, configuration, department of use, customers, and so on. You can add or remove devices to the child groups, and then edit, remove, delete, and clone such groups. NOTE: To perform any tasks on OpenManage Enterprise, you must have necessary user privileges. See Role-based OpenManage Enterprise user privileges. 1. Right-click the Static child group, and then click Add Devices.
3. Click Finish. A new group is created and the devices are added to the selected group. NOTE: For creating groups or adding devices to a group, you must follow the parent-child relationship of groups. See Device Groups. Add devices to existing group NOTE: To perform any tasks on OpenManage Enterprise, you must have necessary user privileges. See Role-based OpenManage Enterprise user privileges. 1. From the OpenManage Enterprise menu, under Devices, click All Devices. 2.
Upgrade or downgrade device firmware by using the firmware baseline NOTE: To perform any tasks on OpenManage Enterprise, you must have necessary user privileges. See Role-based OpenManage Enterprise user privileges. You can upgrade or downgrade the firmware version of device(s) on the: • • • All Devices page: Recommended for updating firmware of multiple devices. From the Devices menu, select Devices. Select the devices, click More Actions > Update Firmware.
COMPLIANCE Indicates the significance of the firmware update, based on the compliance status of the individual component. The possible options are: • • • • OK—The current firmware version of the device or component matches the baseline defined in the catalog file. Critical—The current firmware version of the component or device is older than the baseline defined in the catalog file. The update is essential for the proper functioning of the device or component.
• • • • COMPONENT NAME: Component on the device whose firmware version is later than the baseline version. CURRENT VERSION: Current version of the component. ROLLBACK VERSION: Suggested firmware version to which the component can be downgraded. ROLLBACK SOURCE: Click Browse to select a source from where the firmware version can be downloaded. 7. Click Finish. The firmware version is rolled back. NOTE: Currently, the Rollback feature tracks only the version number from which the firmware is rolled back.
• • • • • • • Health State indicates the working state of the device. The health statuses—OK, critical, and warning—are identified by respective color symbols. See Device health statuses. Power State indicates if the device is turned on or off. Connection State indicates whether or not the device is connected to OpenManage Enterprise. Name indicates device name. TYPE indicates the type of device—Server, Chassis, Dell Storage, and Networking switch.
NOTE: However, a single device inventory can be exported only into a .csv format. See Export the single device inventory. NOTE: Only in case of reports, you can export only selected reports at a time and not all the reports. See Export selected reports. 1. To export data, select Export All or Export Selected. A job is created and the data is exported to the selected location. 2. Download the data and perform strategic and statistical analysis, if necessary.
OpenManage Enterprise provides a built-in report to get an overview of devices monitored by OpenManage Enterprise. Click OpenManage Enterprise > Monitor > Reports > Devices Overview Report. Click Run. See Run reports. 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.
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. Extract and download SupportAssist reports NOTE: To perform any tasks on OpenManage Enterprise, you must have necessary user privileges.
A job is created and displayed in the dialog box. The job is also listed on the Job Details. See View the jobs list. 5. Click Finish. The Recent Alerts section displays the job completion status. Start Management application iDRAC of a device 1. Select the check box corresponding to the device. The device working status, name, type, IP, and Service Tag are displayed. 2. In the right pane, click Launch Management Application. The iDRAC login page is displayed. Log in by using the iDRAC credentials.
8 Manage the device firmware By clicking OpenManage Enterprise > Configuration, and selecting: • • • Firmware Compliance: Manage the firmware of devices by using firmware baselines. Deploy: Create templates to define configuration compliance baseline and manage such templates. Configuration Compliance: Create device or device group configuration compliance baseline and manage device configuration.
Related tasks Delete a firmware baseline Topics: • • • • • • Manage firmware Catalogs Create a firmware baseline Delete a firmware baseline Check the compliance of a device firmware against its baseline Edit a firmware baseline Delete a firmware baseline Manage firmware Catalogs Catalogs are bundles of firmware based on device types. All the available catalogs (update packages) are validated and posted to Dell.com.
NOTE: Ensure to enable SMBv1 in the SMB Settings before you begin any firmware tasks which need communication with any chassis or the PowerEdge YX2X and YX3X servers that have iDRAC version 2.50.50.50 and earlier. See Manage Console preferences and Generic naming convention for Dell EMC PowerEdge servers for more information. • NFS 1. In the Share Address box, enter the IP address of the system where the firmware catalog is stored on the network. 2.
Cancel Closes the Certificate Information window without accepting the SSL certificate. Update a firmware catalog The existing firmware catalogs can be updated from the Dell.com site or the Dell Update Packages (DUPs) located in the network share. To update a firmware catalog: 1. On the Catalog Management page, select a catalog. 2. Click the Check for update button that is located in the right pane of the Catalog Management page. 3. Click YES.
create for a BIOS version can be applied to many servers running the same BIOS. Similarly, you can apply two baselines to one device— say, one for the firmware version and the other for BIOS. To create a firmware baseline: 1. Under Firmware, click Create Baseline. 2. In the Create Firmware Baseline dialog box: a) In the Baseline Information section: 1. From the Catalog drop-down menu, select a catalog. 2. To add a catalog to this list, click Add. See Managing firmware Catalogs. 3.
See Viewing device firmware compliance report. View the device firmware compliance report The compliance level of devices in all the available baselines is indicated by a Donut chart on the Firmware page. When more than one device is associated with a baseline, the status of a device with the least compliance level to the baseline is indicated as the compliance level of that baseline.
• The Clear Jobs and iDRAC reset functions are not supported for the devices under an MCM chassis that are in a 'Proxied' onboarding state. For more information on onboarding states, refer Onboarding devices. After you run a firmware compliance report, if the firmware version on the device is earlier than the version on the catalog, the Compliance Report page indicates the device firmware status as Upgrade ( baseline compliance report: or ). To update a device firmware by using the 1.
9 Manage device configuration templates From the OpenManage Enterprise menu, by clicking Configuration > Deploy, you can set the configuration properties such as network properties, and BIOS versions of servers, and chassis by using device configuration templates—predefined templates or custom templates. Templates enable you to optimize your data center resources, Subject Matter Expert (SME) bandwidth, and reduce the cycle time in creating clones and deployments.
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) In the Reference Device section, click Select Device to select the device whose configuration properties must be used for creating the new template. For more information about selecting devices, see Selecting target devices and device groups. NOTE: You can select only one device as a reference device.
1. Select the required custom template check box, and then click Edit. 2. In the Edit Template dialog box: a) In the Template Information section, edit the template name and description. The template type cannot be edited. b) Click Next. c) In the Edit Components section, the template attributes are displayed in: • The Guided view — This view of attributes displays only common attributes, grouped together by function. Attributes from the following categories are shown: 1.
Edit a chassis template Editing chassis templates is possible with OpenManage Enterprise. NOTE: • To edit chassis templates you must have the privileges of an Administrator or a Device manager. For more details, See Role-based OpenManage Enterprise user privileges . To edit a chassis template: 1. Select OpenManage Enterprise > Configuration > Deploy to get a list of templates. 2. Select the check box corresponding to the required chassis template, and click Edit.
• If an MX7000 chassis is removed from group, it has to be rediscovered in OpenManage Enterprise. • Users on the MX7000 chassis are replaced by the users who are configured in the template. • Imported Active Directory settings are replaced with the values in chassis profile. 1. From the list of templates on the Configuration > Deploy page, select the check box corresponding to the template you want to deploy, and then click Deploy Template. 2.
Clone templates 1. From the OpenManage Enterprise menu, under Configuration, click Deploy. A list of available templates is displayed. 2. Select the check box corresponding to the template you want to clone. 3. Click Clone. 4. Enter the name of new template, and then click Finish. The cloned template is created and displayed in the list of templates.
8. Click Next. 9. If the target device is a server, on the Boot to Network ISO page : • • • • • Select the Boot to Network ISO check box. Select CIFS or NFS. Enter the ISO Path of location where the ISO image file is stored. Enter Share IP Address, Workgroup, Username, and password. Click Next. 10. On the Virtual Identities page, click Reserve identities. The assigned virtual identities of the NIC cards of the selected target device are displayed.
Overview of stateless deployment To deploy a device configuration template with virtual identity attributes on target devices, do the following: 1. Create a device template—Click Create Template task under the Deploy tab to create a device template. You can select to create the template from either a configuration file or a reference device. 2. Create an identity pool—Click the Create task under the Identity Pools tab to create a pool of one or more virtual identity types. 3.
Identities that provide a unique virtual identity for FCoE operations. These identities are defined by both MAC address and the FC addresses (that is WWNN and WWPN). WWNN and WWPN identities are required to support boot-from-SAN and for data access using FC and Fibre Channel over Ethernet (FCoE) protocols. OpenManage Enterprise uses the identity pools to automatically assign virtual identities to the device template that is used for deploying a server.
Number of WWPN/WWNN Addresses Select the number of WWPN or WWNN address. The address can be between 1 and 5000. This option is displayed only if the Include FC Identity check box is selected. 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.
Secondary DNS Server Enter the secondary DNS server address. 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 MAC Identities Select the number of virtual MAC identities. The identities can be 1-50. This option is displayed only if the Include ethernet virtual MAC addresses check box is selected. Actions Previous Displays the Pool Information tab. Next Displays the iSCSI tab.
Table 13. Network types Network types Description Bronze General Purpose Used for low priority data traffic.
6. In the Deploy Template: dialog box, under Target: a) Click Select, and then select device(s) in the Job Target dialog box and click Ok. See Selecting target devices and device groups. b) Click Next. 7. In the Boot to Network ISO section: a) Select the Boot to Network ISO check box. This check box is displayed only if the target device is a server. b) Select either CIFS or NFS, and then enter information in the fields such as an .ISO image file path and share location where the .
CAUTION: When using the 'Force migration if the profile removal fails' option, there is a possibility of identities being duplicated if the source device is turned on. 3. Click Migrate Profile. The virtual identities are now reclaimed from the source device and assigned to the target device.
10 Managing the device configuration compliance By selecting OpenManage Enterprise > Configuration > Configuration Compliance, you can create configuration baselines by using the built-in or user-created compliance templates. You can create a configuration compliance template from an existing deploy 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 baseline 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. You can create baseline templates by using deployment template, reference device, importing from a file. See Manage compliance baseline templates.
6. Click Finish. A template creation job is created and run. The newly created compliance baseline template is listed on the Compliance Templates page. Create a compliance baseline by importing from a file 1. Click Configuration > Configuration Compliance > Template Management > Create > Import from File. 2. In the Import Compliance Template dialog box, enter a name for the baseline compliance template. 3.
When you select a template for creating a baseline, the attributes associated with the templates are also selected. However, you can edit the baseline properties. See Edit a configuration compliance baseline. CAUTION: If a template used for a baseline is already associated with another baseline, editing the template properties changes the baseline compliance levels of devices already associated. Read through the Error and Event message displayed and act accordingly.
Related tasks Manage compliance baseline templates Select a query criteria Related information Managing the device configuration compliance Remove a configuration compliance baseline Remediate noncompliant devices You can remediate the devices which are not conforming to the associated baseline by changing the attribute values to match with the associated baseline attributes. To view the drifted attributes, from the device compliance report, click View Report.
11 Monitoring device alerts By clicking the OpenManage Enterprise menu, and selecting items under Alerts, you can: • • • • • Monitor alerts by: • Acknowledge alerts • Ignore alerts • View archived alerts and Download archived alerts Create and manage alert policies. See Alert policies. View alert definitions. See Alert definitions. Hide and display acknowledged alerts. See Customize the alert display. Export all or selected alert data. See Export all or selected data.
• • • • 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. Click the hyper-linked device name under SOURCE NAME to view and configure device properties that generated the alert. See Viewing and configuring devices.
Related concepts View the alert logs Related information Monitoring device alerts View archived alerts At a time, a maximum of 50,000 alerts can be generated and viewed by using OpenManage Enterprise. When 95% of the 50,000 limit (47,500) is reached, OpenManage Enterprise generates an internal message indicating that, when the count reaches 50,000, OpenManage Enterprise will automatically purge 10% (5000) of the archived alerts. The table lists different scenarios involving the alert purging. Table 14.
A tick mark corresponding to an alert policy indicates that the alert policy is enabled. When an alert is received that meets the policy criteria, you can configure the policy to perform actions such as sending email message and enabling SNMP trap forwarding. After prior setting, you can do the following: • Send an email message: 1. Click the EMAIL cell corresponding to the alert policy. 2. In the Alert Actions: Email dialog box, type information about the message to be sent.
1. Click Alert Policies > Create. 2. In the Create Alert Policy dialog box, in the Name and Description section, enter the name and description of the alert policy. a) To enable an alert policy by default, select the Enable Policy check box. b) Click Next. 3. In the Category section, select the All check box to apply the alert policy to all the available categories. By default, the following categories are displayed, but not applied.
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.
3. In the DESTINATION ADDRESS box, enter the IP address of the destination device that must receive the alert. 4. Select the SNMP version type from the SNMP VERSION drop-down menu. Currently, only SNMP1 and SNMP2 versions are supported. 5. In the COMMUNITY STRING box, enter the SNMP community string of the device that must receive the alert. 6. Default port number for SNMP traps=162. Edit if necessary. See Supported protocols and ports in OpenManage Enterprise. 7.
To enable an alert policy, select the check box corresponding to the alert policy and click Enable. The alert policy is enabled and the tick mark indicating that the alert policy is enabled (the ENABLED column) is displayed. NOTE: You can enable 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. NOTE: The Enable button of an alert policy that is already enabled appears grayed-out.
Alert definitions By clicking OpenManage Enterprise > Alerts > Alert Definitions, you can view alerts that are generated for errors or informational purposes. These messages are: • • • • Called as Event and Error messages. Displayed on the Graphical User Interface (GUI), and Command Line Interface (CLI) for RACADM and WS-Man. Saved in the log files for information purpose only. Numbered and clearly defined to enable you implement corrective and preventive actions effectively.
12 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. NOTE: To perform any tasks on OpenManage Enterprise, you must have necessary user privileges. See Role-based OpenManage Enterprise user privileges.
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.
13 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. NOTE: Each job type is limited to devices that: • The user has permissions to access. • Have the ability to complete the required action. This rule is applicable to all tasks such as blink, power control, managing firmware baselines, and managing configuration compliance baseline, where the device selection task is involved.
Job Status Description 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 16. Job Types and description Job Type Description Health Checks the health status of the devices. See Device health statuses. Inventory Creates inventory report of the devices. See Managing device inventory. Device Config Creates device configuration compliance baseline. See Managing the device configuration compliance.
The job is created and listed in the Jobs list and identified by an appropriate status in the JOB STATUS column. 4. If the job is scheduled for a later point of time, but you want to run the job immediately: • • • On the Jobs page, select the check box corresponding to the Scheduled job. Click Run Now. The job is run and the status is updated. To view job data, click View Details in the right pane. See View an individual job information. Create a job for managing power devices 1.
a) Enter the job name in Job Name. By default, the plugin type is displayed as HTML5. b) Click Next. 4. In the Job Target section, select the target devices and click Next. See Select target devices and device groups. a) Click Next. 5. In the Schedule section, run the job immediately or schedule for a later point of time. See Schedule job field definitions. 6. Click Finish. The job is created and listed in the Jobs list and identified by an appropriate status in the JOB STATUS column. 7.
14 Discovering devices for monitoring or management NOTE: To perform any tasks on OpenManage Enterprise, you must have necessary user privileges. See Role-based OpenManage Enterprise user privileges. 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.
• • • • • • • • Specify discovery mode for creating a chassis discovery job Create customized device discovery job protocol for Chassis – Additional settings for discovery protocols Specify discovery mode for creating a Dell storage discovery job Specify discovery mode for creating a network switch discovery job Create customized device discovery job protocol HTTPS storage devices –Additional settings for discovery protocols Create customized device discovery job protocol for SNMP devices Specify discovery
NOTE: During CMC discovery, the servers, and IOM and storage modules (configured with IP and SNMP set to "public" as community string), residing on CMC are also discovered and are onboarded. If you enable trap reception during CMC discovery, the OpenManage Enterprise is set as the trap destination on all the servers and not on the chassis. NOTE: During CMC discovery, FN I/O Aggregators in Programmable MUX (PMUX) mode are not discovered.
NOTE: The Enable trap reception from discovered check box is effective only for servers discovered by using their iDRAC interface. Selection is ineffective for other servers—such as those devices discovered by using OS discovery. 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.
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 Run a device discovery job NOTE: You cannot rerun a job that is already running. To run a device discovery job: 1. In the list of existing device discovery jobs, select the check box corresponding to the job you want to run now. 2. Click Run.
a) In the Description of Exclude Range box, enter the information about the range that is being excluded. b) In the Enter Ranges to Exclude box, enter address(es) or range of devices to be excluded. The box can take up to 1000 address entries at a time, but separated by a line break. Meaning, every exclusion range must be entered in different lines inside the box. The range that can be excluded is same as the supported ranges that are applicable while discovering a device. See Create a device discovery job.
Create customized device discovery job protocol for servers –Additional settings for discovery protocols In the Additional Settings dialog box, enter details for the appropriate protocol with which you want to discover the server(s): NOTE: The appropriate protocols are automatically preselected based on your initial inputs. 1. To Discover using WS-Man/Redfish (iDRAC, Server, and/or Chassis) a) In the Credentials section, enter User Name and Password.
Specify discovery mode for creating a chassis discovery job 1. From the Device Type drop-down menu, select CHASSIS. Based on your selection, the fields change under Settings. 2. Enter the IP address, host name, or IP range in IP/Hostname/Range. 3. Under Settings, enter the username and password of the server to be detected. 4. Type the community type. 5.
6. Complete the tasks in Create a device discovery job. Specify discovery mode for creating a Dell storage discovery job 1. From the Device Type drop-down menu, select DELL STORAGE. 2. When prompted, select: • • PowerVault ME: To discover the storage devices using the HTTPS protocol like the PowerVault ME. Others: To discover storage devices which use SNMP protocol. Based on your selection, the fields change under Settings. 3. Enter the IP address, host name, or IP range in IP/Hostname/Range. 4.
Create customized device discovery job protocol for SNMP devices By default, the Discover using SNMP check box is selected to enable you detect the storage, networking, or other SNMP devices. 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. 1. Under Credentials, select the SNMP version, and then enter the community type. 2.
15 Managing device inventory NOTE: To perform any tasks on OpenManage Enterprise, you must have necessary user privileges. See Role-based OpenManage Enterprise user privileges. 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.
6. Click Finish. 7. The job is created and listed in the queue. An inventory job is created displayed in the list of inventory jobs. The SCHEDULE column specifies whether the job is Scheduled or Not Scheduled. See Run an inventory job now. Related information Managing device inventory Run an inventory job now NOTE: You cannot rerun a job that is already running. 1. In the list of existing inventory schedule jobs, select the check box corresponding to the inventory job you want to run immediately. 2.
16 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. 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.
• Click Refresh Warranty in the upper right-hand corner to refresh the Warranty table. Warranty statuses automatically change from • • critical to normal for all the devices whose warranties are renewed. A new Device Warranty alert log, with the total number of expired warranties in the console, is generated each time Refresh Warranty is clicked. For information on Alert logs, see View the alert logs To sort data in the table based on a column, click the column title.
17 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. 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. Data displayed in the output cannot be sorted because it is defined in the query used to build a report.
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. Related information Reports Copy reports Only user-created reports can be copied. 1. Select the report, click More Actions, and then click Copy. 2.
• • • Groups: Group status, group description, group membership type, group name, and group type. Alerts: Alert status, alert severity, catalog name, alert type, alert sub-category, and device information. Devices: Alert, alert catalog, chassis fan, device software, and so on. These criteria have further classification based on which data can be filtered and reports generated. Table 19. The role-based access privileges for generating reports on OpenManage Enterprise User Role... Report tasks permitted...
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. Export selected reports 1. Select the check boxes corresponding to the reports to be exported, click More Actions, and then click Export Selected. Currently, you cannot export all the reports at a time. 2.
18 Managing MIB files NOTE: To perform any tasks on OpenManage Enterprise, you must have necessary user privileges. See Role-based OpenManage Enterprise user privileges. 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.
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. 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. In the View Traps section, a list of MIB files is displayed with the following information: • • • • • • Alert category of the trap.
2. Click Remove MIB. 3. In the Remove MIB dialog box, select the check boxes of the MIBs to be removed. 4. Click Remove. The MIB files are removed and the MIB table is updated. Resolve MIB types 1. Import the MIB files. See Import MIB files. If the MIB type is unresolved, the Unresolved Types dialog box lists MIB type(s) indicating that the MIB type(s) will be imported only if resolved. 2. Click Resolve Types. 3. In the Resolve Types dialog box, click Select Files, and then select the missing file(s). 4.
19 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. NOTE: For information about supported browsers, see the OpenManage Enterprise Support Matrix available on the support site.
• OpenManage Mobile settings 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. 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.
• • 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. • • • • USERNAME: Along with the users you created, OpenManage Enterprise displays the following default user roles that cannot be edited or deleted: admin, system, and root. However, you can edit the login credentials by selecting the default username and clicking Edit.
Ending user sessions Related information Manage OpenManage Enterprise users Delete OpenManage Enterprise users 1. Select the check box corresponding to the username and click Delete. 2. When prompted, click YES. Related reference Disable OpenManage Enterprise users Enable OpenManage Enterprise users Related information Manage OpenManage Enterprise users Delete Directory services Select the check box corresponding to the Directory Services to be deleted, and then click Delete.
Table 21.
• • • Administrator Device Manager Viewer For more information, see Role-based OpenManage Enterprise user privileges. 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.
Directory services integration in OpenManage Enterprise Directory Services enables you to import directory groups from AD or LDAP for use on the console. NOTE: If the OpenManage Enterprise is hosted on an IPv6 network, the SSL authentication against domain controller using FQDN would fail if IPv4 is set as preferred address in DNS. To avoid this failure, do one of the following: • DNS should be set to return IPv6 as preferred address when queried with FQDN.
Add or edit Lightweight Directory Access Protocol groups to be used with Directory Services 1. Click Application Settings > Users > Directory Services, and then click Add. 2. In the Connect to Directory Service dialog box, select LDAP as the directory type. NOTE: To create an AD user group by using Directory Services, see Add or edit Active Directory groups to be used with Directory Services. a) Enter a desired name for the LDAP directory.
By clicking OpenManage Enterprise > Application Settings > Security, you can secure your OpenManage Enterprise either by specifying the Restrict Allowed IP Range or the Login Lockout Policy. • Expand Restrict Allowed IP Range: 1. To specify the IP address range that must be allowed to access OpenManage Enterprise, select the Enable IP Range check box. 2. In the IP Range Address (CIDR) box, enter the IP address range. NOTE: Only one IP range is allowed. 3. Click Apply.
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 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.
NOTE: When the Instrumentation(NetBios) option is selected in General Device Naming, for chassis devices the Chassis name is displayed as the device name entry on the All Devices page. 2. Server Device Naming applies to iDRACs only. Select from one of the following naming modes for the discovered iDRACs : • • iDRAC Hostname to use the iDRAC hostname. System Hostname to use the system hostname. NOTE: The default naming preference for iDRAC devices is the System Hostname .
Manage incoming alerts NOTE: To perform any tasks on OpenManage Enterprise, you must have necessary user privileges. See Role-based OpenManage Enterprise user privileges. By clicking OpenManage Enterprise > Application Settings > Incoming Alerts, you can define the properties of the user who receives incoming alerts by using SNMPv3 protocol. You can also set the TrapForward properties. • To set the SNMP credentials for incoming alerts: 1. Select the SNMPV3 Enable check box. 2. Click Credentials. 3.
3. In the Show warning if warranties are expiring in the next box, enter the number of days. You can enter a value 0–1000(both included). The default value is set as 90 days. The warranties expiring based on this setting are represented as the widget. in the report and 4. The Show expired warranties checkbox, which is checked by default, can be cleared. When cleared, OpenManage Enterprise stops reporting the expired warranties on all the places where warranty-related statistics are displayed. 5.
• • Notify other console users of the impending scheduled update. If the upgrade fails, the appliance would restart. It is recommended to revert the VM snapshot and upgrade again. NOTE: Only OpenManage Enterprise versions starting 3.1 and above can be directly updated to version 3.3.1 by the Automatic > Online method. However, to update from OpenManage Enterprise—Tech Release (version 1.0), you must first upgrade the appliance to either versions 3.0 or 3.
3. You can login immediately after the appliance is updated and don't have to wait till the entire inventory is discovered. Post update, the discovery task will run in the background and you can see the progress occasionally. 4. Currently, the status of the associated jobs on the Job Details page is displayed as completed. 5. Currently, an audit log is not created to indicate if the appliance update process was successful or not. 6. Upon install or upgrade to OpenManage Enterprise version 3.3.
• If the upgrade download has a problem connecting through proxy, uncheck the proxy settings and then download. Log in after the update and confirm that the product works as expected. Check the audit log for any warnings or errors that are related to the update. If any errors, export the audit log and save for tech support. NOTE: After the appliance is updated: 1. Clear the browser cache. Not clearing the browser cache, may cause failing of new tasks post update. 2.
3. Click Disable Extension, and in the confirmation window, select I agree that I have captured the snapshot of the OM Enterprise appliance prior to the upgrade option, and then click Disable Extension. NOTE: After disabling the extension, you cannot see any information or pages related to the extension on OpenManage Enterprise. Uninstall an extension Uninstalls and deletes all the data that is collected by the extension. 1.
1. In the Command Name box, enter the command name. 2. In the Command box, type the commands. Up to 100 commands can be typed with each command required to be on a new line. 3. 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.
Delete an OpenManage Mobile subscriber Enable or disable OpenManage Mobile subscribers The check boxes in the Enabled column in the Mobile Subscribers list allow you to enable or disable transmission of alert notifications to the OpenManage Mobile subscribers. NOTE: The administrator rights are required for enabling or disabling OpenManage Mobile subscribers.
Related tasks View the alert notification service status Related information OpenManage Mobile settings Delete an OpenManage Mobile subscriber View the alert notification service status Notification service status The following table provides information about the Notification Service Status displayed on the Application Settings > Mobile page. Table 23. Notification service status Status Icon Status Description The service is running and operating normally.
Field Description FILTER Filters are policies that the subscriber has configured for alert notifications. LAST ERROR The date and time the last error occurred when sending an alert notification to the OpenManage Mobile user. LAST PUSH The date and time the last alert notification was sent successfully from OpenManage Enterprise to the Alert Forwarding Service. LAST CONNECTION The date and time the user last accessed OpenManage Enterprise through OpenManage Mobile.
Related tasks OpenManage Mobile settings Related information OpenManage Mobile settings Managing OpenManage Enterprise appliance settings 135
20 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. Topics: • • • • • • • • • • • • Schedule Reference Firmware baseline field definitions Schedule job field definitions Alert categories after EEMI relocation in OpenManage Enterprise version 3.3.
Alert categories after EEMI relocation in OpenManage Enterprise version 3.3.1 Table of EEMI relocations Table 26. Alert categories in OpenManage Enterprise version 3.3.
Previous Category Previous Subcategory New Category New Subcategory Miscellaneous Generic Configuration Generic Miscellaneous Devices Configuration Devices Miscellaneous Devices Configuration Devices Audit Security Configuration Security Audit Security Configuration Security Audit Security Configuration Security Token substitution in remote scripts and alert policy OpenManage Enterprise supports use of tokens to enhance remote scripting and creation of the alert policies.
4. To determine the duration of the debug capabilities being requested, select a start and end date. 5. On the Choose Requested Debug Capabilities screen, select a debug capability from a list of debug capabilities unique to the console. In the lower-right corner, select Generate. NOTE: The debug capability that is current supported is, RootShell. 6. On the Download DAT file screen, view the signing instructions and the URL address of the share where the DAT.ini file exists. 7.
Catalog Management field definitions CATALOG NAME: Name of the catalog. Built-in catalogs cannot be edited. DOWNLOAD: Indicates the download status of catalogs from its repository folder. Statuses are: Completed, Running, and Failed. REPOSITORY: Repository types such as Dell.com, CIFS, and NFS. REPOSITORY LOCATION: Location where the catalogs are saved. Examples are Dell.com, CIFS, and NFS. Also, indicates the completion status of a job running on the catalog. CATALOG FILE: Type of catalog file.
