- 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
RDU Event Messages
RDU0001
RDU0002
- Message
- Fan redundancy is lost.
- Detailed Description
- One of more fans have failed or have been removed or a configuration change occurred which requires additional fans.
- Recommended Response Action
- Remove and re-install failed fans or install additional fans.
- Category
- System Health (RDU = Redundancy)
- Severity
- Severity 1 (Critical)
- Trap/EventID
- 2473
- LCD Message
- Fan redundancy is lost. Check fans.
RDU0003
- Message
- Fan redundancy is degraded.
- Detailed Description
- One of more fans have failed or have been removed or a configuration change occurred which requires additional fans.
- Recommended Response Action
- Remove and re-install failed fans or install additional fans.
- Category
- System Health (RDU = Redundancy)
- Severity
- Severity 2 (Warning)
- Trap/EventID
- 2474
- OMSA Event ID
- 5305
- OMSA Trap ID
- 5305
RDU0004
- Message
- The fans are not redundant.
- Detailed Description
- One of more fans have failed or have been removed or a configuration change occurred which requires additional fans.
- Recommended Response Action
- Remove and re-install failed fans or install additional fans.
- Category
- System Health (RDU = Redundancy)
- Severity
- Severity 3 (Informational)
- Trap/EventID
- 2475
RDU0005
- Message
- The fans are not redundant. Insufficient resources to maintain normal operations.
- Detailed Description
- One of more fans have failed or have been removed or a configuration change occurred which requires additional fans.
- Recommended Response Action
- Remove and re-install failed fans or install additional fans.
- Category
- System Health (RDU = Redundancy)
- Severity
- Severity 1 (Critical)
- Trap/EventID
- 2473
RDU0011
RDU0012
- Message
- Power supply redundancy is lost.
- Detailed Description
- The current power operational mode is non-redundant because of a power supply exception, a power supply inventory change, or a system power inventory change. The system was previously operating in a power redundant mode.
- Recommended Response Action
- Check the event log for power supply failures. Review system configuration and power consumption.
- Category
- System Health (RDU = Redundancy)
- Severity
- Severity 1 (Critical)
- Trap/EventID
- 2473
- LCD Message
- Lost PSU redundancy. Check PSU cables
- OMSA Event ID
- 5306
- OMSA Trap ID
- 5306
RDU0013
- Message
- Power supply redundancy is degraded.
- Detailed Description
- The current power operational mode is non-redundant because of a power supply exception, a power supply inventory change, or a system power inventory change. The system was previously operating in a power redundant mode.
- Recommended Response Action
- Check the event log for power supply failures. Review system configuration and power consumption.
- Category
- System Health (RDU = Redundancy)
- Severity
- Severity 2 (Warning)
- Trap/EventID
- 2474
- LCD Message
- PSU redundancy degraded. Check PSU cables
- OMSA Event ID
- 5305
- OMSA Trap ID
- 5305
RDU0014
- Message
- The power supplies are not redundant.
- Detailed Description
- The current power supply configuration does not meet the platform requirements to enable redundancy. If a power supply fails the system may shut down.
- Recommended Response Action
- If unintended, review system configuration and power consumption and install power supplies accordingly. Check power supply status for failures.
- Category
- System Health (RDU = Redundancy)
- Severity
- Severity 3 (Informational)
- Trap/EventID
- 2475
RDU0015
- Message
- The power supplies are not redundant. Insufficient resources to maintain normal operations.
- Detailed Description
- The system may power down or operate in a performance degraded state.
- Recommended Response Action
- Check the event log for power supply failures. Review system configuration and power consumption and upgrade or install power supplies accordingly.
- Category
- System Health (RDU = Redundancy)
- Severity
- Severity 1 (Critical)
- Trap/EventID
- 2473
- LCD Message
- PSUs are not redundant. Insufficient resources. Check PSU cables.
RDU0016
RDU0017
- Message
- The storage power redundancy is no longer available.
- Detailed Description
- The storage system has redundant power lines. One of power lines is no longer available.
- Recommended Response Action
- Turn system off and remove AC input power for one minute. Re-apply input power and turn system on. If the issue still persists, contact your service provider. Refer to the product documentation to choose a convenient contact method.
- Category
- System Health (RDU = Redundancy)
- Severity
- Severity 2 (Warning)
- Trap/EventID
- 2474
RDU0018
- Message
- The storage power redundancy is degraded.
- Detailed Description
- The storage system has multiple redundant power lines. One or more of these power lines is no longer available.
- Recommended Response Action
- Turn system off and remove AC input power for one minute. Re-apply input power and turn system on. If the issue still persists, contact your service provider. Refer to the product documentation to choose a convenient contact method.
- Category
- System Health (RDU = Redundancy)
- Severity
- Severity 2 (Warning)
- Trap/EventID
- 2474
RDU0019
RDU0021
- Message
- Unable to determine the redundancy status of the power supply units.
- Detailed Description
- One of the power supply units have failed.
- Recommended Response Action
- Replace the failed power supply with a new power supply.
- Category
- System Health (RDU = Redundancy)
- Severity
- Severity 2 (Warning)
- OMSA Event ID
- 5301
RDU0023
- Message
- Unable to determine the redundancy status of the fans.
- Detailed Description
- One or more fans are non-functional or may have failed.
- Recommended Response Action
- Check that all fans are working properly. Replace any non-fuctional fan with a new fan.
- Category
- System Health (RDU = Redundancy)
- Severity
- Severity 2 (Warning)
RDU0030
- Message
- The storage voltage of arg1 is redundant.
- Arguments
- arg1 = device name
- Detailed Description
- The storage voltage of the device identified in the message is redundant.
- Recommended Response Action
- No response action is required.
- Category
- System Health (RDU = Redundancy)
- Severity
- Severity 3 (Informational)
- Trap/EventID
- 2475
RDU0031
- Message
- The arg1 voltage redundancy is lost.
- Arguments
- arg1 = name
- Detailed Description
- The system has redundant voltage lines. One of voltage line is no longer available.
- Recommended Response Action
- 1) Turn system off and remove input power for one minute. Re-apply input power and turn system on. 2) If the issue still persists, contact technical support. Refer to the product documentation to choose a convenient contact method.
- Category
- System Health (RDU = Redundancy)
- Severity
- Severity 1 (Critical)
- Trap/EventID
- 2473
RDU0032
- Message
- The arg1 voltage redundancy is degraded.
- Arguments
- arg1 = name
- Detailed Description
- The system has multiple redundant voltage lines. One or more of these voltage lines is no longer available.
- Recommended Response Action
- 1) Turn system off and remove input power for one minute. Re-apply input power and turn system on. 2) If the issue still persists, contact technical support. Refer to the product documentation to choose a convenient contact method.
- Category
- System Health (RDU = Redundancy)
- Severity
- Severity 2 (Warning)
- Trap/EventID
- 2474
RDU0033
RDU8501
- Message
- CMC arg1 : waiting to be reset by other CMC
- Arguments
- arg1 = slot number
- Detailed Description
- The Active CMC has detected a problem or a low memory condition. It is waiting for the Standby CMC to reset the Active CMC.
- Recommended Response Action
- No response action is required.
- Category
- Audit (RDU = Redundancy)
- Severity
- Severity 3 (Informational)
RDU8502
- Message
- CMC arg1 cannot go standby since the other CMC is not present or healthy.
- Arguments
- arg1 = slot number
- Detailed Description
- For failover to occur, the standby CMC needs to be present, at the same version as the primary and healthy. During failover, the active CMC resets and the standby CMC becomes active. This message is logged when the standby CMC is absent, unhealthy or at a different firmware version.
- Recommended Response Action
- Check the status of the standby CMC and make sure the firmware version matches the primary CMC. Then reseat the CMC and retry the operation. If the issue persists, contact your service provider.
- Category
- Audit (RDU = Redundancy)
- Severity
- Severity 3 (Informational)
RDU8508
- Message
- CMC arg1 : cannot failover since the other CMC is non-functional.
- Arguments
- arg1 = slot number
- Detailed Description
- For failover to occur, the standby CMC needs to be present, at the same version as the primary and healthy. During failover, the active CMC resets and the standby CMC becomes active. This message is logged when the standby CMC is absent, unhealthy or at a different firmware version.
- Recommended Response Action
- Check the status of the standby CMC and make sure the firmware version matches the primary CMC. Then reseat the CMC and retry the operation. If the issue persists, contact your service provider.
- Category
- Audit (RDU = Redundancy)
- Severity
- Severity 3 (Informational)
RDU8509
- Message
- CMC arg1 : cannot failover, chassis is in non-redundant state
- Arguments
- arg1 = slot number
- Detailed Description
- For failover to occur, the standby CMC needs to be present, at the same version as the primary and healthy. During failover, the active CMC resets and the standby CMC becomes active. This message is logged when the standby CMC is absent, unhealthy or at a different firmware version.
- Recommended Response Action
- Check the status of the standby CMC and make sure the firmware version matches the primary CMC. Then reseat the CMC and retry the operation. If the issue persists, contact your service provider.
- Category
- Audit (RDU = Redundancy)
- Severity
- Severity 3 (Informational)
RDU8510
- Message
- CMC arg1 : cannot failover, CMC firmware versions are different
- Arguments
- arg1 = slot number
- Detailed Description
- For failover to occur, the standby CMC needs to be present, at the same version as the primary and healthy. During failover, the active CMC resets and the standby CMC becomes active. This message is logged when the standby CMC is absent, unhealthy or at a different firmware version.
- Recommended Response Action
- Check the status of the standby CMC and make sure the firmware version matches the primary CMC. Then reseat the CMC and retry the operation. If the issue persists, contact your service provider.
- Category
- Audit (RDU = Redundancy)
- Severity
- Severity 3 (Informational)
RDU8511
- Message
- Unable to failover, CMC arg1 in unknown state.
- Arguments
- arg1 = slot number
- Detailed Description
- For failover, the standby CMC needs to be present, at the same firmware version as the primary CMC and healthy. During failover, the active CMC resets and the standby CMC becomes active. This message is logged when the standby CMC does not meet this criteria
- Recommended Response Action
- Check the status of the standby CMC and make sure the firmware version matches the primary CMC. Then reseat the CMC and retry the operation. If the issue persists, contact your service provider.
- Category
- Audit (RDU = Redundancy)
- Severity
- Severity 3 (Informational)
RDU8512
- Message
- CMC arg1 : firmware versions are different [ arg2 arg3 : arg4 arg5 ]
- Arguments
- arg1 = slot number, arg2 = local fw version, arg3 = factory revision, arg4 = remote version, arg5 = factory revision
- Detailed Description
- The firmware versions of the Active CMC and the Standby CMC are different.
- Recommended Response Action
- Update the firmware so that the Active and Standby CMC firmware versions are the same.
- Category
- Audit (RDU = Redundancy)
- Severity
- Severity 3 (Informational)
RDU8513
- Message
- CMC arg1 : firmware versions are same arg2 arg3
- Arguments
- arg1 = slot number, arg2 = fw version, arg3 = factory revision
- Detailed Description
- The firmware version of Active CMC and Standby CMC are the same.
- Recommended Response Action
- No response action is required.
- Category
- Audit (RDU = Redundancy)
- Severity
- Severity 3 (Informational)
RDU8514
- Message
- CMC arg1 : cannot failover, firmware update is in progress.
- Arguments
- arg1 = slot number
- Detailed Description
- A failover operation has been requested, but a failover operation cannot be completed while CMC firmware update is in progress.
- Recommended Response Action
- No response action is required.
- Category
- Audit (RDU = Redundancy)
- Severity
- Severity 3 (Informational)
RDU8515
- Message
- CMC arg1 : failover was initiated by internal health monitoring process.
- Arguments
- arg1 = slot number
- Detailed Description
- A CMC failover was initiated by the CMC health monitoring process. There should be a reason listed in the chassis log.
- Recommended Response Action
- No response action is required.
- Category
- Audit (RDU = Redundancy)
- Severity
- Severity 3 (Informational)
RDU8516
- Message
- CMC arg1 : failover initiated by RACADM interface.
- Arguments
- arg1 = slot number
- Detailed Description
- A failover has been requested from the RACADM command line interface.
- Recommended Response Action
- No response action is required.
- Category
- Audit (RDU = Redundancy)
- Severity
- Severity 3 (Informational)
RDU8517
- Message
- CMC arg1 : no action allowed while firmware update is in progress
- Arguments
- arg1 = slot number
- Detailed Description
- No failover or other action can occur while a CMC firmware update is in progress.
- Recommended Response Action
- No response action is required. Wait until the firmware update is complete and retry the operation.
- Category
- Audit (RDU = Redundancy)
- Severity
- Severity 3 (Informational)
RDU8518
- Message
- CMC arg1 : active CMC arg2 requests Standby CMC to go active state.
- Arguments
- arg1 = slot number, arg2 = slot number
- Detailed Description
- The active CMC requests the Standby CMC to go active. If the user did not initiate this request, review the chassis log for the reason.
- Recommended Response Action
- No response action is required.
- Category
- Audit (RDU = Redundancy)
- Severity
- Severity 3 (Informational)
RDU8519
- Message
- Unable to communicate with peer CMC arg1 .
- Arguments
- arg1 = slot number
- Detailed Description
- The communication between the primary and standby CMCs was lost. This may occur when the CMC identified in the message is restarting, or a firmware update operation is in progress. If the issue persists, a failover will occur.
- Recommended Response Action
- Wait for 10 minutes for: 1)Firmware update operations to complete and 2) The CMC to finish restarting. If the communication is not reestablished, remove and reinsert the CMC.
- Category
- Audit (RDU = Redundancy)
- Severity
- Severity 3 (Informational)
RDU8520
- Message
- CMC arg1 : recovered from unhealthy state
- Arguments
- arg1 = slot number
- Detailed Description
- The standby CMC is recovered from unhealthy state by the monitoring daemon.
- Recommended Response Action
- No response action is required.
- Category
- Audit (RDU = Redundancy)
- Severity
- Severity 3 (Informational)
RDU8521
- Message
- CMC arg1 : active CMC has been removed
- Arguments
- arg1 = slot number
- Detailed Description
- The active CMC has been removed from the chassis. If standby CMC is present, it will become active.
- Recommended Response Action
- Reinstall the CMC that was removed.
- Category
- Audit (RDU = Redundancy)
- Severity
- Severity 3 (Informational)
RDU8522
- Message
- CMC arg1 : standby CMC arg2 became active
- Arguments
- arg1 = slot number, arg2 = slot number
- Detailed Description
- The standby CMC identified in the message became the active CMC.
- Recommended Response Action
- No response action is required.
- Category
- Audit (RDU = Redundancy)
- Severity
- Severity 3 (Informational)
RDU8523
- Message
- CMC arg1 : reset by peer CMC
- Arguments
- arg1 = slot number
- Detailed Description
- The CMCidentified in the message was reset by other CMC. This occurs during failover and CMC firmware update to the standby CMC.
- Recommended Response Action
- No response action is required.
- Category
- Audit (RDU = Redundancy)
- Severity
- Severity 3 (Informational)
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: <>()\