Quantum Scalar i6000 User Manual page 63

Table 3 Severity Levels
Assigned to Tickets
Severity Level
1 (Failed)
2 (Degraded)
Quantum Scalar i6000 User's Guide
cases, customer repair instructions are provided to isolate the issue and
recover from the failure. Only if the library is able to clearly identify a
failing CRU/FRU will the repair instruction request service or specific
CRU/FRU replacement.
Note: Tickets can indicate failures or other serious problems, but they
also can indicate warning conditions that you should
investigate. For example, opening the library's access door or
intentionally disconnecting drive fibre channel connections,
causes the library to create a ticket, but if such operation is
performed intentionally this condition would not indicate
serious problems. However, you should still investigate the
tickets to make sure no issue has been caused inadvertently by
an aisle access operation or SAN configuration.
The library assigns a severity level to each ticket that it creates, and it
notifies users of the ticket.
tickets.
Description
Indicates that a failure or serious condition has occurred within a library
subsystem that requires immediate corrective action. In some cases, a hardware
component is no longer functioning at an acceptable level or has failed. In other
cases an operation may not have completed without a component having actually
failed.
Examples of failure situations include a FRU that is not functioning, a temperature
threshold that may affect operations, or an Ethernet or FC connectivity issue that
requires resolutions to network or SAN fabric connectivity issues before operations
function normally again.
Indicates that a degraded condition exists within a library subsystem that impacts
system performance or redundancy. Typical library operations can continue
without immediate corrective action, but an administrator should investigate the
condition and correct the problem soon.
Examples of degraded situations include a redundant power supply that has failed
or a connectivity problem that has caused failover to occur.
Chapter 2: Troubleshooting Your Library
How Does the Library Report Issues?
Table 3 describes possible severity levels for
45