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 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries.
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 OpenManage Enterprise—Server Configuration Management License New in this release • You can now edit the deployment template attributes by using: • • • • • • Guided view • Advanced view Support for discovery and inventory of MX7000 chassis—as a standalone chassis and as a lead chassis in a Multi-Chassis Management (MCM) group. Support for configuration compliance and remediation of MX7000 chassis.
Purchasing License You can purchase the OpenManage Enterprise — Server Configuration Management license when you purchase a server or by contacting your sales representative. You can download the purchased license from the Software License Management Portal at Dell.com/support/retail/lkm. Verifying License Information OpenManage Enterprise provides a built-in report to view the list of devices that are monitored by OpenManage Enterprise, and their licenses.
2 Security features in OpenManage Enterprise Some of the security features of OpenManage Enterprise are: • • • • Role-based access that limits access to console settings and device actions. 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 reports Y Y N Manage templates Y Y N Set up the OpenManage Enterprise appliance Y N N Manage discovery Y N N Manage groups Y N N Refresh inventory Y N N Set up security Y N N Manage traps Y N N Related tasks Deploying and managing OpenManage Enterprise Related reference OpenManage Enterprise user role types OpenManage Enterprise user role types NOTE: AD and L
User with this role... Has the following user privileges 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 DM has the same privileges as a viewer. NOTE: A change in the user role will not affect a loggedin user. The changes become effective only after the next user login. NOTE: An audit log is recorded when: • A group is assigned or access permission is changed. • User role is modified.
3 Deploying and managing 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 OpenManage Enterprise version. This chapter describes the installation prerequisites and minimum requirements.
Minimum system requirements for deploying OpenManange Enterprise Table 4. Minimum requirements Particulars Minimum requirements Supported hypervisors • VMware vSphere versions: • • vSphere ESXi 6.5 • vSphere ESXi 6.0 • vSphere ESXi 5.5 Microsoft Hyper-V supported on: • • 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.
• • To allocate storage space to VMs, as required, click Thin Provision. To pre-allocate physical storage space to VMs at the time a drive is created, click Thick provision. 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 1. Extract the openmanage_enterprise_vhd_format.
2. Install Kernel-based Virtual Machine (KVM) by running the following command on any Linux system: yum install qemu-kvm python-virtinst virt-manager \ 3. Start the virtual manager and select File > Properties. 4. On the Network Interfaces page, click Add. 5. Select Bridge as the interface type and click Forward. 6. Set the start mode to onboot and select the Activate now check box. 7. Select the interface to bridge from the list and ensure the properties match with the host device, and then click Finish.
4 Getting 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 Log in to OpenManage Enterprise When you boot the system for the first time from the Text User Interface (TUI), you are prompted to accept the EULA, and then change the admini
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 environments, it is recommended to have at least 16 GB of RAM and CPU of 8000 MHz reserved to the OpenManage Enterprise appliance.
8. Click FINISH. NOTE: For information about supported browsers, see the OpenManage Enterprise Support Matrix available on the support site. Recommended scalability and performance settings for optimal usage of OpenManage Enterprise The following table lists the performance parameters of the supported features in OpenManage Enterprise.
Port Number Protocol Port Type Maximum Encryption Level Directio n Usage 80 HTTP TCP None In/Out The Web GUI landing page. Will redirect a user to HTTPS. 111 NFS TCP None In/Out For read-only NFS share used for iDRAC firmware update. 123 NTP TCP None Out Time synchronization (if enabled). 137, 138 CIFS UDP/TCP None In/Out To upload or download device configuration templates. 139, 445 CIFS TCP None In/Out Miscellaneous Management functions.
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.
• • • • • • G—The number of events generated in the alerts log. Deleting the alerts reduces the count. For information about symbols 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—Number of devices whose warranty status is critical and requires immediate attention. Click to view the system alerts under each category.
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.
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. To view the list of devices that belong to a health state, you can either click the color band associated with a health category, or click the respective health status symbol next to a Donut chart.
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.
• • Storage Devices: Dell EMC Compellent 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 Discovery Group feature is not supported in OpenManage Enterprise 3.0 and later versions.
compliance level of that baseline. For example, if many devices are associated to a firmware baseline, and the 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.
7 Managing All Devices By clicking OpenManage Enterprise > Devices > All 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 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. You can manage the properties of a device in a group.
• • Static Groups: Manually created by the user by adding specific devices to a group. These groups change only when a user manually changes the devices in the group or a sub-group. The items in the group remain static until the parent group is edited or the child device is deleted. Query Group: Groups that are dynamically defined by matching user-specified criteria. Devices in the group change based on the result of devices that are discovered by using criteria.
3. Click Next. 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.
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 Group 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.
• • • • 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. Downgrade—The current firmware version of the component or device is newer than the baseline defined in the catalog file.
• • 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. Rollback does not consider the firmware version that is installed by using the Rollback feature (by rolling back the version).
• • • • • • • 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.
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. • • • • • • • • • • • • • • • • Device Card Information—Information about cards used in the device. Installed Software—List of firmware and software installed on different components in the device.
1. On the page, from the Troubleshoot drop-down menu, select Extract SupportAssist Report. 2. In the Extract SupportAssist Report dialog box: a) Enter the file name where the SupportAssist report must be saved. b) Select the check boxes corresponding to the log types whose SupportAssist report must be extracted. 3. Click OK. A job is created and displayed on the Jobs page. To view information about the job, click View Details in the right pane. See View the jobs list.
For more information about using iDRAC, visit Dell.com/idracmanuals. NOTE: You can also start the management application by clicking the IP address in the Device list. See Devices list. Start the Virtual Console The Virtual Console link works on the iDRAC Enterprise license of 14G servers. On the 12G and 13G servers, the link works on the 2.52.52.52 and later versions of OME Enterprise license.
8 Manage the device firmware By clicking OpenManage Enterprise > Configuration, and selecting: • • • Firmware: Manage the firmware of devices by using firmware baselines. Deploy: Create templates to define configuration compliance baseline and manage such templates. Compliance: Create device or device group configuration compliance baseline and manage device configuration.
• • • • • • 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. You can create firmware baselines which downloads these catalogs and act as a local repository for your devices.
• HTTP 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: \M830Bharath \catalog.xml • HTTPS 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: \M830Bharath \catalog.xml 3.
NOTE: Catalogs cannot be deleted if linked to a firmware baseline. Related information Create a firmware catalog by using local network Create a firmware baseline NOTE: To perform any tasks on OpenManage Enterprise, you must have necessary user privileges. See Role-based OpenManage Enterprise user privileges. NOTE: When a device is connected, the firmware version, if earlier than baseline version, is not automatically updated. You must update the firmware version.
NOTE: When a device is connected, the firmware version, if earlier than baseline version, is not automatically updated. You must update the firmware version. It is recommended to update device firmware during maintenance windows to prevent the devices or environment going offline during business hours. NOTE: You can view the firmware baseline report on the Dashboard also. See Manage firmware baseline by using the OpenManage Enterprise dashboard.
• • • • • • • Info : Symbol corresponding to every device component is linked to the support site page from where the firmware can be updated. Click to open the corresponding Driver Details page on the support site. CURRENT VERSION: Indicates the current firmware version of the device. BASELINE VERSION: Indicates the corresponding version of the device available in the firmware baseline.
9 Manage device configuration templates By clicking OpenManage Enterprise > Configuration > Deploy, and selecting Deploy, you can set the configuration properties such as network properties, and BIOS versions of servers, and chassis by using predefined 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.
• Clone Reference Server: Enables you to clone the configuration of an existing server. NOTE: On the PowerEdge 12G and 13G servers that have iDRAC version 2.52.52.52 and earlier (only up to 2.50.50.50), you must enable SMBv1 for the server configuration and deployment feature to work. • Clone Reference Chassis: Enables you to clone the configuration of an existing chassis. c) Click Next.
• • The partition, max, and min bandwidth are displayed from the template (profile) we created earlier. Click Finish. The network settings of the template is saved. 3. Click Next. In the Summary section, the attributes you edited by using the guided and advanced mode are displayed. 4. This section is read-only. Read through the settings and click Finish. The updated template attributes are saved to the template. Create template by importing a template file 1.
• Imported Active Directory settings will be replaced with the values in chassis profile. 1. From the list of templates, select the check box corresponding to the template you want to deploy. 2. On the Template Details page, click Deploy Template. 3. In the Deploy Template: dialog box, under Target: a) Click Select, and then select device(s) in the Job Target dialog box. See Selecting target devices and device groups.
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.
5. In the iSCSI section: a) b) c) d) Select the Include iSCSI MAC addresses check box to include iSCSI MAC addresses. Enter the starting MAC address and specify the number of iSCSI MAC addresses to be created. Select Configure iSCSI Initiator, and then enter the IQN prefix. Select Enable iSCSI Initiator IP Pool, and then enter the network details. NOTE: The iSCSI Initiator IP Pool does not support IPv6 addresses. 6.
• • • AA:BB:CC:DD:EE:FF AA-BB-CC-DD-EE-FF AABB.CCDD.EEFF The maximum length of a MAC address is 50 characters. This option is displayed only if the Include iSCSI MAC Addresses check box is selected. Number of iSCSI MAC addresses Enter the number of iSCSI MAC addresses. The MAC address can be between 1 and 5000. This option is displayed only if the Include iSCSI MAC Addresses check box is selected. Configure iSCSI Initiator Select the check box to configure the iSCSI initiator.
Starting MAC Address Enter the starting FCoE Initialization Protocol (FIP) 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.EEFF The maximum length of a MAC address is 50 characters. This option is displayed only if the Include FCoE Identity check box is selected. The WWPN/WWNN values are generated from the MAC address. Number of FCoE Identities Select the required number of FCoE identities. The identities can be between 1 and 5000.
3. To view the usage of these identity definitions, click the Usage tab and select the View By filter option. Edit identity pools You can edit an identity pool to add ranges that you had not specified earlier, add an identity type, or delete identity type ranges. To edit the definitions of an identity pool: 1. On the Configuration page, click Identity Pools. 2. Select the identity pool, and then click Edit. The Edit Identity Pool dialog box is displayed. 3.
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 .ISO image file is stored. c) Click Next. 8.
3. Click Migrate Profile. The virtual identities are now reclaimed from the source device and assigned to the target device.
10 Manage the device configuration compliance baseline By clicking OpenManage Enterprise > Configuration > Compliance, and selecting Compliance, you can create configuration baselines by using the built-in or user-created templates. You can create a configuration compliance baseline 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.
Create a configuration compliance baseline OpenManage Enterprise can assign 10 baselines to a single device and check the compliance level of maximum 500 devices at a time. To view the list of baselines, click OpenManage Enterprise > Configuration > Compliance. You can create a configuration compliance baseline by: • • • Using an existing deployment template. See Manage the device configuration compliance baseline. Using a template captured from a support device.
Related tasks Manage compliance baseline templates Select a query criteria Related information Manage the device configuration compliance baseline 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 Monitor device compliance with compliance templates Use compliance template to create compliance baselines and then periodically check the configuration compliance status of devices associated with the baseline. See Manage the device configuration compliance baseline. You can create baseline templates by using deployment template, reference device, importing from a file. See Manage compliance baseline templates.
3. Enter a name for the baseline compliance template. 4. Click Finish. A compliance template is created and listed in the list of configuration compliance baselines. Related tasks Manage compliance baseline templates Clone a compliance baseline template Create a compliance baseline template from reference device To use the configuration properties of device as a template for creating configuration baseline, the device must be already onboarded. See Onboarding devices. 1.
displayed and act accordingly. For more information about error and event messages, see the Error and Event Message Reference Guide available on the support site. 1. On the Compliance Templates page, select the corresponding check box, and then click Edit. 2. On the Template Details page, the configuration properties of the template is listed. 3. Expand the property you want to edit, and then enter or select data in the fields. a) To enable the property, select the check box, if not already enabled. 4.
12 Monitoring device alerts By clicking the OpenManage Enterprise menu, and selecting items under Alerts, you can: • • • • Manage 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. Export all or selected alert data. See Exporting data.
On this page, you can acknowledge, unacknowledge, ignore, export, delete, and archive alert data. For more information about archiving alerts, see View archived alerts. Related tasks Delete alerts Related information Monitoring device alerts Acknowledge alerts After you view an alert and understand its contents, you can acknowledge that you have read through the alert message. To acknowledge, select the check box corresponding to the alert, and then click Acknowledge.
Table 9. Alert purging Workflow Description Result Purge Task Runs after every 30 minutes on the console. If the alerts have reached its maximum capacity (that is, 50,000), check and generate the purge archives. Purge Alert Warning Generates an internal purge alert warning. If the alerts have exceeded more than 95% (that is, 475000), generates an internal purge alert to purge 10% of the alerts . Purge Alerts Alerts purged from the alert log.
1. Click the MOBILE cell corresponding to the alert policy. If enabled, the policy is disabled and the tick mark disappears. Vice-versa if disabled. • Send an SMS message: 1. Click the SMS cell corresponding to the alert policy. 2. In the Alert Actions: SMS dialog box, type phone number. 3. Click Finish. A tick mark is displayed in the cell. SMS message is sent when an alert is received that meets the set policy criteria. NOTE: An SMS is sent to only the US-based cell phones.
b) Click Next. 6. In the Severity section, select the severity level of the alert for which this policy must be activated. a) To select all the severity categories, select the All check box. b) Click Next. 7. In the Actions section, select one or more check boxes to initiate the following actions when the policy is run: • • • • • • • Send email to a designated recipient by selecting the Email check box, and specifying data in the fields.
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 to set up a policy that opens a ticket on your third party ticketing system for alert management.
Disable alert policies You can disable an alert policy, only if enabled. You disable an alert policy while creating an alert policy by clearing the Enable Policy check box in the Name and Description section. See Create alert policies. To disable an alert policy, select the check box corresponding to the alert policy and click Disable. The alert policy is disabled and the tick mark indicating that the alert policy is enabled (the ENABLED column) is removed.
13 Manage audit logs Audit logs lists the actions that were performed on the devices monitored by OpenManage Enterprise. Log data help you or Dell EMC Support teams in troubleshooting and analysis. The audit log files can be exported to the CSV file format. See Export all or selected data. NOTE: To perform any tasks on OpenManage Enterprise, you must have necessary user privileges. See Role-based OpenManage Enterprise user privileges.
14 Using jobs for device control NOTE: To perform any tasks on OpenManage Enterprise, you must have necessary user privileges. See Role-based OpenManage Enterprise user privileges. 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.
• • • • Report_Task: Create reports about devices by using inbuilt or customized data fields. See Reports. Warranty: Generate data about devices' warranty status. See Manage the device warranty. Onboarding_Task: See Onboarding devices. Discovery: Discover devices to be managed by OpenManage Enterprise. See Discovering devices for monitoring or management. OpenManage Enterprise provides a built-in report to view the list of scheduled jobs.
3. Click Finish. 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 the job data, click View Details in the right pane. See View an individual job information.
In the Job Target dialog box, the left pane lists the devices monitored by OpenManage Enterprise. In the working pane, list of devices associated with each group, and device details are displayed. For field descriptions, see Devices list. For information about device groups, see Organize devices into groups. 2. Select the check box corresponding to a device and click OK. The selected devices are displayed in the All Selected Devices section of the selected group.
15 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 Specify discovery mode for creating a Dell storage and network switch discovery job Create customized device discovery job protocol for SNMP devices Specify discovery mode for creating a MULTIPLE protocol discovery job Delete a device discovery job Enable WS-Man in HTTPS mode for discovering Windows or Hyper-V servers Create a device discovery job NOTE: To perform any tasks on OpenManage Enterprise, you must have necessary user privil
Onboarding devices Onboarding enables servers to be managed, rather than just be monitored. • • • • • If administrator-level credentials are provided during discovery, the servers are onboarded (the device status is displayed as "managed" in the All Devices view). If lower privileged credentials are provided during discovery, the servers are not onboarded (the status is displayed as "monitored" in the All Devices view).
Table 10.
Related information Discovering devices for monitoring or management Stop a device discovery job You can stop the job only if running. Discovery jobs that are completed or failed cannot be stopped. To stop a job: 1. In the list of existing discovery jobs, select the check box corresponding to the job you want to stop. NOTE: Multiple jobs cannot be stopped at a time. 2. Click Stop. The job is stopped and a message is displayed in the lower-right corner.
To remove a device from the global exclusion list: a. Select the check box and click Remove from Exclusion. b. When prompted, click YES. The device is removed from the global exclusion list. However, a device removed from the global exclusion list is not automatically monitored by OpenManage Enterprise. You must discover the device so that OpenManage Enterprise starts monitoring.
c) Enter in the Port box to edit the port number. By default, 443 is used to connect to the device. For supported port numbers, see Supported protocols and ports in OpenManage Enterprise. • Generate Trusted key: Disabled by default. Select to generate a trusted device key for communicating with devices. NOTE: First time, a user must generate the trust key by using the REST API, only after which this option can be used.
Related information Discovering devices for monitoring or management 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. 1. Under Credentials, select the SNMP version, and then enter the community type. 2. In the Connection Settings section: a) In the Retries box, enter the number of repeated attempts that must be made to discover a server.
Enable WS-Man in HTTPS mode for discovering Windows or Hyper-V servers By default, the WS-Man service is not enabled on the Windows servers. You must enable the WS-Man service on target servers in HTTPS mode. Pre-requisites: • • • IIS with HTTPS enabled WS-Man service with HTTPS enabled PowerShell 4.0 to configure the WS-Man service with certificate Creating a Self-Sign Certificate NOTE: If you have a publicly-signed certificate, things are easier and you can use Set-WSManQuickConfig -UseSSL.
Kerberos = true Negotiate = true Certificate = true CredSSP = false DefaultPorts HTTP = 5985 HTTPS = 5986 TrustedHosts Service RootSDDL = O:NSG:BAD:P(A;;GA;;;BA)(A;;GR;;;IU)S:P(AU;FA;GA;;;WD)(AU;SA;GXGW;;;WD) MaxConcurrentOperations = 4294967295 MaxConcurrentOperationsPerUser = 1500 EnumerationTimeoutms = 240000 MaxConnections = 300 MaxPacketRetrievalTimeSeconds = 120 AllowUnencrypted = false Auth Basic = true Kerberos = true Negotiate = true Certificate = false CredSSP = false CbtHardeningLevel = Relaxed D
16 Managing device inventory NOTE: To perform any tasks on OpenManage Enterprise, you must have necessary user privileges. See Role-based OpenManage Enterprise user privileges. 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.
17 Manage the device warranty NOTE: To perform any tasks on OpenManage Enterprise, you must have necessary user privileges. See Role-based OpenManage Enterprise user privileges. By clicking OpenManage Enterprise > Monitor > Warranty, you can view the warranty statuses of devices monitored by OpenManage Enterprise. You can export selected or all data to Excel sheet for statistical and analytical purposes.
18 Reports By clicking OpenManage Enterprise > Monitor > Reports, you can build customized reports to view device details at depth. Reports enables you to view data about the devices, jobs, alerts, and other elements of your data center. Reports are built-in, and user-defined. You can edit or delete only the user-defined reports. Definitions and criteria used for a built-in report cannot be edited or deleted. A preview about the report you select from the Reports list is displayed in the right pane.
Run reports NOTE: To perform any tasks on OpenManage Enterprise, you must have necessary user privileges. See Role-based OpenManage Enterprise user privileges. 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.
Table 12. The role-based access privileges for generating reports on OpenManage Enterprise User Role... Report tasks permitted... Administrators and Device Managers Run, create, edit, copy, email, download, and export Viewers Run, email, export, view, and download 1. Click Reports > Create. 2. In the Report Definition dialog box: a) Type the name and description of the new report to be defined. b) Click Next. 3.
Remove a configuration compliance baseline 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. In the Export Selected Reports dialog box, select any one of the following file formats in which the report must be exported — HTML, CSV, or PDF. 3. Click Finish. In the dialog box, open or save the file to a known location for analysis and statistical purposes.
19 Managing MIB files NOTE: To perform any tasks on OpenManage Enterprise, you must have necessary user privileges. See Role-based OpenManage Enterprise user privileges. 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.
20 Managing OpenManage Enterprise appliance settings NOTE: To perform any tasks on OpenManage Enterprise, you must have necessary user privileges. See Role-based OpenManage Enterprise user privileges. NOTE: For information about supported browsers, see the OpenManage Enterprise Support Matrix available on the support site. By clicking OpenManage Enterprise, you can: • • • • • • • • • • • Configure and manage the OpenManage Enterprise network settings such as IPv4, IPV6, time, and proxy 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. NOTE: If you have more than one IP for OpenManage Enterprise by using vNIC, you must use only the IPv4 address that is indicated in the Current IP Address field (click Application Settings > Current Settings) for accessing the REST API.
• • • • A–Z • a–z • '-!"#$%&()*,./:;?@[\]^_`{|}~+<=> USER TYPE: Indicates if the user logged in locally or remotely. ENABLED: Indicates with a tick mark when the user is enabled to perform OpenManage Enterprise management tasks. See Enable OpenManage Enterprise users and Disable OpenManage Enterprise users. ROLE: Indicates the user role in using OpenManage Enterprise. For example, OpenManage Enterprise administrator and Device Manager. See OpenManage Enterprise user role types.
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. Related reference Disable OpenManage Enterprise users Enable OpenManage Enterprise users Related information Managing OpenManage Enterprise appliance settings Manage OpenManage Enterprise users Ending user sessions 1. Select the check box corresponding to the username, and then click Terminate.
OpenManage Enterprise features User levels for accessing OpenManage Enterprise Admin Device Manager Viewer Deploy OS Y Y N Power control Y Y N Manage reports Y Y N Manage templates Y Y N Set up the OpenManage Enterprise appliance Y N N Manage discovery Y N N Manage groups Y N N Refresh inventory Y N N Set up security Y N N Manage traps Y N N Related tasks Deploying and managing OpenManage Enterprise Related reference OpenManage Enterprise user role types Add and
Select device groups for Group Manager 1. In the Add New User dialog box, from the User Role drop-down menu, select Device Manager. The Select Groups button is displayed. 2. In the Select Device Groups dialog box, in the left pane, select the device group that the user must be provided access to. Alternately, you can select a group in the left pane, and then select device(s) that the user must be provided access to. 3. Click Finish.
Directory services integration in OpenManage Enterprise Directory Services allows you to import directory groups from AD or LDAP for use on the console. To use Directory Services: • • • Add a directory connection. See Add or edit Active Directory groups to be used with Directory Services. Import directory groups and map all users in the group to a specific role. See Import AD and LDAP groups. For DM users, edit the directory group to add the groups the DM can manage.
• Manual: In the Method box, enter the FQDN or the IP address of the domain controller. For multiple servers, use a comma separated list. c) Enter the LDAP Binder Distinguished Name (DN) and password. 3. In the Advanced Options section: a) By default, LDAP port number of 636 is populated. To change, enter a port number. b) To match the LDAP configuration on the server, enter the group base DN to search for. c) Enter the user attribute to search for. If it is not configured, use UID.
Security Certificates By clicking OpenManage Enterprise > Application Settings > Security > Certifciates, you can view information about the currently available SLL certificate for the device. NOTE: To perform any tasks on OpenManage Enterprise, you must have necessary user privileges. See Role-based OpenManage Enterprise user privileges. To generate a Certificate Signing Request (CSR), see Generate and download the certificate signing request.
5. Expand Advance Settings: • • Enter one or more invalid hostname separated by a comma in Invalid Device Hostname. By default, a list of invalid device hostname is populated. • Enter the common MAC addresses separated by a comma in Common MAC Addresses. By default, a list of common MAC addresses is populated. 6. Click Apply. 7. To reset the settings to default attributes, click Discard. Set the devices that must be displayed in the All Devices view. 1. Expand All devices View Setting. 2.
• To forward the trap, select AS_IS. • To forward the normalized trap, select Normalized. 2. Click Apply. 3. To reset the settings to default attributes, click Discard. 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.
NOTE: Not automatically connected to Dell.com. You must set up a local share and manually download the update package. An audit log is created after every manual attempt to find an update. • • NOTE: Select Automatic to display information about an available updated version. Updates are automatically checked after every week. This frequency cannot be changed. Click Update Now and perform an update. Log in after the update and confirm that the product works as expected.
Process map for checking and updating the OpenManage Enterprise version Related information Deploying and managing OpenManage Enterprise Execute remote commands and scripts When you get an SNMP trap, you can run a script on OpenManage Enterprise to set up a policy that opens a ticket on your third party ticketing system for alert management. You can create and store only four remote commands for running immediately or at a later time. 1.
2. Click Save. The command is saved. You can set and run these commands also while setting your alert policies. See Creating alert policies. NOTE: • You can run only one executable or script at a time. • The executable or script can be saved on a server that is not necessarily discovered or managed by OpenManage Enterprise—not necessarily discovered by OpenManage Enterprise. • Script can have a maximum of 1024 characters.
3. Click Apply. Related tasks OpenManage Mobile settings Related information OpenManage Mobile settings 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.
View the alert notification service status OpenManage Enterprise forwards alert notifications to OpenManage Mobile subscribers through their respective device platform alert notification service. If the OpenManage Mobile subscriber has failed to receive alert notifications, you can check the Notification Service Status to troubleshoot alert notification delivery. To view the status of the alert notification service, click Application Settings > Mobile.
Field Description STATUS Displays the status of the subscriber, indicating whether or not OpenManage Enterprise is able to send alert notifications successfully to the Alert Forwarding Service. STATUS MESSAGE Status description of the status message. USER NAME Name of the OpenManage Mobile user. DEVICE ID Unique identifier of the mobile device. DESCRIPTION Description about the mobile device. FILTER Filters are policies that the subscriber has configured for alert notifications.
Problem Reason Resolution If the device is no longer connected to OpenManage Enterprise, remove the subscriber. The OpenManage Enterprise registration is being rejected by the Message Forwarding Service. [Code 154] An obsolete version of OpenManage Enterprise is being used. Upgrade to a newer version of OpenManage Enterprise.
21 Other references and field descriptions Definitions about some of the commonly displayed fields on the OpenManage Enterprise Graphical User Interface (GUI) are listed and defined in this chapter. Also, other information that is useful for further reference is described here. Topics: • • • • • • • • • Schedule Reference Firmware baseline field definitions Schedule job field definitions Field service debug workflow Unblock the FSD capability Install or grant a signed FSD DAT.
• • • Allow enabling and copying of debug logs Allow copying of real-time logs Allow backing up or restoring of database to VM. The topics referenced in each task provide detailed instructions. To enable FSD, perform the following tasks: 1. Unblock FSD capability. See Unblock the FSD capability. 2. Install or grant signed FSD DAT.ini file. See Install or grant a signed FSD DAT.ini file. 3. Invoke FSD. See Invoke FSD. 4. Disable FSD. See Disable FSD.
2. On the Invoke Requested Debug Capabilities screen, select a debug capability from a list of debug capabilities that is approved in the Dell EMC signed DAT.ini file. In the lower-right corner, click Invoke. NOTE: The debug capability that is currently supported is, RootShell. While the invoke command is run, OpenManage Enterprise can start an SSH daemon. The external SSH client can attach with OpenManage Enterprise for debugging purposes.
