Owners Manual
Table Of Contents
- Dell EMC PowerVault ME4 Series Storage System Owner’s Manual
- Contents
- Storage system hardware
- Troubleshooting and problem solving
- Module removal and replacement
- ESD precautions
- Dealing with hardware faults
- Firmware updates
- Continuous operation during replacement
- Shutting down attached hosts
- Shutting down a controller module
- Verifying component failure
- Customer-replaceable units (CRUs)
- Attach or remove the front bezel of a 2U enclosure
- Replacing a drive carrier module in a 2U enclosure
- Replacing a DDIC in a 5U enclosure
- Replacing a controller module or IOM in a 2U or 5U enclosure
- Replacing a power supply unit (PSU) in a 5U enclosure
- Replacing a fan cooling module (FCM) in a 5U enclosure
- Replacing a power cooling module (PCM) in a 2U enclosure
- Completing the component installation process
- Verifying component operation
- Performing updates in PowerVault Manager after replacing an FC or SAS HBA
- Events and event messages
- Connecting to the CLI port using a serial cable
- Technical specifications
- Standards and regulations
Table 27. Event descriptions and recommended actions (continued)
Number Severity Description/Recommended actions
● If the PSU is not in the enclosure, install a PSU immediately.
● If the PSU is in the enclosure, ensure that the power supply is fully seated in its slot and that
its latch is locked.
● If none of these recommended actions resolves the issue, the indicated FRU has failed and
should be replaced.
When the problem is resolved, an event with the same code will be logged with Resolved
severity.
Resolved A SES alert for a power supply in the indicated enclosure has been resolved.
Recommended actions:
● No action is required.
552 Error An EMP reported an alert condition.
● A hardware failure has been detected and all fans in the indicated FRU have failed.
● The fan is unable to communicate with the EMP.
Recommended actions:
● If a hardware failure has been detected and all fans in the indicated FRU have failed.
○ Inspect the system health information to determine which FRU contains the affected
fans. Event 551 or 558 should give further information on the containing FRUs.
○ Replace the containing FRUs.
● If the fan is unable to communicate with the EMP.
○ Wait for at least 10 minutes and check if the error resolves.
○
If the error persists, check that all modules in the enclosure are fully seated in their slots
and that their latches, if any, are locked.
○ If this does not resolve the issue, note down the FRU. Ensure the partner FRU is not
degraded. If the partner FRU is degraded, contact technical support.
○ If the partner FRU is not degraded, remove and reinsert the indicated FRU.
○ If these recommended actions do not resolve the issue, the indicated FRU has probably
failed and should be replaced
When the problem is resolved, an event with the same code will be logged with Resolved
severity.
Warning An EMP reported one of the following:
● A fan in the indicated FRU has been uninstalled.
● A fan in the indicated FRU has failed and fan redundancy for the FRU has been lost.
Recommended actions:
● If a fan in the indicated FRU has been uninstalled:
○ Check that the indicated FRU is in the indicated enclosure.
○ If the FRU is not in the enclosure, install the appropriate FRU immediately.
○ If the FRU is in the enclosure, ensure that the FRU is fully seated in its slot and that its
latch is locked.
○ If these recommended actions do not resolve the issue, the indicated FRU has failed and
should be replaced.
● If a fan in the indicated FRU has failed and fan redundancy for the FRU has been lost:
○ The indicated FRU has failed and should be replaced.
When the problem is resolved, an event with the same code will be logged with Resolved
severity.
Resolved A SES alert for a fan in the indicated enclosure has been resolved.
Recommended actions:
● No action is required.
553 Error A temperature sensor reported an alert condition.
● A temperature sensor is outside critical temperature threshold in the indicated FRU.
● The temperature sensor is not able to communicate with the EMP.
Events and event messages 129