logged for many different storage system activities, and the event logs can be viewed by category using different
access methods. These complimentary notification subsystems are further described herein.
Alerts
You can view information about alerts using either the SMU or the CLI. Using the SMU, you can access the Alerts panel
from the system Dashboard to view the scrollable list of alerts. This panel allows you to drill down to acknowledge and
resolve alerts. The Alerts panel allows for compact or expanded views with tables showing the status of active alerts and
alert history. Using the CLI, you can run the
show alerts
command (with additional parameters to filter the output) to
see detail for a storage system component. You can also run the
show alert-condition-history
CLI command to
view a log history of alert conditions that have generated alerts.
Events
If a message tells you to check whether an event has been logged, or to view information about an event in the log, you
can do so using either the SMU or the CLI. Using the SMU, you can view the event log and then click on the event
message to see detail about that event. Using the CLI, you can run the
show events detail
command (with
additional parameters to filter the output) to see the detail for an event.
Typical log data that can be written to a compressed file on the network include device status summary, the event log
from each controller, the debug log from each controller, the boot log from each controller, and critical error dumps from
each controller, if critical errors have occurred. Alternative methods for obtaining log data are to use the Collect Logs
action (Maintenance > Support) in the SMU or the
get logs
command in the FTP or SFTP interface. These methods
transfer the entire contents of a log file without changing its capacity-status level. Use of Collect Logs or
get logs
is
expected as part of providing information for a technical support request.
Use the SMU
The SMU's Dashboard provides access to an Alerts panel listing current issues you should be aware of. You can
acknowledge alerts and determine how to resolve them. Once an alert is acknowledged and resolved, it is removed from
the scrollable list.
The SMU uses health icons to show OK, Degraded, Fault, or Unknown status for the system and its components. The
SMU enables you to monitor the health of the system and its components. If any component has a problem, the system
health will be Degraded, Fault, or Unknown. Use the SMU to drill down to find each component that has a problem, and
follow actions in the Recommendation field for the component to resolve the problem.
Use the CLI
As an alternative to using the SMU, you can run the
show system
command in the CLI to view the health of the
system and its components. If any component has a problem, the system health will be Degraded, Fault, or Unknown,
and those components will be listed as Unhealthy Components. Follow the recommended actions in the component
Health Recommendation field to resolve the problem.
View the enclosure LEDs
You can view the LEDs on the hardware (while referring to
for your enclosure model) to
identify component status. If a problem prevents access to either the SMU or the CLI, this is the only option available.
However, monitoring/management is often done using the SMU interface rather than relying on line-of-sight to LEDs
of racked hardware components.
Performing basic steps
You can use any of the available options in performing the basic steps comprising the fault isolation methodology.
Gather fault information
When a fault occurs, it is important to gather as much information as possible. Doing so will help you determine the
correct action needed to remedy the fault.
Begin by reviewing the reported fault:
48
Chapter 7
Troubleshooting