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
Events and event messages
When an event occurs in a storage system, an event message is recorded in the system event log. Depending on the event
notification settings of the system, the event message can also be sent to users (using email) and host-based applications
(using SNMP or SMI-S).
NOTE: A best practice is to enable notifications to be sent for events having a severity Warning and higher.
Each event has a numeric code that identifies the type of event that occurred, and has one of the following severities:
● Critical: A failure occurred that might cause a controller to shut down. Correct the problem immediately.
● Error: A failure occurred that might affect data integrity or system stability. Correct the problem as soon as possible.
● Warning: A problem occurred that might affect system stability but not data integrity. Evaluate the problem and correct it if
necessary.
● Informational: A configuration or state change occurred, or a problem occurred that the system corrected. No immediate
action is required. In this document, this severity is abbreviated as “Info.”
● Resolved: The condition that caused an event to be logged has been resolved.
An event message might specify an associated error code or reason code, which provides additional detail for technical support.
Error codes and reason codes are outside the scope of this guide.
Topics:
• Event descriptions
• Events
• Removed events
• Events sent as indications to SMI-S clients
• Using the trust command
Event descriptions
This section describes the event messages that may be reported during system operation and specifies any actions
recommended in response to an event.
Depending on your system model and firmware version, some events described in this document may not apply to your system.
The event descriptions should be considered as explanations of events that you do see. They should not be considered as
descriptions of events that you should have seen but did not. In such cases those events probably do not apply to your system.
In this section:
● The term disk group refers to either a vdisk for linear storage or a virtual disk group for virtual storage.
● The term pool refers to either a single vdisk for linear storage or a virtual pool for virtual storage.
For a summary of storage events and corresponding SMI-S indications, see Events sent as indications to SMI-S clients on page
147.
4
Events and event messages 73