Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • 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 Power Manager Version 2.0 User’s Guide

Create static or temperature-triggered policy

Create a static policy to limit the power consumption for devices and groups or apply EPR on devices in a group when the average inlet temperature exceeds the temperature threshold.

Prerequisites

Ensure that the following prerequisites are met:
  • Devices or groups are added to Power Manager.
  • Servers have the iDRAC and OpenManage Enterprise Advanced licenses.
    • If a device is PowerEdge VRTX or PowerEdge FX2 chassis, it has a Chassis Management Controller (CMC) Enterprise license.

About this task

NOTE If you are logging in as a Device Manager, only the device groups and devices that are in your scope are available for viewing and management.

For example, if you are logging in as a Device Manager DM1 user, you can create policies on devices and groups that are in Device Manager DM1 user scope.

When Device Manager users have common groups or devices in their scope, and Device Manager DM1 user creates a policy on any of these groups or devices:
  • All the policies that are created by Device Manager DM1 user are not listed for other Device Manager users.
  • If the Device Manager DM1 user creates a temperature-triggered policy on a group, the Device Manager DM2 user cannot create a temperature-triggered policy on the same group since only one temperature-triggered policy is supported on a group. And, the temperature-triggered policy is not visible or listed for Device Manager DM2 user. However, if the Device Manager DM2 user has to create a temperature-triggered policy on this group, ensure that the Device Manager DM1 user or the Administrator deletes the existing temperature-triggered policy.

To create a policy, perform the following steps:

Steps

  1. Launch OpenManage Enterprise, and then click Plugins > Power Management > Policies.
    The Policies tab is displayed.
  2. Click Create.
    The Create Policy wizard is displayed.
  3. In the General section, provide the following information and click Next.
    1. In Type, select the type of policy.
      • Static policy—applies a cap on the power consumption of a device or group.
      • Temperature-triggered policy—applies Emergency Power Reduction (EPR) on a group of devices when its temperature equals or exceeds a specified value.
      NOTE After a policy is created, you cannot change the type of policy.

      To activate the policy after creation, the Enable option is selected by default.

    2. Provide a policy name and description.
  4. In the Devices/Groups section, select the required option:
    • To add a device:
    1. Select the Device option and click Select Device.
      The Select Device page is displayed.
    2. Click Advanced Filters.
      The following filters are displayed:
      • Health State
      • Power State
      • Connection State
      • Name
      • Identifier
      • Model
      • Type
      • Managed State
      • Part of Group
    3. Select the device, and click Add Selected.
    • To add a group:
    1. Select the Group option and click Select Group.
      The Select Group page is displayed.
    2. Click Advanced Filters.
      The following filters are displayed:
      • Name
      • Type
    3. To clear the filters, click Clear All filters.
    4. Select the group and click Add Selected.
      NOTE You can select only one device or group when creating a policy.
      NOTE After you create a policy for a device, you cannot apply the policy to a group. Similarly, after creating a policy for a group, you cannot apply the policy to a device.
  5. Click Next.
  6. For a static policy:

    In the Policy Settings section, select the monitoring period from the Monitoring time period drop-down menu, and provide the Power cap value, and then click Next.

    Use the Power History section as a reference to set the power cap value.
    • Power History for a device—displays minimum, average, and maximum power consumption with the lower and upper bound values. The values change as you change the duration of the Monitoring time period.
    • Power History for a group—displays minimum, average, and maximum power consumption with lower and upper bound values. The minimum, average, and maximum power history of the group is the sum of all the minimum, average, and maximum power consumption of individual devices in the group. The values change as you change the duration of Monitoring time period. The upper and lower bound value for a group is the sum of upper bound and lower bound values for all devices part of the group. The Power Cap displayed is the sum of all the power cap values of the devices in the group.
    Guidance for providing power cap values:
    • The default Power Cap Value displayed is the upper bound value of the device. You can change the Power Cap value and the Power Cap percentage gets populated automatically.
    • If you change the percentage of Power Cap then the Power Cap value gets populated automatically.
    • If you change the Percentage of Range then the Power Cap Value gets populated automatically.
    • For groups, provide the power cap value or percentage of consumption at the group level or at every device level.
    • Provide the power cap value that ranges between the lower and upper bounds of the device.
    NOTE For the following list of PowerEdge servers, the Lower Bound and Upper Bound threshold range values are always static.
    Table 1. Power cap range for serversPower cap range for servers
    Generation of servers Models Value Range (Watts)
    14th generation
    • PowerEdge XE7440
    • PowerEdge XE7420
    • VxRail G560
    • VxRail G560F
    • PowerEdge C6420
    • PowerEdge R6415
    • PowerEdge R7415
    • PowerEdge R7425
    Zero to 32767
    13th generation
    • PowerEdge C6320
    • PowerEdge C6320p
    Zero to 700
    For a temperature-triggered policy:

    In the Policy Settings section, select a monitoring period from the Monitoring time period drop-down menu, select or provide the Temperature Threshold value, and then click Next.

    Use the Temperature data section as a reference to set the temperature threshold value. Based on your selection of the Monitoring time period value, the temperature summary details are displayed.

    • The values change as you change the duration of the Monitoring time period.
    • Select your preferred American Society of Heating, Refrigerating, and Air-Conditioning Engineers (ASHRAE) temperature threshold from the Temperature Threshold drop-down menu. Based on your ASHRAE class selection, the temperature value is populated.

      Select the ASHRAE standard relevant in your region or provide a custom value in Celsius only.

      • ASHRAE Recommended— 27°c (81°f)
      • ASHRAE Class A1 Allowable—32°c (90°f)
      • ASHRAE Class A2 Allowable— 35°c (95°f)
      • ASHRAE Class A3 Allowable— 40°c (104°f)
      • ASHRAE Class A4 Allowable—45°c (113°f)
    • You can also provide a custom temperature threshold value.
  7. In the Policy Schedule section, provide the following information and click Next.

    Power Manager enables you to create and apply multiple policies on a specific device or group. In any instance, if multiple policies are active on a device, either by policies set on the device or by policies set on the group the device is a part of, the most restrictive power cap among the policies is applied on the device.

    1. For the Time Span option, select Always for the policy to be active from the time of creation. If the policy does not have to be active always when enabled, click Range and provide a time range during which the policy must be active when it is enabled.
    2. For the Day(s) option, select Always for the policy to be active from the time of creation. If the policy does not have to be active always when enabled, click Daily, to select specific days on which the policy must be active when it is enabled.
    3. For the Active Date option, select the date range during which the policy must be active when enabled.
    NOTE A temperature-triggered policy cannot be scheduled.
  8. In the Summary section, view the policy details and click Finish.
    The policy is created successfully.

    The following table provides more information about all the fields in the policy wizard.

    Table 2. Policy wizard detailsPolicy wizard details
    Field Mandatory Value Range
    Type

    Yes

    By default, the type is selected as Static.

    • Static policy
    • Temperature-triggered policy
    Name

    Yes

    Combination of characters, special characters, and numbers

    Limit: 1–255 characters

    Description

    No

    Combination of characters, special characters, and numbers

    Limit: 0–255 characters

    Enable

    No

    By default, the check-box is selected.

    • Select
    • Clear
    Monitoring time period

    Yes

    By default, the time period is selected as 1 Day.

    • 1 Day
    • 7 Days
    • 1 Month
    • 3 Months
    For static policy
    Power cap Yes

    By default, the power cap is populated with the Upper Bound value and a hundred percent.

    Recommended limit: Lower Bound-Upper Bound
    Time Span Yes

    By default, the option is selected as Always.

    Range Limit: 12 hours format
    Day(s) Yes

    By default, the option is selected as Always.

    Daily Select at least one day.
    Active Date Yes

    By default, the option is selected as Always.

    Range
    • From
    • To
    Limit: Current and future dates
    For temperature-triggered policy
    Temperature Threshold

    Yes

    By default, the option that is selected is ASHRAE Recommended.

    • Custom value range: -10 to 60 degrees
    • ASHRAE Recommended
    • ASHRAE Class A1
    • ASHRAE Class A2
    • ASHRAE Class A3
    • ASHRAE Class A4

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