Dell EMC OpenManage Enterprise Version 3.4.1 User's Guide July 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 (version 3.4 and version 3.4.1).................................................................................................... 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................................................................................................................................................. 65 Deploy IOA templates.......................................................................................................................................................66 Clone templates.......................................................................................................................................................
Automatic refresh of MX7000 chassis on insertion and removal sleds......................................................... 93 Create alert policies.................................................................................................................................................... 93 Enable alert policies.....................................................................................................................................................97 Edit alert policies....................
Delete an inventory job................................................................................................................................................... 119 Edit an inventory schedule job..................................................................................................................................... 120 Chapter 17: Manage the device warranty.................................................................................... 121 View and renew device warranty............
Update settings in OpenManage Enterprise....................................................................................................... 145 Update OpenManage Enterprise............................................................................................................................145 Update from Dell.com............................................................................................................................................... 146 Update from an internal network share ..
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 web application delivered as a virtual appliance. It provides a comprehensive view of the Dell EMC servers, chassis, storage, and network switches on the enterprise network. With OpenManage Enterprise, a web-based one‑to‑many systems management application, users can: ● ● ● ● ● ● ● ● ● ● ● Discover devices in a data center environment. View hardware inventory and monitor health of devices.
● ● ● ● ● Manage the device warranty on page 121 Reports on page 123 Managing MIB files on page 128 Role-based OpenManage Enterprise user privileges on page 14 Directory services integration in OpenManage Enterprise on page 136 Topics: • • • • New in this release (version 3.4 and version 3.4.1) Other information you may need Contacting Dell EMC OpenManage Enterprise Advanced license New in this release (version 3.4 and version 3.4.
Table 1. Other information you may need (continued) Document Description Dell EMC OpenManage Mobile User’s Guide Provides information about installing and using the OpenManage Mobile application. Dell EMC Repository Manager User's Guide Provides information about using the Repository Manager to manage system updates.
Purchase OpenManage Enterprise Advanced license You can purchase the OpenManage Enterprise Advanced license when you purchase a server or by contacting your sales representative. You can download the purchased license from the Software License Management Portal at Dell.com/support/ retail/lkm. Verify license information OpenManage Enterprise provides a built-in report to view the list of devices monitored by OpenManage Enterprise, and their licenses.
2 Security features in OpenManage Enterprise Some of the security features of OpenManage Enterprise are: ● ● ● ● ● User roles (Administrator, Device Manager, Viewer) with differing device management functionality. Hardened appliance with Security-Enhanced Linux (SELinux) and an internal firewall. Encryption of sensitive data in an internal database. Use of encrypted communication outside the appliance (HTTPS). Only browsers with 256-bit encryption are supported.
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 Install OpenManage Enterprise NOTE: A fresh installation of OpenManage Enterprise version 3.4.1 is not allowed as this is a patch release to the official OpenManage Enterpise version 3.4. You must first install OpenManage Enterprise version 3.4 and then upgrade it to version 3.4.1. Dell EMC OpenManage Enterprise is provided as an appliance that you can install on a hypervisor and manage resources to minimize downtime.
Table 4. Minimum recommended hardware (continued) Minimum recommended hardware Large deployments Small deployments Hard drive 250 GB 50 GB 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.
● If resource pools are NOT configured — On the Hosts/Clusters page, select the host or cluster on which you want to deploy the appliance VM. 8. If there are more than one datastores available on the host, the Datastore page displays such datastores. Select the location to store virtual machine (VM) files, and then click Next. 9. On the Disk Format page, click Thick provision to pre-allocate physical storage space to VMs at the time a drive is created. 10.
Deploy OpenManage Enterprise on Hyper-V 2016 host NOTE: ● 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.
1. Download the openmanage_enterprise_vhd_format.zip file from the support site. Extract the file and then move or copy the enclosed VHD file into an appropriate location on your system where you want to store the OpenManage Enterprise virtual drive. 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.
10. Navigate the file system and select the QCOW2 file that is downloaded in step 1, and then click Forward. 11. Assign 16 GB as the memory and select two processor cores, and then click Forward. 12. Assign the required disk space for the VM and click Forward. 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.
This script modifies the openmanage_enterprise.x86_64-0.0.1.ovf file for deployment in accordance with the values set in the ovf_properties.config file. When the script finishes execution, a sample ovftool command is displayed. It contains tags such as , , , , and so on, that you must replace as per your deployment environment. These settings define the resources that are used on the target ESXi system and also the credentials and IP address of the target system.
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
You can configure OpenManage Enterprise by using the TUI. The TUI screen has the following options: 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.
Table 7. Text User Interface options (continued) Options Descriptions This interface will have the routing priority if there is any ambiguity. The primary interface is also expected to be the 'public facing' interface which allows for corporate network/ internet connectivity. Different 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.
Table 7. Text User Interface options (continued) Options Descriptions Change keyboard layout Select Change keyboard layout to change the keyboard layout if needed. Reboot the Appliance Select Reboot the Appliance to restart the appliance. NOTE: After running a command to restart the services, the TUI may display the following message: NMI 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.
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 ● Server-initiated discovery. 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.
● G—The number of events generated in the alerts log. Also, based on your settings to whether or not view the unacknowledged alerts, the number of alerts in this section varies. By default, only the unacknowledged alerts are displayed. To hide or unhide the acknowledged alerts, see Customize the alert display on page 143. Deleting the alerts reduces the count. For information about symbols that are used to indicate severity statuses, see Device health statuses on page 37.
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.
under each category, click the respective color bands. 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 on page 48. To filter data, click Advanced Filters. Export data into Excel, CSV, HTML, or PDF format. See Export all or selected data on page 47.
● Hypervisor Systems: Hyper-V servers and VMware ESXi servers ● Modular Systems: PowerEdge Chassis, PowerEdge FX2, PowerEdge 1000e chassis, PowerEdge MX7000 chassis and PowerEdge VRTX chassis. 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.
● Static Groups: Manually created by the user by adding specific devices to a group. These groups change only when a user manually changes the devices in the group or a sub-group. The items in the group remain static until the parent group is edited or the child device is deleted. ● Query Group: Groups that are dynamically defined by matching user-specified criteria. Devices in the group change based on the result of devices that are discovered by using criteria.
Create or edit a Query device group 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. Right-click Query Groups and then click Create New Query Group. Alternatively, click the + icon, select Query Group, and click Create in the Create Custom Group dialog box. For definitions about Static or Query (Dynamic) groups, see Organize devices into groups on page 35. 2.
3. Click Finish. A query criteria is generated and saved in the list of existing queries. An audit log entry is made and displayed in the Audit logs list. See Manage audit logs on page 99.
Add devices to a new group 1. In the working pane, select the check box corresponding to the device(s), click Add to Group , and then click Add to New Group. a. In the Add Devices to New Group Wizard dialog box, type or select data. For more information about groups, see Device Groups. b. To add more devices to the group, click Next. Else, go to step 5. 2. In the Group Member Selection dialog box, select more devices from the Add Devices list.
Related information Organize devices into groups on page 35 Exclude devices from OpenManage Enterprise NOTE: To perform any tasks on OpenManage Enterprise, you must have necessary user privileges. See Role-based OpenManage Enterprise user privileges on page 14. Devices are grouped for efficient handling of repeated tasks such as firmware update, discovery, and inventory generation.
b. Schedule Later: To specify a date and a time when the firmware and/or driver version must be updated. This mode is recommended if you do not want to disturb your current tasks. ● Under Server Options select one of the following reboot options : a. To reboot the server immediately after the firmware/driver update, choose Reboot server immediately and from the dropdown menu select one of the following options: i. Graceful Reboot without Forced Shutdown ii. Graceful Reboot with Forced Shutdown iii.
2. Select the check box corresponding to the device, and then click Refresh Inventory. The job is created and listed in the Jobs list and identified as New in the JOB STATUS column. The inventory of selected device(s) is collected and stored for future retrieval and analysis. For more information about viewing the refreshed inventory data, see Viewing and configuring devices on page 48. To download a device inventory, see Export the single device inventory on page 46.
NOTE: The working pane displays the Donut chart of the selected device group. By using the Donut chart, you can view the list of devices that belongs to other health statuses in that group. To view devices of other health status, click the corresponding color band on the Donut chart. The data in the table changes. For more information about using the Donut chart, see Donut chart.
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. By clicking OpenManage Enterprise > Devices > selecting a device in the device list > View Details, you can: ● View information about the health and power status, device IP, and Service Tag. ● View general information about the device and perform device control and troubleshooting tasks.
Device hardware information OpenManage Enterprise provides a built-in report about the components and their compliance with the firmware compliance baseline. Click OpenManage Enterprise > Monitor > Reports > Firmware Compliance per Component Report. Click Run. See Run reports on page 124. ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● Device Card Information—Information about cards used in the device. Installed Software—List of firmware and software installed on different components in the device.
run, the status of the job is indicated as Diagnostic Completed, and the Download link is displayed in the Recent Activity section. 5. To download the report, click the Download link, and then download the .TXT Diagnostics report file. ● Else, click Troubleshoot > Download Diagnostics Report, and then download the file. 6. In the Download RemoteDiagnostics Files dialog box, click the .TXT file link, and then download the report. 7. Click OK.
NOTE: The RACADM CLI tab is not displayed for the following servers because the corresponding task is not available in the device pack — MX740c, MX840c, and MX5016S. 3. In the Send Remote Command dialog box, type the command. Upto 100 commands can be entered with each command required to be on a new line. To display the results in the same dialog box, select the Open results after sending check box. NOTE: Enter an IPMI command in the following syntax: -I lanplus 4. Click Send.
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.
• • • • • Manage firmware and driver Catalogs Create a baseline 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.
NOTE: Ensure to enable SMBv1 in the SMB Settings before you begin any firmware tasks which need communication with any chassis or the PowerEdge YX2X and YX3X servers that have iDRAC version 2.50.50.50 and earlier. See Manage Console preferences on page 141 and Generic naming convention for Dell EMC PowerEdge servers on page 160 for more information. ● NFS i. In the Share Address box, enter the IP address of the system where the firmware catalog is stored on the network. ii.
If you choose to download the catalog file from the web site within your organization network, you can accept or decline the SSL certificate. You can view details of the SSL certificate in the Certificate Information window. The information comprises the validity period, issuing authority and the name of the entity to which the certificate is issued. NOTE: The Certificate Information window is displayed only if you create the catalog from the Create Baseline wizard.
Create a baseline A baseline is a set of devices or group of devices that are associated with that catalog. A baseline is created for compliance evaluation of the firmware and drivers for the devices in that baseline, against the versions specified in the catalog. To create a baseline: NOTE: To perform any tasks on OpenManage Enterprise, you must have necessary user privileges. See Role-based OpenManage Enterprise user privileges on page 14.
Edit a baseline The baselines on the Configurations > Firmware/Driver Compliance page can be edited as follows: 1. Select a baseline, and then click Edit in the right pane. 2. Modify data as described in Creating the firmware baseline. The updated information is displayed in the Baseline list. 3. To go back to the Firmware/Driver Compliance page, click Return to Firmware/Driver Compliance.
NOTE: If each device has its own status, the highest severity status is considered as the status of the group. For more information about Rollup Health status, see the MANAGING THE ROLLUP HEALTH STATUS BY USING IDRAC ON THE DELL EMC 14TH GENERATION AND LATER POWEREDGE SERVERS white paper on the Dell TechCenter. ● COMPLIANCE: Indicates the compliance level of a device to the baseline.
● The firmware or driver compliance status of network switches, modular IOAs, and Dell storage devices is displayed as Unknown as these are not updatable using the Dell catalog. It is recommended to perform individual firmware or driver updates for these devices using their respective individual Update package. To perform individual firmware or driver updates, select a device on the All Devices page, and click View Details > Firmware/Drivers and select the individual package option.
A firmware/driver update job is created to update the device's firmware and/or driver. You can view the status of the job on the Monitor > Jobs page.
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 .
Edit a server template Built-in templates cannot be edited. Only the user-created templates that are identified as ‘Custom’ can be edited. You can edit the attributes of template irrespective of whether you created it by using a reference template file or a reference device. 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 attributes with secure information, such as passwords, are hidden and would appear as 'empty' when initially loaded and the changes to these secure attribute values are masked. ○ A template’s associated Identity pool cannot be changed if a profile is already associated to it. 3. Click Next. In the Summary section, the attributes you edited by using the Guided and Advanced mode are displayed. 4. This section is read-only. Read through the settings and click Finish.
● If the Propagate VLAN settings immediately check box is selected, then a job named VLAN Propagation is created to apply the changes. Status of the job can be checked on the Monitor > Jobs page. c. Select the Use strict checking check box to match the VLANs with like characteristics. If unselected, only VLAN name and QoS are used for matching. NOTE: This option applies only to the Modular system sleds. d. Make changes to the Untagged Network and Tagged Network attributes of the associated NICs as required.
NOTE: ● Template deployment fails if DHCP settings are assigned during template deployment to a target device that was originally discovered using a static IP. ● If the IP setting is not configured on the discovered MX7000 sled, the Boot to Network ISO operation is not run during the template deployment. 5.
6. Click Finish. Review the warning message and click YES. A Device Configuration job is created under Jobs. See Using jobs for device control on page 101. Clone templates 1. From the OpenManage Enterprise menu, under Configuration, click Templates. A list of available templates is displayed. 2. Select the check box corresponding to the template you want to clone. 3. Click Clone. 4. Enter the name of new template, and then click Finish. The cloned template is created and displayed in the list of templates.
● Import CSV: Click Import CSV to browse the folders and select the respective .csv file with the target device details. A summary of the number of successfully imported and invalid entries is displayed. For a more detailed view of the import result, click View details. The entries in the CSV file must have the following format: The identifiers must be listed in the first column, one per row, starting from the second row. For a template CSV file, click Download sample CSV file. 6. Click Next. 7.
2. Select the auto deploy target from the list and click Export. 3. In the Export All dialog box, select format as either HTML, or CSV, or PDF. Click Finish. A job is created and the auto deploy target data is exported in the selected format. Overview of stateless deployment To deploy a device configuration template with virtual identity attributes on target devices, do the following: 1. Create a device template—Click Create Template task under the Deploy tab to create a device template.
Actions Next Displays the Ethernet tab. Finish Saves the changes and displays the Identity Pools page. Cancel Closes the Create Identity Pool wizard without saving the changes. Identity pools An identity pool is a collection of one or more virtual identity types that are required for network communication. An identity pool can contain a combination of any of the following virtual identity types: ● Ethernet identities The Identities which are defined by the Media Access Control (MAC) address.
c. Select Configure iSCSI Initiator, and then enter the IQN prefix. d. Select Enable iSCSI Initiator IP Pool, and then enter the network details. NOTE: The iSCSI Initiator IP Pool does not support IPv6 addresses. 6. In the FCoE section: a. Select the Include FCoE Identity check box to include FCoE identities. b. Enter the starting MAC address and specify the number of FCoE identities to be created.
● AA-BB-CC-DD-EE-FF ● AABB.CCDD.EEFF The maximum length of a MAC address is 50 characters. This option is displayed only if the Include iSCSI MAC Addresses check box is selected. Number of iSCSI MAC addresses Enter the number of iSCSI MAC addresses. The MAC address can be between 1 and 5000. This option is displayed only if the Include iSCSI MAC Addresses check box is selected. Configure iSCSI Initiator Select the check box to configure the iSCSI initiator.
Include FCoE Identity Select the check box to include the FCoE MAC addresses to the identity pool. FIP MAC Address Enter the starting FCoE Initialization Protocol (FIP) MAC address of the identity pool in one of the following formats: ● AA:BB:CC:DD:EE:FF ● AA-BB-CC-DD-EE-FF ● AABB.CCDD.EEFF The maximum length of a MAC address is 50 characters. This option is displayed only if the Include FCoE Identity check box is selected. The WWPN/WWNN values are generated from the MAC address.
View definitions of identity pools To view the definitions of an identity pool: 1. On the Configuration page, click Identity Pools. 2. Select an identity pool, and then click Summary. The various identity definitions of the identity pool are listed. 3. To view the usage of these identity definitions, click the Usage tab and select the View By filter option.
Table 14.
● Invalid entries or content type in the files are flagged and are not imported. ● VLAN definitions in the .csv and .json file(s) must be entered in the following formats: Table 15. VLAN definition format for CSV file Name Description VLANMin VLANMax Type VLAN1 VLAN with single ID 1 1 1 VLAN2 (Range) VLAN with an ID range 2 10 2 and Table 16.
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.
● ● ● ● ● ● ● ● View profile details. See, View Profile details on page 78 Edit profile attributes and settings. See, Edit a profile on page 79 Assign a profile to a device or service tag (through auto-deploy). See, Assign a Profile on page 79 Unassign a profile from a device or service tag. See, Unassign profiles on page 80 Redeploy profile changes to the associated target device. See, Redeploy profiles on page 81 Migrate profile from one target (device or service tag) to another. Delete profiles.
Profiles — view network To view the network bandwidth and VLAN allocations for the NIC ports associated to a profile: 1. Select a profile on the Configuration > Profiles page. 2. Click View > View Network to activate the View Network wizard. 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.
b. The Details page displays the source template, profile name and description. Click Next. c. On the Target page: ● Click Select and from the list of devices, select a target device. NOTE: Devices that are already assigned a profile will be greyed out and not selectable in the target list. ● If a reboot is required after the deployment, select the Do not forcefully reboot the host OS if the graceful reboot fails check box. ● Click Next. d.
Redeploy profiles For the attribute changes of an already deployed profile to take affect on the associated target device, it must be redeployed. For modular devices, VLAN definitions can be configured during redeployment, however the strict checking to match the VLAN attributes is disabled. To redeploy profile(s): 1. On the Configuration > Profiles page, select the profile(s) that are 'Deployed' and/or 'Modified' ( deploy . ) and click Re- 2.
Delete Profiles The existing 'unassigned' profile(s) can be deleted from the Configuration > Profiles page: NOTE: ● An assigned or deployed profile can be deleted from the Profile portal only if it is unassigned. ● Deleting of an unassigned profile that had identities reserved, returns those identities to the Identity pool they came from. It is recommended to wait for 10 minutes to use these reclaimed identities for future reservations and deployments. To delete the unassigned profiles: 1.
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.
• Remove a configuration compliance baseline 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 83. You can create baseline templates by using deployment template, reference device, importing from a file. See Manage compliance baseline templates on page 84.
Create a compliance baseline template from reference device 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 108. 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.
● If there is a use case of frequent template edits, it is recommended that you associate a maximum of 100 devices per baseline for optimal performance. 1. On the Compliance Templates page, select the corresponding check box, and then click Edit. 2. On the Template Details page, the configuration properties of the template is listed. 3. Expand the property you want to edit, and then enter or select data in the fields. a. To enable the property, select the check box, if not already enabled. 4.
collected. Also, on the Configuration Compliance page a progress bar indicating the progress of Inventory job appears alongside the respective baseline. Related information Managing the device configuration compliance on page 83 Remove a configuration compliance baseline on page 88 Edit a configuration compliance baseline You can edit the devices, name, and other properties associated with a configuration baseline.
IQN, LUN ID, FCoE Target WWPN and so on that are not same across all targets and can cause a permanent noncompliance of the baseline. Remove 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 on page 83.
12 Monitoring device alerts By clicking the OpenManage Enterprise menu, and selecting items under Alerts, you can: ● Monitor alerts by: ● ● ● ● ○ Acknowledge alerts on page 90 ○ Ignore alerts on page 90 ○ View archived alerts on page 91 and Download archived alerts on page 91 Create and manage alert policies. See Alert policies on page 91. View alert definitions. See Alert definitions on page 98. Hide and display acknowledged alerts. See Customize the alert display on page 143.
● 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 48.
The alert is deleted. The total number of alerts displayed in the header row of OpenManage Enterprise is decremented. Related concepts View the alert logs on page 89 Related information Monitoring device alerts on page 89 View archived alerts At a time, a maximum of 50,000 alerts can be generated and viewed by using OpenManage Enterprise.
NOTE: Previous alert policies won't get implemented post upgrade until the Time Interval check box is enabled. See Edit alert policies on page 97. By clicking OpenManage Enterprise > Alerts > Alert Policies, you can: ● Automatically trigger actions based on the input from an alert. ● Send your alerts to email address, phone, SNMP traps, and perform device power control actions such as turning on or turning off a device when an alert of a predefined category is generated.
Related tasks Delete alert policies on page 98 Disable alert policies on page 97 Enable alert policies on page 97 Edit alert policies on page 97 Create alert policies on page 93 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.
3. In the Category section, the Built-in and third-party MIBs are listed. By default, the categories are displayed but not applied. You can select the All check box to apply the alert policy to all the available categories or manually select the categories. To view sub-categories under each category, expand the category: a. Click Next. 4. In the Target section, add devices or groups. See Select target devices and device groups on page 104.
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.
5. Select the Use SSL check box to secure your SMTP transaction. 6. Click Apply. 7. To reset the settings to default attributes, click Discard. To configure the SNMP alert forwarding configuration: 1. 2. 3. 4. 5. 6. 7. 8. Expand SNMP Alert Forwarding Configuration. Select the ENABLED check box to enable the respective SNMP traps to send alerts in case of predefined events. In the DESTINATION ADDRESS box, enter the IP address of the destination device that must receive the alert.
iii. Click Finish 3. To edit a remote command setting, select the command, and then click Edit. 4. To delete a remote command setting, select the command, and then click Delete. Enable alert policies You can enable an alert policy, only if disabled. Enable an alert policy while creating an alert policy by selecting the Enable Policy check box in the Name and Description section. See Create alert policies on page 93.
Delete 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 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 Completed with errors Job run was partially successful and was completed with errors. 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.
2. In the Blink Devices Wizard dialog box: a. In the Options section: i. In the Job Name box, enter a job name. ii. From the Blink LED Duration drop-down menu, select options to blink the LED for a set duration, turn on, or to turn off. iii. Click Next. b. In the Target section, select the target devices and click Next. See Select target devices and device groups on page 104. c. In the Schedule section, run the job immediately or schedule for a later point of time.
NOTE: The commands in the Arguments box are run one at a time. d. Click Next. A green tick mark next to Options indicates that the necessary data is provided. 3. In the Target section, select the target devices and click Next. See Select target devices and device groups on page 104. 4. In the Schedule section, run the job immediately or schedule for a later time. See Schedule job field definitions on page 155. 5. Click Finish.
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 Specify discovery mode for creating Create customized device discovery Specify discovery mode for creating Specify discovery mode for creating Create customized device discovery Create customized device discovery Specify discovery mode for creating Delete a device discovery job job protocol for servers –Additional settings for discovery protocols a chassis discovery job job protocol for Chassis – Additional settings for discovery protocols a Dell storag
4. The Monitor > Server Initiated Discovery page lists the servers that establish contact with the console. Also, the servers whose credentials have been added in the console, but which are yet to initiate contact are also listed. The following statuses of the servers based on the previously mentioned conditions are displayed: ● Announced—Server initiates contact with the console, however, the credentials of the server are not added to the console.
NOTE: When discovering a large number of devices, avoid creating multiple discovery jobs using individual IP address and instead use IP range of the devices. ● To discover devices by importing ranges from the .csv file. See Specify multiple devices by importing data from the .csv file on page 111. ● To exclude certain devices, remove devices from being excluded, or to view the list of devices excluded from being discovered, see Globally excluding device(s) from discovery results. 3.
If you want to onboard devices with a different user account apart from the account specified for discovery, or re-attempt onboarding because of a failure in onboarding during discovery, do the following: NOTE: ● All devices that have been onboarded through this wizard remain onboarded through this user account and is not substituted by the discovery user account during future discoveries against these devices.
Table 22.
Related information Discovering devices for monitoring or management on page 105 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.
When discovering device(s) from all the available devices, you can exclude certain device(s) from getting monitored by OpenManage Enterprise by doing the following: 1. In the Global Exclusion of Ranges dialog box: a. In the Description of Exclude Range box, enter the information about the range that is being excluded. b. In the Enter Ranges to Exclude box, enter address(es) or range of devices to be excluded. The box can take up to 1000 address entries at a time, but separated by a line break.
7. Schedule the discovery job. See Schedule job field definitions on page 155. 8. Click Finish. A discovery job is created and displayed in the list of discovery jobs.
Related information Discovering devices for monitoring or management on page 105 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.
● Select Verify known Host key, to verify the remote host identity. ● Select Use SUDO Option if needed. 5. Click Finish. 6. Complete the tasks in Create a device discovery job on page 107. 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.
e. Select the Enable Certificate Authority (CA) check check box. 3. Click Finish. 4. Complete the tasks in Create a device discovery job on page 107. 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.
Related information Discovering devices for monitoring or management on page 105 Discovering devices for monitoring or management 117
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 configuration inventory check box to generate an inventory of the configuration compliance baseline. ● 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.
Related information Managing device inventory on page 118 Edit an inventory schedule job 1. Click Edit. 2. In the Inventory Schedule dialog box, edit the inventory job name in Inventory Job Name. See Create an inventory job on page 118. 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.
● Select the check box corresponding to the device. In the right pane, warranty status and other important details of the device such as the service level code, service provider, the warranty start date, the warranty end date, and so on are displayed. ● 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.
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.
● Report definition must have at least one field and one category ● For reports having Device and Alert as categories, device name or device group must be one of the mandatory fields 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.
NOTE: When selected, the filters of an existing query criteria is copied only virtually to build a new query criteria. The default filters associated with an existing query criteria is not changed. The definition (filters) of a built-in query criteria is used as a starting point for building a customized query criteria. For example: 1. Query1 is a built-in query criteria that has the following predefined filter: Task Enabled=Yes. 2.
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.
● Only one MIB file can be imported at a time. 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 130. 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.
Remove MIB files NOTE: You cannot remove a MIB file that has trap definitions used by any of the alert policies. See Alert policies on page 91. 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.
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.
• • Execute remote commands and scripts OpenManage Mobile settings Configure OpenManage Enterprise network settings NOTE: To perform any tasks on OpenManage Enterprise, you must have necessary user privileges. See Role-based OpenManage Enterprise user privileges 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: Any change to the user role will take effect immediately and the impacted user(s) will be logged out of their active session. 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.
Disable OpenManage Enterprise users Select the check box corresponding to the user name and click Disable. The user is disabled and a tick mark disappears in the corresponding cell of the ENABLED column. If the user is disabled while creating the username, the Disable button appears grayed-out.
Related information Manage OpenManage Enterprise users on page 132 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 132.
Add and edit OpenManage Enterprise users 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: 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.
Pre-requisites/supported attributes for LDAP Integration Table 27. OpenManage Enterprise Pre-requisites/supported attributes for LDAP Integration Attribute of User Login Attribute of Group Membership Certificate Requirement AD/LDAP Cn, sAMAccountName Member ● Subject to Domain Controller Certificate needs to have FQDN. SAN field can have IPv4 and/or IPv6 or FQDN.
a. From the Directory Source drop-down menu, select an AD or LDAP source that must be imported for adding groups. For adding directories, see Add or edit Active Directory groups to be used with Directory Services on page 138. b. Click Input Credentials. c. In the dialog box, type the username and password of the domain where the directory is saved. Use tool tips to enter the correct syntax. d. Click Finish. 3. In the Available Groups section: a.
5. In the dialog box, enter the username and password of the domain to be connected to. NOTE: The username must be entered in either the UPN (username@domain) or in the NetBIOS (domain\username) format. 6. Click Test connection. In the Directory Service Information dialog box, a message is displayed to indicate successful connection. 7. Click Ok. 8. Click Finish. A job is created and run to add the requested directory in the Directory Services list. 1. In the DIRECTORY NAME column, select the directory.
In the Directory Service Information dialog box, a message is displayed to indicate successful connection. 6. Click Ok. 7. Click Finish. A job is created and run to add the requested directory in the Directory Services list. 1. In the DIRECTORY NAME column, select the directory. The Directory Service properties are displayed in the right pane. 2. Click Edit. 3. In the Connect to Directory Service dialog box, edit the data and click Finish. The data is updated and saved.
Related information Set the login security properties on page 140 Generate and download the certificate signing request To generate a Certificate Signing Request (CSR) for your device, and then apply for an SSL: NOTE: You must generate the CSR from within the OpenManage Enterprise appliance only. 1. Click Generate Certificate Signing Request. 2. In the Generate Certificate Signing Request dialog box, enter information in the fields. 3. Click Generate.
b. Enter the frequency at which the device health must be recorded and data stored. c. Select: ● Last Known: Display the latest recorded device health when the power connection was lost. ● Unknown: Display the latest recorded device health when the device status moved to 'unknown'. A device becomes unknown to OpenManage Enterprise when the connection with iDRAC is lost and the device is not anymore monitored by OpenManage Enterprise. d.
7. Email Sender Settings: To set the address of the user who is sending an email message: a. Enter an email address in the Sender Email ID box. b. Click Apply to save the changes or click Discard to reset the settings to the default attributes. 8. Trap Forwarding Format: To set the trap forwarding format — a. Select one of the following options ● Original Format (Valid for SNMP traps only): To retain the trap data as-is. ● Normalized (Valid for all events): To normalize the trap data.
6. Click Apply. The SNMP credentials and settings are saved. 7. To reset the settings to default attributes, click Discard. NOTE: If SNMPv3 alert settings are configured before upgrading the appliance, you have to reconfigure the settings by providing the username, authentication passphrase, and privacy passphrase to continue receiving the alerts. If the issues persists, restart the services using the Text User Interface (TUI). ● To apply the TrapForward settings: 1. Expand TrapForward Settings.
2. Download and install more plugins (extensions) such as the Power Manager plugin to enhance the functionality of the appliance. For more information about the installation of plugins, see plugin NOTE: The OpenManage Enterprise Advanced license is required for the plugins to be fully functional after installation. For more in-depth information about the plugins, refer the respective documentation available on the Dell Support site.
with details of the new version is displayed. All users can view the banner, however, only users with Administrator privilege can opt for the remind later or dismiss the message option. NOTE: ● An upgrade to OpenManage Enterprise version 3.4.1 is only allowed from OpenManage Enterprise version 3.4 as this is a patch release to the official version 3.4. ● Only OpenManage Enterprise versions starting 3.2 and above can be directly updated to version 3.4 by the Automatic > Online method.
with details of the new version is displayed. All users can view the banner, however, only users with Administrator privilege can opt for the remind later or dismiss the message option. 1. Click Update and perform an update. NOTE: ● Clicking Update initiates an Upgrade Bundle Download job. This job finishes by itself after all the update files are downloaded and cannot be terminated. ● If the upgrade fails, the appliance would restart. It is recommended to revert the VM snapshot and upgrade again 2.
3. Enter the local path information where the downloaded files are saved, and then click Check Now. Example paths: nfs:///, http:///, https:///. The available update version with a brief description of the new features are displayed. 4. To validate a connection to the catalog click Test now. If the connection to the catalog is established, a Connection Successful message is displayed.
1. Click Application Settings > Console and plugin The Console and Plugins page is displayed. 2. In the plugins section, click More Actions > Disable The Disable plugin window is displayed 3. Click Disable plugin, and in the confirmation window, select I agree that I have captured the snapshot of the OM Enterprise appliance prior to the upgrade option, and then click Disable plugin. NOTE: After disabling the plugin, you cannot see any information or pages related to the plugin on OpenManage Enterprise.
e. If you select RACADM, do the following: i. In the Command Name box, enter the command name. ii. In the Command box, type the commands. Up to 100 commands can be typed with each command required to be on a new line. iii. Click Finish f. If you select IPMI Tool, do the following: i. In the Command Name box, enter the command name. ii. In the Command box, type the commands. Up to 100 commands can be typed with each command required to be on a new line. iii. Click Finish 3.
Related tasks OpenManage Mobile settings on page 150 Related information OpenManage Mobile settings on page 150 Delete an OpenManage Mobile subscriber on page 151 Enable or disable OpenManage Mobile subscribers The check boxes in the Enabled column in the Mobile Subscribers list allow you to enable or disable transmission of alert notifications to the OpenManage Mobile subscribers. NOTE: The administrator rights are required for enabling or disabling OpenManage Mobile subscribers.
View the alert notification service status OpenManage Enterprise forwards alert notifications to OpenManage Mobile subscribers through their respective device platform alert notification service. If the OpenManage Mobile subscriber has failed to receive alert notifications, you can check the Notification Service Status to troubleshoot alert notification delivery. To view the status of the alert notification service, click Application Settings > Mobile.
Table 29. OpenManage Mobile subscriber information Field Description ENABLED Select or clear the check box, and then click Enable or Disable respectively to enable or disable the alert notifications to an OpenManage Mobile subscriber. STATUS Displays the status of the subscriber, indicating whether or not OpenManage Enterprise is able to send alert notifications successfully to the Alert Forwarding Service. STATUS MESSAGE Status description of the status message.
Table 30. Troubleshooting OpenManage Mobile (continued) Problem Reason Resolution The Message Forwarding Service is unable to connect to a device platform notification service. [Code 100-105, 200-202, 211-212] The platform provider service is temporarily unavailable to the Message Forwarding Service. Wait for the service to become available. The device communication token is no longer registered with the platform provider service.
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.
NOTE: By default, the job scheduler clock is reset at 12:00 A.M. everyday. The cron format does not consider the job creation time while calculating the job frequency. For example, if a job is started at 10:00 A.M. to run after every 10 hours, the next time the job runs is at 08:00 P.M. However, the subsequent time is not 06:00 A.M. next day but 12:00 A.M. This is because the scheduler clock is reset at 12:00 A.M. everyday. Alert categories after EEMI relocation Table of EEMI relocations Table 31.
Table 31.
Unblock the FSD capability You can unblock the FSD capability through the TUI screen. 1. Navigate to the TUI main menu. 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.
While the invoke command is run, OpenManage Enterprise can start an SSH daemon. The external SSH client can attach with OpenManage Enterprise for debugging purposes. Disable FSD After you invoke a debug capability on a console, it continues to operate until the console is restarted, or the debug capability is stopped. Else, the duration determined from the start and end date exceeds. 1. To stop the debug capabilities, on the FSD Functions screen, select Disable Debug Capabilities. 2.
NOTE: For the complete list of devices in the SC, MD, ME, and XC series, refer https://topics-cdn.dell.com/pdf/dellopenmanage-enterprise_compatibility-matrix2_en-us.pdf Generic naming convention for Dell EMC PowerEdge servers To cover a range of server models, the PowerEdge servers are now be referred to using the generic naming convention and not their generation. This topic explains how to identify the generation of a PowerEdge server that are referred to using the generic naming convention.
