Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

OpenManage Enterprise 4.0.x User's Guide

Manage console settings

Set and manage console preferences such as backup and restore settings, report settings, device discovery and health monitoring frequency, and device naming. Click Application Settings > Console Preferences to set the default console settings.

NOTE:To perform any tasks on OpenManage Enterprise, you must have the necessary user privileges. See Role and scope-based access.
The following options are available:

Configure Backup and Restore settings

Expand Backup/Restore settings to set Backup/Restoration Timeout (Max: 120 minutes) and Max Number of Backups (Range: 2-20). When the user crosses the Max Number of Backups the system will automatically replace the earlier backup with the latest one.

  1. Click Apply to save the changes or click Discard to reset the settings to the default attributes.

Customize report rows limit

To set the maximum number of rows that you can view on OpenManage Enterprise reports:

  1. Expand Report Settings.
  2. Enter a number in the Reports row limit box. The default limit is 1,000 rows, however, the maximum rows permitted are 2,000,000,000.
  3. Click Apply.

Automate device health monitoring frequency

To set the time after which the health of the devices are automatically monitored and updated on the OpenManage Enterprise Dashboard:

  1. Expand Device Health.
  2. Enter the frequency at which the device health is recorded and the data that is stored.
  3. 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 OpenManage Enterprise does not monitor the device anymore.
  4. Click Apply to save the changes to the settings or click Discard to reset the settings to default attributes.

Set device names for easy identification

Expand the Discovery Setting to set the device naming used by the OpenManage enterprise to identify the discovered iDRACs and other devices using the General Device Naming and the Server Device Naming settings.

NOTE:The device naming choices in the General Device Naming and the Server Device Naming are independent of each other and they do not affect each other.
  1. ICMP Ping affects the discovered devices while using the Multiple option as the Device Type while creating a Discovery job:
    • Enable check box is selected by default. Clear to allow the appliance to pursue discovery without an initial ICMP ping.
    • In the Retries box, specify the number of ICMP ping attempts by the appliance on the target devices. By default, this is set as 3 attempts.
    • In the Timeout box, specify the duration that the appliance must wait for a response before the next attempt. By default, this is 30 seconds.
  2. General Device Naming applies to all the discovered devices other than the iDRACs. Select from one of the following naming modes:
    • DNS to use the DNS name.
    • Instrumentation (NetBIOS) to use the NetBIOS name.
    NOTE:
    • 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 screen.
  3. Server Device Naming applies to iDRACs only. Select from one of the following naming modes for the discovered iDRACs:
    • iDRAC Hostname to use the iDRAC hostname.
    • System Hostname to use the system hostname.
    NOTE:
    • The default naming preference for iDRAC devices is the System Hostname .
    • If any of the iDRACs do not have the iDRAC hostname or the System hostname to satisfy the setting, then the appliance identifies such iDRACs using their IP addresses.
  4. To specify the invalid device hostnames and the common MAC addresses expand the Advance Settings
    1. Enter one or more invalid hostnames that are separated by a comma in Invalid Device Hostname. By default, a list of invalid device hostname is populated.
    2. Enter the common MAC addresses separated by a comma in Common MAC Addresses. By default, a list of common MAC addresses is populated.
  5. Click Apply to save the changes to the settings or click Discard to reset the settings to the default attributes.

Choose between automatic or manual server-initiated discovery

In Server Initiated Discovery, select one of the following discovery-approval policies:

  • Automatic: To allow servers with iDRAC Firmware version 4.00.00.00, which are on the same network as the console, to be discovered automatically by the console.
  • Manual: For the servers to be discovered by the user manually.
  • Click Apply to save the changes or click Discard to reset the settings to the default attributes.

MX7000 Onboarding Preferences

In MX7000 Onboarding Preferences: Specify one of the following alert-forwarding behaviors on MX7000 chassis when they are on-boarded:

  • Receive All Alerts
  • Receive 'Chassis' category alerts only.

Manage appliance access control

Appliance Access control allows users to select whether managed devices access the appliance's internal share using the IP or FQDN:

  • IP [default]: Requires all communication to happen using IP address.
  • FQDN : Allows iDRACs to communicate with appliances in an environment where access is controlled via Domain Naming Services or routing policies, such as when the appliance is part of a software-defined network.
    NOTE:
    • The FQDN option cannot be selected unless a DNS hostname and domain name are specified for the appliance; they must be set via the TUI tool.
    • Windows driver updates are not supported on devices managed via FQDN.

Built-in Appliance Share

In Built-in Appliance Share, select one of the following external network share options that the appliance must access to complete operations such as updating of the device firmware and/or drivers, extraction, and deployment of templates and profiles, and for downloading of the diagnostic and technical support reports:

NOTE:The share type or the credentials of an active network share cannot be changed if the appliance tasks are using that network share.
  • CIFS v2(Default): To enable SMBv2.
    NOTE: On OpenManage Enterprise 4.0 and later, SMBv1 is not a supported protocol for accessing the built-in appliance share.
    Table 1. Minimum firmware version required for SMBv2 supportThis table shows the minimum firmware version required for SMBv2 support
    Device Type Minimum FW version
    PowerEdge VRTX chassis 3.21
    PowerEdge FX2 and FX2s sleds 2.21
    iDRAC7, iDRAC8 and iDRAC9 All versions
  • HTTPS: To disable the default CIFS and to enable HTTPS.
    • Device operations using HTTPS may fail on PowerEdge servers with older iDRAC firmware versions that do not support HTTPS. See Firmware and DSU requirements for HTTPS.
    • When the internal share uses HTTPS then template creation, template deployment, Boot to Network ISO, and firmware updating are not supported on FX2, and VRTX chassis.
    • The credentials to the HTTPS share are automatically rotated every 6 hours.

Configure the sender's email address for outgoing messages

Expand the Email Sender Settings to set the address of the user who is sending an email message:

  1. Enter an email address in the Sender Email ID box.
  2. Click Apply to save the changes or click Discard to reset the settings to the default attributes.

Configure trap forwarding format

Expand Trap Forwarding Format to set the trap forwarding format—

  1. 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. When the Trap-forwarding format is set to 'Normalized,' the receiving agent such as the Syslog receives a tag containing the device IP from which the alert was forwarded.
      NOTE:To forward internal alerts, select Normalized (Valid for all events). By default Original Format (Valid for SNMP traps only) is selected that does not forward internal alerts via SNMP trap forwarding.
  2. Click Apply to save the changes or click Discard to reset the settings to the default attributes.

iDRAC vConsole Settings

Expand iDRAC vConsole Settings to set Maximum Allowed Sessions (Max: 10)

  1. Click Apply to save the changes or click Discard to reset the settings to the default attributes.

Alert Correlation Settings

In Alert Correlation Settings: This feature considers correlating alerts from a managed or monitored device. When enabled, an internal correlation task correlates any outstanding Critical or Warning alerts to the corresponding Informational alert. While there is no visible difference on the UI, the API (/api/AlertService/Actions/AlertService.GetCorrelatedAlerts) can be used to get the last correlated alerts.

NOTE:Enable Alert Correlation is disabled by default.
  1. Interval (minutes)can be set at 3 minutes minimum or 60 minutes maximum.
    NOTE:The default value is 3 minutes.
  2. Click Apply to save the changes or click Discard to reset the settings to the default attributes.

Power Manager metric collection settings

In Metrics Collection Settings: To set the frequency of the Power Manager extension data maintenance and purging do the following:

  1. In the Data purge interval box, enter the frequency to delete the Power Manager data. You can enter values within 30 to 365 days.
  2. Click Apply to save changes or click Discard to reset the settings to the default attributes.

Configure iDRAC password management

iDRAC Password Management feature enables the management of credentials for supported iDRACs either internally by OME (if the feature is installed during initial-onboarding) or externally via CyberArk integration to perform various device management operations. Expand iDRAC Password Management to configure the preferred management solution. When password management is enabled, it applies to all eligible iDRACs, resulting in password rotation for each of them.

NOTE:
  • To avoid performance issues in a scaled environment, it is recommended to schedule iDRAC password rotation tasks with the longest interval possible.
  • When changing password management/rotation settings on the appliance or CyberArk, all saved discovery jobs are triggered to ensure the eligible devices have the appropriate credentials.

Related tasks

Internal iDRAC credential management

Enable internal OME password rotation feature

CyberArk integration for password management


Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\