Table 65. Description of data fields for the event log (continued)
Data field Description
Object name The name of the object in the system to which the event relates.
Copy ID If the object is a volume and the event refers to a specific copy of the
volume, this field is the number of the copy to which the event relates.
Reporting node ID Typically identifies the node responsible for the object to which the
event relates. For events that relate to nodes, it identifies the node that
logged the event, which can be different from the node that is
identified by the object ID.
Reporting node
name
Typically identifies the node that contains the object to which the
event relates. For events that relate to nodes, it identifies the node that
logged the event, which can be different from the node that is
identified by the object name.
Fixed Where an alert is shown for an error or warning condition, it indicates
that the user marked the event as fixed, completed the fix procedure,
or that the condition was resolved automatically. For a message event,
this field can be used to acknowledge the message.
First time stamp The time when this error event was reported. If events of a similar
type are being coalesced together, so that one event log record
represents more than one event, this field is the time the first error
event was logged.
Last time stamp The time when the last instance of this error event was recorded into
this event log record.
Root sequence
number
If set, it is the sequence number of an event that represents an error
that probably caused this event to be reported. Resolve the root event
first.
Sense data Additional data that gives the details of the condition that caused the
event to be logged.
Event notifications
Storwize V7000 Unified can use Simple Network Management Protocol (SNMP)
traps, syslog messages, emails and Call Homes to notify you and IBM(r) Remote
Technical Support when significant events are detected. Any combination of these
notification methods can be used simultaneously. Notifications are normally sent
immediately after an event is raised. However, there are some events that might
occur because of service actions that are being performed. If a recommended
service action is active, these events are notified only if they are still unfixed when
the service action completes.
Only events recorded in the event log can be notified. Most CLI messages in
response to some CLI commands are not recorded in the event log so do not cause
an event notification.
Table 66 on page 229 describes the levels of event notifications.
228 Storwize V7000 Unified: Problem Determination Guide 2073-720
To Next Page
Loading...
Need help?
General
