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 indicated FRU is the enclosure, set up a preventive maintenance window and power
cycle the enclosure at that time.
○ If these recommended actions do not resolve the issue, the indicated FRU has probably
failed and should be replaced.
● If the current sensor is outside critical threshold values:
○ Check that all modules in the enclosure are fully seated in their slots and that their
latches, if any, are locked.
○ 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 Enclosure Management Processor (EMP) reported an alert condition on a current sensor.
● A current sensor is outside the defined warning threshold values.
● A current sensor has been uninstalled.
Recommended actions:
● If a current sensor has exceeded the defined warning threshold values:
○ 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, the indicated FRU has probably failed and should be
replaced.
● If a current sensor has been uninstalled:
○ Check that the indicated FRU is in the indicated enclosure.
○ If the FRU is not in the enclosure, install the FRU immediately.
○ If the FRU is in the enclosure, ensure that the FRU is fully seated in its slot and that its
latches, if any, are locked.
○ 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.
Resolved A SES alert for a current sensor in the indicated enclosure has been resolved.
Recommended actions:
● No action is required.
558 Error An Enclosure Management Processor (EMP) reported an alert condition on a fan control module.
A fan module in the enclosure has failed.
Recommended actions:
● Replace the fan module.
Warning An Enclosure Management Processor (EMP) reported an alert condition on a fan control module.
The hot swap circuit in the indicated fan module has failed. The fan will continue to operate.
However, it is unsafe to remove this FRU while the enclosure is powered up.
Recommended actions:
● -Check that the indicated fan control module is in the indicated enclosure.
● If the fan control module is not in the enclosure, install a fan control module FRU
immediately.
● If the fan control module is in the enclosure, ensure that the fan control module is fully
seated in its slot and that its latch is locked. If the fan control module is fully seated and the
Fault/Service Required LEDs for the fan control module and for the enclosure are on, replace
the fan control module FRU immediately. If that does not resolve the problem, replace the
chassis FRU immediately.
● When the problem is resolved, an event with the same code will be logged with Resolved
severity.
Events and event messages 133