Skip Headers

StorageTek SL3000 User's Guide E20875-05 |
| Contents | Index

Previous | Next |

# 12 SLConsole Diagnostics and Utilities

The SLConsole enables you to perform many diagnostic tasks, including library self-tests, monitoring events, and device diagnostics.

- "Library and Device Self-Tests"

- "Diagnostic Support Information"

- "Troubleshooting"

- "Library Events"

- "Create an Event Monitor"

- "Display Device Status or Result Code"

For information on using SLConsole diagnostic tools not described in this chapter, see:

- "Import/Export Diagnostic Cartridges"

- "Robot Diagnostic Moves"

## Library and Device Self-Tests

Self-tests can help diagnose issues with the library or devices. Refer to:

- "Perform a Library Self-Test"

- "Perform CAP Self-Test"

- "Perform a Drive Self-Test"

- "Perform a Robot Self-Test"

## Diagnostic Support Information

The following diagnostic tools aid in troubleshooting. Your Oracle support representative may request that you capture and transfer these files.

- Management Information Base (MIB) file - an SNMP database used to manage your library devices. This file can be saved as a text file. See "Transfer the Library MIB File".

- Log Snapshot file - an encrypted snapshot of the library event log. You cannot view or edit this file. This file is available for only 15 minutes from the time it is generated. See "Generate and Transfer the Library Log Snapshot File".

- Device Reserve Table - a table displaying device information and status. See "Library Reports".

- Event monitors - spool of events that captures error data. See "Create an Event Monitor".

## Troubleshooting

Before you run diagnostic tests, check the following areas of the library by using the following troubleshooting tips.

Service Required (amber) LED is constantly on

  Use SLConsole to check the health of the library and the attached devices (drives, CAPs, and robots). See Chapter 6, "Library Management" for more details.

  To perform a health check:

  1. Log in to the SLConsole.

  2. Access the System Detail module, View > System Detail.

  3. Check the navigation tree for the following indicators: Device Healthy or Device Error

  Additional checks:

  1. Check the Status (for example, online/offline) and Statistics (for example, uptime, downtime, errors and warnings) tabs for more information on the health of the library and devices.

  2. Make sure the cartridges are fully seated and properly oriented in their storage cells.

  3. Inspect the X table for any foreign objects or debris and remove them if found.

Library does not power-on and SLConsole does not display any messages

  1. Check that the library power switch is in the ON position.

  2. Check all power cord connections.

  3. Replace the power cord.

  4. Make sure that there is power to the outlet.

CAP Open LED is on and blinking

  Open the CAP and make sure the cartridges in the CAP cells are properly seated. Close the CAP.

SLConsole does not display modified data or information remains static

  Check the SLConsole Heartbeat icon.

Robot Fault or Library Fault Amber LED is constantly on

  1. Check the SLConsole for any displayed error messages. Write down the error messages reported.

  2. Open the front door. Observe and note the state of the cartridges, hand, and tape drives.

  3. Make sure cartridges are fully seated and properly oriented in their storage cells.

  4. Make sure packing materials have been removed.

  5. Inspect the library floor for any objects or debris. If there are any, remove them.

  6. Check the status of the tape drives.

  7. Close the front door.

  8. Make sure the tape drives are fully seated and locked forward by pushing and pulling on the rear of the drive tray. Any motion of the tray indicates that it requires re-seating and locking down.

Client computer cannot communicate with the library or tape drives

  Make sure cables are securely attached to their connectors on the rear of the library, the tape drives, and the client computer.

Library is unable to communicate with the drives and drive status on the SLConsole displays "Not communicating"

  Make sure cables are securely attached to their connectors on the rear of the library, the drives, and the client computer.

Repeated or excessive drive cleaning or cleaning messages

  1. Replace the cleaning cartridge with a new cleaning cartridge.

  2. Run the Library Self-Test and note if errors are reported for the drive.

  3. Run any client computer-based drive diagnostic tests.

## Library Events

The library controller continually monitors library operations and logs all events. Using SLConsole, you can spool event data to a file (see "Create an Event Monitor")

### Event Monitors

The system stores event monitors under the following three headings:

- Communication events: Includes host-to-library, library-to-library, and library-to-drive communications.

- Error event: Each error event is assigned a four-digit (hexadecimal) action code.

- Warning events: Indicate a loss of performance or conditions that may be indicative of future fatal errors.

The following information can help you diagnose the cause of the event:

- Date/time stamp: Identifies when the event occurred.

- Action codes: Identifies the command that was issued, such as "load drive".

- Result codes: Identify the result of the requested action.

- Known service plan diagnosis: Identifies the mechanism or component responsible for the task or fault.

### Event Codes Reference

The following tables list the event types, descriptions, and their respective codes.

#### Activity Code

Activity associated with the event. For example, HLI host mount, diagnostic fetch, robot communication diagnostic

Valid Code | Description
--- | ---
0000 | no action /no activity
0100 - 0199 | common/shared activity (across devices and the controller)
0200–0299 | common/shared activity (across devices - robot, drive, PTP, and so on)
0400–0499 | common/shared configuration activity
1000–1999 | host interface activity
2000–2999 | management interface activity
3000–3999 | internal server/library activity
4000–4999 | partner library-initiated activity
5000–5999 | robot activity
6000–6999 | drive activity
7000–7999 | CAP activity
8000–8999 | elevator activity
9000–9999 | PTP activity

#### Result Code

Reason for the activity. For example: Activity: HLI host mount, Result: robot X cartridge fetch failure.

Valid Code | Description
--- | ---
0000 | no problem /normal
0100–0199 | common/shared results (across devices and the controller)
1000–1999 | host interface results
2000–2999 | management interface results
3000–3999 | internal server/library controller results
4000–4999 | partner library interface results
5000–5999 | robot results
6000–6999 | drive results
7000–7999 | CAP results
8000–8999 | elevator activity
9000–9999 | PTP activity

#### Severity

Identifies the significance of the event from the perspective of the activity associated with the event. The severity levels also identify log activity that must persist across system power cycles from that which might be considered volatile.

Valid Codes:

Error (1): Indicates a fault occurred which prevented a request (host or diagnostic) from completing successfully. Error data is non-volatile and accumulates across system power cycles.

Warning (2): Indicates a fault occurred, but the fault has not stopped the library's ability to complete requests (host or diagnostic). Warning data is non-volatile and accumulates across system power cycles.

Information (3): Indicates data that is not significant, but may be important to establish a history of activity around a severity 1 or 2 event. Information data is volatile.

Configuration (4): Indicates change in the library's configuration. This includes the addition and removal of drives, robots, controllers, and interface cards. This also includes changes to the software configuration. Configuration data are non-volatile resources and accumulate across system power cycles.

Diagnostic (5): Records normal diagnostic activity tracing. This is independent of the debug or trace activity when a diagnostic activity affects the availability of drives or other devices to host operations. Diagnostic data is volatile.

#### Request Identifier

Identifies all host interface requests. Helps track the sequence of log activity resulting from each host request.

## Create an Event Monitor

Event monitors are useful tools for root cause analysis of errors. Open an event monitor and spool all events to a file to capture the error data, then send the file to your Oracle support representative for analysis. See "Event Codes Reference" for a listing of event types and codes.

### Display an Event Monitor

1. Select Tools > Monitors.

2. Expand the Permanent Monitors folder in the navigation tree.

3. Click an event monitor type. Click Open.

4. Use the Monitor menu to pause, resume, permanently stop, or clear the event monitor.

5. To close a monitor, click the X in the upper right corner of the window.

### Spool Event Monitor Data to a File

Use this procedure to spool and save event monitor data to a file. You can send the file to your Oracle support representative to assist in diagnosing problems.

1. Select Tools > Monitors.

2. Expand the Permanent Monitors folder in the navigation tree.

3. Select an event monitor. Click Open.

4. In the event monitor window, select Spool File > Start Spooling.

5. Browse to the desired directory, enter the file name, and click Save.

6. To stop spooling, select Monitor > Stop Spooling.

### Display Multiple Monitors

You can open and manage multiple event monitors using the Window menu:

Table 12-1 Controls for Displaying Multiple Monitors

To | Select
--- | ---
Custom arrange the open monitors on screen | Window > Arrange
Arrange the event monitor windows horizontally | Window > Tile Horizontal
Arrange the event monitor windows vertically | Window > Tile Vertical
Stack the event monitors | Window > Cascade

## Display Device Status or Result Code

1. Select Tools > Diagnostics.

2. Click the Library folder in the navigation tree.

3. Click the Search tab.

4. In the Search Type list, select either:

   - Device Status — device status codes and their descriptions

   - Result Code — result codes and their descriptions

5. Complete the remaining fields:

   1. To search for a specific device status code, enter the complete code. Wildcards or partial codes are not accepted.

   2. To list all device status codes, select List All.

6. Click Search.