
PowerEdge Servers Error and Event Messages Reference Guide
CPWR—Power Configuration Event Messages
CPWR0001
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The Power Management settings is successfully saved.
- Detailed Description
- The Power Management settings is successfully saved.
- Recommended Response Action
- No response action is required.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Informational
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0002
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to save the Power Management settings because of internal issues.
- Detailed Description
- The Power Management settings cannot be saved because of internal issues.
- Recommended Response Action
- Retry the operation. If the issue persists, contact your OpenManage Enterprise administrator.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0003
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The following power management job is unsuccessful. Job Name: arg1, Job Type: arg2, Job ID: arg3, Job Status: arg4, Invalid Input: arg5.
- Arguments
- arg1 = jobName
- arg2 = jobType
- arg3 = jobID
- arg4 = jobStatus
- arg5 = Attribute
- Detailed Description
- The power management job identified in the message is unsuccessful.
- Recommended Response Action
- Retry the operation. If the issue persists, contact your OpenManage Enterprise administrator.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0004
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The following power management job is successful. Job Name: arg1, Job Type: arg2, Job ID: arg3, Job Status: arg4.
- Arguments
- arg1 = jobName
- arg2 = jobType
- arg3 = jobID
- arg4 = jobStatus
- Detailed Description
- The power management job identified in the message is successful.
- Recommended Response Action
- No response action is required.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Informational
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0005
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The group arg1 is successfully added for monitoring the arg2.
- Arguments
- arg1 = group ID
- arg2 = group Type
- Detailed Description
- The group is successfully added for monitoring the group type identified in the message.
- Recommended Response Action
- No response action is required.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Informational
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0006
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The group arg1 is successfully deleted from list of arg2 monitoring.
- Arguments
- arg1 = group ID
- arg2 = group Type
- Detailed Description
- The group is successfully deleted from the group type identified in the message.
- Recommended Response Action
- No response action is required.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Informational
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0007
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The Power Management settings is successfully saved.
- Detailed Description
- The Power Management settings is successfully saved.
- Recommended Response Action
- No response action is required.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Informational
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0008
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to save the Power Management settings because of internal issues.
- Detailed Description
- The Power Management settings cannot be saved because of internal issues.
- Recommended Response Action
- Retry the operation. If the issue persists, contact your OpenManage Enterprise administrator.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0009
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The following devices are not anymore monitored by the Power Manager application because the OpenManage Enterprise license has expired: arg1.
- Arguments
- arg1 = device Names
- Detailed Description
- The devices identified in the message are not anymore monitored by the Power Manager application because OpenManage Enterprise the license has expired.
- Recommended Response Action
- To continue monitoring the devices, procure a valid OpenManage Enterprise license. For license information, see the OpenManage Enterprise Users Guide available on the support site.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Informational
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0010
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to add the specified group because the number of groups monitored for power management in the dashboard is more than three.
- Detailed Description
- The specified groups cannot be added because the number of groups monitored for power management in the dashboard is more than three.
- Recommended Response Action
- Make sure that the number of groups is less than three, and then retry the operation. To reduce the number of groups, remove it from the existing list. To set the group number, do the following: 1) In OpenManage Enterprise, click Add Groups. In the Add group(s) to dashboard dialog box, in the Selected group(s) section, select the group and click the remove symbol. 2) By using the REST API command, enter the group ID and run the command.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Informational
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0011
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The properties of group arg1 for power management and monitoring are successfully updated.
- Arguments
- arg1 = groupNames
- Detailed Description
- The properties of the groups identified in the message are successfully updated for power management and monitoring.
- Recommended Response Action
- No response action is required.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Informational
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0012
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The group membership properties of the following groups are successfully updated: arg1.
- Arguments
- arg1 = groups names
- Detailed Description
- The group membership properties of the following groups are successfully updated as identified in the message.
- Recommended Response Action
- For optimized power performance, it is recommended that you re-evaluate the power policies applied to these groups.
- Category
- System Health (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0013
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The power policy arg1 of the group arg2 is violated because of the devices added to the group.
- Arguments
- arg1 = policy name
- arg2 = group name
- Detailed Description
- The power policy of the group identified in the message is violated because of the devices added to the group.
- Recommended Response Action
- Reevaluate the power policy based on the newly added devices, and update the power cap value, if necessary.
- Category
- System Health (CPWR = Power Configuration)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0014
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The violation on the power policy arg1 of the group arg2 is now rectified.
- Arguments
- arg1 = policy name
- arg2 = group name
- Detailed Description
- The violation on the power policy of the group identified is now rectified.
- Recommended Response Action
- No response action is required.
- Category
- System Health (CPWR = Power Configuration)
- Severity
- Informational
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0015
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to create or modify the power policy arg1 because a power policy already exists with the same name.
- Arguments
- arg1 = Power Policy Name
- Detailed Description
- The power policy cannot be created or updated because a power policy already exists with the same name.
- Recommended Response Action
- Enter a unique power policy name and retry the operation.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0016
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to create policy because some of the target devices do not have capability arg1.
- Arguments
- arg1 = CapabilityType
- Detailed Description
- Policy cannot be created because some of the target devices do not have capability as identified in the message.
- Recommended Response Action
- Make sure that all the target devices have the required capability and retry the operation.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0017
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to create the power policy because some of the target devices are not part of the group arg1.
- Arguments
- arg1 = groupName
- Detailed Description
- The power policy cannot be created because some of the target devices are not part of the group identified in the message.
- Recommended Response Action
- Enter a device name that belong to the group, and then retry the operation.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0018
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to complete the operation because the entity arg1 is currently not monitored and managed for power.
- Arguments
- arg1 = entity ID
- Detailed Description
- The operation cannot be completed because the entity identified in the message is not monitored and managed for power.
- Recommended Response Action
- Ensure that the specified entity is monitored and managed for power and retry the operation.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0019
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The Power Cap value arg1 is successfully applied on arg2.
- Arguments
- arg1 = power cap value
- arg2 = target name
- Detailed Description
- The Power Cap value is successfully applied on the target identified in the message.
- Recommended Response Action
- No response action is required.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Informational
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0020
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to apply the Power Cap value arg1 on arg2 because the device is either unreachable or does not have the necessary license or the supplied power cap value is not applicable for the device.
- Arguments
- arg1 = power cap value
- arg2 = target name
- Detailed Description
- The Power Cap value cannot be applied on the device identified in the message because the device is either unreachable or does not have the necessary license or the supplied power cap value is not applicable for the device.
- Recommended Response Action
- Make sure that the target is reachable and has the required license and the power cap value is within supported range,and then retry the operation.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0021
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The Power Cap feature is disabled on the target arg1.
- Arguments
- arg1 = target device name
- Detailed Description
- The Power Cap value is disabled on the target identified in the message.
- Recommended Response Action
- No response action is required.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Informational
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0022
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to disable the power cap value on the device arg1 because it is unreachable.
- Arguments
- arg1 = target device name
- Detailed Description
- The power cap value cannot be disabled on the device identified in the message because it is unreachable.
- Recommended Response Action
- Make sure that the target is reachable, and then retry the operation.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0023
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to enable the Emergency Power Reduction feature on the target arg1 because the feature is already enabled on the target.
- Arguments
- arg1 = target name
- Detailed Description
- The Emergency Power Reduction feature on the target identified in the message cannot be enabled because the feature is already enabled on the target.
- Recommended Response Action
- No response action is required.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0024
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to enable the Emergency Power Reduction feature because target devices are unavailable in the group.
- Detailed Description
- The Emergency Power Reduction feature cannot be enabled because target devices are unavailable in the group.
- Recommended Response Action
- Ensure that valid target devices are available in the group for enabling the Emergency Power Reduction feature, and then retry the operation.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0025
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The Emergency Power Reduction feature is enabled on the target arg1.
- Arguments
- arg1 = target name
- Detailed Description
- The Emergency Power Reduction feature is enabled on the target identified in the message.
- Recommended Response Action
- No response action is required.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Informational
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0026
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to enable the Emergency Power Reduction feature on the target arg1 because the device is either unreachable or does not have necessary license.
- Arguments
- arg1 = target name
- Detailed Description
- The Emergency Power Reduction feature cannot be enabled on the target because the device is either unreachable or does not have necessary license.
- Recommended Response Action
- Make sure that the target is reachable and has the required license, and then retry the operation.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0027
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The Emergency Power Reduction feature is successfully disabled on the target arg1.
- Arguments
- arg1 = target name
- Detailed Description
- The Emergency Power Reduction feature is successfully disabled on the target identified in the message.
- Recommended Response Action
- No response action is required.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Informational
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0028
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to disable Emergency Power Reduction on the device arg1 because it is unreachable.
- Arguments
- arg1 = target device name
- Detailed Description
- The Emergency Power Reduction feature cannot be disabled on the device identified in the message because it is unreachable.
- Recommended Response Action
- Ensure that the target device is reachable and retry the operation.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0029
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to remove or disassociate devices or groups from power management and monitoring because the Emergency Power Reduction feature is active on arg1.
- Arguments
- arg1 = entityType
- Detailed Description
- The devices or groups cannot be removed or disassociated from power management and monitoring because the Emergency Power Reduction feature is active on the entity identified in the message.
- Recommended Response Action
- Disassociate or disable all the Emergency Power Reduction features, and then retry the operation.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0030
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The arg1 are successfully arg2 in the Power Monitoring list.
- Arguments
- arg1 = Entity Type
- arg2 = task Name
- Detailed Description
- The devices of groups identified in the message are successfully updated in the Power Monitoring list.
- Recommended Response Action
- No response action is required.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Informational
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0031
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to arg1 the arg2 for power management and monitoring because arg3.
- Arguments
- arg1 = action
- arg2 = entityType
- arg3 = reason
- Detailed Description
- The devices identified in the message cannot be added for power management and monitoring because a valid license is unavailable.
- Recommended Response Action
- Retry the operation by using valid device IDs.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0032
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The power policy arg1 is successfully deleted.
- Arguments
- arg1 = policy names
- Detailed Description
- The power policy identified in the message is successfully deleted.
- Recommended Response Action
- No response action is required.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Informational
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0033
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The power policy arg1 is disabled.
- Arguments
- arg1 = policy names
- Detailed Description
- The power policy identified in the message is disabled.
- Recommended Response Action
- No response action is required.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Informational
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0034
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The power policy arg1 is successfully created.
- Arguments
- arg1 = policy names
- Detailed Description
- The power policy identified in the message is successfully created.
- Recommended Response Action
- No response action is required.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Informational
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0035
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The power policy arg1 is successfully modified.
- Arguments
- arg1 = policy names
- Detailed Description
- The power policy identified in the message is successfully modified.
- Recommended Response Action
- No response action is required.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Informational
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0036
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The power policy arg1 is successfully enabled.
- Arguments
- arg1 = policy names
- Detailed Description
- The power policy identified in the message is successfully enabled.
- Recommended Response Action
- No response action is required.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Informational
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0037
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The device arg1 and other devices are no longer monitored and managed for power because the OpenManage Enterprise license has expired.
- Arguments
- arg1 = deviceName
- Detailed Description
- The device identified in the message and other devices are no longer monitored and managed for power because the OpenManage Enterprise license has expired.
- Recommended Response Action
- Purchase a valid OpenManage Enterprise license, deploy, and successfully monitor the devices. For information about OpenManage license, see the OpenManage Enterprise Users Guide available on the support site.
- Category
- System Health (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0038
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The current frequency for gathering power-related metric is set to arg1 minutes because more than arg2 devices are added for power management and monitoring.
- Arguments
- arg1 = interval
- arg2 = device count
- Detailed Description
- The power-related metric collection frequency is configured to 15 minutes due to the addition of over 1,000 devices for power management and monitoring. Similarly, for over 8,000 devices, it is configured to 30 minutes. The supported collection intervals include 5, 15, and 30 minutes.
- Recommended Response Action
- No response action is required.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Informational
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0039
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The arg1 are successfully arg2 from the Power Monitoring list.
- Arguments
- arg1 = Entity Type
- arg2 = task Name
- Detailed Description
- The devices or groups identified in the message are successfully removed from the Power Monitoring list.
- Recommended Response Action
- No response action is required.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Informational
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0040
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The unmonitored device arg1 is successfully arg2.
- Arguments
- arg1 = device Name
- arg2 = action Name
- Detailed Description
- An operation is successfully completed on the unmonitored device identified in the message.
- Recommended Response Action
- No response action is required.
- Category
- Audit (CPWR = Power Configuration)
- Severity
- Informational
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0041
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to create or edit the device because the device name entered already exists.
- Detailed Description
- The device cannot be created or edited because the device name entered already exists.
- Recommended Response Action
- Enter a unique device name and retry the operation.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0042
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to create or edit the device because the device identifier name entered already exists.
- Detailed Description
- The device cannot be created or edited because the device identifier name entered already exists.
- Recommended Response Action
- Enter a unique device identifier name and retry the operation.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0043
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to disassociate devices from power management and monitoring because the devices arg1 are already associated with groups.
- Arguments
- arg1 = deviceNames
- Detailed Description
- The device cannot be disassociated from power management and monitoring because the devices identified in the message are already associated with groups.
- Recommended Response Action
- By using OpenManage Enterprise, remove the devices from groups, and then retry the operation. After the devices are removed, the devices status is automatically updated.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0044
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to place the device arg1 because the device size (U) is not conforming to the defined standards.
- Arguments
- arg1 = deviceName
- Detailed Description
- The device identified in the message cannot be placed because the device size (U) is not conforming to the defined standards.
- Recommended Response Action
- Make sure that the device size (U) is correct and retry the operation. For information about compatible device types, see the OpenManage Enterprise-Modular Users Guide available on the support site.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0046
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to move the device arg1 to the space because the device arg2 is occupying the space.
- Arguments
- arg1 = device Name
- arg2 = target Device Name
- Detailed Description
- The device identified in the message cannot be moved in the rack because some other device is occupying the space.
- Recommended Response Action
- Ensure that there is enough consecutive unoccupied slots in the Rack for the device and retry the operation.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0047
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The temperature of the group arg1 has exceeded the threshold temperature set by the temperature triggered policy arg2.
- Arguments
- arg1 = group Name
- arg2 = policy Name
- Detailed Description
- The temperature of the group has exceeded the threshold temperature set by the temperature triggered policy identified in the message.
- Recommended Response Action
- Make sure that the cooling infrastructure is operational. For more information about the cooling system, see the respective hardware documentation of the device in the group.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0048
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The issue of temperature of the group arg1, exceeding the threshold temperature set by the temperature triggered policy arg2, is now resolved.
- Arguments
- arg1 = group Name
- arg2 = policy Name
- Detailed Description
- The issue of temperature of the group, exceeding the threshold temperature set by the temperature triggered policy, is successfully resolved.
- Recommended Response Action
- No response action is required.
- Category
- Audit (CPWR = Power Configuration)
- Severity
- Informational
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0049
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Emergency Power Reduction (EPR) cannot be enabled on the group arg1 because the member group devices are not supported for the operation, cannot be accessed, do not have necessary license, or EPR is already enabled.
- Arguments
- arg1 = groupName
- Detailed Description
- The Emergency Power Reduction feature cannot be enabled on the group identified in the message the member group devices are not supported for the operation, cannot be accessed, do not have necessary license, or EPR is already enabled.
- Recommended Response Action
- Make sure that the member devices in the group are accessible, have necessary license, and then retry the operation.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0050
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The Emergency Power Reduction feature is successfully enabled on the group arg1 by using the temperature triggered policy arg2.
- Arguments
- arg1 = group Name
- arg2 = policy Name
- Detailed Description
- The Emergency Power Reduction feature is successfully enabled on the group by using the temperature triggered policy identified in the message.
- Recommended Response Action
- No response action is required.
- Category
- Audit (CPWR = Power Configuration)
- Severity
- Informational
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0051
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The unmonitored device arg1 is successfully created.
- Arguments
- arg1 = deviceName
- Detailed Description
- The unmonitored device identified in the message is successfully created.
- Recommended Response Action
- No response action is required.
- Category
- Audit (CPWR = Power Configuration)
- Severity
- Informational
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0052
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The unmonitored device arg1 is successfully deleted.
- Arguments
- arg1 = deviceName
- Detailed Description
- The unmonitored device identified in the message is successfully deleted.
- Recommended Response Action
- No response action is required.
- Category
- Audit (CPWR = Power Configuration)
- Severity
- Informational
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0053
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The unmonitored device arg1 is successfully modified.
- Arguments
- arg1 = device Names
- Detailed Description
- The unmonitored device identified in the message is successfully modified.
- Recommended Response Action
- No response action is required.
- Category
- Audit (CPWR = Power Configuration)
- Severity
- Informational
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0054
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to create the temperature-triggered policy because a similar policy already exists on the group arg1.
- Arguments
- arg1 = group Name
- Detailed Description
- The temperature-triggered policy cannot be created because a similar policy already exists on the group identified in the message.
- Recommended Response Action
- Do one of the following: 1) Instead of creating a new policy, update the existing policy with the required temperature threshold value. 2) Delete the current temperature-triggered policy, and then create a new policy.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0055
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to create the temperature-triggered policy because the group arg1 is either empty or does not contain any devices that have the required license.
- Arguments
- arg1 = group Name
- Detailed Description
- The temperature-triggered policy cannot be created because the group name entered is either empty or does not contain any devices that have the required license.
- Recommended Response Action
- Make sure that the group contains devices having necessary license, and then retry the operation. Use GUI or REST API for adding devices to the group.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0056
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The Emergency Power Reduction feature, with the ID arg1, cannot be manually disabled because it is applied by a temperature-triggered policy.
- Arguments
- arg1 = EPR Policy ID
- Detailed Description
- The Emergency Power Reduction feature, with the ID identified in the message, cannot be manually disabled because it is applied by a temperature-triggered policy. The feature will be automatically disabled when the temperature of the target group is less than the specified threshold value.
- Recommended Response Action
- Make sure that the cooling infrastructure is functional and the temperature-triggered policy is set to the required temperature threshold value.
- Category
- System Health (CPWR = Power Configuration)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0057
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The temperature-triggered policy arg1 is successfully created.
- Arguments
- arg1 = policy name
- Detailed Description
- The temperature-triggered policy identified in the message is successfully created.
- Recommended Response Action
- No response action is required.
- Category
- Audit (CPWR = Power Configuration)
- Severity
- Informational
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0058
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The temperature-triggered policy arg1 is successfully modified.
- Arguments
- arg1 = policy name
- Detailed Description
- The temperature-triggered policy identified in the message is successfully modified.
- Recommended Response Action
- No response action is required.
- Category
- Audit (CPWR = Power Configuration)
- Severity
- Informational
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0059
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The temperature-triggered policy arg1 is successfully deleted.
- Arguments
- arg1 = policy name
- Detailed Description
- The temperature-triggered policy identified in the message is successfully deleted.
- Recommended Response Action
- No response action is required.
- Category
- Audit (CPWR = Power Configuration)
- Severity
- Informational
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0060
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The temperature-triggered policy arg1 is successfully enabled.
- Arguments
- arg1 = policy name
- Detailed Description
- The temperature-triggered policy identified in the message is successfully enabled.
- Recommended Response Action
- No response action is required.
- Category
- Audit (CPWR = Power Configuration)
- Severity
- Informational
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0061
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The temperature-triggered policy arg1 is successfully disabled.
- Arguments
- arg1 = policy name
- Detailed Description
- The temperature-triggered policy identified in the message is successfully disabled.
- Recommended Response Action
- No response action is required.
- Category
- Audit (CPWR = Power Configuration)
- Severity
- Informational
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0062
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The arg1 policy and other policies are successfully enabled for power management and monitoring.
- Arguments
- arg1 = policyName
- Detailed Description
- The policy identified in the message and other policies are successfully enabled for power management and monitoring. For more information, see the Policies page in the Power Management feature.
- Recommended Response Action
- No response action is required.
- Category
- Audit (CPWR = Power Configuration)
- Severity
- Informational
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0063
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The arg1 policy and other policies are successfully disabled for power management and monitoring.
- Arguments
- arg1 = policyName
- Detailed Description
- The policy identified in the message and other policies are successfully disabled for power management and monitoring. For more information, see the Policies page in the Power Management feature.
- Recommended Response Action
- No response action is required.
- Category
- Audit (CPWR = Power Configuration)
- Severity
- Informational
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0064
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The Emergency Power Reduction feature that was earlier enabled on the arg1 group, by using the temperature-triggered policy arg2, is now automatically disabled.
- Arguments
- arg1 = group name
- arg2 = policy name
- Detailed Description
- The Emergency Power Reduction feature that was earlier enabled on the group, by using the temperature-triggered policy identified in the message, is now automatically disabled. The feature is disabled because one or more of the following reasons: 1) The issue of temperature of the group, exceeding the threshold temperature set by the temperature-triggered policy, is successfully resolved. 2) The temperature-triggered policy is disabled or deleted.
- Recommended Response Action
- No response action is required.
- Category
- Audit (CPWR = Power Configuration)
- Severity
- Informational
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0065
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Power consumed by the arg1 group is arg2 which has exceeded the power capacity arg3 allocated by the user for the group.
- Arguments
- arg1 = group Name
- arg2 = power Consumption
- arg3 = power Allocation
- Detailed Description
- Power consumed by the group identified in the message has exceeded the power allocated by the user for the group.
- Recommended Response Action
- Make sure that sufficient Power Supply Units (PSUs) are available. If necessary, update the power allocated for the group.
- Category
- System Health (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0066
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Power consumed by the arg1 group, which had exceeded the power capacity arg2 allocated by the user for the group, is now within the set limit.
- Arguments
- arg1 = group Name
- arg2 = power Allocation
- Detailed Description
- Power consumed by the group, which had exceeded the allocated power capacity, is now within the user allocated limit as identified in the message.
- Recommended Response Action
- No response action is required.
- Category
- System Health (CPWR = Power Configuration)
- Severity
- Informational
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0067
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to create the physical group because multiple group tag names are entered.
- Detailed Description
- The physical group cannot be created because multiple group tag names are entered.
- Recommended Response Action
- Enter only one tag name and retry the operation. For information about creating physical groups, see the OpenManage Enterprise Users Guide available on the support site.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0068
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to assign the PHYSICAL_HIERARCHY_ROOT tag to the group.
- Detailed Description
- The PHYSICAL_HIERARCHY_ROOT tag cannot be assigned to the group.
- Recommended Response Action
- Enter a valid tag name and retry the operation. For information about tags, see the OpenManage Enterprise - Power Manager Users Guide available on the support site.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0069
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to create the physical group because the group tag name is not entered.
- Detailed Description
- The physical group cannot be created because the group tag name is not entered.
- Recommended Response Action
- Enter a valid tag name and retry the operation. For information about creating physical groups, see the OpenManage Enterprise - Power Manager Users Guide available on the support site.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0070
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to create the physical group because the power and space capacity attributes are not entered.
- Detailed Description
- The physical group cannot be created because the power and space capacity attributes are not entered.
- Recommended Response Action
- Enter a valid power and space capacity attributes in the payload and retry the operation. For information about creating physical groups, see the OpenManage Enterprise Users Guide available on the support site.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0071
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to create the physical group because the arg1 attribute is non-editable.
- Arguments
- arg1 = attributeName
- Detailed Description
- The physical group cannot be created because the attribute is non-editable.
- Recommended Response Action
- Enter valid editable attribute in the payload and retry the operation. For information about creating physical groups, see the OpenManage Enterprise Users Guide available on the support site.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0072
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to update the rack space capacity because the slot arg1 is occupied.
- Arguments
- arg1 = slot number
- Detailed Description
- The rack space capacity cannot be updated because the slot identified in the message is occupied by a device.
- Recommended Response Action
- Rearrange or remove the device to vacate slots and retry the operation. For information about updating rack space capacity, see the OpenManage Enterprise Users Guide available on the support site.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0073
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to complete the operation because the Emergency Power Reduction (EPR) feature is enabled on the group arg1.
- Arguments
- arg1 = groupName
- Detailed Description
- The operation cannot be completed because the Emergency Power Reduction (EPR) feature is enabled on the group identified in the message.
- Recommended Response Action
- Disable the Emergency Power Reduction (EPR) feature on the group, and then retry the operation. For information about disabling the EPR feature, see the OpenManage Enterprise Users Guide available on the support site.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0074
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to complete the operation because the device IDs and slot numbers must be unique.
- Detailed Description
- The operation cannot be completed because the device IDs and slot numbers must be unique.
- Recommended Response Action
- Enter unique values for device IDs and slot numbers and retry the operation.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0075
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to complete the operation because the group ID entered is not of "Rack" type.
- Detailed Description
- The operation cannot be completed because the group ID entered is not of "Rack" type.
- Recommended Response Action
- Enter a group ID of "Rack" type, and then retry the operation.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0076
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to accommodate the arg1 device in the rack because consecutive empty slots are unavailable in the rack.
- Arguments
- arg1 = deviceName
- Detailed Description
- The device identified in the message cannot be accommodated because consecutive empty slots are unavailable in the rack.
- Recommended Response Action
- Make sure that the necessary consecutive slots are available in the rack, and then retry the operation. For information about rack management, see the OpenManage Enterprise Users Guide available on the support site.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0077
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to add the device arg1 to the rack because the device is not rack-mountable.
- Arguments
- arg1 = deviceName
- Detailed Description
- The device identified in the message cannot be added to the rack because the device is not rack-mountable.
- Recommended Response Action
- Enter valid rack-mountable device ID in the payload, and then retry the operation. For information about valid rack-mountable devices, see the OpenManage Enterprise Users Guide available on the support site.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0078
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to add the arg1 device to rack because the device is already associated with another rack.
- Arguments
- arg1 = deviceName
- Detailed Description
- The device identified in the message cannot be added to the rack because the device is already associated with another rack.
- Recommended Response Action
- Make sure that the device is not associated with any other rack, and then retry the operation.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0079
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to virtually place the device in the rack because the U-size information of the device is unavailable.
- Detailed Description
- The device cannot be virtually placed because the U-size information of the device is unavailable.
- Recommended Response Action
- Make sure device U size is available and retry the operation.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0080
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to add the device to the rack because the Emergency Power Reduction (EPR) feature is currently enabled on the group arg1.
- Arguments
- arg1 = target Rack
- Detailed Description
- The device cannot be added to the rack because the Emergency Power Reduction (EPR) feature is currently enabled on the group identified in the message.
- Recommended Response Action
- Disable the Emergency Power Reduction (EPR) feature on the group from Power Management page, and then retry the operation.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0081
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to remove the device from the group because the device is not associated with the group.
- Detailed Description
- The device cannot be removed from the group because the device is not associated with the group.
- Recommended Response Action
- Make sure that the device is a part of the group, and then retry the operation.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0082
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to move the device within the rack because the device is not associated with the rack.
- Detailed Description
- The device cannot be moved within the rack because the device is not associated with the rack.
- Recommended Response Action
- Make sure that the device is a part of the rack, and then retry the operation.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0083
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to explicitly add the arg1 physical group to the monitored list, because by default, the physical group is a part of the list of monitored groups.
- Arguments
- arg1 = groupName
- Detailed Description
- The physical group identified in the message cannot be explicitly added to the monitored list, because by default, the physical group is a part of the list of monitored groups.
- Recommended Response Action
- Enter valid data in the field and retry the operation. For information about valid data permitted in a field, see the OpenManage Enterprise Users Guide available on the support site.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0084
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to explicitly remove the arg1 physical group from the monitored list, because by default, the physical group is a part of the list of monitored groups.
- Arguments
- arg1 = groupName
- Detailed Description
- The physical group identified in the message cannot be explicitly removed from the list of monitored group list, because by default, the physical group is a part of the list of monitored groups.
- Recommended Response Action
- Log into OpenManage Enterprise, and then delete the physical group. This action removes the physical group from the list of groups monitored using Power Management.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0085
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to update the size of the device arg1 because the device is placed in a rack that does not have slots to accommodate the size of the installed device.
- Arguments
- arg1 = deviceName
- Detailed Description
- Size of the device identified in the message cannot be updated because the device is placed in a rack that does not have slots to accommodate the size of the installed device.
- Recommended Response Action
- Make sure that the device is of recommended size that the rack can hold. For information about compatible device sizes, see the Rack Installation Guide of the respective device available on the support site.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0086
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to add the device to the rack because empty slots are unavailable in the rack.
- Detailed Description
- The device cannot be added to the rack because empty slots are unavailable in the rack.
- Recommended Response Action
- Make sure that the rack has empty slots of compatible device size, and then retry the operation.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0087
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to add the device arg1 and other devices to the rack because the devices are not rack-mountable.
- Arguments
- arg1 = deviceName
- Detailed Description
- The device identified in the message and other devices cannot be added to the rack because the devices are not rack-mountable.
- Recommended Response Action
- Enter valid rack-mountable device IDs in the payload, and then retry the operation. For information about valid rack-mountable devices, see the OpenManage Enterprise Users Guide available on the support site.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0088
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The device arg1 information is successfully updated for power management and monitoring.
- Arguments
- arg1 = deviceName
- Detailed Description
- The information of the device identified in the message is successfully updated for power management and monitoring.
- Recommended Response Action
- No response action is required.
- Category
- Audit (CPWR = Power Configuration)
- Severity
- Informational
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0089
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The device arg1 information and other devices are successfully updated for power management and monitoring.
- Arguments
- arg1 = deviceName
- Detailed Description
- The information of the device identified in the message and other devices are successfully updated for power management and monitoring.
- Recommended Response Action
- No response action is required.
- Category
- Audit (CPWR = Power Configuration)
- Severity
- Informational
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0090
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to complete the operation because data entered in the field arg1 is invalid.
- Arguments
- arg1 = field
- Detailed Description
- The operation cannot be completed because invalid data is entered in the field identified in the message.
- Recommended Response Action
- Enter valid data in the field and retry the operation. For information about valid data permitted in a field, see the OpenManage Enterprise Users Guide available on the support site.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0091
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to add the device to the physical group arg1 because devices can be added only using the OpenManage Enterprise API.
- Arguments
- arg1 = groupID
- Detailed Description
- The device cannot be added to the physical group identified in the message because devices can be added only using the OpenManage Enterprise API.
- Recommended Response Action
- Add the device to the physical group only by using the the OpenManage Enterprise API. For more information, see the OpenManage Enterprise API Guide available on the developer portal.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0092
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to remove the device from the physical group arg1 because devices can be removed only using the OpenManage Enterprise API.
- Arguments
- arg1 = groupID
- Detailed Description
- The device cannot be removed from the physical group identified in the message because devices can be added only using the OpenManage Enterprise API.
- Recommended Response Action
- Remove the device from the physical group only by using the OpenManage Enterprise API. For more information, see the OpenManage Enterprise API Guide available on the developer portal.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0093
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- One or more devices are successfully added to the group arg1.
- Arguments
- arg1 = rack Name
- Detailed Description
- One or more devices are successfully added to the group identified in the message.
- Recommended Response Action
- No response action is required.
- Category
- Audit (CPWR = Power Configuration)
- Severity
- Informational
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0094
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The slot information, about one or more devices in the rack arg1, is successfully updated.
- Arguments
- arg1 = rack Name
- Detailed Description
- The slot information, about one or more devices in the rack identified in the message, is successfully updated.
- Recommended Response Action
- No response action is required.
- Category
- Audit (CPWR = Power Configuration)
- Severity
- Informational
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0095
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- One or more devices are successfully removed from the group arg1.
- Arguments
- arg1 = rack Name
- Detailed Description
- One or more devices are successfully removed from the group identified in the message.
- Recommended Response Action
- No response action is required.
- Category
- Audit (CPWR = Power Configuration)
- Severity
- Informational
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0096
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to add the device arg1, or other devices to the group arg2 because: 1) Device ID is not valid. 2) Device is not rack-mountable. 3) Device is already added to a group. 4) Size details of the device does not exist or is invalid.
- Arguments
- arg1 = device Name
- arg2 = rack Name
- Detailed Description
- One or more devices cannot be added to the group identified in the message because: 1) Device ID is not valid. 2) Device is not rack-mountable. 3) Device is already added to a group. 4) Size details of the device does not exist or is invalid.
- Recommended Response Action
- Make sure that the device ID is valid and have valid size information associated to them, and then retry the operation. For information about valid rack-mountable devices, see the OpenManage Enterprise Users Guide available on the support site.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0097
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to update size of one or more devices arg1 because they are not rack-mountable.
- Arguments
- arg1 = device IDs
- Detailed Description
- Unable to update size of one or more devices identified in the message because they are not rack-mountable.
- Recommended Response Action
- Ensure that the specified entity is monitored and managed for power and retry the operation.
- Category
- Audit (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0098
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to assign the outlet arg1 to the device arg2 because the device ID entered does not belong to a Power Distribution Unit (PDU).
- Arguments
- arg1 = outletNum
- arg2 = deviceID
- Detailed Description
- The outlet to the device identified in the message cannot be assigned because the device ID entered does not belong to a Power Distribution Unit (PDU).
- Recommended Response Action
- Enter a valid Power Distribution Unit (PDU) device ID and retry the operation.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0099
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to assign the outlet arg1 to the device arg2 because the Power Distribution Unit (PDU) device ID entered is invalid.
- Arguments
- arg1 = outletNum
- arg2 = deviceID
- Detailed Description
- The outlet to the device identified in the message cannot be assigned because the Power Distribution Unit (PDU) device ID entered is invalid.
- Recommended Response Action
- Enter a valid Power Distribution Unit (PDU) device ID and retry the operation.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0100
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to assign the outlet arg1 to the device arg2 because the Power Distribution Unit (PDU) outlet is already associated to another device.
- Arguments
- arg1 = outletNum
- arg2 = deviceID or deviceName
- Detailed Description
- The outlet to the device identified in the message cannot be assigned because the Power Distribution Unit (PDU) outlet is already associated to another device.
- Recommended Response Action
- Enter a valid and free (unoccupied) outlet number and retry the operation.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0101
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to assign the outlet arg1 to the device arg2 because the Power Distribution Unit (PDU) and the device to be associated with the outlet is not in the same group.
- Arguments
- arg1 = outletNum
- arg2 = deviceID
- Detailed Description
- The outlet to the device identified in the message cannot be assigned because the Power Distribution Unit (PDU) and the device to be associated with the outlet is not in the same group.
- Recommended Response Action
- Make sure that the device and the Power Distribution Unit (PDU) are from the same group, and then retry the operation.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0102
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to assign the outlet arg1 to the device arg2 because the Power Distribution Unit (PDU) and the device to be associated with the outlet does not have the minimum required Power Supply Units (PSUs).
- Arguments
- arg1 = outletNum
- arg2 = deviceID
- Detailed Description
- DevicesPSUs are already occupied so cannot assign outlet to device.
- Recommended Response Action
- Devices PSU is already occupied by PDU outlet, Clear the existing assignment using REST API /api/PowerService/PowerDevices/Actions/PowerDevices.DissociateDevices and retry the operation.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0103
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to disassociate the device from the Power Distribution Unit (PDU) because the device ID entered does not belong to a Power Distribution Unit (PDU).
- Detailed Description
- The outlet to the device identified in the message cannot be disassociated from the PDU because the device ID entered does not belong to a Power Distribution Unit (PDU).
- Recommended Response Action
- Enter a valid Power Distribution Unit (PDU) device ID and retry the operation.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0104
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to disassociate the device from the Power Distribution Unit (PDU) because the PDU is not associated with any rack.
- Detailed Description
- The outlet to the device identified in the message cannot be disassociated from the PDU because the PDU is not associated with any rack.
- Recommended Response Action
- Enter a valid Power Distribution Unit (PDU) device ID and retry the operation.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0105
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to clear the Power Distribution Unit (PDU) outlet arg1 because the PDU outlet is not assigned to any device.
- Arguments
- arg1 = outletNum
- Detailed Description
- The outlet identified in the message cannot be cleared because the Power Distribution Unit (PDU) outlet is not assigned to any device.
- Recommended Response Action
- Enter a valid occupied Power Distribution Unit (PDU) outlet and retry the operation.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0106
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to assign the Power Distribution Unit (PDU) arg1 to the rack because the PDU can be assigned to only one rack at any given time.
- Arguments
- arg1 = deviceID
- Detailed Description
- The Power Distribution Unit (PDU) device ID identified in the message cannot be assigned to rack because the PDU can be assigned to only one rack at any given time.
- Recommended Response Action
- Enter a valid unassigned Power Distribution Unit (PDU) device ID and retry the operation.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0107
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to associate the Power Distribution Unit (PDU) arg1 to the rack because the PDU cannot be placed in the rack slot.
- Arguments
- arg1 = deviceID
- Detailed Description
- The Power Distribution Unit (PDU) cannot associated to the rack because the PDU cannot be placed in the rack slot.
- Recommended Response Action
- Enter a valid value(zero or null) for the rack slot and retry the operation.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0108
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to assign Power Distribution Unit (PDU) arg1 to rack because PDU is already associated with given rack.
- Arguments
- arg1 = deviceID
- Detailed Description
- The Power Distribution Unit (PDU) device identified in the message cannot be associated to rack because the PDU is already associated to rack.
- Recommended Response Action
- Enter a valid free (Unassociated) Power Distribution Unit (PDU) device ID and retry the operation.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0109
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to retrieve Power Distribution Unit (PDU) outlet assignment details because the PDU with given ID does not exist.
- Detailed Description
- The Power Distribution Unit (PDU) outlet assignment details cannot be retrieved because the PDU with the given ID does not exist.
- Recommended Response Action
- Enter a valid existing Power Distribution Unit (PDU) device ID and retry the operation.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0110
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to update details of the device arg1 because device PSU count is lesser than the total Power Distribution Unit (PDU) outlet assigned to it.
- Arguments
- arg1 = deviceID
- Detailed Description
- The operation cannot be completed because the device identified in the message has more Power Distribution Unit (PDU) outlet assignment than the PSU count.
- Recommended Response Action
- Make sure that PSU count of the device is same or more than the total Power Distribution Unit (PDU) outlet assigned to it.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0111
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to move the device arg1 to other rack because device is assigned to Power Distribution Unit (PDU) outlet.
- Arguments
- arg1 = deviceID
- Detailed Description
- The operation cannot be completed because device identified in the message is assigned to Power Distribution Unit (PDU) outlet.
- Recommended Response Action
- Clear the outlet assignments of the device identified in the message and retry the operation.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0112
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to update details of the device arg1 because device PSU count cannot be more than 8.
- Arguments
- arg1 = deviceID
- Detailed Description
- Data of the device identified in the message cannot be updated because the device PSU count is more than the recommended threshold value of 1-8.
- Recommended Response Action
- Make sure that the device PSU count is between 1 to 8 and retry the operation.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0113
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- One or more Power Distribution Unit (PDU) outlets are successfully updated.
- Detailed Description
- One or more Power Distribution Unit (PDU) outlets are successfully updated.
- Recommended Response Action
- Noresponse action is required.
- Category
- Audit (CPWR = Power Configuration)
- Severity
- Informational
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0114
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to add the Virtual Machine (VM) arg1 to virtual machine group because the server in which the VM exists is not monitored and managed for power.
- Arguments
- arg1 = vmName
- Detailed Description
- Virtual Machine (VM) identified in the message cannot be added to Virtual machine group because the server in which the VM exists is not monitored and managed for power.
- Recommended Response Action
- Make sure that the server in which the Virtual Machine (VM) exists is part of the Power Management motoring list and retry the operation.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0115
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to add Virtual Machine (VM) arg1 to Virtual machine group because the VM already exist in the Virtual machine group.
- Arguments
- arg1 = vmName
- Detailed Description
- The Virtual Machine (VM) identified in the message cannot be added to the VM group because a VM already exists in the VM group.
- Recommended Response Action
- Make sure that the Virtual Machine (VM) to be added is not exist in the Virtual Machine Group and retry the operation.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0116
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to add Virtual Machine(s) (VM) to Virtual Machine Group because the value entered for Virtual Machine Group is invalid.
- Detailed Description
- The operation cannot be completed because the value entered for Virtual Machine Group is invalid.
- Recommended Response Action
- Enter valid existing Virtual Machine Group ID and retry the operation.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0117
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to remove the virtual machine arg1 from the Virtual Machine Group because the entered VM ID is not associated to the VM group.
- Arguments
- arg1 = VMname
- Detailed Description
- The Virtual Machine (VM) identified in the message cannot be removed from the VM group because the entered VM ID is not associated to the VM group.
- Recommended Response Action
- Enter a valid and availableVM ID which is associated to the group, and then retry the operation.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0118
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to move Virtual Machine (VM) arg1 because 1) VM does not belong source group. 2) VM is already exist in the destination group.
- Arguments
- arg1 = vmName
- Detailed Description
- The Virtual Machine (VM) cannot be moved because 1) VM does not belong source group. 2) VM is already exist in the destination group.
- Recommended Response Action
- Make sure that the Virtual Machine (VM) identified in the message is present in source Virtual Machine Group and not part of destination Virtual Machine Group and retry the operation.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0119
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The Virtual machine(s) are successfully added in the Virtual Machine group arg1.
- Arguments
- arg1 = groupName
- Detailed Description
- The Virtual Machines (VMs) are added to the VM group identified in the message.
- Recommended Response Action
- Noresponse action is required.
- Category
- Audit (CPWR = Power Configuration)
- Severity
- Informational
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0120
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The Virtual machine(s) are successfully removed from the Virtual Machine group arg1.
- Arguments
- arg1 = groupName
- Detailed Description
- The Virtual Machines (VMs) are removed from the VM group identified in the message.
- Recommended Response Action
- Noresponse action is required.
- Category
- Audit (CPWR = Power Configuration)
- Severity
- Informational
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0121
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to get rack placeable device details because 1) Device ID is invalid. 2) Device is not rack mountable. 3) Device is already added to rack. 4) Device size details does not exist or is invalid.
- Detailed Description
- Data about the rack-placeable device cannot be retrieved because 1) Device ID is invalid. 2) Device is not rack mountable. 3) Device is already added to rack. 4) Device size details does not exist or is invalid.
- Recommended Response Action
- Enter a valid device ID and retry the operation.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0122
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to move the device within the rack because the device is of type PDU.
- Detailed Description
- The device cannot be moved within the rack because the device of type Power Distribution Unit (PDU).
- Recommended Response Action
- Makesure that device to be moved is not PDU device type and retry the operation.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0123
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to retrieve the device data because of one or more of the following reasons: 1) The device ID is invaid. 2) The device is not rack-mountable. 3) The device is already added to a rack. 4) The device size data does not exist or is invalid.
- Detailed Description
- The device data cannot be retrieved because of one or more of the following reasons: 1) The device ID is invaid. 2) The device is not rack-mountable. 3) The device is already added to a rack. 4) The device size data does not exist or is invalid.
- Recommended Response Action
- Make sure that the device ID is valid and have valid size information associated tothem, and then retry the operation. For information about valid rack-mountabledevices, see the OpenManage Enterprise Users Guide available on thesupport site.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0124
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The device arg1 is successfully moved from rack arg2 to rack arg3.
- Arguments
- arg1 = deviceName
- arg2 = fromGroup
- arg3 = toGroup
- Detailed Description
- The device identified in the message is successfully moved from one rack group to the other rack group.
- Recommended Response Action
- No response action is required.
- Category
- Audit (CPWR = Power Configuration)
- Severity
- Informational
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0125
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The power consumed by the device arg1, for policy arg2, has exceeded or equals the power cap threshold value of arg3.
- Arguments
- arg1 = deviceName
- arg2 = policyName
- arg3 = thresholdPolicy
- Detailed Description
- The Power Consumption of the device has exceeded or equals the defined power cap threshold.
- Recommended Response Action
- No response action is required.
- Category
- Audit (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0126
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The power consumed by the group arg1, for policy arg2, has exceeded or equals the power cap threshold value of arg3.
- Arguments
- arg1 = groupName
- arg2 = policyName
- arg3 = thresholdPolicy
- Detailed Description
- The Power Consumption of the group has exceeded or equals the defined power cap threshold.
- Recommended Response Action
- No response action is required.
- Category
- Audit (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0127
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The location information is successfully updated on the device based on the physical hierarchy data.
- Detailed Description
- The location information is updated on the device based on the physical hierarchy grouping information in OpenManage Enterprise.
- Recommended Response Action
- No response action is required.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Informational
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0128
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to update the device location data in arg1 by using similar data configured in the console because the device cannot be detected.
- Arguments
- arg1 = targetName
- Detailed Description
- The location information cannot be updated on the device based on the physical hierarchy grouping information in OpenManage Enterprise because the device cannot be detected.
- Recommended Response Action
- Make sure that the target device is available and retry the operation. For information about detecting the device, see the OpenManage Enterprise Users Guide available on the support site.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0129
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The physical location of device in iDRAC, CMC, or MSM need not be updated or synced with the data configured in the console because both device location data are the same.
- Detailed Description
- The physical location of device in iDRAC, CMC, or MSM need not be updated or synced with the data configured in the console because both device location data are the same.
- Recommended Response Action
- Make sure that the devices whose location matches the physical hierarchy are removed from the list, and then retry the operation.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0130
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The policy arg1 is activated on arg2.
- Arguments
- arg1 = policyName
- arg2 = deviceName or groupName
- Detailed Description
- The policy identified in the message is activated on the device or group. This activation impacts the powercap of the device or group.
- Recommended Response Action
- No response action is required.
- Category
- System Health (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0131
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The Power-Throttle or Shutdown EPR is enabled on the group arg1 by the temperature-trigged policy arg2.
- Arguments
- arg1 = groupName
- arg2 = policyName
- Detailed Description
- The Power-Throttle or Shutdown EPR is enabled on the group by the temperature-triggered policy identified in the message.
- Recommended Response Action
- No response action is required.
- Category
- System Health (CPWR = Power Configuration)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0132
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The manual EPR is applied on the arg1.
- Arguments
- arg1 = deviceName or groupName
- Detailed Description
- The manual EPR is applied on the device or group identified in the message.
- Recommended Response Action
- No response action is required.
- Category
- System Health (CPWR = Power Configuration)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0133
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The policy arg1 is deactivated on arg2.
- Arguments
- arg1 = policyName
- arg2 = deviceName or groupName
- Detailed Description
- The policy identified in the message is deactivated on the device or group. This activation impacts the powercap of the device or group.
- Recommended Response Action
- No response action is required.
- Category
- System Health (CPWR = Power Configuration)
- Severity
- Informational
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0134
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The Power-Throttle or Shutdown EPR is disabled on the group arg1 by the temperature-trigged policy arg2.
- Arguments
- arg1 = groupName
- arg2 = policyName
- Detailed Description
- The Power-Throttle or Shutdown EPR is disabled on the group by the temperature-triggered policy identified in the message.
- Recommended Response Action
- No response action is required.
- Category
- System Health (CPWR = Power Configuration)
- Severity
- Informational
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0135
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The manual EPR is revoked on the arg1.
- Arguments
- arg1 = deviceName or groupName
- Detailed Description
- The manual EPR is revoked on the device or group identified in the message.
- Recommended Response Action
- No response action is required.
- Category
- System Health (CPWR = Power Configuration)
- Severity
- Informational
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0136
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to implement the resolution arg1 on target arg2. An incorrect resolution value is entered or target device is not reachable.
- Arguments
- arg1 = resolutionType
- arg2 = targetName
- Detailed Description
- The resolution value identified in the message cannot be implemented because an incorrect resolution value is entered or target device is not reachable. For information about supported values, see the OpenManage Enterprise Users Guide available on the support site.
- Recommended Response Action
- Make sure that the resolution value entered is correct and target device is reachable.
- Category
- Audit (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0137
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to start the task because a task of similar type is already running.
- Detailed Description
- The task cannot be started because a task of similar type is already running.
- Recommended Response Action
- Cancel the current task or wait for the task to complete, and then retry the operation.
- Category
- Audit (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0138
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to implement the resolution arg1 on target arg2. The resolution is not applicable for the targeted device.
- Arguments
- arg1 = resolutionType
- arg2 = targetName
- Detailed Description
- The resolution type identified in the message cannot be implemented because non applicable resolution type is entered.
- Recommended Response Action
- Enter a valid resolution value that can applied on the target device, and then retry the operation.
- Category
- Audit (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0139
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The Power-Throttle or Shutdown EPR is enabled on the device arg1 by Liquid Cooling System alert.
- Arguments
- arg1 = deviceName
- Detailed Description
- The Power-Throttle or Shutdown EPR is enabled by Liquid Cooling System alert on the device identified in the message.
- Recommended Response Action
- No response action is required.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0140
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The Power-Throttle or Shutdown EPR which was enabled earlier on the device arg1 by Liquid Cooling System alert is disabled.
- Arguments
- arg1 = deviceName
- Detailed Description
- The Power-Throttle or Shutdown EPR which was enabled by Liquid Cooling System alert earlier on the device identified in the message is disabled.
- Recommended Response Action
- No response action is required.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Informational
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0141
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The properties of the group arg1 and the group hierarchy are successfully updated for power management and monitoring.
- Arguments
- arg1 = groupName
- Detailed Description
- The properties of the group identified in the message are successfully updated for power management and monitoring.
- Recommended Response Action
- No response action is required.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Informational
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0142
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to add the device arg1 to the physical group arg2 because the device is already associated or placed in a physical group that is part of another hierarchy.
- Arguments
- arg1 = deviceName
- arg2 = physicalGroupLocation
- Detailed Description
- The device cannot be added to the physical group because the device is already associated or placed in a physical group that is part of another hierarchy identified in the message.
- Recommended Response Action
- Disassociate or remove the device from rack slot and retry the operation.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0143
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to move the device arg1 because the device is associated with the hierarchy arg2 and cannot be moved to another hierarchy.
- Arguments
- arg1 = deviceName
- arg2 = physicalGroupLocation
- Detailed Description
- The device cannot be moved because the device is associated with another hierarchy and cannot be moved outside the hierarchy identified in the message.
- Recommended Response Action
- Make sure that the device is not associated with any physical group and retry the operation.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0144
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to update the parent hierarchy of the group arg1 because the UPS device is associated with it.
- Arguments
- arg1 = groupName
- Detailed Description
- The parent hierarchy of a group cannot be updated because the UPS device is associated with a group identified in the message.
- Recommended Response Action
- Make sure that the device is not associated with any physical group and retry the operation.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0145
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to remove the device arg1 from the physical group arg2 because the device is associated with the physical group arg3.
- Arguments
- arg1 = deviceName
- arg2 = physicalGroupLocation
- arg3 = rootPhysicalGroupLocation
- Detailed Description
- The device cannot be removed from the physical group because the device is associated with another physical group identified in the message.
- Recommended Response Action
- Make sure that the device is not associated with any physical group and retry the operation.
- Category
- Configuration (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0163
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to collect the metrics for the device arg1.
- Arguments
- arg1 = deviceName
- Detailed Description
- The metrics cannot be collected for the device identified in the message.
- Recommended Response Action
- Ensure the device meets the following requirements: 1) It is reachable. 2) It is discovered with valid authentication credentials. 3) It has the necessary license. 4) It has not exceeded the telemetry metric report definition limit.
- Category
- System Health (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0164
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- Unable to collect the metrics for the device arg1 and several other devices.
- Arguments
- arg1 = deviceName
- Detailed Description
- The metrics cannot be collected for the device identified in the message and several other devices.
- Recommended Response Action
- Ensure the device meets the following requirements: 1) It is reachable. 2) It is discovered with valid authentication credentials. 3) It has the necessary license. 4) It has not exceeded the telemetry metric report definition limit.
- Category
- System Health (CPWR = Power Configuration)
- Severity
- Warning
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
CPWR0166
NOTE: Event or Alert types that are enabled by default are identified using an asterisk (*) symbol in the
Applicable Event or Alert Types section.
- Message
- The IRC device arg1 reported a critical failure, which triggered the arg2 of the rack device arg3. The current operation status is arg4.
- Arguments
- arg1 = irc_device_name
- arg2 = shutdown_type
- arg3 = rack_device_name
- arg4 = operation_status
- Detailed Description
- The IRC device indicated critical failure triggering shutdown of rack device.
- Recommended Response Action
- Resolve the IRC critical alerts, then power on the affected devices.
- Category
- System Health (CPWR = Power Configuration)
- Severity
- Critical
- Redfish Event Type
- Not Applicable
- Applicable Event or Alert Types
- No alerts are applicable for this message
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: <>()\