Dell EMC OpenManage Enterprise Version 3.4 User's Guide June 2020 Rev.
Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your product. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. © 2017 - 2020 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries.
Contents Tables............................................................................................................................................9 Chapter 1: About Dell EMC OpenManage Enterprise......................................................................... 10 New in this release................................................................................................................................................................11 Other information you may need...................
Adding or editing devices in a Static child group.......................................................................................................42 Rename child groups of Static or Query Dynamic groups....................................................................................... 42 Clone a Static or Query group..................................................................................................................................... 42 Add devices to a new group.....................
Deploy device templates.....................................................................................................................................................64 Deploy IOA templates......................................................................................................................................................... 65 Clone templates.................................................................................................................................................
Automatic refresh of MX7000 chassis on insertion and removal sleds.................................................................. 91 Create alert policies........................................................................................................................................................91 Enable alert policies....................................................................................................................................................... 94 Edit alert policies.....
Edit an inventory schedule job.......................................................................................................................................... 116 Chapter 17: Manage the device warranty........................................................................................ 118 View and renew device warranty..................................................................................................................................... 118 Chapter 18: Reports.....................
Update from Dell.com..................................................................................................................................................143 Update from an internal network share ................................................................................................................... 143 Install an Extension.......................................................................................................................................................
Tables 1 Other information you may need...............................................................................................................................11 2 Role-based user privileges in OpenManage Enterprise......................................................................................... 14 3 OpenManage Enterprise User role types................................................................................................................ 15 4 Minimum recommended hardware.....
1 About Dell EMC OpenManage Enterprise OpenManage Enterprise is a systems management and monitoring application that provides a comprehensive view of the Dell EMC servers, chassis, storage, and network switches on the enterprise network. With OpenManage Enterprise, a web-based and one‑to‑many systems management application, you can: • • • • • • • • • • • Discover and manage devices in a data center environment. Create and manage OpenManage Enterprise users. Group and manage devices.
• • • • • Manage the device warranty on page 118 Reports on page 120 Managing MIB files on page 125 Role-based OpenManage Enterprise user privileges on page 14 Directory services integration in OpenManage Enterprise on page 133 Topics: • • • • New in this release Other information you may need Contacting Dell EMC OpenManage Enterprise Advanced license New in this release • • • • • • • • • Server-initiated discovery—With this feature, new servers in a datacenter can notify OpenManage Enterprise and can
Table 1. Other information you may need (continued) Document Description Availability Dell EMC SupportAssist Enterprise User's Guide Provides information about installing, configuring, Dell.com/ServiceabilityTools using, and troubleshooting SupportAssist Enterprise. Contacting Dell EMC NOTE: If you do not have an active internet connection, you can find contact information on your purchase invoice, packing slip, bill, or Dell EMC product catalog.
• In the Licenses dialog box, read through the message and click appropriate links to view and download OpenManage Enterprise related open-source files, or other open-source licenses. License-based features in OpenManage Enterprise The OpenManage Enterprise Advanced license is required to use the following features of OpenManage Enterprise: • • • • Server configuration deployment. Server configuration compliance baseline creation and remediation. Boot to ISO.
2 Security features in OpenManage Enterprise Some of the security features of OpenManage Enterprise are: • • • • User roles (Administrator, Device Manager, Viewer) with differing device management functionality. Hardened appliance with Security-Enhanced Linux (SELinux) and an internal firewall. Encryption of sensitive data in an internal database. Use of encrypted communication outside the appliance (HTTPS).
Table 2.
Table 3. OpenManage Enterprise User role types (continued) User with this role... Has the following user privileges Device Manager (DM) • • Run tasks, policies, and other actions on the devices assigned by the administrator. Cannot delete or modify any groups. NOTE: Users with Device Manager (DM) privileges cannot be assigned groups. Viewer • • • Can only view information displayed on OpenManage Enterprise and run reports. By default, has read-only access to the console and all groups.
3 Deploy and manage OpenManage Enterprise Dell EMC OpenManage Enterprise is provided as an appliance that you can deploy on a hypervisor and manage resources to minimize downtime. The virtual appliance can be configured from the application web console after initial network provisioning in the Text User Interface (TUI). For steps to view and update the console version, see Check and update the version of the OpenManage Enterprise and the available extensions on page 141.
Minimum system requirements for deploying OpenManage Enterprise Table 5. Minimum requirements Particulars Minimum requirements Supported hypervisors • VMware vSphere versions: • ○ vSphere ESXi 5.5 onwards Microsoft Hyper-V supported on: • ○ Windows Server 2012 R2 onwards KVM supported on: ○ Red Hat Enterprise Linux 6.5 onwards Network Available virtual NIC which has access to the management networks of all the devices which is managed from OpenManage Enterprise.
9. On the Disk Format page, click Thick provision to pre-allocate physical storage space to VMs at the time a drive is created. 10. On the Ready to Complete page, review the options you selected on previous pages and click Finish to run the deployment job. A completion status window displays where you can track job progress. Deploy OpenManage Enterprise on Hyper-V 2012 R2 and earlier host NOTE: • To perform any tasks on OpenManage Enterprise, you must have necessary user privileges.
• To perform any tasks on OpenManage Enterprise, you must have necessary user privileges. See Role-based OpenManage Enterprise user privileges on page 14 • If a secondary adapter is added before powering on the appliance for the first time, the adapter will be configured with IPv4 and IPv6 disabled. Upon login to the TUI, and after accepting the EULA and changing the admin password, the adapter will show up as DISABLED and must be configured by the user.
2. Start the Hyper-V Manager in the Windows Server 2019. The Windows Hyper-V should be displayed under the Hyper-V Manager. If not, right-click Hyper-V Manager, and then select Connect to Server. 3. Click Actions > New > Virtual Machine to start the New Virtual Machine Wizard. 4. Click Next on the initial Before You Begin page. 5. On the Specify Name and Location page • • provide the Virtual machine name.
13. Under Advanced options, ensure that the bridged host device network is selected and KVM is selected as the Virt Type. 14. Click Finish. OpenManage Enterprise appliance is now deployed by using the KVM. To get started with OpenManage Enterprise, see Log in to OpenManage Enterprise on page 24. Deploy OpenManage Enterprise programmatically OpenManage Enterprise can be deployed programmatically (using a script) on VMWare ESXi version 6.5 or later.
NOTE: Remember to replace the entire tag including the < and > symbols. 4. Run the modified ovftool command from the previous step. NOTE: The ovftool command must be run with the --X:injectOvfEnv and --powerOn flags because they are required for programmatic deployment. After the ovftool command is run, the manifest validates and the deployment begins.
4 Get started with OpenManage Enterprise Topics: • • • • • • Log in to OpenManage Enterprise Configure OpenManage Enterprise by using Text User Interface Configure OpenManage Enterprise Recommended scalability and performance settings for optimal usage of OpenManage Enterprise Supported protocols and ports in OpenManage Enterprise Use case links for the supported protocols and ports in OpenManage Enterprise Log in to OpenManage Enterprise When you boot the system for the first time from the Text User Inte
Table 7. Text User Interface options Options Descriptions Change the Admin Password Select Change the Admin Password screen to enter a new password and confirm the password. For the first time, you must change the password by using the TUI screen. Display Current Appliance Status Select Display Current Appliance Status to view the URL and the status of the appliance. You can also view statuses of the Task Execution, Event Processing, Tomcat, Database, and Monitoring services.
Table 7. Text User Interface options (continued) Options Descriptions firewall rules are applied to the primary interface, which allow for tighter access control such as access restriction by IP range. NOTE: If multihoming is enabled, the appliance can be accessed from two networks. In this case, the primary interface is used by the appliance for all external communication and when proxy settings are used.
Table 7. Text User Interface options (continued) Options Descriptions watchdog: BUG: soft lockup - CPU#0 stuck for 36s! [java:14439]. The soft lockup issue likely occurs as a result of the hypervisor being overloaded. In such situations, it is recommended to have at least 16 GB of RAM and CPU of 8000 MHz reserved to the OpenManage Enterprise appliance. It is also recommended that the OpenManage Enterprise appliance be restarted when this message is displayed.
Recommended scalability and performance settings for optimal usage of OpenManage Enterprise The following table lists the performance parameters of the supported features in OpenManage Enterprise. To ensure an optimal performance of OpenManage Enterprise, Dell EMC recommends to run the tasks at the specified frequency on the maximum number of devices that are recommended per task. Table 8.
Table 9. OpenManage Enterprise Supported protocols and ports on management stations (continued) Port Number Protocol Port Type Maximum Encryption Level Source Direction Destination Usage 53 DNS UDP/TCP None OpenManage Enterprise appliance Out Management station • For DNS queries. 68 / 546 (IPv6) DHCP UDP/TCP None OpenManage Enterprise appliance Out Management station • Network configuration.
Table 9. OpenManage Enterprise Supported protocols and ports on management stations (continued) Port Number Protocol Port Type Maximum Encryption Level Source Direction Destination Usage 514 Syslog TCP None OpenManage Enterprise appliance Out Syslog server • To send alert and audit log information to Syslog server. 3269 LDAPS TCP None OpenManage Enterprise appliance Out Management station • AD/ LDAP login for Global Catalog.
Use case links for the supported protocols and ports in OpenManage Enterprise Table 11. Use case links for the supported protocols and ports in OpenManage Enterprise Use case URL Upgrade OpenManage Enterprise appliance https://downloads.dell.com/openmanage_enterprise/ Access device warranty https://apigtwb2c.us.dell.com/PROD/sbil/eapi/v5/assetentitlements Update catalogs https://downloads.dell.com/catalog/ Push new alert notifications using the OpenManage Mobile application https://openmanagecloud.
5 OpenManage Enterprise Graphical User Interface overview On the OpenManage Enterprise Graphical User Interface (GUI), you can use menu items, links, buttons, panes, dialog boxes, lists, tabs, filter boxes, and pages to navigate between pages and complete device management tasks. Features such as devices list, Donut charts, audit logs, OpenManage Enterprise settings, system alerts, and firmware/driver update are displayed at more than one place.
• • • • • acknowledged alerts, see Customize the alert display on page 139. Deleting the alerts reduces the count. For information about symbols that are used to indicate severity statuses, see Device health statuses on page 37. Click a severity symbol to view all events in that severity category on the Alerts page. To view all the events, click All events. See Managing device alerts. H—Total number of device warranties in Critical (expired) and in Warning (expiring soon) statuses.
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.
See Viewing and configuring devices on page 47. To filter data, click Advanced Filters. Export data into Excel, CSV, HTML, or PDF format. See Export all or selected data on page 47. For more information about a Donut chart, see Donut chart on page 37 and Device health statuses on page 37. To view the summary of devices in a different device group monitored by OpenManage Enterprise, select from the Device Groups drop-down menu.
NOTE: An MX7000 chassis can be a lead, stand-alone, or member chassis. If an MX7000 chassis is a lead chassis and has a member chassis, the latter is discovered by using the IP of its lead chassis.
Donut chart You can view a Donut chart in different sections of your OpenManage Enterprise. The output displayed by the Donut chart is based on the items you select in a table. A Donut chart indicates multiple statuses in OpenManage Enterprise: • The health status of devices: Displayed on the Dashboard page. Colors in the Donut chart split the ring proportionally to indicate the health of devices monitored by OpenManage Enterprise. Every device status is indicated by a color symbol.
7 Managing devices By clicking OpenManage Enterprise > Devices you can view the devices and device groups managed by OpenManage Enterprise. The System groups are default groups created by OpenManage Enterprise when shipped, and Custom groups are created by users such as administrators and device managers. You can create child groups under these two parent groups. For information about the parent-child rules, see Device Groups.
• • Start Management application iDRAC of a device Start the Virtual Console Organize devices into groups In a data center, for effective and quick device management, you can: • • • Group the devices. For example, you can group devices based on functions, OSs, user profiles, location, jobs run, and then run queries to manage devices. Filter the device-related data while managing devices, updating firmware, discovering devices, and managing alert policies and reports.
• Query Group: Groups that are dynamically defined by matching user-specified criteria. Devices in the group change based on the result of devices that are discovered by using criteria. For example, a query is run to discover servers that are assigned to the Finance department. However, the Query Groups have a flat structure without any hierarchy. NOTE: Static and Query groups: • Cannot have more than one parent group. Meaning, a group cannot be added as a sub-group under its parent group.
For definitions about Static or Query (Dynamic) groups, see Organize devices into groups on page 35. 2. In the Create Query Group Wizard dialog box, enter a name and description for the group. 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 on page 41. 5. Click Finish. The query group is created and listed in line with the parent group in the left pane.
Adding or editing devices in a Static child group By using the Static child groups, you can classify your servers based on their use, configuration, department of use, customers, and so on. You can add or remove devices to the child groups, and then edit, remove, delete, and clone such groups. NOTE: To perform any tasks on OpenManage Enterprise, you must have necessary user privileges. See Role-based OpenManage Enterprise user privileges on page 14. 1.
After you select devices under the All Devices tab, the selected devices are listed under All Selected Devices. See Device list. 3. Click Finish. A new group is created and the devices are added to the selected group. NOTE: For creating groups or adding devices to a group, you must follow the parent-child relationship of groups. See Device Groups. Add devices to existing group NOTE: To perform any tasks on OpenManage Enterprise, you must have necessary user privileges.
1. In the left pane, select the System group or Custom group whose device must be excluded. 2. In the devices list, select the check box corresponding to the device(s), and then click Exclude. 3. When prompted whether or not to exclude the selected device(s), click YES. The devices are excluded, added to the global exclusion list, and not anymore monitored by OpenManage Enterprise. 4.
Roll back an individual device's 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 on page 47. 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 Organize devices into groups on page 35 Export the single device inventory You can export inventory data of only one device at a time to only the .csv 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.
• • • • RACADM CLI: Click to run a RACADM command. See Create a Remote command job for managing devices on page 101. Update Firmware: See Update the device firmware and drivers by using baselines on page 44. Onboarding: See Onboarding devices on page 106. Export All and Exported Selected: See Export all or selected data on page 47. Hardware information displayed for MX7000 chassis • • • • • • Chassis Power Supplies—Information about the Power Supply Units (PSUs) used in the sleds and other components.
Device Overview • On the page, under Overview, the health, power status, and Service Tag of the device is displayed. Click the IP address to open the iDRAC login page. See the iDRAC User's Guide available on the Dell support site. ○ Information: Device information such as Service Tag, DIMM slots, iDRAC DNS name, processors, chassis, operating system, and data center name.
• Guest Information—Displays the guest devices monitored by OpenManage Enterprise. UUID is the Universally Unique Identifier of the device. The GUEST STATE column indicates the working status of the guest device. Run and download Diagnostic reports NOTE: To perform any tasks on OpenManage Enterprise, you must have necessary user privileges.
5. In the Download SupportAssist Files dialog box, click the .TXT file link, and then download the report. Each link represents the log type you selected. 6. Click OK. Managing individual device hardware logs NOTE: The hardware logs are available for YX4X servers, MX7000 chassis and sleds. See Generic naming convention for Dell EMC PowerEdge servers on page 155 for more information. • • • • • • On the page, click Hardware logs.
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 Manage the device firmware and drivers On the OpenManage Enterprise > Configuration > Firmware/Driver Compliance page, you can manage the firmware of all the 'managed' devices. With OpenManage Enterprise version 3.4, you can also update the drivers of the Windows-based devices. NOTE: • To perform any tasks on OpenManage Enterprise, you must have the necessary user privileges. See Role-based OpenManage Enterprise user privileges on page 14.
• • • Delete baselines Edit a baseline Check the compliance of a device firmware and driver Manage firmware and driver Catalogs Catalogs are bundles of firmware and drivers based on device types. All the available catalogs (update packages) are validated and posted to Dell.com. You can use the catalog directly from the online repository or it can be downloaded to a network share. Using these catalogs, you can create firmware/driver baselines for the discovered devices and check their compliance.
• NFS i. In the Share Address box, enter the IP address of the system where the firmware catalog is stored on the network. ii. In the Catalog File Path box, enter the full file path of the catalog file location. Example path: nfsshare\catalog.xml • CIFS i. In the Share Address box, enter the IP address of the system where the firmware catalog is stored on the network. ii. In the Catalog File Path box, enter the full file path of the catalog file location. Example path: Firmware\m630sa \catalog.xml iii.
Update a catalog The existing firmware and driver catalogs can be updated from the Dell.com site or the Dell Update Packages (DUPs) located in the network share. To update a catalog: 1. On the Catalog Management page, select a catalog. 2. Click the Check for update button that is located in the right pane of the Catalog Management page. 3. Click YES. If the selected catalog was an online catalog, it is replaced by the most up-to-date version that is maintained at the Dell.com site.
a. In the Baseline Information section: i. ii. iii. iv. From the Catalog drop-down menu, select a catalog. To add a catalog to this list, click Add. See Managing firmware Catalogs. In the Baseline Name box, enter a name for the baseline, and then enter the baseline description. Click Next. b. In the Target section: • To select the target device(s): • i. Select Select Devices, and then click the Select Devices button. ii.
• To perform any tasks on OpenManage Enterprise, you must have necessary user privileges. See Role-based OpenManage Enterprise user privileges on page 14. • The firmware and drivers (64-bit Windows) for the non-compliant devices in the baseline are not automatically updated and must be updated by the user. It is recommended to update device firmware and drivers during the maintenance windows to prevent the devices or environment going offline during business hours.
• • • • • • • Info : Symbol corresponding to every device component is linked to the support site page from where the firmware/driver 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 firmware and driver version of the device available in the associated catalog.
To update a device firmware and/or driver by using the baseline compliance report: 1. On the Configuration > Firmware/Driver Compliance page, select the check box corresponding to the baseline to which the device is attached, and then click View Report in the right pane. On the Compliance Report page, the list of devices associated with the baseline and their compliance level is displayed. For field descriptions, see View the baseline compliance report on page 57. 2.
9 Manage device configuration templates From the Configuration > Templates page, you can configure the servers and chassis by using the device configuration templates(predefined or custom). Templates enable you to optimize your data center resources and reduce the cycle time in creating clones and deployments. Templates enhance your business-critical operations in converged infrastructure that uses software-defined infrastructures.
d. In the Reference Device section, click Select Device to select the device whose configuration properties must be used for creating the new template. For more information about selecting devices, see Selecting target devices and device groups. NOTE: You can select only one device as a reference device. NOTE: Only the IOA templates that were extracted at the time of chassis discovery are available for cloning .
1. On the Configuration > Templates page, select the required custom template check box, and then click Edit. 2. In the Edit Template dialog box: a. In the Template Information section, edit the template name and description. The template type cannot be edited. b. Click Next. c. In the Edit Components section, the template attributes are displayed in: • The Guided view — This view of attributes displays only common attributes, grouped together by function.
4. This section is read-only. Read through the settings and click Finish. The updated template attributes are saved to the template. Edit a chassis template Editing chassis templates is possible with OpenManage Enterprise. NOTE: To edit chassis templates you must have the privileges of an Administrator or a Device Manager. For more details, see Role-based OpenManage Enterprise user privileges on page 14. To edit a chassis template: 1.
Deploy device templates You can deploy a template that includes a set of configuration attributes to specific devices. Deploying a device configuration template on the devices ensures that the devices are uniformly configured. NOTE: To perform any tasks on OpenManage Enterprise, you must have necessary user privileges. See Role-based OpenManage Enterprise user privileges on page 14.
b. Expand the attribute categories and then select or clear the attributes that must be included or excluded during template deployment on the target device. c. Click Next. 6. In the Virtual Identities section, click Reserve identities. The assigned virtual identities of the NIC cards of the selected target device are displayed. To view all the assigned identities of the identity pool of the selected target device, click View all NIC details.
Auto deployment of configuration on yet-to-bediscovered servers or chassis Existing configuration templates in the OpenManage Enterprise can be assigned to the servers and chassis which are awaiting discovery. These configuration templates are automatically deployed on the respective devices when they are discovered and onboarded. To access the Auto Deploy page, click OpenManage Enterprise > Configuration > Auto Deploy.
• Click Next. 10. On the Virtual Identities page, click Reserve identities. The assigned virtual identities of the NIC cards of the selected target device are displayed. To view all the assigned identities of the identity pool of the selected target device, click View all NIC details. 11. In the Target Attributes section, the non-virtual identity attributes specific to each of the selected target devices, such as the location attributes and IP address, can be changed before the deployment of the template.
Manage identity pools—Stateless deployment The I/O interfaces of a server, such as NICs or HBAs, have unique identity attributes that are assigned by the manufacturer of the interfaces. These unique identity attributes are collectively known as the I/O identity of a server. The I/O identities uniquely identify a server on a network and also determine how the server communicates with a network resource using a specific protocol.
Identities that provide a unique virtual identity for FCoE operations. These identities are defined by both MAC address and the FC addresses (that is WWNN and WWPN). WWNN and WWPN identities are required to support boot-from-SAN and for data access using FC and Fibre Channel over Ethernet (FCoE) protocols. OpenManage Enterprise uses the identity pools to automatically assign virtual identities to the device template that is used for deploying a server.
• AABB.CCDD.EEFF The length of the postfix can be a maximum of 50 characters. This option is displayed only if the Include FC Identity check box is selected. Number of WWPN/WWNN Addresses Select the number of WWPN or WWNN address. The address can be between 1 and 5000. This option is displayed only if the Include FC Identity check box is selected. Actions Previous Displays the FCoE tab. Finish Saves the changes and displays the Configuration page.
Primary DNS Server Enter the primary DNS server address. Secondary DNS Server Enter the secondary DNS server address. NOTE: The IP Address Range, Gateway, Primary DNS Server, and Secondary DNS Server must be valid IPv4 addresses. Actions Previous Displays the Ethernet tab. Next Displays the FCoE tab. Finish Saves the changes and displays the Configuration page. Cancel Closes the Create Identity Pool wizard without saving the changes.
• AABB.CCDD.EEFF The maximum length of a MAC address is 50 characters. This option is displayed only if the Include ethernet virtual MAC addresses check box is selected. Number of Virtual MAC Identities Select the number of virtual MAC identities. The identities can be 1-50. This option is displayed only if the Include ethernet virtual MAC addresses check box is selected. Actions Previous Displays the Pool Information tab. Next Displays the iSCSI tab.
Network types NOTE: You can select a network type for MX7000 chassis only. Table 14. Network types Network types Description General Purpose (Bronze) Used for low priority data traffic.
Import network definitions The following options are available to import the network definitions: 1. Import VLAN definitions from a file To import VLAN definitions from a file: a. Click Configuration > VLANs. b. Click Import and select Import from File. c. Navigate to the file location and select an existing .json or .csv file containing the VLAN definitions, and click Open. NOTE: • Invalid entries or content type in the files are flagged and are not imported. • VLAN definitions in the .csv and .
10 Manage Profiles A 'Profile' is a specific instance of an existing template that is customized with attributes unique to an individual device. Profiles can be created either implicitly during a template's deployment/auto-deployment or from the existing templates by the user. A Profile consists of target-specific attribute values along with the BootToISO choices, and iDRAC management IP details of the target device.
• • • • • • Assign a profile to a device or service tag (through auto-deploy). See, Assign a Profile on page 77 Unassign a profile from a device or service tag. See, Unassign profiles on page 78 Redeploy profile changes to the associated target device. See, Redeploy profiles on page 78 Migrate profile from one target (device or service tag) to another. Delete profiles. See, Delete Profiles on page 79 Export and then download profile(s) data to HTML, CSV or PDF.
3. The Bandwidth section displays the following bandwidth settings of the partitioned NICs: NIC identifier, Port, Partition, Min Bandwidth (%), and Max Bandwidth (%). Click Next 4. The VLANs section displays the following VLAN details of the profiles: NIC teaming, NIC identifier, Port, Team, Untagged Network, and Tagged Network. 5. Click Finish to close the View Network wizard. Edit a profile An existing profile can be edited on the Configurations > Profiles page.
• Don't change IP settings • Set as DHCP • Set static IP f. On the Target Attributes page, the attributes are displayed under the BIOS, System, NIC, and iDRAC sections. You can select, unselect, or edit the attributes before deployment. g. On the Virtual Identities page, click Reserve identities. The assigned virtual identities of the NIC cards of the selected target device are displayed. To view all the assigned identities of the identity pool of the selected target device, click View all NIC details. h.
• Enable Schedule and select a date and time to schedule the redeployment. 4. Click Finish to proceed. When a profile is redeployed, a Redeploy Profiles job is executed. The status of the job can viewed on the Monitor > Jobs page. Migrate a Profile A deployed or an autodeployed profile can be migrated from it's existing target device or service tag to a another identical target device or service tag. When a migration is successful, the profile target assignment reflects the new target.
Export Profile(s) data as HTML, CSV, or PDF To export the profile(s) data as a HTML, CSV, or PDF file. 1. On the Configuration > Profiles page, select the profile(s). 2. Click Export and in the Export Selected dialog box choose from HTML, CSV, or PDF. 3. Click Finish. The profile(s) data is downloaded in the selected format.
11 Managing the device configuration compliance By selecting OpenManage Enterprise > Configuration > Configuration Compliance, you can create configuration baselines by using the built-in or user-created compliance templates. You can create a configuration compliance template from an existing deploy template, reference device, or by importing from a file. To use this feature, you must have the Enterprise level license of OpenManage Enterprise and iDRAC for servers.
Manage compliance baseline templates Use compliance template to create compliance baselines and then periodically check the configuration compliance status of devices that are associated with the baseline. See Managing the device configuration compliance on page 81. You can create baseline templates by using deployment template, reference device, importing from a file. See Manage compliance baseline templates on page 82.
To use the configuration properties of a device as a template for creating configuration baseline, the device must be already onboarded. See Onboarding devices on page 106. 1. Click Configuration > Configuration Compliance > Template Management > Create > From Reference Device. 2. In the Create Compliance Template dialog box, enter a name and description for the baseline compliance template. 3. Select the options to create the template by cloning properties of either a server or chassis. 4. Click Next. 5.
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. Click Save or Discard to implement or to reject the changes. The template is edited and the updated information is saved.
Remove a configuration compliance baseline on page 85 Edit a configuration compliance baseline You can edit the devices, name, and other properties associated with a configuration baseline. For field descriptions displayed in the list, see Managing the device configuration compliance on page 81. CAUTION: If a template used for a baseline is already associated with another baseline, editing the template properties changes the baseline compliance levels of devices already associated.
• If a device is removed, its configuration inventory is no longer retrieved, and the already retrieved information is also deleted, unless the inventory is associated with an Inventory job. A template used as a compliance baseline cannot be deleted if associated with a device. Appropriate messages are displayed in such cases. Read through the error and event message displayed and act accordingly.
12 Monitoring device alerts By clicking the OpenManage Enterprise menu, and selecting items under Alerts, you can: • • • • • Monitor alerts by: ○ Acknowledge alerts on page 88 ○ Ignore alerts on page 88 ○ View archived alerts on page 89 and Download archived alerts on page 89 Create and manage alert policies. See Alert policies on page 89. View alert definitions. See Alert definitions on page 95. Hide and display acknowledged alerts. See Customize the alert display on page 139.
• • • • SEVERITY indicates the severity of an alert. ACKNOWLEDGE displays a tick mark when an alert is viewed and acknowledged. The total number of alerts generated is also displayed in the header of OpenManage Enterprise. See OpenManage Enterprise Graphical User Interface overview on page 32. Click the hyper-linked device name under SOURCE NAME to view and configure device properties that generated the alert. See Viewing and configuring devices on page 47.
Related concepts View the alert logs on page 87 Related information Monitoring device alerts on page 87 View archived alerts At a time, a maximum of 50,000 alerts can be generated and viewed by using OpenManage Enterprise. When 95% of the 50,000 limit (47,500) is reached, OpenManage Enterprise generates an internal message indicating that, when the count reaches 50,000, OpenManage Enterprise will automatically purge 10% (5000) of the archived alerts.
A tick mark corresponding to an alert policy indicates that the alert policy is enabled. When an alert is received that meets the policy criteria, you can configure the policy to perform actions such as sending email message and enabling SNMP trap forwarding. After prior setting, you can do the following: • Send an email message: 1. Click the EMAIL cell corresponding to the alert policy. 2. In the Alert Actions: Email dialog box, type information about the message to be sent.
Automatic refresh of MX7000 chassis on insertion and removal sleds OpenManage Enterprise can almost instantly reflect the addition or removal of sleds after a standalone or a lead MX7000 chassis is discovered or onboarded. When a standalone or a lead MX7000 chassis is discovered or onboarded by using OpenManage Enterprise version 3.4, an alert policy is created simultaneously on the the MX7000 chassis.
• NOTE: Alerts of SNMPv1, SNMPv2, and SNMPv3 protocols sent by such undiscovered (foreign) devices are recognized by OpenManage Enterprise. Click Next. 5. (Optional) By default, the alert policies are always active. To limit the dates and the time when the policy is applicable, in the Date and Time section you can— a. b. c. d. Select the Date Range, by filling the from and to dates. To specify the time when the policy would apply, select and Time interval check box and enter the time frames.
NOTE: Selecting target devices or groups is not applicable while forwarding the audit logs to the Syslog server. 5. (Optional) By default, the alert policies are always active. To limit activity, in the Date and Time section, select the 'from' and 'to' dates, and then select the time frame. a. Select the check boxes corresponding to the days on which the alert policies must be run. b. Click Next. 6. In the Severity section, select the severity level of the alerts for which this policy must be activated. a.
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 on page 28. 5. Click Apply. 6. To reset the settings to default attributes, click Discard. Execute remote commands and scripts When you get an SNMP trap, you can run a script on OpenManage Enterprise. This sets up a policy that opens a ticket on your third party ticketing system for alert management.
Edit alert policies 1. Select the check box corresponding to the alert policy and click Edit. 2. In the Create Alert Policy dialog box, edit the properties of the alert policy. For navigating through different sections in the dialog box, see Create alert policies on page 91. NOTE: The Time Interval check box is disabled by default for alert policies on OpenManage Enterprise versions before version 3.3.1. After upgrading, enable the Time Interval and update the fields to reactivate the policies.
• • • CATEGORY: Class to which the error message belongs to. For information about categories, see the Event and Error Message Reference Guide for Dell EMC PowerEdge Servers available on the support site. Recommended Action: Resolution to the error by using GUI, RACADM, or WS-Man commands. Where necessary, you are recommended to refer to documents on the support site or TechCenter for more information. Detailed Description: More information about an issue for easy and fast resolution.
13 Manage audit logs Audit logs lists the actions that were performed on the devices monitored by OpenManage Enterprise. Log data help you or Dell EMC Support teams in troubleshooting and analysis. The audit log files can be exported to the CSV file format. See Export all or selected data on page 47. NOTE: To perform any tasks on OpenManage Enterprise, you must have necessary user privileges. See Role-based OpenManage Enterprise user privileges on page 14.
Forward audit logs to remote Syslog servers To monitor all the audit logs of OpenManage Enterprise from Syslog servers, you can create an alert policy. All the audit logs such as user login attempts, creation of alert policies, and running different jobs can be forwarded to Syslog servers. To create an alert policy to forward audit logs to Syslog servers: 1. Select Alerts > Alert Policies > Create. 2.
14 Using jobs for device control NOTE: To perform any tasks on OpenManage Enterprise, you must have necessary user privileges. See Role-based OpenManage Enterprise user privileges on page 14. NOTE: Each job type is limited to devices that: • The user has permissions to access. • Have the ability to complete the required action.
Table 20. Job status and description (continued) Job Status Description Failed Job run was unsuccessful. Stopped Job run was interrupted by the user. A job can belong to any one of the following types: Table 21. Job Types and description Job Type Description Health Checks the health status of the devices. See Device health statuses on page 37. Inventory Creates inventory report of the devices. See Managing device inventory on page 115.
iii. Click Next. b. In the Target section, select the target devices and click Next. See Select target devices and device groups on page 102. c. In the Schedule section, run the job immediately or schedule for a later point of time. See Schedule job field definitions on page 151. 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.
6. If the job is scheduled for a later point, 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 on page 100. Create a job to change the virtual console plugin type You can change the virtual console plugin type to HTML5 on multiple devices.
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 on page 14. 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.
• • • • • • • • • Create customized device discovery job protocol for servers –Additional settings for discovery protocols Specify discovery mode for creating a chassis discovery job Create customized device discovery job protocol for Chassis – Additional settings for discovery protocols Specify discovery mode for creating a Dell storage discovery job Specify discovery mode for creating a network switch discovery job Create customized device discovery job protocol HTTPS storage devices –Additional settings
• • • • Credentials Added—The credentials of the server are added in the console, however, the server has not initiated contact with the console. Ready to Discover—The credentials of the server are added and the server has initiated contact. NOTE: The appliance triggers a Discovery job every 10 minutes to discover all the servers in the 'Ready to Discover' status.
3. From the Device Type drop-down menu, to discover: • • • • A server, select SERVER. See Specifying discovery mode for creating a server discovery job. A chassis, select CHASSIS. See Specifying discovery mode for creating a chassis discovery job. A Dell EMC storage device, or network switch, select DELL STORAGE, or NETWORKING SWITCH. See Specifying discovery mode for creating a storage, Dell storage, and network switch discovery job. To discover devices by using multiple protocols, select MULTIPLE.
on the All Devices page remains the same as its initial discovered state of 'Monitored,' 'Managed' or 'Managed with Alerts.' • The All Devices page displays the Managed State of all the onboarded chassis as "Managed" irrespective of which chassis user-role credentials were used at the time of onboarding. If the chassis was onboarded with credentials of a "read-only" user, then there may be a failure during update activities performed on chassis.
Table 22.
Run a device discovery job NOTE: You cannot rerun a job that is already running. To run a device discovery job: 1. In the list of existing device discovery jobs, select the check box corresponding to the job you want to run now. 2. Click Run. The job starts immediately and a message is displayed in the lower-right corner. Related information Discovering devices for monitoring or management on page 103 Stop a device discovery job You can stop the job only if running.
2. Click Add. 3. When prompted, click YES. The IP address or the range is globally excluded, and then displayed in the list of excluded ranges. Such devices are globally excluded which implies that they do not take part in any activity performed by OpenManage Enterprise. NOTE: The device that is globally excluded is clearly identified as 'Globally excluded' on the Job Details page. You can view the list of globally excluded devices by clicking: • • • Devices > Global Exclude.
Create customized device discovery job protocol for servers –Additional settings for discovery protocols In the Additional Settings dialog box, enter details for the appropriate protocol with which you want to discover the server(s): NOTE: The appropriate protocols are automatically preselected based on your initial inputs. 1. To Discover using WS-Man/Redfish (iDRAC, Server, and/or Chassis) a. In the Credentials section, enter User Name and Password. b.
Specify discovery mode for creating a chassis discovery job 1. From the Device Type drop-down menu, select CHASSIS. Based on your selection, the fields change under Settings. 2. Enter the IP address, host name, or IP range in IP/Hostname/Range. 3. Under Settings, enter the username and password of the server to be detected. 4. Type the community type. 5.
5. Click Finish. 6. Complete the tasks in Create a device discovery job on page 105. Specify discovery mode for creating a Dell storage discovery job 1. From the Device Type drop-down menu, select DELL STORAGE. 2. When prompted, select: • • PowerVault ME: To discover the storage devices using the HTTPS protocol like the PowerVault ME. Others: To discover storage devices which use SNMP protocol. Based on your selection, the fields change under Settings. 3.
Create customized device discovery job protocol for SNMP devices By default, the Discover using SNMP check box is selected to enable you detect the storage, networking, or other SNMP devices. NOTE: Only the IO Modules with Standalone, PMUX (Programmable MUX), VLT (Virtual Link Trunking) Modes are discoverable. Full switch and Stacked Modes will not be discovered. 1. Under Credentials, select the SNMP version, and then enter the community type. 2. In the Connection Settings section: a.
16 Managing device inventory NOTE: To perform any tasks on OpenManage Enterprise, you must have necessary user privileges. See Role-based OpenManage Enterprise user privileges on page 14. By clicking OpenManage Enterprise > Monitor > Inventory, you can generate a device inventory report to better manage your data center, reduce maintenance, maintain minimum stock, and reduce operational costs.
• Select the Collect driver inventory check box to collect driver inventory information from the Windows server. Also, to install the Inventory Collector and Dell System Update on the Windows server if these components are not available on the server. NOTE: • 'Collect driver inventory' applies only to devices discovered as 64-bit Windows servers. • Inventory collection of Windows-based devices is supported only using OpenSSH. Other SSH implementations on Windows, like the CygWin SSH, are not supported.
The inventory schedule job is updated and displayed in the table.
17 Manage the device warranty NOTE: To perform any tasks on OpenManage Enterprise, you must have necessary user privileges. See Role-based OpenManage Enterprise user privileges on page 14. By clicking OpenManage Enterprise > Monitor > Warranty, you can view the warranty statuses of all the devices that are monitored by OpenManage Enterprise. You can also export selected or all data to an Excel sheet for the statistical and analytical purposes.
• • Expired warranties can be renewed by clicking Dell Warranty Renewal for Device, which redirects you to the Dell EMC support site allowing you to manage your device warranty. Click Refresh Warranty in the upper right-hand corner to refresh the Warranty table. Warranty statuses automatically change from • • critical to normal for all the devices whose warranties are renewed.
18 Reports By clicking OpenManage Enterprise > Monitor > Reports, you can build customized reports to view device details at depth. Reports enables you to view data about the devices, jobs, alerts, and other elements of your data center. Reports are built-in, and user-defined. You can edit or delete only the user-defined reports. Definitions and criteria used for a built-in report cannot be edited or deleted. A preview about the report you select from the Reports list is displayed in the right pane.
Run reports NOTE: To perform any tasks on OpenManage Enterprise, you must have necessary user privileges. See Role-based OpenManage Enterprise user privileges on page 14. When you run a report, the first 20 rows are displayed and paginated results can be paged through. To view all the rows at one time, download the report. To edit this value, see Export all or selected data on page 47. Data displayed in the output cannot be sorted because it is defined in the query used to build a report.
Edit reports Only user-created reports can be edited. 1. Select the report and click Edit. 2. In the Report Definition dialog box, edit the settings. See Creating reports. 3. Click Save. The updated information is saved. An audit log entry is made whenever you generate, edit, delete, or copy a report definition. NOTE: While editing a customized-report, if the category is changed, the associated fields are also removed.
By default, Devices is selected as the category, and device name, device Service Tag, and device model columns are displayed in the working pane. If you select any other category while editing a report criteria, a message is displayed indicating that the default fields will be removed. Every category has predefined properties that can be used as column titles where the data is filtered by using the criteria you define.
2. Copy the filter properties of Query1, create Query2, and then customize the query criteria by adding another filter: Task Enabled=Yes AND (Task Type=Discovery). 3. Later, open Query1. Its filter criteria still remains as Task Enabled=Yes. 1. In the Query Criteria Selection dialog box, select from the drop-down menu based on whether you want to create a query criteria for Query groups or for report generation. 2. Add or remove a filter by clicking the plus or dustbin symbol respectively. 3. Click Finish.
19 Managing MIB files NOTE: To perform any tasks on OpenManage Enterprise, you must have necessary user privileges. See Role-based OpenManage Enterprise user privileges on page 14. Third party tools in your data center may generate alerts that are vital for your operations. Such alerts are stored in the Management Information Base (MIB) files defined and understood by respective vendor tools.
1. Click MIB > Import MIB. 2. In the Import MIB dialog box, in the Upload MIB Files section, click Choose File to select a MIB file. If the MIB has import statements that are resolved by external MIBs, a message is displayed. a. Click Resolve Types. Resolve the MIB types. See Remove MIB files on page 126. 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.
NOTE: Events that are received before removing a MIB will not be affected by the associated MIB removal. However, events generated after the removal will have unformatted traps. 1. In the MIB FILENAME column, expand the folder, and select the MIB files. 2. Click Remove MIB. 3. In the Remove MIB dialog box, select the check boxes of the MIBs to be removed. 4. 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 on page 125.
20 Managing OpenManage Enterprise appliance settings NOTE: To perform any tasks on OpenManage Enterprise, you must have necessary user privileges. See Role-based OpenManage Enterprise user privileges on page 14. NOTE: For information about supported browsers, see the OpenManage Enterprise Support Matrix available on the support site.
• OpenManage Mobile settings Configure OpenManage Enterprise network settings NOTE: To perform any tasks on OpenManage Enterprise, you must have necessary user privileges. See Role-based OpenManage Enterprise user privileges on page 14. 1. To only view the current network settings of all the active network connections of OpenManage Enterprise such as DNS domain name, FQDN, and IPv4 and IPv6 settings, expand Current Settings. 2.
• • • NOTE: You cannot enable, disable, or delete the admin/system/root users. You can change the password by clicking Edit in the right pane. View details about the logged-in users, and then end (terminate) a user session. Manage Directory Services. Import and manage users from Active Directory. By default, the list of users is displayed under Users. The right pane displays the properties of a user name that you select in the working pane.
Related tasks Delete Directory services on page 131 Delete OpenManage Enterprise users on page 131 Ending user sessions on page 131 Related information Manage OpenManage Enterprise users on page 129 Delete OpenManage Enterprise users 1. Select the check box corresponding to the username and click Delete. 2. When prompted, click YES.
Role-based OpenManage Enterprise user privileges Users are assigned roles which determine their level of access to the appliance settings and device management features. This feature is termed as Role-Based Access Control (RBAC). The console enforces one role per account. For more information about managing users on OpenManage Enterprise, see Manage OpenManage Enterprise users on page 129. This table lists the various privileges that are enabled for each role. Table 26.
NOTE: AD and LDAP directory users can be imported and assigned one of the OpenManage Enterprise roles (Admin, DeviceManager, or Viewer). The Single-Sign-On (SSO) feature stops at login to the console. Actions run on the devices require a privileged account on the device. This procedure is specific to only adding and editing the local users. While editing local users, you can edit all the user properties.
Table 27. OpenManage Enterprise Pre-requisites/supported attributes for LDAP Integration (continued) Attribute of User Login Attribute of Group Membership Certificate Requirement • OpenLDAP uid, sn Uniquemember PHP LDAP uid MemberUid Only Base64 certificate format is supported Only PEM certificate format is supported User pre-requisites for directory service integration You must ensure that the following user pre-requisites are met before you begin with the directory service integration: 1. 2. 3.
b. Select the check boxes corresponding to the groups be imported, and then click the >> or << buttons to add or remove the groups. 4. In the Groups to be Imported section: a. Select the check boxes of the groups, and then select a role from the Assign Group Role drop-down menu. For more information about the role-based access, see Role-based OpenManage Enterprise user privileges on page 14. b. Click Assign.
Add or edit Lightweight Directory Access Protocol groups to be used with Directory Services 1. Click Application Settings > Users > Directory Services, and then click Add. 2. In the Connect to Directory Service dialog box, select LDAP as the directory type. NOTE: To create an AD user group by using Directory Services, see Add or edit Active Directory groups to be used with Directory Services on page 135. a. Enter a desired name for the LDAP directory. b.
NOTE: AD and LDAP directory users can be imported and assigned one of the OpenManage Enterprise roles (Admin, DeviceManager, or Viewer). By clicking OpenManage Enterprise > Application Settings > Security, you can secure your OpenManage Enterprise either by specifying the Restrict Allowed IP Range or the Login Lockout Policy.
• Click Finish. Assigning a webserver certificate to OpenManage Enterprise using the Microsoft Certificate Services 1. Generate and download the Certificate Signing Request (CSR) in OpenManage Enterprise. See Generate and download the certificate signing request on page 137 2. Open a web session to the certification server (https://x.x.x.x/certsrv) and click on the Request a certificate link . 3. On the Request a Certificate page, click on the submit an advanced certificate request link. 4.
• The default setting for General Device Naming is DNS. • If any of the discovered devices do not have the DNS name or the NetBIOS name to satisfy the setting, then the appliance identifies such devices with their IP addresses. • When the Instrumentation(NetBios) option is selected in General Device Naming, for chassis devices the Chassis name is displayed as the device name entry on the All Devices page. b. Server Device Naming applies to iDRACs only.
a. All — to enable the display of both acknowledged and unacknowledged alerts. b. Unacknowledged — to enable the display of only the unacknowledged alerts. NOTE: By default, the Alert Display Settings is set as Unacknowledged. c. Acknowledged — to enable the display of only the acknowledged alerts. 3. Click Apply. Changes to the Alert Display Settings would be impact the following OpenManage Enterprise pages: • • • • The upper-right corner of all the OpenManage Enterprise pages.
c. In the Authentication Passphrase box, enter the passphrase pertaining to SHA or MD_5 based on your selection. d. From the Privacy Type drop-down menu, select either DES or AES_128 as your encryption standard. e. In the Privacy Passphrase box, enter the passphrase based on your privacy type. 3. Click Save.
a. Automatic: The appliance checks for the availability of the updates automatically every Monday from the source specified in the Where to check for updates. b. Manual: When configured to Manual, the user has to manually check for the availability of the update from the source specified in the Where to check for updates. 2. Where to check for updates — The location from where the appliance checks for updates can be specified. The following options are available: a. Dell.
• You can login immediately after the appliance is updated and don't have to wait till the entire inventory is discovered. Post update, the discovery task will run in the background and you can see the progress occasionally. • For future upgrades from OpenManage Enterprise version 3.4, clicking Update would initiate an Upgrade Bundle Download job. This job finishes by itself after all the update files are downloaded and cannot be terminated by the user. 1. To update online from Dell.
because the file does not exist" and "The status of downloading the Extension Catalog is Failed". These error messages do not have any functional impact on the upgrade process and can be ignored. • For more detailed information about updating OpenManage Enterprise to the latest version, see the Upgrade the Dell EMC OpenManage Enterprise appliance version technical white paper on the support site (https:// downloads.dell.
○ For offline, server is configured with the required extension catalog and extension installation files. NOTE: Installing an extension on OpenManage Enterprise restarts the appliance services. To install an extension perform the following steps: 1. Click Application Settings > Console and Extensions The Console and Extensions page is displayed 2. In Extensions section, against the extension you like to install, click More Actions > Install The Install Extension window is displayed. 3.
Execute remote commands and scripts When you get an SNMP trap, you can run a script on OpenManage Enterprise. This sets up a policy that opens a ticket on your third party ticketing system for alert management. You can create and store only up to four remote commands. 1. Click Application Settings > Script Execution. 2. In the Remote Command Setting section, do the following: a. To add a remote command, click Create. b. In the Command Name box, enter the command name. c.
View the alert notification service status on page 148 Troubleshooting OpenManage Mobile on page 149 Related information Enable or disable alert notifications for OpenManage Mobile on page 147 Enable or disable OpenManage Mobile subscribers on page 147 Troubleshooting OpenManage Mobile on page 149 Enable or disable alert notifications for OpenManage Mobile By default, OpenManage Enterprise is configured to send alert notifications to the OpenManage Mobile application.
Delete an OpenManage Mobile subscriber Deleting an OpenManage Mobile subscriber removes the user from the subscribers list, preventing the user from receiving alert notifications from OpenManage Enterprise. However, the OpenManage Mobile user can re-subscribe to alert notifications from the OpenManage Mobile application at a later time. NOTE: The administrator rights are required for deleting an OpenManage Mobile subscriber. To delete an OpenManage Mobile subscriber: 1.
Table 28. Notification service status (continued) Status Icon Status Description The service experienced an error delivering a message. Follow troubleshooting procedures or contact technical support as necessary. View information about OpenManage Mobile subscribers After an OpenManage Mobile user successfully adds OpenManage Enterprise, the user is added to the Mobile Subscribers table in OpenManage Enterprise.
Table 30. Troubleshooting OpenManage Mobile (continued) Problem Reason Resolution If connection is unavailable, complete the following network troubleshooting tasks: • • • • The Message Forwarding Service is unable to connect to a device platform notification service. [Code 100-105, 200-202, 211-212] Verify if the network cables are connected. Verify the IP address and DNS server settings. Verify if the firewall is configured to allow outbound traffic. Verify if the ISP network is operating normally.
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.
Alert categories after EEMI relocation Table of EEMI relocations Table 31.
Table 31.
2. On the TUI screen, to use the FSD option, select Enable Field Service Debug (FSD) Mode. 3. To generate a new FSD unblock request, on the FSD Functions screen, select Unblock FSD Capabilities 4. To determine the duration of the debug capabilities being requested, select a start and end date. 5. On the Choose Requested Debug Capabilities screen, select a debug capability from a list of debug capabilities unique to the console. In the lower-right corner, select Generate.
2. On the Disable Invoked Debug Capabilities screen, select a debug capability or capabilities from a list of currently invoked debug capabilities. From the lower right corner of the screen, select Disable. Ensure that you stop any SSH daemon or SSH sessions that are currently using the debug capability. Catalog Management field definitions CATALOG NAME: Name of the catalog. Built-in catalogs cannot be edited. DOWNLOAD: Indicates the download status of catalogs from its repository folder.
Example: The R740 server model is a rack, two processor system from the 14th generation of servers with Intel processors. In the documentation, to refer to R740, generic naming convention YX4X server is used, where: • • • • The letter Y (alphabet) denotes the type (form factor: Cloud (C), Flexible(F), Modular (M or MX), Rack(R), Tower(T)) of the server. The letter X (digit) denotes the class (number of processors) of the server. The digit 4 denotes the generation of the server.
