IBM Flex System V7000 Storage Node 4939H49 User Manual
Product codes
4939H49
Chapter 13. Maintenance and Troubleshooting
553
Draft Document for Review January 29, 2013 12:52 pm
8068ch13-Maintenance and Troubleshooting.fm
3. If enabled, event notifications can be forwarded from a sender to a receiver through Call
Home email.
4. If Call Home is enabled, critical faults generate a problem management record (PMR) that
is sent directly to the appropriate IBM Support Center.
In general, events are classified as either alerts or messages:
��
An alert is logged when the event requires some action. Some alerts have an associated
error code that defines the service action that is required. The service actions are
automated through the fix procedures. If the alert does not have an error code, the alert
represents an unexpected change in state. This situation must be investigated to see if it is
expected or represents a failure. Investigate an alert and resolve it as soon as it is
reported.
error code that defines the service action that is required. The service actions are
automated through the fix procedures. If the alert does not have an error code, the alert
represents an unexpected change in state. This situation must be investigated to see if it is
expected or represents a failure. Investigate an alert and resolve it as soon as it is
reported.
��
A message is logged when a change that is expected is reported, for instance, an IBM
FlashCopy operation completes.
FlashCopy operation completes.
13.8.5 Viewing the event log
Follow the below procedure to view the event log.
On IBM Flex System V7000 Storage node
You can view the event log by using the IBM Flex System V7000 management GUI or the
command-line interface (CLI).
command-line interface (CLI).
You can view the event log by using the Monitoring
Events options in the management
GUI. The event log contains many entries. You can, however, select only the type of
information that you need.
information that you need.
You can also view the event log by using the command-line interface (lseventlog). See the
“Command-line interface” topic for the command details at the below link
“Command-line interface” topic for the command details at the below link
The event log has a limited size. After it is full, newer entries replace entries that are no longer
required. To avoid having a repeated event that fills the event log, some records in the event
log refer to multiple occurrences of the same event. When event log entries are coalesced in
this way, the time stamp of the first occurrence and the last occurrence of the problem is
saved in the log entry. A count of the number of times that the error condition has occurred is
also saved in the log entry. Other data refers to the last occurrence of the event.
required. To avoid having a repeated event that fills the event log, some records in the event
log refer to multiple occurrences of the same event. When event log entries are coalesced in
this way, the time stamp of the first occurrence and the last occurrence of the problem is
saved in the log entry. A count of the number of times that the error condition has occurred is
also saved in the log entry. Other data refers to the last occurrence of the event.
On IBM FSM
You can select an event filter to display a specific set of events for a selected resource, as
shown in Figure 13-26 on page 554 and Figure 13-27 on page 554. You can also select Event
Log Preferences to customize how many events to display.
shown in Figure 13-26 on page 554 and Figure 13-27 on page 554. You can also select Event
Log Preferences to customize how many events to display.