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
● Check for any obstructions to the airflow.
● Check that there is a module or blank plate in every module slot in the enclosure.
If the problem persists, replace the controller module that logged the error.
309 Info. Normally when the Management Controller (MC) is started, the IP settings are obtained from
the midplane FRU ID SEEPROM where it persists. If the system is unable to write it to the
SEEPROM the last time it changed, a flag is set in flash memory. This flag is checked during
startup, and if set, this event is logged and the IP data that is in the SEEPROM is used by the
controller module.
The IP settings of the Management Controller (MC) may be incorrect after a controller module
is swapped or the storage enclosure chassis is replaced.
● If a controller module is swapped, the IP settings in the flash memory of the replacement
controller module may be used.
● If the storage enclosure chassis is replaced, the IP settings are lost and they must be
reentered on both controller modules.
Recommended actions:
● No action is required.
310 Info. After a rescan, back-end discovery and initialization of data for at least one EMP (Enclosure
Management Processor) has completed. This event is not logged again when processing
completes for other EMPs in the system.
Recommended actions:
● No action is required.
311 Info. This event is logged when a user initiates a ping of a host using the iSCSI interface.
Recommended actions:
● If the ping operation failed, check connectivity between the storage system and the remote
host.
312 Info. This event is used by email messages and SNMP traps when testing notification settings. This
event is not recorded in the event log.
Recommended actions:
● No action is required.
313 Error The indicated controller module has failed. This event can be ignored for a single-controller
configuration.
Recommended actions:
● If this is a dual-controller system, replace the failed controller module. The module’s Fault/
Service Required LED will be illuminated (not blinking).
314 Error The indicated FRU has failed or is not operating correctly. This event follows some other FRU-
specific event indicating a problem.
Recommended actions:
● To determine whether the FRU needs to be replaced, see the topic about verifying
component failure in your product's Hardware Installation and Maintenance Guide.
315 Critical This IOM is incompatible with the enclosure in which it is inserted.
Recommended actions:
● Replace this IOM with an IOM that is compatible with this enclosure.
316 Warning The temporary license for a feature has expired.
Any components created with the feature remain accessible but new components cannot be
created.
Recommended actions:
Events and event messages 105