- Notes, Cautions, and Warnings
- Introduction
- AMP Event Messages
- ASR Event Messages
- BAR Event Messages
- BAT Event Messages
- BIOS Event Messages
- BOOT Event Messages
- CBL Event Messages
- CMC Event Messages
- CPU Event Messages
- CPUA Event Messages
- CTL Event Messages
- DH Event Messages
- DIAG Event Messages
- DIS Event Messages
- DKM Event Messages
- ECM Event Messages
- ENC Event Messages
- EPP Event Messages
- FAN Event Messages
- FC Event Messages
- FCD Event Messages
- FLDC Event Messages
- FSD Event Messages
- HWC Event Messages
- IOID Event Messages
- IOV Event Messages
- IPA Event Messages
- ISM Event Messages
- JCP Event Messages
- LC Event Messages
- LIC Event Messages
- LNK Event Messages
- LOG Event Messages
- MEM Event Messages
- NIC Event Messages
- OSD Event Messages
- OSE Event Messages
- PCI Event Messages
- PDR Event Messages
- PFM Event Messages
- POW Event Messages
- PR Event Messages
- PST Event Messages
- PSU Event Messages
- PSUA Event Messages
- PWR Event Messages
- RAC Event Messages
- RDU Event Messages
- RED Event Messages
- RFL Event Messages
- RFLA Event Messages
- RFM Event Messages
- RRDU Event Messages
- RSI Event Messages
- SEC Event Messages
- SEL Event Messages
- SSD Event Messages
- STOR Event Messages
- SUP Event Messages
- SWC Event Messages
- SWU Event Messages
- SYS Event Messages
- TMP Event Messages
- TMPS Event Messages
- TST Event Messages
- UEFI Event Messages
- USR Event Messages
- VDR Event Messages
- VF Event Messages
- VFL Event Messages
- VFLA Event Messages
- VLT Event Messages
- VME Event Messages
- VRM Event Messages
Event and Error Message Reference Guide for 13th Generation Dell PowerEdge ServersVersion 1.2
PWR Event Messages
PWR1000
PWR1001
- Message
- The system performance degraded.
- Detailed Description
- To avoid shutdown, system performance has been degraded.
- Recommended Response Action
- Review system configuration and power consumption.
- Category
- System Health (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
- Trap/EventID
- 2274
- LCD Message
- System performance degraded. Check PSUs and system configuration
PWR1002
- Message
- The system performance degraded because of thermal protection.
- Detailed Description
- To avoid shutdown, system performance has been degraded.
- Recommended Response Action
- Review system configuration and system logs for thermal or environmental failures and warnings.
- Category
- System Health (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
- Trap/EventID
- 2274
PWR1003
- Message
- The system performance degraded because cooling capacity has changed.
- Detailed Description
- To avoid shutdown, system performance has been degraded.
- Recommended Response Action
- If unintended, review system configuration changes and thermal policy.
- Category
- System Health (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
- Trap/EventID
- 2274
PWR1004
- Message
- The system performance degraded because power capacity has changed.
- Detailed Description
- To avoid shutdown, system performance has been degraded.
- Recommended Response Action
- if unintended, review system configuration changes and power policy.
- Category
- System Health (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
- Trap/EventID
- 2274
PWR1005
- Message
- The system performance degraded because of user-defined power capacity has changed.
- Detailed Description
- To avoid exceeding the user defined capacity, system performance has been degraded.
- Recommended Response Action
- If unintended, review system configuration changes and power policy.
- Category
- System Health (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
- Trap/EventID
- 2274
PWR1006
- Message
- The system halted because system power exceeds capacity.
- Detailed Description
- The system may shutdown.
- Recommended Response Action
- Review system configuration, upgrade power supplies or reduce system power consumption.
- Category
- System Health (PWR = Power Usage)
- Severity
- Severity 1 (Critical)
- Trap/EventID
- 2273
- LCD Message
- System power exceeds capacity. System halted. Contact support
PWR1007
- Message
- The system performance degraded because power exceeds capacity.
- Detailed Description
- To avoid shutdown, system performance has been degraded.
- Recommended Response Action
- Review system configuration, upgrade power supplies or reduce system power consumption.
- Category
- System Health (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
- Trap/EventID
- 2274
- LCD Message
- System power exceeds capacity. Performance degraded. Check PSU configuration
PWR1008
- Message
- The system performance degraded because power draw exceeds the power threshold.
- Detailed Description
- To avoid shutdown, system performance has been degraded.
- Recommended Response Action
- Review system configuration, upgrade power supplies or reduce system power consumption.
- Category
- System Health (PWR = Power Usage)
- Severity
- Severity 1 (Critical)
- Trap/EventID
- 2273
- LCD Message
- System power exceeds threshold. Performance degraded. Check PSU configuration
PWR1009
PWR200
- Message
- Enabling the Max Power Conservation Mode (MPCM) feature will disable the Extended Power Performance (EPP) feature.
- Detailed Description
- Enabling the Max Power Conservation Mode (MPCM) feature will disable the Extended Power Performance (EPP) feature. MPCM forces servers in to a low-power and limited-performance mode, and then disables the ability to turn on additional servers.
- Recommended Response Action
- No response action required.
- Category
- System Health (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
PWR201
- Message
- Selecting the Server Based Power Management Mode option sets your power cap to a maximum value, server priorities to a default priority, and then disables the Max Power Conservation Mode. Do you want to continue?
- Detailed Description
- Selecting the Server Based Power Management Mode option sets your power cap to a maximum value, server priorities to a default priority, and then disables the Max Power Conservation Mode.
- Recommended Response Action
- No response action required.
- Category
- System Health (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
PWR202
- Message
- Enabling the Max Power Conservation Mode (MPCM) feature forces servers in to a low-power and limited-performance mode, and then disables the ability to turn on additional servers.
- Detailed Description
- Enabling the Max Power Conservation Mode (MPCM) feature forces servers in to a low-power and limited-performance mode, and then disables the ability to turn on additional servers.
- Recommended Response Action
- No response action required.
- Category
- System Health (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
PWR203
- Message
- Unable to set the System Input Power Cap value to less than or equal to 13300 W (45381 BTU/h), because the Extended Power Performance feature is enabled.
- Detailed Description
- The System Input Power Cap value cannot be set to less than or equal to 13300 W, because the Extended Power Performance feature is enabled.
- Recommended Response Action
- Enter a Power cap value greater than 13300 W, and then retry the operation.
- Category
- System Health (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
PWR204
- Message
- Object value is successfully modified. Max Power Conservation Mode will deactivate the Extended Power Performance feature.
- Detailed Description
- Object value is successfully modified. Max Power Conservation Mode will deactivate the Extended Power Performance feature.
- Recommended Response Action
- No response action required.
- Category
- System Health (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
PWR205
- Message
- The Server Performance Over Power Redundancy (SPOPR) feature cannot be enabled because the Extended Power Performance is enabled.
- Detailed Description
- The Server Performance Over Power Redundancy (SPOPR) feature cannot be enabled because the Extended Power Performance is enabled.
- Recommended Response Action
- Disable Extended Power Performance and retry the operation.
- Category
- System Health (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
PWR206
- Message
- The Server Based Power Management (SBPM) feature cannot be enabled because the Extended Power Performance mode is enabled.
- Detailed Description
- The Server Based Power Management (SBPM) feature cannot be enabled because the Extended Power Performance mode is enabled.
- Recommended Response Action
- Disable Extended Power Performance and retry the operation.
- Category
- System Health (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
PWR207
- Message
- The Dynamic Power Supply Engagement (DPSE) feature cannot be enabled because the Extended Power Performance mode is enabled.
- Detailed Description
- The Dynamic Power Supply Engagement (DPSE) feature cannot be enabled because the Extended Power Performance mode is enabled.
- Recommended Response Action
- Disable Extended Power Performance and retry the operation.
- Category
- System Health (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
PWR209
- Message
- Unable to change the redundancy policy to either Power Supply Redundancy or No Redundancy because the Extended Power Performance is enabled.
- Detailed Description
- The redundancy policy cannot be changed to either Power Supply Redundancy or No Redundancy because the Extended Power Performance is enabled.
- Recommended Response Action
- Disable Extended Power Performance and retry the operation.
- Category
- System Health (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
PWR210
- Message
- The redundancy policy cannot be changed to either Power Supply Redundancy or No Redundancy because the Extended Power Performance is enabled.
- Detailed Description
- The redundancy policy cannot be changed to either Power Supply Redundancy or No Redundancy because the Extended Power Performance is enabled.
- Recommended Response Action
- No response action required.
- Category
- System Health (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
PWR211
- Message
- Unable to set the Fresh Air (FA) mode because the Extended Power Performance (EPP) feature is enabled.
- Detailed Description
- The Fresh Air (FA) mode cannot be set because the Extended Power Performance (EPP) feature is enabled.
- Recommended Response Action
- No response action required.
- Category
- System Health (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
PWR213
- Message
- Cannot enable the Extended Power Performance (EPP) mode because the Max Power Conservation Mode (MPCM) is enabled.
- Detailed Description
- Cannot enable the Extended Power Performance (EPP) mode because the Max Power Conservation Mode (MPCM) is enabled.
- Recommended Response Action
- Disable the Max Power Conservation Mode and retry the operation.
- Category
- System Health (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
PWR214
- Message
- Cannot enable the Extended Power Performance (EPP) mode because Dynamic Power Supply Engagement (DPSE) is enabled.
- Detailed Description
- Cannot enable the Extended Power Performance (EPP) mode because Dynamic Power Supply Engagement (DPSE) is enabled.
- Recommended Response Action
- DIsable Dynamic Power Supply Engagement (DPSE) and retry the operation.
- Category
- System Health (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
PWR216
- Message
- Unable to enable Extended Power Performance, because Redundancy Policy is set to Grid Redundancy or No Redundancy.
- Detailed Description
- Unable to enable Extended Power Performance, because redundancy policy is set to Grid Redundancy or No Redundancy.
- Recommended Response Action
- Configure Redundancy Policy to Power Supply Redundancy and retry the operation. Using the CMC Web GUI, click Power > Configuration. From the Redundancy Policy drop-down menu, select Power Supply Redundancy.
- Category
- System Health (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
PWR218
- Message
- Cannot enable the Extended Power Performance (EPP) feature because the Fresh Air (FA) mode is enabled.
- Detailed Description
- Cannot enable the Extended Power Performance (EPP) the feature because the Fresh Air (FA) mode is enabled.
- Recommended Response Action
- No response action is required.
- Category
- System Health (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
PWR219
- Message
- The Extended Power Performance (EPP) feature cannot be enabled because the PSU in slot arg1 is not a 3000 W PSU.
- Arguments
- arg1 = slot number
- Detailed Description
- The Extended Power Performance (EPP) feature cannot be enabled because PSU in the slot identified in the message is not a 3000 W PSU.
- Recommended Response Action
- In order to use the Extended Power Performance (EPP) feature, replace the PSU identified in the message with a 3000 W PSU.
- Category
- System Health (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
PWR220
- Message
- The Extended Power Performance (EPP) feature cannot be enabled because slot arg1 is empty.
- Arguments
- arg1 = slot number
- Detailed Description
- The Extended Power Performance (EPP) feature cannot be enabled because the slot identified in the message is empty.
- Recommended Response Action
- Insert an appropriate PSU in the slot identified in the message and retry the operation.
- Category
- System Health (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
PWR223
- Message
- Cannot perform a 110V AC operation because the Extended Power Performance (EPP) feature is enabled.
- Detailed Description
- Cannot perform a 110V AC operation because the Extended Power Performance (EPP) feature is enabled.
- Recommended Response Action
- Disable the Extended Power Performance (EPP) feature and retry the operation.
- Category
- System Health (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
PWR2250
- Message
- Unable to turn on the server because the chassis infrastructure not ready.
- Detailed Description
- The server did not turn on bacause the chassis infrastructure is not ready. The chassis infrstructure includes: PCIe subsystem, storage components, and the chassis management controller.
- Recommended Response Action
- Check the status of the chassis infrastructure in the CMC Web or RACADM interface. Wait until the chassis infrastructure components are fully turned on.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
PWR2252
- Message
- Unable to turn on the server because an NDC or Mezzanine card is incompatible with the I/O Module or PCIe subsystem.
- Detailed Description
- The server did not turn on because an NDC or Mezzanine card is incompatible with the I/O Module or PCIe subsystem.
- Recommended Response Action
- Check the release notes for the product and make sure to install compatible componenets in the server.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
PWR2253
- Message
- Unable to turn on the server because a PCIe card or Mezzanine card is not installed.
- Detailed Description
- The server did not turn on because a PCIe card or Mezzanine card is not installed.
- Recommended Response Action
- Install a PCI or Mezzanine card in the appropriate slot and retry the operation.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
PWR2254
- Message
- The use of 110V is unacknowledged and the chassis cannot grant power on permission to the server.
- Detailed Description
- The use of 110V is unacknowledged for the chassis and the chassis cannot grant power on permission to the server.
- Recommended Response Action
- Check for unacknowledged use of 110V and change to acknowledged. Using the Chassis Management Controller (CMC) web interface, select Chassis Overview>Power>Configuration and then check the 110V Acknowledge field. Retry the operation to turn on the server.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
PWR2255
- Message
- The Chassis Managment Controller (CMC) is configured in Max Power Conservation Mode and is unable to grant power on permission to the server.
- Detailed Description
- The Chassis Managment Controller (CMC) is configured in Max Power Conservation Mode and is unable to grant power on permission to the server.
- Recommended Response Action
- Disable the Max Powe Conservation Mode on the chassis and retry the operation. Using the Chassis Management Controller (CMC) web interface, select Chassis Overview>Power>Configuration and then uncheck the Max Power Conservation Mode field.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
PWR2256
- Message
- Unable to allocate power for servers to turn on because the Chassis Management Controller (CMC) is initializing chassis infrastructure components.
- Detailed Description
- The chassis infrastructure components are being initialized and are not ready to grant power on permission to the servers.
- Recommended Response Action
- Wait until the chassis infrastructure has been initialized and then retry the operation. To check that the infrastructure is initialized, using the RACADM command line utility run the command "racadm getmodinfo" and check that the "pwrstate" field is on for the chassis component.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
PWR2257
- Message
- The target power allocation override is arg1 . The target power allocation (AC) is arg2 Watts.
- Arguments
- arg1 = override state, arg2 = target power
- Detailed Description
- The target power allocation override has been enabled or disabled as identified in the message.
- Recommended Response Action
- No response action required.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 3 (Informational)
PWR2258
- Message
- The Power Supply Unit (PSU) hotspare thresholds were modified. Wake Threshold: arg1 %, Sleep Threshold: arg2 %.
- Arguments
- arg1 = wake threshold, arg2 = sleep threshold
- Detailed Description
- The Power Supply Unit (PSU) hotspare thresholds were modified to the Wake Threshold and Sleep Threshold identified in the message.
- Recommended Response Action
- No response action required.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 3 (Informational)
PWR2260
- Message
- The Intel Management Engine is unresponsive and the server thermal failsafe state is activated.
- Detailed Description
- The iDRAC experienced an IPMB communication issue with the Intel Management Engine and was not able to recover IPMB communications. The server thermal failsafe state is activiated.
- Recommended Response Action
- Disconnect power from the server and reconnect power. Turn on the server. If the issue persists, contact your service provider.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
PWR2261
- Message
- Current Monitor initialization issue observed, IMON Revision arg1 , CPLD IMON MFR Revision arg2 .
- Arguments
- arg1 = current monitor revision number, arg2 = CPLD revision number
- Detailed Description
- The iDRAC experienced an issue initializing the Current Monitor. The system motherboard may need replacement.
- Recommended Response Action
- Contact your service provider.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
PWR2262
- Message
- The Intel Management Engine has reported an internal system error.
- Detailed Description
- The Intel Management Engine is unable to utilize the PECI over DMI facility.
- Recommended Response Action
- Look for the PWR2264 "normal system operation" message in the Lifecycle Log after the PWR2262 entry. It may take 30 seconds for the message to be logged. If the PWR2264 message does not appear, do the following: Disconnect power from the server and reconnect power. Turn on the server. If the issue persists, contact your service provider.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
PWR2264
- Message
- The Intel Management Engine has reported normal system operation.
- Detailed Description
- The Intel Management Engine ihas recovered the ablility to utilize the PECI over DMI facility.
- Recommended Response Action
- If the PWR2262 "internal system error" was logged within the previous 30 seconds, ignore the message. No response action required.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 3 (Informational)
PWR2400
- Message
- Power management firmware unable to maintain power limit
- Detailed Description
- The power management firmware cannot reduce power consumption to meet configuration or user defined settings,
- Recommended Response Action
- "1) Review system power policy. 2) Check system event logs for thermal or power related exceptions."
- Category
- System Health (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
PWR2401
- Message
- Power management firmware initialization error
- Detailed Description
- The iDRAC controller detected that the power management firmware did not initialize properly. The system may operate in a performance degraded state.
- Recommended Response Action
- "1) Disconnect system input power, wait one minute, reconnect system input power. 2) Re-flash system BIOS. 3) Upgrade system BIOS to the latest revision."
- Category
- System Health (PWR = Power Usage)
- Severity
- Severity 1 (Critical)
PWR2402
- Message
- iDRAC is unable to communicate with power management firmware.
- Detailed Description
- The iDRAC controller cannot communicate with the power management firmware due to an problem with the interface to the power management engine or with the power management engine itself. The system may operate in a performance degraded state.
- Recommended Response Action
- Check the Lifecycle Controller Log (LC Log) and make sure that there are no subsequent log entries indicating that Communication with power management firmware has been restored. If this log entry is not present then do one of the following: 1) Disconnect system input power, wait one minute, reconnect system input power. 2) Re-flash system BIOS. 3) Upgrade system BIOS to the latest revision.
- Category
- System Health (PWR = Power Usage)
- Severity
- Severity 1 (Critical)
PWR2403
- Message
- iDRAC communication with power management firmware has been restored.
- Detailed Description
- The iDRAC controller established communication to the power management firmware. System performance will return to normal.
- Recommended Response Action
- No response action is required.
- Category
- System Health (PWR = Power Usage)
- Severity
- Severity 3 (Informational)
PWR3000
- Message
- The system is being shut down for thermal protection.
- Detailed Description
- To avoid system damage because of insuffecient cooling, the system is being shut down.
- Recommended Response Action
- Review the Embedded System Management Log for thermal or environmental failures and warnings, and replace the faulty components. If the issue persists, contact your service provider.
- Category
- System Health (PWR = Power Usage)
- Severity
- Severity 1 (Critical)
PWR3001
- Message
- Detected new peak power value. Peak value (in Watts): arg1 .
- Arguments
- arg1 = peak value
- Detailed Description
- The system has detected a new peak power value.
- Recommended Response Action
- Make sure that the power usage corresponds to the the current hardware configuration and workload.
- Category
- System Health (PWR = Power Usage)
- Severity
- Severity 3 (Informational)
- OMSA Event ID
- 5013
PWR8500
- Message
- Chassis power state updated to arg1 from arg2 .
- Arguments
- arg1 = new power state, arg2 = old power state
- Detailed Description
- The chassis power state from the configuration database and the current state are different. The current chassis power state will be updated in the configuration database. This is to insure the chassis power state will be the same if the CMC is rebooted or a CMC failover occurs. Note that the numerical value of the state is intended for technical support use.
- Recommended Response Action
- No response action is required.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 3 (Informational)
PWR8501
- Message
- Successfully set Virtual Infrastructure Device power to arg1 WDC
- Arguments
- arg1 = power reading
- Detailed Description
- Power allocation succeeded for Virtual infrastructure.
- Recommended Response Action
- No response action is required.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 3 (Informational)
PWR8503
- Message
- The current value of System Input Power Cap ( arg1 AC) is less than the upper limit ( arg2 AC).
- Arguments
- arg1 = power value, arg2 = power value
- Detailed Description
- This Information is provided to enable checking whether the powercap is lower than the maximum supported powercap limit.
- Recommended Response Action
- No response action is required.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 3 (Informational)
PWR8504
- Message
- Chassis power button is pressed, but the button is disabled.
- Detailed Description
- The chassis power button press is detected but the button has been disabled.
- Recommended Response Action
- The chassis power button is disabled. To enable the chassis power button use the CMC RACADM command line interface, CMC Web interface. Using the command line, enter "racadm config -g cfgChassisPower -o cfgChassisPowerButtonEnable 1". Using the Web interface, click Chassis Overview > Power > Configuration. Clear the Disable Chassis Power Button check box.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 3 (Informational)
PWR8505
- Message
- The Dynamic Power Supply Engagement feature was not successfully enabled.
- Detailed Description
- The Dynamic Power Supply Engagement feature was not successfully enabled.
- Recommended Response Action
- Restart the Chassis Management Controller and retry the operation. To restart the Chassis Management Controller, using the WEB UI, go to Chassis Overview > Power > Control, select the Reset CMC option, and then click Apply.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
PWR8506
- Message
- Cumulative power computation (KWH) time is reset on arg1 .
- Arguments
- arg1 = time
- Detailed Description
- Resetting the power computation reading causes the log to report time at which it is reset.
- Recommended Response Action
- No response action is required.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 3 (Informational)
PWR8507
- Message
- System Input Power Cap changed from arg1 W AC to arg2 W AC.
- Arguments
- arg1 = previous power value, arg2 = new power value
- Detailed Description
- The system Input Power Cap was changed from the value to the value indicated in the message.
- Recommended Response Action
- No response action is required.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 3 (Informational)
PWR8508
- Message
- New power budget ( arg1 W AC) may permit future degradation of redundancy.
- Arguments
- arg1 = power value
- Detailed Description
- If the power budget exceeds the effective capacity for the current redundancy policy, it is possible for power allocations to grow beyond the effective capacity, which would reduce redundancy capabilities.
- Recommended Response Action
- No response action is required. Make sure there are enough PSUs to support redundancy at the specified power budget.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
PWR8509
- Message
- Unable to change the server power priority because Server Based Power Management mode is enabled.
- Detailed Description
- Unable to change the server power priority because Server Based Power Management mode is enabled.
- Recommended Response Action
- The server power priority can be changed once Server Based Power Management mode is disabled. Using the CMC Web UI, navigate to the Chassis Overview > Power > Configuration page, then uncheck the Enable Server Based Power Management checkbox. Retry the operation.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
PWR8510
- Message
- Unable to set chassis power property arg1 .
- Arguments
- arg1 = property name
- Detailed Description
- Unable to set the chassis power identified in the message.
- Recommended Response Action
- Retry the operation. If the issue persists, contact your service provider.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
PWR8511
- Message
- Unable to set the CHASSIS_POWER_button_disable chassis power property.
- Detailed Description
- Unable to set the CHASSIS_POWER_button_disable chassis power property.
- Recommended Response Action
- Retry the operation. If the issue persists, contact your service provider.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
PWR8512
- Message
- CMC rebooted, because the power configuration data could not be accessed.
- Detailed Description
- Power configuration data in memory cannot be accessed due to synchronization issues.
- Recommended Response Action
- No response action is required.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 1 (Critical)
PWR8514
- Message
- Unable to perform chassis power action due to insufficient privileges.
- Detailed Description
- The user account credentials provided for this chassis power action do not have the correct privilege. Chassis control privilege is required to perform chassis power actions.
- Recommended Response Action
- Retry to action with a different user account that has chassis power control privilege.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
PWR8515
- Message
- Unable to perform the chassis power action because the chassis is not turned on.
- Detailed Description
- Unable to perform the chassis power action because the chassis is not turned on.
- Recommended Response Action
- Turn the chassis on and retry the operation.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 3 (Informational)
PWR8516
- Message
- Unable to perform the chassis power action requested..
- Detailed Description
- Unable to perform the chassis power action requested.
- Recommended Response Action
- Check the tracelog for more information. If the issue persists, contact your service provider.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 3 (Informational)
PWR8517
- Message
- Unable to turn off chassis power.
- Detailed Description
- Chassis power state transition did not complete successfully. This may be due to one of the following: 1) Unable to turn off one or more servers, 2) A firmware update may be in progress.
- Recommended Response Action
- Check the tracelog for more information. If the issue persists, contact your service provider.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
PWR8518
- Message
- Unable to perform the chassis power action because the chassis is already turned on.
- Detailed Description
- Unable to perform the chassis power action because the chassis is already turned on.
- Recommended Response Action
- No response action is required.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 3 (Informational)
PWR8519
- Message
- Unable to perform the chassis power action because the chassis is already turned off.
- Detailed Description
- Unable to perform the chassis power action because the chassis is already turned off.
- Recommended Response Action
- No response action is required.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 3 (Informational)
PWR8523
PWR8524
- Message
- Redundancy was lost, while Server Performance Over Power Redundancy is enabled.
- Detailed Description
- The redundancy was lost because the power requirement of the chassis exceeds the current redundant policy.
- Recommended Response Action
- No response action is required. Review the power requirements and determine if more PSUs are needed to restore redundancy.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 3 (Informational)
PWR8525
PWR8526
PWR8527
- Message
- Server slot power priorities changed - reallocating power.
- Detailed Description
- Server slot power priorities were changed. Power to servers is being reallocated.
- Recommended Response Action
- No response action is required.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 3 (Informational)
PWR8528
- Message
- Unable to set Max Power Conservation Mode because the Server Based Power Management mode is enabled.
- Detailed Description
- The Max Power Conservation Mode can be enabled only when Server Based Power Management Mode is disabled.
- Recommended Response Action
- The Max Power Conservation Mode can be changed when Server Based Power Management mode is disabled. Using the CMC Web UI, navigate to the Chassis Overview > Power > Configuration page, then uncheck the Enable Server Based Power Management checkbox. Retry the operation.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
PWR8529
PWR8530
PWR8531
PWR8532
PWR8533
PWR8534
- Message
- Unable to set Server Based Power Management Mode to enable.
- Detailed Description
- Unable to set Server Based Power Management Mode to enable.
- Recommended Response Action
- Retry the operation. If the issue persists, contact your service provider.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
PWR8535
- Message
- Unable to set Server Based Power Management Mode to disable.
- Detailed Description
- Unable to set Server Based Power Management Mode to disable.
- Recommended Response Action
- Retry the operation. If the issue persists, contact your service provider.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
PWR8538
PWR8539
PWR8540
- Message
- Power Remote Logging Interval set to arg1
- Arguments
- arg1 = interval
- Detailed Description
- The interval for remote logging of power information is set to the value identified in the message
- Recommended Response Action
- No response action is required.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 3 (Informational)
PWR8543
- Message
- Server arg1 power inventory is not valid. Power inventory reading is Max Power= arg2 AC Watt, Min Power= arg3 AC Watt, Allocated Power= arg4 AC Watt
- Arguments
- arg1 = slot number, arg2 = max power reading, arg3 = min power reading, arg4 = allocated power reading
- Detailed Description
- Invalid power inventory reported by the iDRAC of the server identified in the message to the CMC.
- Recommended Response Action
- Turn on the server identified in the message. If the issue persists, contact your service provider.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
PWR8544
- Message
- Chassis Management Controller turned off the Server arg1 because of insufficient power at inventory.
- Arguments
- arg1 = slot number
- Detailed Description
- Insufficient power is available for the server identified in the message to function. The server will be turned off until there is sufficient power available.
- Recommended Response Action
- Make sure there is enough power supply to distribute power. Using the CMC Web UI, go to Chassis Overview > Power > Power Budget Status. In the Total Input Power Available For Allocation field view the available power. To add more power, insert more PSUs or remove unused components from the chassis.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 1 (Critical)
PWR8545
- Message
- Chassis Management Controller turned off the server arg1 because of incorrect power data retrieved from iDRAC at inventory.
- Arguments
- arg1 = slot number
- Detailed Description
- Incorrect power inventory information reported by the iDRAC for the server identified in the message.
- Recommended Response Action
- Invalid power inventory information could be due to outdated iDRAC firmware or server BIOS firmware versions. Update the components to their latest versions.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 1 (Critical)
PWR8549
PWR8550
PWR8551
- Message
- Successfully set Virtual Infrastructure Device power to arg1 DC Watt.
- Arguments
- arg1 = power reading
- Detailed Description
- This will be logged when a Virtual Infrastructure Device power allocation is configured.
- Recommended Response Action
- No response action is required.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 3 (Informational)
PWR8552
- Message
- Chassis Management Controller is unable to turn on arg1 - arg2 because of insufficient power.
- Arguments
- arg1 = component name, arg2 = component id
- Detailed Description
- There is insufficient power for the component identified in the message to turn on.
- Recommended Response Action
- Make sure there is enough power supply to distribute power. Using the CMC Web UI, go to Chassis Overview > Power > Power Budget Status. In the Total Input Power Available For Allocation field view the available power. To add more power, insert more PSUs or remove unused components from the chassis. Contact your service provider for information on the power required for the component identified in the message.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
- Trap/EventID
- 8418
PWR8554
- Message
- Chassis Management Controller is unable to send power allocation information to arg1 - arg2 at priority arg3 .
- Arguments
- arg1 = component name, arg2 = component id, arg3 = priority number
- Detailed Description
- This situation occurs if the iDRAC is found to be turned off after power allocation information is sent by the CMC or if the communications between the CMC and iDRAC is non functional.
- Recommended Response Action
- Perform a Virtual Reseat of the component identified in the message. Using the CMC Web UI, go to Chassis Overview > Troubleshooting > Reset Components, and then select slot for the component identified in the message and apply the Virtual Reseat.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 1 (Critical)
PWR8555
- Message
- Chassis Management Controller unable to turn on arg1 - arg2 at priority arg3 because of insufficient power. Minimum power needed is arg4 AC Watt, but only arg5 AC Watt is available.
- Arguments
- arg1 = component name, arg2 = slot number, arg3 = priority number, arg4 = min power, arg5 = avaialble power
- Detailed Description
- The request to turn on the component identified in the message was not successful because insuffficient power is available at the identified priority for the component.
- Recommended Response Action
- Make sure there is enough power supply to distribute power. Using the CMC Web UI, go to Chassis Overview > Power > Power Budget Status. In the Total Input Power Available For Allocation field view the available power. To add more power, insert more PSUs or remove unused components from the chassis.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
- Trap/EventID
- 8418
PWR8556
- Message
- Server arg1 was shutdown due to insufficient power.
- Arguments
- arg1 = slot number
- Detailed Description
- The Server identified in the message was shutdown due to insufficient power.
- Recommended Response Action
- No response action is required.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 1 (Critical)
- Trap/EventID
- 8417
PWR8557
- Message
- The System Input Power Cap is too low to be enforced using the current Power Supply configuration.
- Detailed Description
- The current Power Cap setting cannot be enforced. This may be the result of changing the redundancy mode or by changing the PSUs. The power cap setting must be increased to be usable.
- Recommended Response Action
- Increase the Power Cap value. To increase the Power Cap do one of the following: 1) Using CMC Web interface: Select "Chassis Overview" -> Power -> Configuration and then adjust System Input Power Cap values. 2) Run the following RACADM command at the command line interface: "config -g cfgChassisPower -o cfgChassisPowerCap <value>". Try setting the power cap above the lower bound displayed on the power configuration page.
- Category
- System Health (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
- Trap/EventID
- 2274
PWR8558
- Message
- The System Input Power Cap is being enforced with the current Power Supply configuration.
- Detailed Description
- A configuration change has occurred such that the current power cap is now supported.
- Recommended Response Action
- No response action is required.
- Category
- System Health (PWR = Power Usage)
- Severity
- Severity 3 (Informational)
- Trap/EventID
- 2275
PWR8559
- Message
- Power cycle initiated for I/O Module arg1 .
- Arguments
- arg1 = iIOM slot name
- Detailed Description
- Power cycle initiated for the I/O module in the slot identified in the message.
- Recommended Response Action
- No response action is required.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 3 (Informational)
PWR8560
- Message
- Unable to turn on I/O Module arg1 due to insufficient chassis power.
- Arguments
- arg1 = IOM slot name
- Detailed Description
- Unable to turn on the I/O Module identified in the message due to insufficient chassis power.
- Recommended Response Action
- Utilize the Chassis Management Controller (CMC) web interface to check available power and I/O Module power requirements. If sufficient power is available, restart the CMC and retry the operation. If sufficient power is not available due to an insufficient number of PSUs, add additional PSU(s) and reinsert the I/O Module.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 1 (Critical)
- Trap/EventID
- 8417
PWR8561
- Message
- Unable to power on server arg1 because of iDRAC communication issue.
- Arguments
- arg1 = server number
- Detailed Description
- The Chassis Management Controller is unable to communicate with the Server iDRAC service processor and the server could not be powered on. This situation may occur when iDRAC is rebooting.
- Recommended Response Action
- Wait for three minutes and then retry the operation. If the issue persists, remove and reinsert the server and wait for the iDRAC to finish restarting.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 1 (Critical)
- Trap/EventID
- 8417
PWR8562
- Message
- Unable to power on the server arg1 before power on timer expired.
- Arguments
- arg1 = server number
- Detailed Description
- Unable to power on the server before the power on timer has expired. This happens if the server did not show power on status change within 30 seconds after the power on operation was initiated. This issue may also occur when iDRAC is rebooting.
- Recommended Response Action
- The Server may need more time to power on. Wait for ten seconds and check the power status. If the server was not powered on, retry the operation. If the issue persists, remove and reinsert the server, wait for the iDRAC to complete startup, and retry the operation.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
PWR8563
- Message
- Unable to turn on Server arg1 due to I/O fabric inconsistency.
- Arguments
- arg1 = server number
- Detailed Description
- The Server identified in the message did not turn on due to a fabric mismatch between the I/O Module and the Mezzanine card on the Server.
- Recommended Response Action
- Make sure that the hardware compatibility between the I/O Module (IOM) and the Mezzanine (Mezz) card is correct. Check the M1000e Hardware Manual for correct component compatibility.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 1 (Critical)
- Trap/EventID
- 8417
PWR8564
- Message
- Unable to turn on the Server arg1 because the power request exceeded the System Input Power Cap.
- Arguments
- arg1 = slot number
- Detailed Description
- The server identified in the message was not turned on because the available power is less than the requested power.
- Recommended Response Action
- Utilize the Chassis Management Controller web interface to check the System Input Max Power Capacity Power and server power requirements. If sufficient power is available, retry the operation. Otherwise, increase the System Input Power Cap value.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
- Trap/EventID
- 8418
PWR8565
- Message
- Unable to turn off the Server arg1 due to iDRAC communication issue.
- Arguments
- arg1 = server number
- Detailed Description
- The Chassis Management Controller is unable to communicate with the iDRAC service processor for the Server identified in the message and the Server could not be turned off. This situation may occur when iDRAC is rebooting.
- Recommended Response Action
- Do the following: 1) Wait for a few minutes for the iDRAC service processor to complete startup. 2) Retry the operation. 3) If the issue persists, reset the iDRAC and wait a few minutes for the iDRAC startup to complete before retrying the operation.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 1 (Critical)
- Trap/EventID
- 8417
PWR8566
- Message
- Unable to turn off the Server arg1 before the Power Off timer expired.
- Arguments
- arg1 = server number
- Detailed Description
- Unable to turn off the Server before the Power Off timer has expired. This happens if the Server did not show "power off" status change within 30 seconds after the operation was initiated. This situation may also occur when iDRAC is rebooting.
- Recommended Response Action
- The Server may need more time to turn off. Wait for ten seconds and check the power status. If the Server was not turned off, retry the operation. If the issue persists, remove and reinsert the Server, wait for the iDRAC to complete startup, and retry the operation.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
PWR8567
- Message
- Unable to turn off Server arg1 on a power cycle action.
- Arguments
- arg1 = server number
- Detailed Description
- Unable to turn off the Server on a power cycle operation. This happens if the Server did not show a "power off" status change within the expected time.
- Recommended Response Action
- The Server could have taken more time to turn off than expected. If the Server is turned off, turn on to complete the power cycle. If the Server has not completed a power cycle, retry the operation.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
PWR8568
- Message
- Server arg1 did not gracefully shutdown before the timer expired.
- Arguments
- arg1 = slot number
- Detailed Description
- The server identified in the message did not gracefully shutdown before the CMC shutdown timer expired. This happens if the server did not show power off status change within 60 seconds after the operation was initiated, or if the OS in the server has not successfully shutdown.
- Recommended Response Action
- Check if the OS in the server identified in the message has successfully shutdown, if not, manually complete the shutdown or wait for the shutdown to complete normally. If the issue persists, perform a forced power down of the server identified in the message.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
PWR8569
- Message
- Unable to power cycle the server arg1 because the server is off.
- Arguments
- arg1 = slot number
- Detailed Description
- The requested power cycle operation cannot be performed when the server is not turned on. The server should be already turned on for the power cycle operation to be successful.
- Recommended Response Action
- Turn on the server, if necessary, before requesting a power cycle operation.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 3 (Informational)
PWR8570
- Message
- Unable to communicate to the iDRAC, when trying to power cycle the server arg1 .
- Arguments
- arg1 = slot number
- Detailed Description
- The Chassis Management Controller is not able to communicate with the iDRAC on the server identified in the message. Therefore, the server could not be power cycled. This situation may occur when iDRAC is rebooting.
- Recommended Response Action
- Wait for few minutes, and then retry the operation. If the issue persists, do one of the following: 1) Reset the iDRAC, 2) Perform a Virtual Reseat of the server, 3) Remove and re-insert the server.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
PWR8571
- Message
- Unable to perform the power action requested for the server arg1 because another power action is in progress.
- Arguments
- arg1 = server idr
- Detailed Description
- Another power action is in progress. The requested power action cannot be carried out until the power action in progress completes
- Recommended Response Action
- Wait for the power action in progress to complete and retry the operation. It may take a few minutes for the current power action to complete.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 3 (Informational)
PWR8572
- Message
- Unable to shutdown the server arg1 because the server is off.
- Arguments
- arg1 = server id
- Detailed Description
- The server identified in the message can be shutdown only if the server is turned on.
- Recommended Response Action
- No response action is required.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 3 (Informational)
PWR8573
- Message
- The Chassis Management Controller is unable to communicate to the iDRAC, when trying to turn off the server arg1 .
- Arguments
- arg1 = server id
- Detailed Description
- The Chassis Management Controller is not able to communicate with the iDRAC on the server identified in the message. Therefore the server could not be turned off. This situation may occur when iDRAC is restarting.
- Recommended Response Action
- Wait for three minutes, and then retry the operation. If the issue persists, remove and reinsert the server and wait for the iDRAC to finish restarting before retying the operation.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
- Trap/EventID
- 8418
PWR8574
- Message
- The Chassis Management Controller is unable to communicate to the iDRAC, when trying to hard reset the server arg1 .
- Arguments
- arg1 = slot number
- Detailed Description
- The Chassis Management Controller is not able to communicate with the iDRAC on the server identified in the message. Therefore the server could not be hard reset. This situation may occur when iDRAC is restarting.
- Recommended Response Action
- Wait for three minutes, and then retry the operation. If the issue persists, remove and reinsert the server and wait for the iDRAC to finish restarting before retying the operation.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 1 (Critical)
- Trap/EventID
- 8417
PWR8575
- Message
- Initiated the Virtual Reseat of server arg1 .
- Arguments
- arg1 = server id
- Detailed Description
- A Virtual Reseat for the server identified in the message is initiated. A Virtual Reseat is the same as removing and inserting a server.
- Recommended Response Action
- No response action is required.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 3 (Informational)
PWR8576
- Message
- Unable to turn on the Sleeve or Sled arg1 after a virtual reseat operation.
- Arguments
- arg1 = slot number
- Detailed Description
- The virtual reseat initiated on the Sleeve or Sled identified in the message successfully turned off the component. However, the Sleeve or Sled did not turn on successfully. A virtual reseat is the same as removing and inserting a Sleeve or Sled.
- Recommended Response Action
- Retry the virtual reseat operation on the Sleeve or Sled identified in the message. If the issue persists, manually remove and reinsert the Sleeve or Sled in the chassis.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
PWR8577
- Message
- A virtual reseat operation is initiated on Sleeve or Sled arg1 .
- Arguments
- arg1 = slot number
- Detailed Description
- A virtual reseat operation is initiated on the Sleeve or Sled identified in the message. A virtual reseat is the same as removing and inserting a Sleeve or Sled.
- Recommended Response Action
- No response action is required.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 3 (Informational)
PWR8578
- Message
- Chassis Management Controller is unable to turn on the iDRAC on server- arg1 because power required is less than available power.
- Arguments
- arg1 = slot number
- Detailed Description
- The Chassis Management Controller is unable to turn on the iDRAC because power required is less than available power.
- Recommended Response Action
- Make sure there is enough power supply to distribute power. Go to, the Chassis Overview > Power > Power Budget Status. In the Total Input Power Available For Allocation field, view the available power. To add more power, insert more PSUs or remove unused components from the chassis. Remove and reinsert the server when enough power is available.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
- Trap/EventID
- 8418
PWR8579
- Message
- Request to reset the CMC arg1 is initiated.
- Arguments
- arg1 = slot id
- Detailed Description
- A request to reset the CMC identified in the message is initiated. If a second CMC is present, a failover to the other CMC will occur as a result.
- Recommended Response Action
- No response action is required.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 3 (Informational)
PWR8580
- Message
- Chassis Management Controller is unable to turn on server- arg1 because the Chassis is not turned on.
- Arguments
- arg1 = slot number
- Detailed Description
- The power on request for the server identified in the message was not successful because the Chassis is turned off.
- Recommended Response Action
- Turn on the Chassis, and then retry the operation. To turn on the Chassis using the Chassis Management Controller Web UI, go to Chassis Overview > Power > Control, select the Power On System option, and then click Apply.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 3 (Informational)
PWR8581
- Message
- Chassis Management Controller is unable to turn on server- arg1 because another chassis power operation is in progress.
- Arguments
- arg1 = slot number
- Detailed Description
- A chassis power operation is currently in progress and the server identified in the message could not be turned on.
- Recommended Response Action
- Wait until the current chassis power operation is complete and the chassis is On and then retry the operation.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 3 (Informational)
PWR8582
- Message
- Chassis Management Controller is unable to turn on server- arg1 because Max Power Conservation Mode is enabled.
- Arguments
- arg1 = slot number
- Detailed Description
- Unable to turn on the server identified in the message because the Max Power Conservation Mode (MPCM) is enabled. After MPCM is enabled, the chassis will be in power conservation mode and the CMC cannot process any further server power on operation requests.
- Recommended Response Action
- Disable the Max Power Conservation Mode and retry the operation.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 3 (Informational)
PWR8583
- Message
- Chassis Management Controller is unable to turn on server- arg1 because unacknowledged 110V PSUs are present.
- Arguments
- arg1 = slot number
- Detailed Description
- To enable 110V operation, the Allow 110VAC Operation feature must be enabled. If the feature is not enabled, the server turn-on operation will not be processed.
- Recommended Response Action
- On the Power Configuration page, in the Web UI, select the Allow 110VAC Operation for power supplies and retry the operation. Using the RACADM utility, run the following command, "racadm config -g cfgChassisPower -o cfgChassisAllow110VACOperation 1".
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 3 (Informational)
PWR8584
- Message
- Chassis Management Controller is unable to turn on server- arg1 because the power supply redundancy is lost and Performance Over Power Redundancy feature is disabled and the power required is less than the available power.
- Arguments
- arg1 = slot number
- Detailed Description
- If power redundancy is lost and the server Performance Over Power Redundancy feature is disabled, the server turn-on will not be allowed.
- Recommended Response Action
- To enable the server to be turned-on, on the Power Configuration page in the Web UI, enable the server Performance Over Power Redundancy option . Using the RACADM utility, run the following command "racadm config -g cfgChassisPower -o cfgChassisPerformanceOverRedundancy 1". Then retry the operation.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 3 (Informational)
PWR8585
- Message
- Chassis Management Controller granted the power required to turn on server- arg1 .
- Arguments
- arg1 = slot number
- Detailed Description
- Chassis Management Controller granted the power required to turn on the server identified in the message.
- Recommended Response Action
- No response action is required.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 3 (Informational)
PWR8586
- Message
- Chassis Management Controller is unable to turn on server- arg1 because it is not supported in the VRTX chassis.
- Arguments
- arg1 = slot number
- Detailed Description
- The Chassis does not support the server identified in the message.
- Recommended Response Action
- The server inserted is not supported in the Chassis. Remove the server from the Chassis.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 3 (Informational)
PWR8587
- Message
- Chassis Management Controller is unable to turn on server- arg1 because the chassis enclosure is open.
- Arguments
- arg1 = slot number
- Detailed Description
- The server cannot be turned on if the chassis enclosure is open.
- Recommended Response Action
- The chassis enclosure is open. Retry the operation after closing the enclosure.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 3 (Informational)
PWR8588
- Message
- Chassis Management Controller is unable to turn on server- arg1 because a chassis infrastructure firmware update is in progress.
- Arguments
- arg1 = slot number
- Detailed Description
- The server identified in the message cannot be turned on while a chassis infrastructure firmware update operation is in progress.
- Recommended Response Action
- The chassis infrastructure firmware update is in progress. Retry the operation after the firmware update is complete.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 3 (Informational)
PWR8589
- Message
- The server- arg1 does not have PCIe Mezzanine card in slot B1.
- Arguments
- arg1 = slot number
- Detailed Description
- The PCIe Mezzanine card in the slot B1 is absent. Without PCIe Mezzannine cards, the chassis PCIe cards will not be available for servers.
- Recommended Response Action
- Insert a PCIe Mezzanine card in slot B1.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 3 (Informational)
PWR8590
- Message
- The server- arg1 does not have PCIe Mezzanine card in slot C1.
- Arguments
- arg1 = slot number
- Detailed Description
- The PCIe Mezzanine card in the slot C1 is absent. Without PCIe Mezzannine cards, the chassis PCIe cards will not be available for servers.
- Recommended Response Action
- Insert a PCIe Mezzanine card in slot C1.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 3 (Informational)
PWR8591
- Message
- Servers are turned off to allocate power to the newly inserted hard disk drives.
- Detailed Description
- Before inserting hard disk drives, always make sure the Chassis has enough available power. Otherwise operating servers may be turned off.
- Recommended Response Action
- Make sure there is enough power supply to distribute power. Go to, the Chassis Overview > Power > Power Budget Status. In the Total Input Power Available For Allocation field, view the available power. To add more power, insert more PSUs or remove unused components from the chassis.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 1 (Critical)
- Trap/EventID
- 8417
PWR8592
- Message
- Chassis Management Controller is unable to turn on or turn off the chassis because another chassis power operation is in progress.
- Detailed Description
- The request to turn on or turn off the chassis was issued before the previous power operation was completed.
- Recommended Response Action
- Retry the operation after the current operation is complete.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 3 (Informational)
- No alerts are applicable for this message
PWR8593
- Message
- Chassis Management Controller is unable to turn on or turn off the chassis because the chassis infrastructure component firmware update is in progress.
- Detailed Description
- The chassis power operation cannot be performed when a chassis infrastructure firmware update is in progress.
- Recommended Response Action
- Retry the operation after the chassis infrastructure component firmware update is complete.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 3 (Informational)
- No alerts are applicable for this message
PWR8594
- Message
- Chassis Management Controller is unable to set the Enhanced Cooling Mode because the requested power arg1 AC Watt is more than available power arg2 AC Watt.
- Arguments
- arg1 = requested watts, arg2 = available watts
- Detailed Description
- The available power is not sufficient to enable the Enhanced Cooling Mode feature.
- Recommended Response Action
- Make sure there is enough power supply to enable the Enhanced Cooling Mode feature. Go to, the Chassis Overview > Power > Power Budget Status. In the Total Input Power Available For Allocation field view the available power. To add more power, insert more PSUs or remove unused components from the chassis.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
- No alerts are applicable for this message
PWR8595
- Message
- Chassis Management Controller is unable to turn on server arg1 due to insufficient power for the arg2 .
- Arguments
- arg1 = slot id, arg2 = chassis component name
- Detailed Description
- The turn-on request for the server identified in the message did not succeed because of insufficient power to the chassis component identified in the message.
- Recommended Response Action
- The Chassis Management Controller (CMC) will retry turning on the server and the corresponding components associated to the server after a predefined interval. If the issue persists, refer to the Managing and Monitoring Power section in the CMC User Guide for more information on configuring power management settings.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
PWR8596
- Message
- Chassis Management Controller is unable to turn on server- arg1 because PSU redundancy is lost and the available power is insufficient.
- Arguments
- arg1 = slot number
- Detailed Description
- The Chassis Management Controller cannot turn on the server identified in the message, because PSU redundancy is lost or PSUs are removed. Sufficient power is not available for the operation.
- Recommended Response Action
- Make sure there is enough power supply to distribute power. Go to, the Chassis Overview > Power > Power Budget Status. In the Total Input Power Available For Allocation field, view the available power. To add more power, insert more PSUs or remove unused components from the chassis. When enough power is available, retry the operation.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
- No alerts are applicable for this message
PWR8597
- Message
- The Power Supply Unit (PSU) arg1 is turned off because it is not supported by the Chassis.
- Arguments
- arg1 = PSU number
- Detailed Description
- The identified Power Supply Unit (PSU) is turned off because it is not supported by the Chassis.
- Recommended Response Action
- Replace the PSU identified in the message with an appropriate unit, and then retry the operation. For a list of PSUs that are compatible, consult the system Owners Manual or contact your service provider.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 1 (Critical)
- Trap/EventID
- 8417
PWR8598
- Message
- The Power Supply Unit (PSU) arg1 is turned off because it is not compatible with the other PSUs used in the Chassis.
- Arguments
- arg1 = PSU number
- Detailed Description
- The Power Supply Unit (PSU) identified in the message is turned off because it is not compatible with the other PSUs in the Chassis.
- Recommended Response Action
- Replace the PSU with an appropriate unit, and then retry the operation. For a list of PSUs that are compatible, consult the system Owners Manual or contact your service provider.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 1 (Critical)
- Trap/EventID
- 8417
PWR8601
- Message
- The multinode sled power button is disabled.
- Detailed Description
- The power buttons for all multinode sleds in the chassis are disabled. The operation to disable the power button is only applicable to the multinode sleds available, and does not affect other servers in the chassis.
- Recommended Response Action
- To enable the chassis power button use the CMC RACADM command line interface (CLI) or CMC Web interface. At the CLI, enter "racadm config -g cfgChassisPower -o cfgChassisSledPowerButtonEnable 1". Using the Web interface, click Server Overview > Power > Control. Clear the Disable power button for all multinode sleds in the chassis" check box.
- Category
- Configuration (PWR = Power Usage)
- Severity
- Severity 3 (Informational)
PWR8602
- Message
- The multinode sled power button is enabled.
- Detailed Description
- The power buttons for all multinode sleds in the chassis are enabled. The operation to enable the power button is only applicable to the multinode sleds available, and does not affect other servers in the chassis.
- Recommended Response Action
- To disable the chassis power button use the CMC RACADM command line interface (CLI) or CMC Web interface. At the CLI, enter "racadm config -g cfgChassisPower -o cfgChassisSledPowerButtonEnable 0". Using the Web interface, click Server Overview > Power > Control. Select the "Disable power button for all multinode sleds in the chassis" check box.
- Category
- Configuration (PWR = Power Usage)
- Severity
- Severity 3 (Informational)
PWR8654
- Message
- Chassis Management Controller (CMC) is unable to send power allocation information to the component arg1 - arg2 .
- Arguments
- arg1 = component name, arg2 = component id
- Detailed Description
- CMC could not successfully send the power allocation information to the component identified in the message, because either iDRAC is stopped after the power allocation was sent by CMC or the communication between CMC and iDRAC has ended.
- Recommended Response Action
- Perform a Virtual Reseat operation of the component, and then retry the operation. To virtually reseat a component, log in to the CMC Web interface, select Chassis Overview > Troubleshooting > Reset Components > select the option corresponding to the component, and then click Virtual Reseat.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 1 (Critical)
PWR8655
- Message
- Chassis Management Controller (CMC) is unable to turn on the component arg1 - arg2 because of insufficient power. The minimum required power is arg3 AC Watts, but only arg4 AC Watts is available.
- Arguments
- arg1 = component name, arg2 = slot number, arg3 = min power, arg4 = available power
- Detailed Description
- CMC could not successfully turn on the component identified in the message, because of insufficient power available.
- Recommended Response Action
- Make sure there is sufficient power available, and then retry the operation. To view the available power, on the CMC Web interface, click Chassis Overview > Power > Power Budget Status. The available power is displayed in the Total Input Power Available For Allocation field. To increase available power, add more PSUs or remove unused components from the Chassis.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
- Trap/EventID
- 8418
PWR8656
- Message
- Chassis Management Controller (CMC) is unable to turn on the component arg1 - arg2 because of insufficient power.
- Arguments
- arg1 = component name, arg2 = slot number
- Detailed Description
- CMC could not successfully turn on the component identified in the message, because of insufficient power available.
- Recommended Response Action
- Make sure there is sufficient power available, and then retry the operation. To increase available power, add more PSUs, use PSUs with higher voltage inputs or a higher power rating, remove unused components from the Chassis, or change the redundancy policy to Redundancy Alerting Only or Non-redundant.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
- Trap/EventID
- 8418
PWR8663
- Message
- Unable to turn on the server arg1 because of an inconsistency between the I/O module and mezzanine card.
- Arguments
- arg1 = server number
- Detailed Description
- The server identified in the message could not be successfully turned on because of incompatibility between the I/O module and mezzanine card.
- Recommended Response Action
- Make sure that the I/O module and mezzanine card are compatible. For information about compatibility of hardware components, see the Modular System Chassis Hardware Manual.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 1 (Critical)
- Trap/EventID
- 8417
PWR8664
- Message
- The Dynamic Power Supply Engagement feature is arg1 .
- Arguments
- arg1 = enabled or disabled
- Detailed Description
- The power configuration property dynamic power supply engagement feature is disabled or enabled as identified in the message.
- Recommended Response Action
- No response action is required.
- Category
- Configuration (PWR = Power Usage)
- Severity
- Severity 3 (Informational)
PWR8665
- Message
- The Chassis power button is arg1 .
- Arguments
- arg1 = enabled or disabled
- Detailed Description
- The property chassis power button is either enabled or disabled as identified in the message.
- Recommended Response Action
- No response action is required.
- Category
- Configuration (PWR = Power Usage)
- Severity
- Severity 3 (Informational)
PWR8667
- Message
- Chassis Management Controller (CMC) is resetting iKVM to its default settings.
- Detailed Description
- Chassis Management Controller (CMC) is resetting iKVM to its default settings.
- Recommended Response Action
- No response action is required
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 3 (Informational)
PWR8668
- Message
- Chassis Management Controller (CMC) has initiated the process of resetting iKVM.
- Detailed Description
- Chassis Management Controller (CMC) has initiated the process of resetting iKVM.
- Recommended Response Action
- No response action is required.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 3 (Informational)
PWR8669
- Message
- Unable to turn on the server arg1 because of an inconsistency between the chassis and server components.
- Arguments
- arg1 = server number
- Detailed Description
- The server identified in the message could not be successfully turned on because of incompatibility between the chassis PCIe components and mezzanine card.
- Recommended Response Action
- Make sure that the chassis PCIe components and mezzanine card are compatible. For information about compatibility of hardware components, see the Modular System Chassis Hardware Manual available at the support site.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 1 (Critical)
- Trap/EventID
- 8417
PWR8670
- Message
- Unable to turn on server arg1 because the required power arg2 AC Watts exceeds the subsystem Connector Limit arg3 AC Watts for IO modules, Blowers and Servers.
- Arguments
- arg1 = slot ID, arg2 = power level, arg3 = power limit
- Detailed Description
- The server identified in the message cannot be turned on if the Connector Limit for the subsystems identified in the message is exceeded .
- Recommended Response Action
- Make sure the system operates within the subsystem Connector Limit for the components specified. To review power budget information select Chassis Overview -> Power -> Budget Status. Turn off unused components within the subsystem to make power available for the server to turn on or turn off low priority servers and try the operation again.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
- Trap/EventID
- 8418
PWR8671
- Message
- The Chassis Management Controller is unable to set the Enhanced Cooling Mode because the requested power arg1 AC Watts exceeds the subsystem power limit arg2 AC Watts for IO Modules, Blowers and Servers.
- Arguments
- arg1 = requested power level, arg2 = power limit
- Detailed Description
- The Enhanced Cooling Mode feature cannot be enabled because the requested power exceeds the Chassis subsystem power limit for IO Modules, Blowers and Servers.
- Recommended Response Action
- Make sure the system operates within the subsystem Connector Limit for the components specified. To review power budget information select Chassis Overview -> Power -> Budget Status. Turn off unused components within the subsystem to make power available to set Enhanced Cooling Mode.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 3 (Informational)
- Trap/EventID
- 8419
PWR8672
- Message
- The server in slot arg1 does not have a arg2 mezzanine card in slot arg3 .
- Arguments
- arg1 = server slot number, arg2 = card type, arg3 = mezzanine position number
- Detailed Description
- The server identified in the message does not have a card in the Mezzanine slot as identified in the message. A mezzanine card position is identified with the following numbers: For quarter-width server, the position number is 1. For half-width server mezzanine C & B maps to position numbers 1 & 2 respectively. For full-width server, mezzanine C & B on the upper- or left part of the server maps to position numbers 1 & 2 respectively. Mezzanine C & B on the lower- or right part of the server maps to position numbers 3 & 4 respectively.
- Recommended Response Action
- Insert a mezzanine card in the slot identified in the message.
- Category
- Configuration (PWR = Power Usage)
- Severity
- Severity 3 (Informational)
PWR8673
- Message
- arg1 hassis configuration detected at arg2 arg3 .
- Arguments
- arg1 = Carrier grade, arg2 = voltage, arg3 = power state
- Detailed Description
- Displays voltage change with power configuration change.
- Recommended Response Action
- No response action is required.
- Category
- Configuration (PWR = Power Usage)
- Severity
- Severity 3 (Informational)
PWR8674
- Message
- Unable to change the value of Allow 110 VAC Operation property because it is not supported in NEBS configuration PWR or PSU.
- Detailed Description
- Unable to change the value of the Allow 110 VAC Operation property because it is not supported in NEBS configuration PWR or PSU.
- Recommended Response Action
- No response action is required.
- Category
- System Health (PWR = Power Usage)
- Severity
- Severity 3 (Informational)
PWR8676
- Message
- Unable to set the chassis power property arg1 .
- Arguments
- arg1 = property name
- Detailed Description
- The chassis power property identified in the message cannot be set.
- Recommended Response Action
- Contact your service provider.
- Category
- Configuration (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
PWR8678
- Message
- The value of the property arg1 is arg2 .
- Arguments
- arg1 = power property name, arg2 = enable or disable
- Detailed Description
- The power property identified in the mesage is changed as identified in the message..
- Recommended Response Action
- No response action is required.
- Category
- Configuration (PWR = Power Usage)
- Severity
- Severity 3 (Informational)
PWR8680
- Message
- The arg1 firmware in the server slot arg2 does not support the storage sled.
- Arguments
- arg1 = iDRAC/BIOS, arg2 = slot number
- Detailed Description
- The firmware identified in the message does not support the storage sled.
- Recommended Response Action
- Update the firmware identified in the message to the supported latest available version. See the latest iDRAC User Guide for information on the versions that support the storage sled.
- Category
- System Health (PWR = Power Usage)
- Severity
- Severity 1 (Critical)
- Trap/EventID
- 2273
PWR8681
- Message
- The arg1 firmware in the server slot arg2 does not support additional PCIe slots.
- Arguments
- arg1 = iDRAC/BIOS, arg2 = slot number
- Detailed Description
- The firmware identified in the message does not support the PCIe reassignment operation.
- Recommended Response Action
- Update the firmware identified in the message to the supported latest available version. See the latest iDRAC User Guide for information on the versions that support the PCIe reassignment.
- Category
- System Health (PWR = Power Usage)
- Severity
- Severity 1 (Critical)
- Trap/EventID
- 2273
PWR8682
- Message
- Unable to turn on the storage sled controller arg1 in slot arg2 because the arg3 module is not functioning.
- Arguments
- arg1 = controller number, arg2 = slot number, arg3 = module name
- Detailed Description
- The Chassis Management Controller (CMC) is unable to turn on the storage sled controller identified in the message. The Chassis storage sled controller is unable to turn on due to a configuration or hardware issue.
- Recommended Response Action
- Remove the storage sled identified in the message, re-insert it and observe whether the issue is resolved. If the issue persists, contact your service provider.
- Category
- System Health (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
- Trap/EventID
- 2274
PWR8683
- Message
- Initiated the Virtual Reseat of peripheral arg1 .
- Arguments
- arg1 = slot number
- Detailed Description
- A Virtual Reseat for the peripheral sled identified in the message is initiated. A Virtual Reseat is the same as removing and inserting a peripheral sled.
- Recommended Response Action
- No response action is required.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 3 (Informational)
PWR8684
- Message
- Storage sled controller arg1 in slot arg2 turned on successfully.
- Arguments
- arg1 = controller number, arg2 = slot number
- Detailed Description
- The storage sled controller in the slot identified in the message turned on successfully.
- Recommended Response Action
- No response action is required.
- Category
- System Health (PWR = Power Usage)
- Severity
- Severity 3 (Informational)
PWR8685
- Message
- The arg1 firmware in the server slot arg2 supports the storage sled.
- Arguments
- arg1 = iDRAC/BIOS, arg2 = slot number
- Detailed Description
- The firmware identified in the message supports the storage sled.
- Recommended Response Action
- No response action is required.
- Category
- Audit (PWR = Power Usage)
- Severity
- Severity 3 (Informational)
- Trap/EventID
- 8419
PWR8686
- Message
- The Chassis Management Controller (CMC) is unable to turn on the storage sleds associated with server in slot arg1 because the iDRAC firmware version in the server does not support the chassis storage module.
- Arguments
- arg1 = slot number
- Detailed Description
- The Chassis Management Controller (CMC) is unable to turn on the storage sled controller identified in the message because iDRAC version installed on the server is not compatible.
- Recommended Response Action
- Update the the iDRAC firmware identified in the message to the supported latest available version and retry the operation. For information about the supported firmware versions, refer to the Chassis Management Controller users Guide available at the support site.
- Category
- System Health (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
- Trap/EventID
- 2274
PWR8687
- Message
- The Chassis Management Controller (CMC) is unable to turn on the storage sled controller installed on server in slot arg1 because the server does not have a Mezzanine card.
- Arguments
- arg1 = server slot
- Detailed Description
- The Chassis Management Controller (CMC) is unable to turn on the storage sled controller installed on the server in the slot identified in the message because the server does not have a Mezzanine card. A Mezzanine card position is identified with the following numbers: For quarter-width server, the position number is 1. For half-width server mezzanine C & B maps to position numbers 1 & 2 respectively. For full-width server, Mezzanine C & B on the upper- or left part of the server maps to position numbers 1 & 2 respectively. Mezzanine C & B on the lower- or right part of the server maps to position numbers 3 & 4 respectively.
- Recommended Response Action
- Install a Mezzanine card in the Mezzanine card slot of the server identified in the message, and then retry the operation.
- Category
- System Health (PWR = Power Usage)
- Severity
- Severity 2 (Warning)
- Trap/EventID
- 2274
평점(별 1~5개)을 매겨주십시오.
평점(별 1~5개)을 매겨주십시오.
평점(별 1~5개)을 매겨주십시오.
문서가 도움이 되었는지 여부를 선택하십시오.
의견에는 <>()\와 같은 특수 문자를 사용할 수 없습니다.