The Alerts page, as shown in Figure 29, displays all system-generated alerts along with associated message information. Alerts are usually events that require attention from the user in some manner. Some alerts indicate that there is a problem or issue with the system, while others provide specific information, depending on the system status. For example, an alert might indicate that a drive has faulted, or a specific pool is out of space, which means some type of action would be needed to remedy the event. Alerts provide the user with information about the source of an event, the symptoms and cause, and actions to resolve it. Sometimes they include a Knowledge Base (KB) article link. If an alert is known or no longer relevant to the environment, the Alerts page provides a way to acknowledge alerts for book-keeping purposes as well as the ability to delete alerts as needed. Users can also configure Unisphere to send alert notifications to a specified email or SNMP trap using the Settings menu.
With Dell Unity OE 5.0 and later, all Alerts are assigned an alert State. The alert State can be used to determine which alerts are current, and which have been resolved. There are four States for alerts:
Updating: The current State of the alert is being updated (this State can only be seen when upgrading to OE 5.0 or later).
Inactive: The alert condition has been resolved.
Active_Auto: The alert is still Active and will be marked Inactive automatically when the condition is cleared.
Active_Manual: The alert is still Active, and a user will need to deactivate the alert to mark the alert Inactive when the condition is investigated or cleared.
Each alert is associated with a severity level, as defined in the following table:
Icon | Label | Indicates |
| Information | An event has occurred that does not impact system functions. No action is required. |
| Warning | An error has occurred that you should be aware of, but it does not have a significant impact on the system. For example, a component is working, but its performance may not be optimal. |
| Error | An error has occurred that has a minor impact on the system and should be remedied, but it does not have to be fixed immediately. For example, a component is failing and some or all its functions may be degraded or not working. |
| Critical | An error has occurred that has a significant impact on the system, and it should be remedied immediately. For example, a component is missing or has failed, and recovery may not be possible. |