Dell EMC OpenManage Enterprise Version 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. © 2018 - 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........................................................................................................................... 37 Adding or editing devices in a Static child group.......................................................................................................38 Rename child groups of Static or Query Dynamic groups....................................................................................... 39 Clone a Static or Query group......................
Edit a chassis template....................................................................................................................................................... 58 Edit IOA template................................................................................................................................................................ 59 Edit network properties..................................................................................................................................
Alert policies..........................................................................................................................................................................77 Create alert policies....................................................................................................................................................... 78 Enable alert policies................................................................................................................................
16 Manage the device warranty..................................................................................................... 102 View and renew device warranty.....................................................................................................................................102 17 Reports...................................................................................................................................104 Run reports......................................................
Disable an extension.......................................................................................................................................................... 126 Uninstall an extension........................................................................................................................................................126 Enable 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.
• 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 • • • • • • • • • • • • • • Discovery and monitoring of PowerVault MD3, PowerVault ME4 devices In-band discovery of Windows servers and hypervisors using the OpenSSH protocol Support for the latest versions of KVM, ESXi, and Hyper-V Support for deployment of IOA template Programmatic appliance deployme
Document Description Availability Dell EMC OpenManage Enterprise and OpenManage Enterprise - Modular Edition RESTful API Guide Provides information about integrating OpenManage Enterprise by using Representational State Transfer (REST) APIs and also includes examples of using REST APIs to perform common tasks. Dell EMC SupportAssist Enterprise User's Guide Provides information about installing, configuring, Dell.com/ServiceabilityTools using, and troubleshooting SupportAssist Enterprise.
You can verify if the OpenManage Enterprise Advanced license is installed on a server by: • • On all pages of OpenManage Enterprise, in the upper-right corner, click the i symbol, and then click Licenses. In the Licenses dialog box, read through the message and click appropriate links to view and download OpenManage Enterprise related open-source files, or other open-source licenses.
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 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 OpenManage Enterprise Related reference OpenManage Enterprise
User with this role... Has the following user privileges • • 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. • A change in the user role will not affect a logged-in user. The changes become effective only after the next user login.
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 6.7 • vSphere ESXi 6.5 • vSphere ESXi 6.0 • vSphere ESXi 5.5 Microsoft Hyper-V supported on: • • Windows Server 2019 • Windows Server 2016 • Windows Server 2012 R2 KVM supported on: • • • Red Hat Enterprise Linux 7.2 Red Hat Enterprise Linux 7.0 Red Hat Enterprise Linux 6.
8. If there are more than one datastores available on the host, the Datastore page displays such datastores. Select the location to store virtual machine (VM) files, and then click Next. 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.
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. NOTE: Open-manage Enterprise does not support Generation 2. 8. On the Assign Memory page, enter the startup memory in the Startup memory field and click Next. NOTE: Ensure that a minimum of 16,000 MB (16 GB) is assigned. 9. On the Configure Networking page, select the network adapter in the Connection drop-down list.
Deploy OpenManage Enterprise by using Kernelbased Virtual Machine 1. Install the required virtualization packages while installing the operating system. 2. Download the openmanage_enterprise_kvm_format.zip file from the support site. Extract the file to an appropriate location on your system where you want to store the OpenManage Enterprise virtual drive. 3. Start the virtual manager and select File > Properties. 4. On the Network Interfaces page, click Add. 5.
Parameter Accepted Values Description bEnableIpv6AutoConfig true or false Set to true if you want the appliance to enable IPv6 auto configuration and to ignore the static IPv6. staticIP static IP in CIDR format Can be IPv4 or IPv6. (You cannot set both the IPv4 and IPv6 types at a time.) gateway IPv4 or IPv6 You cannot set static Gateway as IPv4 and IPv6 types at a time. 3. Run the update_ovf_property.py script. This script modifies the openmanage_enterprise.x86_64-0.0.1.
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
• • Enable Field Service Debug (FSD) Mode Reboot the Appliance NOTE: Possibly after running a command to restart the services, it may be observed that the TUI displays the following message: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 36s! [java:14439]. This • soft lockup issue likely occurs as a result of the hypervisor being overloaded. In such situations, it is recommended to have at least 16 GB of RAM and CPU of 8000 MHz reserved to the OpenManage Enterprise appliance.
NOTE: When the NTP Server settings are updated, the currently logged in users are automatically logged out from their OpenManage Enterprise sessions. • • Select the Use NTP check box. Enter the IP address or hostname in Primary NTP Server Address and Secondary NTP Server Address (optional) for time synchronization 3. If you want to set proxy server for external communication, In the Proxy Configuration section do the following: • • • • Select the Enable HTTP Proxy Settings check box.
Supported protocols and ports in OpenManage Enterprise Supported protocols and ports on management stations Table 8. OpenManage Enterprise supported protocols and ports on the management stations Port Number Protocol Port Type Maximum Source Encryption Level Direction Destination Usage 22 SSH TCP 256-bit Management station In OpenManage Enterprise appliance Required for incoming only if FSD is used.
Port Number Protocol Port Type Maximum Source Encryption Level Direction Destination Usage HTTPS for the web GUI. 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. 636 LDAPS TCP None OpenManage Enterprise appliance Out Management station AD/ LDAP login for Domain Controller.
Use case URL Push new alert notifications using the OpenManage Mobile application. https://openmanagecloud.dell.
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.
compliance level of few devices is Healthy or Downgrade , but if the compliance of one device in the group is Upgrade , the compliance level of the firmware baseline is indicated as Upgrade. The rollup status is equal to the status of the device that has high severity. For more information about Rollup Health status, see the MANAGING THE ROLLUP HEALTH STATUS BY USING IDRAC ON THE DELL EMC 14TH GENERATION AND LATER POWEREDGE SERVERS technical white paper on the Dell TechCenter.
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.
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. In the left pane, right-click the child Query group and click Edit. b. Alternately, click the child Query group in the left pane. The list of devices in the group is listed in the working pane.
1. Right-click the Static child group, and then click Add Devices. For definitions about Static groups, see Organize devices into groups. 2. In the Add Devices to New Group Wizard dialog box, select the check boxes of devices that must be added to the group. The selected devices are displayed under the All Selected Devices tab. 3. Click Finish. The devices are added to the selected Static child group and displayed in the right pane.
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. In the Devices list, click the device name or IP address to view device configuration data, and then edit. See Viewing and configuring devices. 3.
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.
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. For more information about using iDRAC, visit Dell.com/idracmanuals.
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.
• NFS 1. In the Share Address box, enter the IP address of the system where the firmware catalog is stored on the network. 2. In the Catalog File Path box, enter the full file path of the catalog file location. Example path: nfsshare\catalog.xml • CIFS 1. In the Share Address box, enter the IP address of the system where the firmware catalog is stored on the network. 2. In the Catalog File Path box, enter the full file path of the catalog file location. Example path: Firmware\m630sa \catalog.xml 3.
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. If the selected catalog was an online firmware catalog, it is replaced by the most up-to-date version that is maintained at the Dell.com site.
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. In the Baseline Name box, enter a name for the baseline, and then enter the baseline description. 4. Click Next. b) In the Select Devices section: • To select the target device(s): • 1. Select Select Devices, and then click the Select Devices button. 2.
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. For example, if many devices are associated to a firmware baseline, and the compliance level of many devices is OK and Downgrade as Critical.
On the Compliance Report page the list of devices associated with the baseline and their compliance level is displayed. For field descriptions, see Viewing device firmware compliance report. 2. Select the check box corresponding to the device whose firmware must be updated. You can select more than one device with similar properties. 3. Click Update Firmware. 4.
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.
• • The Guided view enables you to edit the attributes such as BIOS, boot sequence, and networking. If the configuration elements are not set while creating the template, they will not be displayed during the edit mode. The Advanced mode enables you to edit all the available server configuration settings. 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.
5. In the Edit Components section under Advanced View, you can select or unselect the attributes to include or exclude in the template. For example, Miscellaneous Attributes, CMC, Event Filters, and so on. 6. Click Next . 7. You can review the changes to the attributes under Summary. A circle appears next to the changed attributes. 8. Click Finish to save the changes to the chassis template. Edit IOA template The attributes in the IOA template are uneditable.
b) Select either CIFS or NFS as the share type, and then enter information in the fields such as ISO image file path and share location where the ISO image file is stored. c) Click Next. 4. In the Schedule section, run the job immediately or schedule for a later time. See Schedule job field definitions. 5. Click Finish. Review the Warning message and click YES. A Device Configuration job is created under Jobs. See Using jobs for device control.
Auto deployment of configuration on yet-to-bediscovered servers or chassis Existing configuration templates in the OpenManage Enterprise can be assigned to the servers and chassis which are awaiting discovery. These configuration templates are automatically deployed on the respective devices when they are discovered and onboarded. To access the Auto Deploy page, click OpenManage Enterprise > Configuration > Auto Deploy.
11. Click Finish. An alert message Deploying a template can cause data loss and can cause a restart of the device. Are you sure you want to deploy the template? is displayed. 12. Click Yes. A new Auto Deploy target is created and listed on the Auto Deploy page. Delete auto deployment targets NOTE: To perform any tasks on OpenManage Enterprise, you must have necessary user privileges.
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.
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. In the Ethernet section: a) Select the Include ethernet virtual MAC addresses check box to include the MAC addresses. b) Enter a starting MAC address and specify the number of virtual MAC identities to be created. 5. In the iSCSI section: a) b) c) d) Select the Include iSCSI MAC addresses check box to include iSCSI MAC addresses.
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. Include iSCSI MAC Select the check box to add the iSCSI MAC addresses to the identity pool. Addresses Starting MAC Address Enter the starting MAC address of the identity pool in one of the following formats: • • • AA:BB:CC:DD:EE:FF AA-BB-CC-DD-EE-FF AABB.CCDD.
Cancel Closes the Create Identity Pool wizard without saving the changes. Create Identity Pool - Fibre channel over Ethernet You can add the required number of Fibre Channel over Ethernet (FCoE) Initialization Protocol (FIP) MAC addresses to the identity pool. The World Wide Port Name (WWPN)/World Wide Node Name (WWNN) values are generated from these MAC addresses. Include FCoE Identity Select the check box to include the FCoE MAC addresses to the identity pool.
Finish Saves the changes and displays the Identity Pools page. Cancel Closes the Create Identity Pool wizard without saving the changes. View definitions of identity pools To view the definitions of an identity pool: 1. On the Configuration page, click Identity Pools. 2. Select an identity pool, and then click Summary. The various identity definitions of the identity pool are listed. 3. To view the usage of these identity definitions, click the Usage tab and select the View By filter option.
Network types Description FCoE Storage Used for FCoE VLANs Data Replication Storage Used for VLANs supporting storage data replication such as for VMware Virtual Storage Area Network (VSAN) VM Migration Used for VLANs supporting vMotion and similar technologies VMWare FT Logging Used for VLANs supporting VMware Fault Tolerance Edit or delete a configured network 1. On the Configuration page, click Networks. 2.
11. In the Schedule section, run the job immediately or schedule for a later point of time. See Schedule job field definitions. 12. Click Finish. Review the message and click YES. A Device Configuration job is created under Jobs. See Using jobs for device control. Delete identity pools You cannot delete an identity pool if the identities are reserved or assigned to a configuration template. To delete an identity pool: 1. On the Configuration page, click Identity Pools. 2.
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.
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. The Compliance Report table 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.
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.
3. Click Finish. A tick mark is displayed in the cell. Email message is sent when an alert is received that meets the set policy criteria. • Forward an SNMP trap: 1. 2. 3. 4. • Click the SNMP TRAP cell corresponding to the alert policy. When prompted, click YES. Under Alerts, expand SNMP Configuration. Complete the tasks in Configure SMTP, SNMP, and Syslog alerts. A tick mark is displayed in the cell. An SNMP trap is activated when an alert is received that meets the set policy criteria.
4. In the Target section, add devices or groups. See Select target devices and device groups. • • To specify an undiscovered device (third-party device), select Specific Undiscovered Devices, and then type the IP address or host name. To specify any undiscovered device, select Any Undiscovered Devices. NOTE: The Remote Script Execution and Power Action tasks cannot be performed on the undiscovered devices. NOTE: Alerts from such foreign and undiscovered devices can be ignored.
4. In the Target section, the Select Devices option is selected by default. Click Select Devices and select devices from the left pane. Click Next. NOTE: Selecting target devices or groups is not applicable while forwarding the audit logs to the Syslog server. 5. (Optional) By default, the alert policies are always active. To limit activity, in the Date and Time section, select the 'from' and 'to' dates, and then select the time frame.
4. Default port number by using UDP=514. Edit if necessary by entering or selecting from the box. See Supported protocols and ports in OpenManage Enterprise. 5. Click Apply. 6. To reset the settings to default attributes, click Discard. Execute remote commands and scripts When you get an SNMP trap, you can run a script on OpenManage Enterprise. This sets up a policy that opens a ticket on your third party ticketing system for alert management. You can create and store only up to four remote commands. 1.
Edit alert policies 1. Select the check box corresponding to the alert policy and click Edit. 2. In the Create Alert Policy dialog box, edit the properties of the alert policy. For navigating through different sections in the dialog box, see Create alert policies. Related information Alert policies Forward audit logs to remote Syslog servers Disable alert policies You can disable an alert policy, only if enabled.
• • Recommended Action: Resolution to the error by using GUI, RACADM, or WS-Man commands. Where necessary, you are recommended to refer to documents on the support site or TechCenter for more information. Detailed Description: More information about an issue for easy and fast resolution. You can view more information about an alert by using filters such as message ID, message text, category, and Subcategory. To view the alert definitions: 1.
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.
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. Report_Task Creates reports about devices by using built-in or customized data fields. See Reports.
Create a job for managing power devices 1. Click Create, and then select Power Control Devices. 2. In the Power Control Devices Wizard dialog box: a) In the Options section: 1. Enter the job name in Job Name. 2. From the Power Options drop-down menu, select any one of the tasks: Power on, Power off, or Power cycle. 3. Click Next. b) In the Target section, select the target devices and click Next. See Select target devices and device groups.
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. 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 the job data, click View Details in the right pane. See View an individual job information.
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 functionality of the supported protocols to discover, monitor, and manage the PowerEdge 11G servers with iDRAC6 is limited. Table 17.
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. The job starts immediately and a message is displayed in the lower-right corner. Related information Discovering devices for monitoring or management Stop a device discovery job You can stop the job only if running.
3. When prompted, click YES. The IP address or the range is globally excluded, and then displayed in the list of excluded ranges. Such devices are globally excluded which implies that they do not take part in any activity performed by OpenManage Enterprise. NOTE: The device that is globally excluded is clearly identified as 'Globally excluded' on the Job Details page. You can view the list of globally excluded devices by clicking: • • • Devices > Global Exclude.
1. Select the Discover using WS-Man/Redfish (iDRAC, Server, and/or Chassis) check box to discover servers. 2. Enter username and password of the server to be detected. 3. 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. By default, 443 is used to connect to the device.
1. Select the Discover using WS-Man/Redfish (iDRAC, Server, and/or Chassis) . NOTE: For chassis, the Discover using WS-Man/Redfish check box is selected by default. Implies that the chassis can be discovered by using either of these two protocols. The M1000e, CMC VRTX, and FX2 chassis support the WSMan commands. The MX7000 chassis supports Redfish protocol. 2. Enter username and password of the chassis to be detected. 3.
Specify discovery mode for creating a network switch discovery job 1. From the Device Type drop-down menu, select NETWORK SWITCH. 2. Enter the IP address, host name, or IP range in IP/Hostname/Range. 3. Under Settings enter the SNMP version and the community type of the device to be detected. 4. Click Additional Settings to customize the respective discover protocol. See Creating customized device discovery job template for SNMP devices 5. Complete the tasks in Create a device discovery job.
3. To create customized discovery template by clicking Additional Settings, see Create customized device discovery job protocol for servers –Additional settings for discovery protocols. Related information Discovering devices for monitoring or management 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.
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...
2. Add or remove a filter by clicking the plus or dustbin symbol respectively. 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. Related information Managing the device configuration compliance Edit a configuration compliance baseline Remove a configuration compliance baseline Export selected reports 1.
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.
• • • • • Disable an extension Uninstall an extension Enable Extension Execute remote commands and scripts 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 OpenManage Enterprise such as DNS domain name, FQDN, and IPv4 and IPv6 settings, expand Current Settings. 2.
• • • 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. • • • • 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.
Delete OpenManage Enterprise users 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.
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.
• 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 range of IP addresses separated by a comma in CIDR notation. 3. Click Apply. To reset to default properties, click Discard. Expand Login Lockout Policy : 1. Select the By User Name check box to prevent a specific user name from logging in to OpenManage Enterprise. 2.
• 1. Expand Report Settings. 2. Enter a number in the Reports row limit box. Maximum rows permitted=1000. 3. Click Apply. A job is run and the setting is applied. To set the time after which the health of devices must be automatically monitored and updated on the OpenManage Enterprise Dashboard: 1. Expand Device Health. 2. Enter the frequency at which the device health must be recorded and data stored. 3.
1. Expand Trap Forwarding Format. 2. To retain the trap data as-is, select Original Format. To normalize, select Normalized. 3. Click Apply. Customize the alert display 1. Click OpenManage Enterprise > Application Settings>Alerts and expand the Alert Display Settings. 2. Select one of the following: a) All — to enable the display of both acknowledged and unacknowledged alerts. b) Unacknowledged — to enable the display of only the unacknowledged alerts.
Set SNMP Credentials 1. Click Credentials. 2. In the SNMP Credentials dialog box: a) b) c) d) e) In the User Name box, enter the login ID of the user managing the OpenManage Enterprise settings. From the Authentication Type drop-down menu, select either the SHA or MD_5 algorithm as the authentication type. In the Authentication Passphrase box, enter the passphrase pertaining to SHA or MD_5 based on your selection.
Updating the OpenManage Enterprise version The user is automatically alerted about the availability of a new update package or Warranty information on the Home portal. Before updating to the latest version, ensure that you: • • • • Allocate at least an hour for the update process. Allocate more time if the update must be downloaded by using a slower network connection. Ensure that no device configuration tasks or deployment tasks are running or are scheduled to run during the planned downtime.
Related tasks Check and update the version of the OpenManage Enterprise and the available extensions Update from an internal network share You must set up a local share and manually download the update package when you are not automatically connected to Dell.com. An audit log is created after every manual attempt to find an update. NOTE: Before you begin the 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).
3. Review and ensure that you meet the list of prerequisites that are mentioned under the Prerequisite section. NOTE: The lists of prerequisites change as you select the version of extension that you want to install. 4. In Install Details, select the required version of the extension from the Version(s) drop-down menu, and then click Install Extension. The details of the number of users logged in to OpenManage Enterprise, tasks in progress, and schedule jobs are displayed in the confirmation window.
b) In the Command Name box, enter the command name. c) Select any one of the following command type: 1. Script 2. RACADM 3. IPMI Tool d) If you select Script, do the following: 1. 2. 3. 4. 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.
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.
To delete an OpenManage Mobile subscriber: 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.
Problem Reason Resolution • The Message Forwarding Service is unable to connect to a device platform notification service. [Code 100-105, 200-202, 211-212] 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. The platform provider service is temporarily unavailable to the Message Forwarding Service.
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.
Token substitution in remote scripts and alert policy OpenManage Enterprise supports use of tokens to enhance remote scripting and creation of the alert policies. Table 26.
• Upload the DAT.ini file to appropriate Dell Field Service Debug Authentication Facility (FSDAF) and submit. 9. Wait for a Dell EMC signed and approved DAT.ini file to be returned. Install or grant a signed FSD DAT.ini file Ensure that you have received the DAT.ini file, which is signed and approved by Dell EMC. NOTE: After Dell EMC approves the DAT.ini file, you must upload the file to the console appliance that generated the original unblock command. 1. To upload a signed DAT.
