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-71-1474184.1
Update Date:2018-04-30
Keywords:

Solution Type  Technical Instruction Sure

Solution  1474184.1 :   SL150 - How to View the Library Health and Health Log (Healthlog.xls) for a StorageTek SL150 Modular Tape Library  


Related Items
  • StorageTek SL150 Modular Tape Library
  •  
Related Categories
  • PLA-Support>Sun Systems>TAPE>Tape Hardware>SN-TP: SL150 Library
  •  




In this Document
Goal
Solution


Applies to:

StorageTek SL150 Modular Tape Library - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Goal

How to View the Library Health and Health Log for a StorageTek SL150 Modular Tape Library.

Solution

If a SL150 library shows degraded on the front OP Panel or on the Web GUI or you simply want to see how a SL150 library has been running you can view the Library Health and the Health Log of the SL150 library.

To View the Library Health of a SL150 Library:

1. Log in as an admin user to the Web GUI of the SL150 library.

2. Click on Degraded up at the top of the page. 

This will cause a Library Health pop up window to appear.

In the Library Health pop up window you will see the fault/faults that have caused the library to be in a degraded state.  These faults consist of the following columns:

     1 .Date & Time - The time and date that the fault occurred.

     2. Fault Code - A code assigned to each individual fault.

     3. Fault Name - A description of the fault.

     4. Suspect Components - The suspect component/components that either caused the fault or are degraded as a result of the fault.

     5. Recommended Action - The recommended action given to try to fix the fault.

Note: The Library Health pop up window only contains the current fault/faults on the SL150 library and should always be provided when opening a Service Request from My Oracle Support.

 

To View the Health Log of a SL150 Library:

1. Log in as an admin user to the Web GUI of the SL150 library.

2. Click on Service from the main menu on the left hand side of the page.

3. Click on the Health Log tab.

This will show the Health Log for the SL150 library. 

The Health Log consists of the following columns:

     1. Type - Shows if an event is open (still causing a degraded state) or closed (fixed).

     2. ID - The Event ID for each event that has occurred and/or been closed.

     3. Date and Time - The time and date that a fault occurred.

     4. Fault Code - A code assigned to each individual fault.

     5. Fault Name - A description of the fault.

     6. Suspect Components - The suspect component/components that either caused the fault or are degraded as a result of the fault.

     7. Recommended Action - The recommended action given to try to fix the fault.

Note: The Health Log is a historical listing of the faults that have been taken by the components in a SL150 library and how the SL150 library has been running.

Note: The Library Health and the Health Log can also be viewed from the front Operators Panel on the SL150 library if the Web GUI isn't available.

 

Saving the Health Log to a File


If you need to work on diagnostics off-line or if you need to open a service request, save the contents of the system health log to a file. Proceed as follows:


Export the Health Log


1.Log in to the browser-based user interface under the Administrator or Service role.


2.Select Service from the menu on the left side of the interface. A set of tabbed property sheets appears.


3.Select the Health Log tab.


4.Select Export from the control bar at the top of the tab.


5.When the download dialog appears, save the file to disk.


The HTML-based SL150_HealthLog.xls file is compatible with current spreadsheet applications, such as Microsoft Excel 2010 and Apache OpenOffice Calc 3.4. You can also view these files in web browsers: simply rename the file using the .html file extension in place of .xsl.


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