Hardware manual

14–1
14 Group event logging
A PS Series group generates events when normal group operations occur and also when significant events occur.
Events enable you to track operations and also detect and solve problems before they affect performance or data
availability.
In addition, you can use SNMP traps to tr
ack significant group events.
About event messages
When an event occurs in the group (for example, you create a volume or a power supply fails), the group generates
an event message.
Event messages help you monitor normal operat
ions and also identify problems before they disrupt service.
Events appear in the Monitoring window, the CLI console, an
d in the output of the show recentevents
command.
Note: You can disable the display of informational messages in the GUI and
CLI; however, the group still logs
these events. See Enabling or disabling the display of INFO event messages on pa
ge 14-5.
Examples of event messages seen on the console are:
484:2:gigan34mem1:netmgtd:15-Mar-2010 11:25:04.310003:rcc_util.c:714:INFO:25.2.9:CLI: Login
to account grpadmin succeeded
.
10:5:gigan34mem1:SP:13-Mar-2010 22:30:19.250006:emm.c:1922:WARNING:28.3.51:Warning health
conditions currently exist. Correct these conditions before they affect array operation
.
Control modules are initializing. Control module failover cannot occur until the
initialization completes
.
There are 1 outstanding health conditions. Correct these conditions before they affect array
operation
.
Each event message includes the following information:
• Event priority: INFO, WARNING, ERROR, or FATAL (see Event priorities on pa
ge 14-2)
• Date and time that the event occurred
• Member on which the event occurred
• Descriptive event text
In addition, the group generates hardware alarms. An alarm is
a
persistent condition in an array (for example, high
temperature). Alarms help you find and correct problems before they disrupt operations. An alarm always has a
corresponding event. See About hardware alarms on
page 14-2.