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.

Dell EMC OpenManage Enterprise 3.9 User's Guide

Manage Console preferences

NOTE To perform any tasks on OpenManage Enterprise, you must have the necessary user privileges. See Role and scope-based access control in OpenManage Enterprise.
By clicking OpenManage Enterprise > Application Settings > Console Preferences, you can set the default properties of the OpenManage Enterprise GUI. For example, default time after which a device health is automatically checked and updated on the dashboard, and preferred settings used for discovering a device. The following options are available:
  1. Report Settings: 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 set at 1,000 rows, however, the maximum rows permitted is 2,000,000,000.
    3. Click Apply. A job is run and the setting is applied.
  2. Device Health: To set the time after which the health of the devices must be automatically monitored and updated on the OpenManage Enterprise Dashboard:
    1. Expand Device Health.
    2. Enter the frequency at which the device health must be recorded and data 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 the device is not anymore monitored by OpenManage Enterprise.
    4. Click Apply to save the changes to the settings or click Discard to reset the settings to default attributes.
  3. Discovery Setting: 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. Unselect 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 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 page.
    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 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.
  4. 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.
  5. MX7000 Onboarding Preferences: Specify one of the following alert-forwarding behavior on MX7000 chassis when they are onboarded:
    • Receive All Alerts
    • Receive 'Chassis' category alerts only
  6. 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(Default):
      • Enable V1: To enable SMBv1.
      • Enable V2(Default): To enable SMBv2.
      NOTE Ensure to enable SMBv1 in the SMB Settings before you begin any tasks which need communication with any chassis or the PowerEdge YX2X and YX3X servers that have iDRAC version 2.50.50.50 and earlier. For more information, see the Openmanage Enterprise Support Matrix and PowerEdge server naming conventions.
    • HTTPS: To shut the default CIFS and to enable HTTPS.
      NOTE
      • Device operations using HTTPS may fail on PowerEdge servers with older iDRAC firmware versions that don't support HTTPS. See Firmware and DSU requirement for HTTPS.
      • When the internal share uses HTTPS, then, template creation, template deployment, Boot to Network ISO, and firmware updation are not supported on FX2, VRTX, and M1000e chassis.
      • When the internal share uses HTTPS, then, template creation and deployment, and firmware updates are not supported on the MX7000 chassis and proxied sleds.
      • The credentials to the HTTPS share is automatically rotated every 6 hours.
  7. 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.
  8. 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.
    2. Click Apply to save the changes or click Discard to reset the settings to the default attributes.
  9. Metrics Collection Settings: To set the frequency of the PowerManager extension data maintenance and purging do the following:
    1. In the Data purge interval box, enter the frequency to delete the PowerManager 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.

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: <>()\