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

Frequently Asked Questions

Why am I not able to view the metrics?

Cause: After removing the required iDRAC or DC License, or the OpenManage Enterprise Advanced Feature license, the license-dependent features are not available on the User Interface (UI). Therefore, the metric is not available, and the values are not collected by Power Manager from the next inventory cycle.

Why do I see two entries with the same date in the graph when the time duration chosen for showing the graph is changed?

Cause: When viewing the Metrics and Monitoring History graphs for 3 months, 6 months, or 1 year, the data is auto-converted from the UTC time zone to your current time zone and displayed. Due to the time zone differences, there are two entries for the same day on the graphs. Therefore, the last entry is for the current day, and the last but one entry is for the previous day.

Why do I see slight variations in values of power and temperature in the Alert Thresholds section?

Cause: When the power and temperature values are provided in BTU/Hour and Fahrenheit, they are converted to Watt and Celsius. When the values are displayed, they are reconverted and rounded off to the next highest numbers. Therefore, the values are slightly higher when displayed in BTU/Hour and Fahrenheit scale.

Why are there same number of power cap or threshold violations for all the entries in my report?

Cause: For a in-built or custom report which consists of a violation attribute along with a timestamp attribute, the violation count that is displayed for all the entries is always for the latest value.

Why do I see blank entries for total energy consumed in reports or metrics graphs?

Cause: The Total Energy Consumed field has no entry for servers and PowerEdge MX7000 devices due to the following reasons:
  • The energy consumption value is not available until the second metric collection is taken.
  • If you change the Data gathering interval to 60 minutes, then for a 60 minutes time period the Energy Consumption value cannot be calculated. This happens when data is collected for a day with hourly granularity for reports.
  • If the power metric in iDRAC is reset during the interval that is chosen, and the latest reading has a lower value than the oldest reading.

Why do I not see all metric types for different types of devices?

Cause: Different devices support different types of metrics.

Table 1. List of supported devices and metricsList of supported devices and metrics
Device Type Supported Metrics
12th generation of PowerEdge servers
  • Maximum, minimum, and average power
  • Maximum and average temperature
  • System airflow
  • Energy consumption
13th generation and 14th generation of PowerEdge servers
  • Maximum, minimum, and average power
  • Maximum and average temperature
  • Maximum, minimum, and average CPU utilization
  • Maximum, minimum, and average Input Output utilization
  • Maximum, minimum, and average Memory Utilization
  • System airflow
  • Energy consumption
PowerEdge M1000e, VRTX, FX2, and FX2s chassis
  • Maximum, minimum, and average power
  • Instant temperature
  • Energy consumption
PowerEdge MX7000 chassis
  • Maximum and minimum power
  • Maximum and minimum temperature
  • Energy consumption
NOTE Modular servers do not support System Airflow values.
Also, if all the criteria is met and still you are not able to view Power Manager data, ensure that the Server Power Monitoring feature is enabled on the device you are discovering. To view the discovery log of a device:
  1. In OpenManage Enterprise, click Monitor > Jobs.

    The Jobs page is displayed.

  2. Search for the discovery type job for the device and select the job.
  3. Click the View Details on the right side of the tab.

    Details about the job are displayed.

    In the Messages: section, check the status for Server Power Monitoring feature.

NOTE If the Server Power Monitoring feature is disabled, then the device is not compatible with Power Manager.

Why do I see a failure of EPR in audit log but EPR is applied successfully for the device?

Cause: Applying EPR on the target device may fail due to the following reasons:
  • Connectivity issues between the appliance and the target device.
  • If the target device is part of Power Manager with an expired license.

Why do I see a failure of EPR in audit log but EPR is applied successfully for the group?

Cause: When EPR option is applied for a group, and if the EPR option is applied successfully for at least one device in the group, the EPR banner is displayed at the group level. However, the EPR option may fail on other devices within the group due to connectivity issues or license expiry and so on. Therefore, use the EPR audit logs for successful and failure scenarios for all devices of the group.

Why are devices not listed for addition to Power Manager?

Cause: You cannot view certain devices in Power Manager because of the following reasons:
  • If devices do not have OpenManage Enterprise Advanced license.
  • If the devices are discovered in OpenManage Enterprise, and then Power Manager is installed, then the devices are not displayed in Power Manager until you Run Inventory on OpenManage Enterprise.
  • Devices like switches, storage sleds, I/O modules are not supported in Power Manager.
  • Servers that are discovered through the operating system(in-band) are not supported in Power Manager.

Why am I not able to install Power Manager?

Cause: There are two cases in which the installation of Power Manager may fail:
  • If you have selected the online updates option in OpenManage Enterprise, check that the connectivity for the online path is successful.
  • If you have selected the offline updates option in OpenManage Enterprise, ensure that the ome_powermanager_1.0.0.tar.gz folder has all the files for the plugin catalog with the sign file and the plugin installer packages, including the RPMs. The installation fails if there is a mismatch between the catalog and .tar files.

Why am I not able to disable or uninstall Power Manager?

Cause: If active policies or an EPR option is enabled, you cannot disable or uninstall Power Manager.

Resolution: Disable the active policies and EPR option, and then try to disable or uninstall Power Manager.

Why are policies being disabled when too many policies are selected for deletion or disable or enable?

Cause: When you select multiple policies for enabling or disabling or deleting, the job is initiated. However, the policies are disabled on the user interface (UI) until the action is complete. After the job is complete, there are entries to the audit logs for these actions.

Why cannot I remove some devices or groups from Power Manager?

Cause: If you have applied an Emergency Power Reduction (EPR) option on the device or a group, then you cannot remove the device or group from Power Manager.

Resolution: Disable the EPR option on the device or group, and then remove them from Power Manager.

Why is Power Manager not listed on Console and plugins page?

Cause: Power Manager may not be listed due to the following reasons:
  • The offline share folder is not accessible.
  • Power Manager plugin and tar folder.s are not present in the offline share folder.
  • If the plugin catalog file is edited, then the signature files can get corrupted.
Resolution: Ensure that the offline share folder is reachable through OpenManage Enterprise with the following files:
  • ome_powermanager_1.0.0.tar.gz
  • plugins_catalog
  • plugins_catalog.json.asc

Also, download and replace the corrupt plugins_catalog file.

Why am I not able to apply policies on some devices or groups?

Cause: You can apply a policy only on devices that are supported by Power Manager, having a valid license, and that are added to Power Manager.

You can apply policies on supported PowerEdge servers with iDRAC Enterprise, PowerEdge FX2, FX2s, and VRTX chassis with CMC Enterprise license.

NOTE PowerEdge M1000e and PowerEdge MX7000 chassis do not require a CMC Enterprise license.

Why are some alerts not being forwarded using SNMP?

Cause: The following events are not forwarded as SNMP alerts:
  • Device membership or group membership changes
  • Device management such as change in license status

Alerts are generated by OpenManage Enterprise or Power Manager, that is displayed in the system health category and metric/power configuration subcategory the SNMP trap forwarding is not supported.

Why some email alerts are not getting forwarded?

Cause: The following events are not forwarded as SNMP alerts:
  • Device membership or group membership changes.
  • Device management such as change in license status.

SNMP trap forwarding is not supported.

Why are some devices automatically removed from Power Manager?

Cause: If the OpenManage Enterprise Advanced license has expired or is removed from a target node, then the device is removed from Power Manager after the device capability check is run.

Why do I not see temperature metric for some devices?

Cause: The temperature metric is not visible for devices if they are powered off.

Why can I not select a particular child group?

Cause: When you select a group, all the child groups within this group are also selected. Likewise, when you clear a child group the selection gets cleared at the main group level.

Why am I seeing No Data Available or No Information available message for some devices metrics?

Cause: When the first metric collection has not yet happened or if the device is not reachable, the following message is displayed: No Data Available

When a device is not added to Power Manager even though it is a supported device, the following message is displayed: No Information available.

Why are some of the fields in reports empty?

Cause: The fields may be empty in a report due to the following reasons:
  • The device was not reachable for that duration.
  • That category is not applicable for that device.
  • The values are not defined for certain fields in Power Manager and these fields are part of the report.
    For example, when you have not configured the power and temperature threshold values for a device, the following fields are added to the report, but the values are not populated:
    • Upper Warning Power
    • Upper Critical Power
    • Lower Critical Temperature
    • Lower Warning Temperature
    • Upper Warning Temperature
    • Upper Critical Temperature
If you have configured the above threshold values and only when the threshold values are violated, the following fields are populated and displayed in the report:
  • Lower Critical Violation Count
  • Lower Warning Violation Count
  • Upper Critical Violation Count
  • Upper Warning Violation Count

Why do I not see regular metric data points in the metric graphs?

Cause: A metric graph having irregular metric points indicate that data was not collected for that device at that duration of time.

Why can I not clear the checkbox for policies?

Cause: The checkbox for policies in the Power Policies page is disabled if that policy is being enabled, disabled, or edited. After the job is completed, you can clear the policy.

How do I see the old metric data?

Cause: The old metric data is not available after a few days because the data is deleted. This configuration depends on the selection of the Delete Power Manager data option available in the Power Manager Preferences section.

Why are the values I set using threshold REST API not configured?

Cause: If you use threshold REST API before installing and adding the devices to Power Manager, the values are not retained.

Resolution: Install and add the devices to Power Manager, and then use the threshold REST APIs.

How to delete power cap from devices when they are removed from Power Manager?

Cause: When a power policy is applied on a static group through Power Manager and a member device is removed from that static group in OpenManage Enterprise, and the policy is active, then the power cap on the device is retained on the management console of the device.

Resolution: To remove the power cap on the device, login to the respective management console and disable the power cap policy.

How to remove EPR on device that was part of deleted physical group

Cause:

Resolution: If one of the devices part of a physical group, have an Emergency Power Reduction (EPR) applied on them, and you delete the physical group from OpenManage Enterprise, the EPR is still active on the device.

Resolution: Though the device being a part of physical group is deleted in OpenManage Enterprise, the device is still part of Power Manager. To remove EPR on the device:
  1. Click Power Manager > Emergency Power Reduction.

    The Emergency Power Reduction tab is displayed.

  2. Select the device and click Disable.

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