Dell EMC OpenManage Enterprise–Tech Release User's Guide
Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your product. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. © 2017 - 2018 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries.
1 About OpenManage Enterprise–Tech Release OpenManage Enterprise–Tech Release is a hardware management and monitoring application that provides a comprehensive view of the Dell EMC servers, chassis, network switches, and other devices on the enterprise network. With OpenManage Enterprise–Tech Release, a web-based and one‑to‑many Systems Management application for Dell EMC systems and other third-party devices, you can: • • • • • • • • • Discover and manage devices in a data center environment.
Topics: • OpenManage Enterprise—Server Configuration Management License OpenManage Enterprise—Server Configuration Management License NOTE: Installing and using OpenManage Enterprise–Tech Release does not require the OpenManage Enterprise — Server Configuration Management license. Only the server configuration management feature requires that the OpenManage Enterprise — Server Configuration Management license is installed on target servers.
NOTE: To view if any newer version of OpenManage Enterprise–Tech Release is available, see Checking and updating the OpenManage Enterprise–Tech Release version. Also, see the OpenManage Enterprise–Tech Release Release Notes available on the support site.
2 Security features in OpenManage Enterprise– Tech Release Some of the security features of OpenManage Enterprise–Tech Release 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–Tech Release features User levels for accessing OpenManage Enterprise–Tech Release Configure device Y Y N Update device Y Y N Manage discovery Y N N Manage groups Y N N Refresh inventory Y N N Manage jobs Y Y N Create monitoring policies Y Y N Deploy OS Y Y N Power control Y Y N Manage reports Y Y N Run reports Y Y Y Set up security Y N N Manage templates Y Y N Manage traps Y N N View Y Y Y Related tasks Deploying and managi
User with this role... Has the following user privileges Device Manager (DM) NOTE: DMs can share permissions to the tasks and policies created by each other. This sharing occurs by having complete overlap with the device groups contained in the task or policy, and those assigned to the DM. If the DM loses complete overlap with the groups contained in the task or policy, the DM will no longer be able to run or edit it unless this overlap is restored.
3 Deploying and managing OpenManage Enterprise–Tech Release Dell EMC OpenManage Enterprise–Tech Release 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 Checking and updating the OpenManage Enterprise– Tech Release version.
Minimum system requirements for deploying OpenManange Enterprise–Tech Release Table 4. Minimum requirements Particulars Minimum Requirement Hypervisors VMware vSphere, and HyperV Network Available virtual NIC which has access to the management networks of all the devices to be managed from OpenManage Enterprise–Tech Release.
2. Select the host and select Action > Import Virtual Machine. 3. Select the folder that contains the OpenManage Enterprise–Tech Release virtual appliance including snapshots, virtual drives, VMs, and import files. Click Next. 4. On the Select Virtual Machine page, select the virtual machine to import (there is only one option available), and then click Next. 5. On the Choose Import Type page, select Copy the virtual machine, and then click Next. 6.
4 Getting started with OpenManage Enterprise– Tech Release Topics: • • • Logging in to OpenManage Enterprise–Tech Release Configuring OpenManage Enterprise–Tech Release Supported protocols and ports in OpenManage Enterprise–Tech Release Logging in to OpenManage Enterprise–Tech Release When you boot the system for the first time, you are prompted to accept the EULA, and then change the administrator password.
• Reboot the Appliance 2. To confirm the current appliance administrator password, select Change the Admin Password, and then provide the password. Press Tab and select Continue. 3. On the TUI screen: a) To view appliance status and the IPv4 and IPv6 statuses and addresses, select Current Appliance Status. b) To configure network interface, select Set Networking Parameters. On the Configure Network Interface screen, to enable IPv4, or IPv6, or both, press Enter. Select Apply.
Port Number Protocol Port Type Maximum Encryption Level Direction Usage 25 SMTP TCP None Out Optional e-mail alert action 53 DNS UDP/TCP None Out Network configuration 68 / 546 (IPv6) DHCP UDP/TCP None Out Network configuration 111 NFS TCP None In/Out Miscellaneous Management functions 123 NTP TCP None Out Time synchronization (if enabled) 137, 138 CIFS UDP/TCP None In/Out Miscellaneous Management functions 139, 445 CIFS TCP None In/Out Miscellaneous Management
5 OpenManage Enterprise–Tech Release Graphical User Interface overview On the OpenManage Enterprise–Tech Release 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–Tech Release 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–Tech Release Home portal By clicking OpenManage Enterprise > Home, the Home page of OpenManage Enterprise–Tech Release 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.
In the Alerts dialog box, the Critical section lists the alerts in critical status. To view all the generated alerts, click All. The SOURCE NAME column indicates the device that generated the alert. Click the name to view and configure device properties. See Viewing and configuring devices. To filter data, click Advanced Filters. Export data into Excel, CSV, HTML, or PDF format. See Exporting all or selected data. For more information about a Donut chart, see Donut chart and Device health statuses.
Managing the device compliance baseline by using the OpenManage Enterprise–Tech Release dashboard On the OpenManage Enterprise–Tech Release 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.
• 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 be mixed. • Cannot have more than one parent group.
Device health statuses Table 7. Device health statuses in OpenManage Enterprise–Tech Release Health status Definition Critical Indicates an occurrence of a failure of an important aspect of the device or environment. Warning Ok The device is about to fail. Indicates that some aspects of the device or environment are not normal. Requires immediate attention. The device is fully functional.
7 Managing All Devices By clicking OpenManage Enterprise > Devices > All Devices you can view the devices and device groups managed by OpenManage Enterprise–Tech Release. The System groups are default groups created by OpenManage Enterprise–Tech Release 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.
Organizing 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. See Viewing and configuring devices.
NOTE: To perform any tasks on OpenManage Enterprise–Tech Release, you must have necessary user privileges. See Role-based OpenManage Enterprise–Tech Release user privileges. To delete the child group of a Static or Query group: 1. Right-click the Static or Query group, and then click Delete. 2. When prompted, click YES. The group is deleted and the list under the group is updated.
Define the query criteria by using two options: • • Select existing query to copy: By default, OpenManage Enterprise–Tech Release provides a list of built-in query templates that you can copy and build your own query criteria. The number of filters predefined for every existing query varies based on the query type. For example, the query for Hypervisor Systems has 6 predefined filters, while the query for Networking Switches has only three.
1. Right-click the Static or Query group, and then click Rename. For definitions about Static or Query (Dynamic) groups, see Organizing devices into groups. 2. In the Rename Group dialog box, type the group name, and then click Finish. The updated name is listed in the left pane. Cloning a Static or Query Group By using the Static or Query groups, you can classify your servers based on their use, configuration, department of use, customers, and so on.
Deleting devices from OpenManage Enterprise–Tech Release 1. In the left pane, select the device(s). 2. In the devices list, select the check box corresponding to the device(s), and then click Delete. 3. When prompted indicating that the device(s) will be globally excluded, click YES. The device is deleted and not anymore monitored by OpenManage Enterprise–Tech Release. After device deletion, all onboarding information corresponding to the deleted devices is removed.
2. In the devices list, select the check box corresponding to the device(s). 3. Click More Actions > Update Firmware. 4. In the Update Firmware dialog box: a. In the Select Source section: • From the Baseline drop-down menu, select the baseline that must be used for comparing and upgrading or rolling back the device firmware. A list of devices that are associated with the selected firmware baseline is displayed. The compliance level of each device is displayed in the COMPLIANCE column.
Rolling back an individual device firmware version You can roll back the firmware version of a device that is later than the firmware version of the baseline it is associated with. This feature is available only when you view and configure properties of an individual device. See Viewing and configuring devices. You can upgrade or roll back the firmware version of an individual device. You can roll back the firmware version of only one device at a time.
Related information Organizing devices into groups Exporting the single device inventory You can export inventory data of only one device at a time to only the MS-Excel format. 1. In the left pane, select the device group. A list of devices in the group is displayed in the Devices list. A Donut chart indicates the device status in the working pane. See Donut chart. A table lists the properties of devices selected. See Device list. 2.
NOTE: If you export data in the .csv format, you must have the administrator-level credentials to open the file. Viewing and configuring devices NOTE: In the Device list, click the device name or IP address to view device configuration data, and then edit device configuration as described in this section.
• • • • • • • • • • • • • • • Installed Software—List of firmware and software installed on different components in the device. Processor—Processor information such as sockets, family, speed, cores, and model. RAID Controller Information—PERC and RAID controller used on the storage devices. The rollup status is equal to the status of the RAID that has high severity.
A job is created and displayed on the Jobs page. To view information about the job, click View Details in the right pane. See Viewing the jobs list. The job status is also displayed in the Recent Activity section. After the job is successfully run, the status of the job is indicated as Diagnostic Completed, and the Download link is displayed in the Recent Activity section. 4. To download the report, click the Download link, and then download the .
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 Virtual Console. The remote console page on the server is displayed.
8 Managing 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.
Topics: • • • • • • • Managing firmware Catalogs Editing a firmware catalog Creating a firmware baseline Deleting a firmware baseline Checking the compliance of a device firmware against its baseline Editing a firmware baseline Deleting a firmware baseline Managing firmware Catalogs Catalogs are bundles of firmware based on device types. All the available catalogs (update packages) are validated and posted to Dell.
1. In the Share Address box, type the IP address of the system where the firmware catalog is stored on the network. 2. In the Catalog File Path box, type the full file path of the catalog file location. • HTTPS 1. 2. 3. 4. 5. In the Share Address box, type the IP address of the system where the firmware catalog is stored on the network. In the Catalog File Path box, type the full file path of the catalog file location. In the User Name box, type the user name of the device where the catalog is stored.
Creating a firmware baseline NOTE: To perform any tasks on OpenManage Enterprise–Tech Release, you must have necessary user privileges. See Role-based OpenManage Enterprise–Tech Release 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. It is recommended to update device firmware during maintenance windows to prevent the devices or environment going offline during business hours.
After you create firmware baseline, you can periodically check the compliance of firmware version of components of a device against the baseline version defined by using a catalog. To check the firmware version compliance of a device: 1. Select the check box corresponding to the baseline, and click Check Compliance. The firmware baseline compliance job is rerun. NOTE: If the devices are not associated to a catalog, the compliance is not verified.
• To search for a device in the table, click Advanced Filters, and select or type data in the filter boxes. See Advanced Filters in OpenManage Enterprise–Tech Release Graphical User Interface overview. Updating the device firmware version by using the baseline compliance report NOTE: To perform any tasks on OpenManage Enterprise–Tech Release, you must have necessary user privileges. See Role-based OpenManage Enterprise–Tech Release user privileges.
9 Managing device configuration templates By clicking OpenManage Enterprise > Configuration > Deploy, and selecting Deploy, you can set the configuration properties such as firmware version, network properties, and BIOS versions of servers, chassis, and storage devices 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.
e) In the Configuration Elements section, select the check boxes corresponding to the device elements that must be cloned. For creating template by using server as the device, you can select to clone the server properties such as iDRAC, BIOS, Lifecycle Controller, and Event Filters. For example, iDRAC and RAID. By default, all elements are selected. f) Click Finish. A template creation job is started and the status is displayed in the STATUS column.
• The OpenManage Enterprise license is installed on all the target devices. CAUTION: Ensure that only the appropriate devices are added to the repurpose and bare-metal devices group. After deploying a configuration template on a repurpose and bare-metal device, it may not be possible to revert the device to its original configuration. 1. From the list of templates, select the check box corresponding to the device whose template must be deployed. 2. On the Template Details page, click Deploy Template. 3.
10 Managing 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. To create a configuration compliance baseline template, you must clone the existing built-in templates. To use this feature, you must have the Enterprise level license of OpenManage Enterprise–Tech Release and iDRAC for servers.
Creating a configuration compliance baseline OpenManage Enterprise–Tech Release 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 built-in baselines, click OpenManage Enterprise > Configuration > Compliance. You can create a configuration compliance baseline by: • • • Using an existing deployment template. See Managing the device configuration compliance baseline. Using template captured from a support device.
Related tasks Managing compliance baseline templates Selecting a query criteria Related information Managing the device configuration compliance baseline Removing a configuration compliance baseline Removing a configuration compliance baseline You can remove the configuration compliance level of devices associated with a configuration baseline. For field descriptions displayed in the list, see Managing the device configuration compliance baseline.
11 Monitoring 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 Managing the device configuration compliance baseline. You can create baseline templates by using deployment template, reference device, importing from a file. See Managing compliance baseline templates.
3. Type 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 Managing compliance baseline templates Cloning a compliance baseline template Creating 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 type 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: • • • • Acknowledging alerts • Ignoring alerts • Viewing archived alerts and Downloading 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.
Related tasks Deleting alerts Related information Monitoring device alerts Acknowledging 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. A tick mark is displayed in the ACKNOWLEDGE column. Unacknowledging alerts You can unacknowledge an alert if incorrect or repeated.
Workflow Description Result 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. If the number of alerts have exceeded more than 100% then 10% of the old alerts are purged to return to 90% (that is 45,000). Download Purge Alerts Download the purged alerts.
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. • Perform a power control action on the device: 1. Click the Power Control cell corresponding to the alert policy. 2. In the Alert Actions: Power Control dialog box, select to indicate if you want power cycle, turn off, or turn on a device. 3. Click Finish.
• • From the drop-down menu, select the script you want to run when this alert policy is run. You can set up running the remote command also as described in Managing OpenManage Enterprise–Tech Release appliance settings. Mobile: Send notifications to the mobile phone(s) registered with this OpenManage Enterprise–Tech Release version. See OpenManage Mobile Settings. 8. Click Next. 9. In the Summary section, details of the alert policy you defined is displayed. Carefully read through the information. 10.
d) Type the command that must be run on the OpenManage Enterprise–Tech Release server to open a ticket. For example, ./ RCE.sh $IP $MODEL $DATE $ASSETTAG $SERVICETAG 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–Tech Release.
Deleting alert policies To delete an alert policy, select the check box corresponding to the alert policy and click Delete. The alert policy is deleted and removed from the Alert Policies table. NOTE: You can delete multiple alert policies at a time by selecting the respective check boxes. To select or clear all the check boxes, select the check box in the header row next to ENABLED.
13 Managing audit logs Audit logs lists the actions that were performed on the devices monitored by OpenManage Enterprise–Tech Release. 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 Exporting all or selected data. NOTE: To perform any tasks on OpenManage Enterprise–Tech Release, you must have necessary user privileges. See Role-based OpenManage Enterprise–Tech Release user privileges.
14 Using jobs for device control NOTE: To perform any tasks on OpenManage Enterprise–Tech Release, you must have necessary user privileges. See Role-based OpenManage Enterprise–Tech Release 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.
• • • • Report_Task: Create reports about devices by using inbuilt or customized data fields. See Reports. Warranty: Generate data about devices' warranty status. See Managing the device warranty. Onboarding_Task: See Onboarding devices. Discovery: Discover devices to be managed by OpenManage Enterprise–Tech Release. See Discovering devices for monitoring or management. OpenManage Enterprise–Tech Release provides a built-in report to view the list of scheduled jobs.
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 Viewing an individual job information. Creating a Remote command job for managing devices 1.
In the Job Target dialog box, the left pane lists the devices monitored by OpenManage Enterprise–Tech Release. 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 Organizing 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–Tech Release, you must have necessary user privileges. See Role-based OpenManage Enterprise–Tech Release 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.
2. For more information about managing jobs, see Using jobs for device control. Related information Discovering devices for monitoring or management Deleting a device discovery job NOTE: A device can be deleted even when tasks are running on it. Task initiated on a device fails if the device is deleted before the completion. To delete a device discovery job: 1. Select the check box corresponding to the discovery job you want to delete, and then click Delete. 2.
2. In the Create Discovery Job dialog box, a default job name is populated. To change it, type the discovery job name. By default, the dialog box enables you to define properties of similar devices at a time. • • • To include more devices or ranges to the current discovery job, click Add. Another set of the following fields are displayed where you can specify the device properties: Type, IP/Hostname/Range, and Settings. To discover devices by importing ranges from the .csv file.
5. In the COMMUNITY STRING box, type the SNMP community string of the device that must receive the alert. 6. Default port number for SNMP traps=162. Edit if necessary. See Supported protocols and ports in OpenManage Enterprise–Tech Release. 7. To test an SNMP message, click the Send button of the corresponding trap. 8. Click Apply. To reset the settings to default attributes, click Discard. To configure the Syslog messages: 1. 2. 3. 4. Expand Syslog Configuration.
Specifying multiple devices by importing data from the .csv file 1. In the Discover Devices dialog box, type the discovery job name in Discovery Job Name. By default, a discovery job name is populated. 2. Click Import. NOTE: An error message is displayed if the .csv file contains invalid ranges, and duplicate ranges are excluded during the import operation. 3. In the Import dialog box, click Import, browse through to the .csv file which contains a list of valid ranges, and then click OK.
Specifying discovery mode for creating a server discovery job 1. From the Device Type drop-down menu, select SERVER. 2. When prompted, select: • • • Dell iDRAC: To discover by using iDRAC. Host OS: To discover by using an VMware ESXi, Microsoft Hyper-V, Windows, or Linux operating system. Non-Dell Servers (via OOB): To discover third party servers by using IPMI. 3. Click OK. Based on your selection, the fields change under Settings. 4.
Related information Discovering devices for monitoring or management Specifying discovery mode for creating a chassis discovery job 1. From the Type drop-down menu, select CHASSIS. Based on your selection, the fields change under Settings. 2. Type the IP address, host name, or IP range in IP/Hostname/Range. 3. Under Settings, type the user name and password of the server to be detected. 4. Type the community type. 5.
Specifying discovery mode for creating a MULTIPLE protocol discovery job 1. From the Type drop-down menu, select MULTIPLE to discover devices using multiple protocols. 2. Type the IP address, host name, or IP range in IP/Hostname/Range. 3. To create customized discovery template by clicking Additional Settings, see Creating customized device discovery job protocol for servers–Additional Settings for Discovery Protocols.
2. Remove all the WS-Man listeners to add the new HTTPS listener: Remove-Item -Path WSMan:\Localhost\listener\listener* -Recurse 3. Add your WS-Man HTTPS listener: New-Item -Path WSMan:\LocalHost\Listener -Transport HTTPS -Address * CertificateThumbPrint $Cert.Thumbprint –Force NOTE: Use the $Cert variable that you defined earlier to read the Thumbprint. This variable allows the New-Item cmdlet to locate the certificate in your certificates store. 4.
MaxMemoryPerShellMB = 2147483647 MaxShellsPerUser = 2147483647 NOTE: If service-basic-authentication is false, run the following command: winrm set winrm/config/service/auth @{Basic="true"} NOTE: In the WinRM configuration, enable HTTPS by running the command: winrm set winrm/config/service @{EnableCompatibilityHttpsListener="true"} 6.
16 Managing device inventory NOTE: To perform any tasks on OpenManage Enterprise–Tech Release, you must have necessary user privileges. See Role-based OpenManage Enterprise–Tech Release 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.
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 Running an inventory job now. Related information Managing device inventory Running 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. Click Run Now.
17 Managing the device warranty NOTE: To perform any tasks on OpenManage Enterprise–Tech Release, you must have necessary user privileges. See Role-based OpenManage Enterprise–Tech Release user privileges. By clicking OpenManage Enterprise > Monitor > Warranty, you can view the warranty statuses of devices monitored by OpenManage Enterprise–Tech Release. 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.
Running reports NOTE: To perform any tasks on OpenManage Enterprise–Tech Release, you must have necessary user privileges. See Role-based OpenManage Enterprise–Tech Release user privileges. When you run a report, by default, a maximum of 1000 rows are displayed. To edit this value, see Exporting all or selected data. Data displayed in the output cannot be sorted because it is defined in the query used to build a report. To sort data, edit the report query or export it to an Excel sheet.
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 Copying reports Only customized reports can be copied. 1. Select the report, click More Actions, and then click Copy. 2.
Table 10. The role-based access privileges for generating reports on OpenManage Enterprise–Tech Release 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.
Removing a configuration compliance baseline Exporting 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.
19 Managing MIB files NOTE: To perform any tasks on OpenManage Enterprise–Tech Release, you must have necessary user privileges. See Role-based OpenManage Enterprise–Tech Release 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 Removing 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.
1. In the MIB FILENAME column, expand the folder, and select the MIB files. 2. Click Remove MIB. 3. In the Remove MIB dialog box, select the check boxes of the MIBs to be removed. 4. Click Remove. The MIB files are removed and the MIB table is updated. Resolving MIB types 1. Import the MIB files. See Importing 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.
20 Managing OpenManage Enterprise–Tech Release appliance settings NOTE: To perform any tasks on OpenManage Enterprise–Tech Release, you must have necessary user privileges. See Role-based OpenManage Enterprise–Tech Release user privileges. NOTE: For information about supported browsers, see the OpenManage Enterprise–Tech Release Support Matrix available on the support site.
• OpenManage Mobile Settings Configuring OpenManage Enterprise–Tech Release network settings NOTE: To perform any tasks on OpenManage Enterprise–Tech Release, you must have necessary user privileges. See Role-based OpenManage Enterprise–Tech Release user privileges.
• • • 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–Tech Release management tasks. See Enabling OpenManage Enterprise–Tech Release users and Disabling OpenManage Enterprise–Tech Release users. ROLE: Indicates the user role in using OpenManage Enterprise–Tech Release. For example, OpenManage Enterprise–Tech Release administrator and Device Manager.
Related reference Disabling OpenManage Enterprise–Tech Release users Enabling OpenManage Enterprise–Tech Release users Related information Managing OpenManage Enterprise–Tech Release users Deleting Directory services Select the check box corresponding to the Directory Services to be deleted, and then click Delete.
OpenManage Enterprise–Tech Release features User levels for accessing OpenManage Enterprise–Tech Release Configure device Y Y N Update device Y Y N Manage discovery Y N N Manage groups Y N N Refresh inventory Y N N Manage jobs Y Y N Create monitoring policies Y Y N Deploy OS Y Y N Power control Y Y N Manage reports Y Y N Run reports Y Y Y Set up security Y N N Manage templates Y Y N Manage traps Y N N View Y Y Y Related tasks Deploying and managi
• link is displayed. Select the device group that the new user must manage. For information about selecting groups, see Selecting device groups for Group Manager. Viewer: Can only view info about all the groups and devices. However, role permissions restrict the tasks a user perform on the devices. 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.
It is possible for a domain user, for example john_smith, to be a member of multiple directory groups, and also for those groups to be assigned different roles. In this case, the user will receive the highest level role for all the directory groups the user is a member of. • • Example 1: The user is a member of three groups with admin, DM, and viewer roles. In this case, user becomes an administrator. Example 2: The user is a member of three DM groups and a viewer group.
e. In the Lockout Penalty Time box, type the duration for which the user is prevented from making any login attempt after multiple unsuccessful attempts. f. Click Apply. To reset the settings to default attributes, click Discard. Related reference Security Certificates Security Certificates By clicking OpenManage Enterprise > Application Settings > Security > Certifciates, you can view information about the currently available SLL certificate for the device.
• • Unknown: Display the latest recorded device health when the device status moved to 'unknown'. A device becomes unknown to OpenManage Enterprise–Tech Release when the connection with iDRAC is lost and the device is not anymore monitored by OpenManage Enterprise–Tech Release. 4. Click Apply. 5. To reset the settings to default attributes, click Discard. To set the mode by using which the device must be discovered. For example, DNS name and hostname: 1. Expand Discovery Setting. 2.
To configure the Syslog messages: 1. 2. 3. 4. Expand Syslog Configuration. Select the check box to enable the Syslog feature on the respective server in the SERVER column. In the DESTINATION ADDRESS/HOST NAME box, type the IP address of the device that receives the Syslog messages. Default port number by using UDP=514. Edit if necessary by typing or selecting from the box. See Supported protocols and ports in OpenManage Enterprise–Tech Release. 5. Click Apply. 6.
Managing warranty settings By clicking OpenManage Enterprise > Application Settings > Warranty Settings, you can enable the warranty scoreboard notification which is present in the OpenManage Enterprise–Tech Release header by doing the following. All the parameters or settings on this page determine the logic for the count of the warranty scoreboard. By default, the user is alerted 90 days before the warranty expires. To edit the number of days: 1.
Table 13. The role-based access privileges for updating the OpenManage Enterprise–Tech Release version User with this role... Can... Administrator View the current OpenManage Enterprise–Tech Release version and update the version Device Manger and Viewer Only view the current OpenManage Enterprise–Tech Release version NOTE: If an updated version of OpenManage Enterprise–Tech Release is available, a message is displayed on the Dashboard.
Process map for checking and updating the OpenManage Enterprise–Tech Release version Related information Deploying and managing OpenManage Enterprise–Tech Release Executing remote commands and scripts When you get an SNMP trap, you can run a script on OpenManage Enterprise–Tech Release 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.
d) Type the command that must be run on the OpenManage Enterprise–Tech Release server to open a ticket. For example, ./ RCE.sh $IP $MODEL $DATE $ASSETTAG $SERVICETAG 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–Tech Release.
Related tasks OpenManage Mobile Settings Related information OpenManage Mobile Settings Deleting an OpenManage Mobile subscriber Enabling or disabling 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 omeAdministrator user rights are required for enabling or disabling OpenManage Mobile subscribers.
Viewing the alert notification service status OpenManage Enterprise–Tech Release 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 Settings.
Field Description Status Displays the status of the subscriber, indicating whether or not OpenManage Enterprise–Tech Release is able to send alert notifications successfully to the Alert Forwarding Service. Status Message Status description of the status message. Username Name of the OpenManage Mobile user. Device Id Unique identifier of the mobile device. Description Description about the mobile phone. Filter Filters are policies that the subscriber has configured for alert notifications.
Problem Reason Resolution device operating system has been upgraded troubleshooting procedures specified in the or restored. OpenManage Mobile User’s Guide and reconnect the device to OpenManage Enterprise–Tech Release. If the device is no longer connected to OpenManage Enterprise–Tech Releasee, remove the subscriber. The OpenManage Enterprise–Tech Release registration is being rejected by the Message Forwarding Service. [Code 154] An obsolete version of OpenManage Enterprise–Tech Release is being used.
21 Other references and field descriptions Definitions about some of the commonly displayed fields on the OpenManage Enterprise–Tech Release 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 Unblocking the FSD capability Installing or granting a signed FSD DAT.
Field service debug workflow In OpenManage Enterprise–Tech Release, you can authorize console debugging by using the Field Service Debug (FSD) option. By using FSD, you can perform the following tasks: • • • 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 Unblocking the FSD capability. 2.
Invoking FSD Ensure that the DAT.ini file is signed, returned by Dell EMC, and uploaded to OpenManage Enterprise–Tech Release. 1. To invoke a debug capability, on the FSD Functions screen, select Invoke FSD Capabilities. 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.
