Skip to main content
Sign Out

Welcome to Dell

My Account
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.
Sign In Create an Account Dell Financial Services Premier Sign In Partner Program Sign In
Contact Us

Your Dell.com Carts

Dell Unity™ Family Unisphere® Command Line Interface User Guide

PDF

View event logs and alerts

The system monitors and reports on a variety of system events. It collects the events and writes them to the user log. The log contains a record for each event. Some log entries generate alerts. Alerts are usually events that require attention from the system administrator and typically indicate a system problem. For example, you might receive an alert telling you that a drive has faulted, or that the system is low on storage capacity.

In Unisphere, events appear as messages and alerts. The Unisphere CLI displays additional event attributes that provide more detailed event reports than what appears in Unisphere. Configure alert settings explains the commands for configuring alerts. The Unisphere online help provides more details on logs and alerts.

Each event record and alert is identified by an ID.

The following table lists the attributes for event records:

Table 1. Event record attributes
Attribute Description
Message ID ID of the event record.
Description Brief description of the event.
Severity Severity of the event. Valid values are:
  • info – Some event has occurred that does not have an impact on the functioning of the system.
  • notice – An important event has occurred that does not have an impact on the functioning of the system.
  • warning – An error has occurred that you should be aware of but has not had a significant impact on the system.
  • error – An error has occurred that has a minor impact on the system and should be remedied at some point but does not need to be fixed immediately.
  • critical – An error has occurred that has a significant impact on the system and should be remedied immediately.
Time Date and time when the event occurred, in Greenwich Mean Time (GMT).
Node Name of the SP that generated the event. Valid values are:
  • spa
  • spb
Process ID of the system process that generated the event.
Category Event category.
NOTE:After a successful login to the system, when you run a command through the CLI, events that include the category attribute with the authentication value will appear twice, as there are separate events for successful login and authentication.
Account User account of the user that caused the event. N/A appears if a user did not cause the event or the account is unavailable.
Component System component that caused the event. Intended for service personnel.
Product System product that caused the event. Intended for service personnel.
Table 2. Alert attributes
Attribute Description
ID ID of the alert.
Time Date and time (in GMT) when the alert occurred.
Message ID Alert message ID.
Message Alert message.
Description Description of a problem.
Severity Alert severity. Valid values are:
  • info – Some event has occurred that does not have an impact on the functioning of the system.
  • notice – An important event has occurred that does not have an impact on the functioning of the system.
  • warning – An error has occurred that you should be aware of but has not had a significant impact on the system.
  • error – An error has occurred that has a minor impact on the system and should be remedied at some point but does not need to be fixed immediately.
  • critical – An error has occurred that has a significant impact on the system and should be remedied immediately.
Acknowledged Indicates whether or not the alert was acknowledged. Valid values are:
  • yes
  • no
State Displays the alert state for each alert. Values are:
  • Active_Auto – Active alerts that will be automatically cleared once resolved.
  • Active_Manual – Active alerts that must be manually cleared using the /event/alert/hist deactivate command after being resolved.
  • Inactive – Alerts that are already resolved.
  • Updating – Alerts transitioning between the other states.
Duplications Indicates how many duplicate alerts occurred within three minutes of the initial alert. Displays 0 if there were no duplicate alerts.

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\