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
● Because the remote pool volume limit was reached.
● Because of an unknown reason.
A replication operation cannot complete because it needs to create a proxy volume and a
replication snapshot in the secondary pool, but the maximum number of volumes exists for that
pool or its owning controller and the pool contains no suitable snapshot to automatically delete.
This event is logged in the secondary volume's system only.
Recommended actions:
● To enable the replication operation to continue, delete at least one unneeded volume from
the destination pool or from another pool owned by the same controller. After performing the
above action, if the replication fails for the same reason and becomes suspended, events 431
and 418 will be logged. Repeat the above action and resume the replication.
● To allow additional volumes to be created in the future (standard volumes, replication
volumes, or snapshots), delete any unneeded volumes.
419 Info. A request to add a secondary volume started.
Recommended actions:
● No action is required.
420 Error A request to add a secondary volume failed.
This can occur for several reasons, such as:
● The volume is already a replication volume.
● The volume is not local to the system.
● The communication link is busy or experienced an error.
● The volume is not the same size as the existing volume or is no longer in the set.
● The volume record is not up to date.
● Replication is not licensed or the license limit would be exceeded.
Recommended actions:
● If any of the above problems exist, resolve them. Then repeat the add operation with a valid
volume.
421 Info. A request to add a secondary volume completed successfully.
Recommended actions:
● No action is required.
422 Info. A request to remove a secondary volume completed successfully.
Recommended actions:
● No action is required.
423 Error A request to remove a secondary volume failed.
This can occur for several reasons, such as:
● The volume record is not found.
● The volume record is not yet available.
● A primary volume conflict exists.
● You cannot delete the volume from a remote system.
● You cannot remove the volume because it is the primary volume.
Recommended actions:
● If any of the above problems exist, resolve them. Then repeat the remove operation with a
valid volume.
424 Info. A request to modify a secondary volume completed successfully.
Recommended actions:
● No action is required.
110 Events and event messages