Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-79-1933727.1
Update Date:2017-08-16
Keywords:

Solution Type  Predictive Self-Healing Sure

Solution  1933727.1 :   SL500/SL3000/SL8500 – How to Collect Information Using SL Console  


Related Items
  • StorageTek Library Console
  •  
  • Sun StorageTek SL3000 Modular Library System
  •  
  • Sun StorageTek SL500 Modular Library System
  •  
  • Sun StorageTek SL8500 Modular Library System
  •  
Related Categories
  • PLA-Support>Sun Systems>TAPE>Tape Hardware>SN-TP: SL500 Library
  •  
  • Tools>Type>Data Collector
  •  


This document lists outputs usually requested at the start of diagnosing a Service Request and should be used as a starting point for obtaining and providing outputs for all SL Console-managed libraries (SL500, SL3000 and SL8500).

In this Document
Purpose
Scope
Details
 Library event logs
 Overview of library components
References


Applies to:

Sun StorageTek SL3000 Modular Library System - Version All Versions to All Versions [Release All Releases]
Sun StorageTek SL500 Modular Library System - Version All Versions to All Versions [Release All Releases]
Sun StorageTek SL8500 Modular Library System - Version All Versions to All Versions [Release All Releases]
StorageTek Library Console - Version 3.0 and later
Information in this document applies to any platform.

Purpose

Collecting relevant and useful information in SL Console. This is a starting point in collecting outputs and other information or outputs may be requested.

Scope

This guide is applicable to all users and administrators of Oracle Storagetek tape libraries managed with SL Console.

The document assumes you have downloaded and installed SL Console on your computer or that you are using a remote SL Console session installed on a server.  It also assumes that you have network access to the library and admin credentials were set up.
- If you do not have SL Console, please see document ID 1511569.1 for information how to obtain SLC.
- If you do not have network access to the library or if you do not have admin credentials set up, please open a Service Request to have this sorted out.

Details

Note: (Apr-2016) "Consider SDP2 installation as easy way to automatically send logs etc." Refer to following KB for "SDP2 Introduction", article https://support.oracle.com/epmos/faces/DocumentDisplay?id=1942540.1

Cross reference to KB 1377490.1

SL500/SL3000/SL8500 - Procedure for Collecting One Button Log Snapshot From Library (Doc ID 1377490.1)

Log in to SL Console using admin credentials.

Library event logs

1. When collecting library logs, a Log SnapShot is always preferred. If you are running recent firmware and current SL Console version, the log snapshot can be gathered very easily.

Minimum requirements for one-click snapshot:
SL8500 code FRS_7.05, SLC FRS_5.53
SL3000 code FRS_3.50, SLC FRS_5.60
SL500 code 1466, SLC FRS_5.60


If your library and SLC combination satisfy the requirements above, follow these steps in SL Console to obtain a log snapshot:
Go to Tools → Diagnostics → Library folder.
Go to TransferFile tab, select All Devices (should be selected by default).
Click 'Generate Log Snapshot On Library', confirm with 'OK'.
Once the log snapshot is generated, you have 15 minutes to save it by clicking 'Transfer Log Snapshot To Your Computer'.
The log snapshot is encrypted and must be sent to Oracle support for analysis.

2. If you are unable to gather the log snapshot, please gather the log using SL Console:
- Tools → Reports → Log → Event Log : Error, Warn, Info
Once the log has been generated, click "Save" if you are running a local copy of SL Console. If you are running SLC remotely, you may prefer to copy and paste the contents of the window. This also applies to outputs requested in next steps.

Overview of library components

3. Please collect the following outputs for an overview of library components:
- Tools → Reports → Status Summary → Library Information (not Library Details, please)
- Tools → Reports → Status Detail → Robot Details
- Tools → Reports → Status Detail → Drive Details
It is good practice to collect both Robot and Drive details, even if your issue does not seem to concern either or both of these, as some issues may not be immediately obvious.

4. If supplying logs for diagnosing media or read/write errors you noticed on the drive, please include the following outputs:
- Tools → Reports → Statistics → Drive Media Events
- Tools → Reports → Statistics → Drive Events
- Tools → Reports → Statistics → Media Events

Note: The last two outputs are only available on SL3000 and SL8500 libraries. Do not be alarmed that they are not present in your SL500 library.
It may be possible that the library did not capture any media and/or drive events. In such a case, you may receive an "Open report file failed" error message. This does not mean that there are no such events, only that the library did not receive them from its drives.

Other outputs that can be obtained in Tools → Reports are not usually needed unless your issue is specific to the pertinent part, therefore there is no need to spend additional time collecting these outputs.

Note: This KB is a replacement for SL500/SL8500/SL3000 - How to Collect Data Information for Drive/Media Error Using SL Console (Doc ID 1563844.1) that has been deleted.

References

<NOTE:1511569.1> - SL500/SL3000/SL8500 - How to Download the SLConsole (SLC)
<NOTE:1307534.1> - SL3000/SL8500 - How to Collect Log Snapshot From SL8500 or SL3000 Library

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback