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-2391613.1
Update Date:2018-04-26
Keywords:

Solution Type  Technical Instruction Sure

Solution  2391613.1 :   SL8500 - How to Run Robot Diagnostics With Library Firmware Version 8.60 and Above  


Related Items
  • Sun StorageTek SL8500 Modular Library System
  •  
Related Categories
  • PLA-Support>Sun Systems>TAPE>Tape Hardware>SN-TP: SL3000-8500 Library
  •  




In this Document
Goal
Solution


Applies to:

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

Goal

Instructions step through running robot diagnostics on a SL8500 for a suspected defective robot.

Solution

Instructions as follows.

Pre-Requisites
For 8 and 4 bot libraries:
  a. You must be running Library microcode version 8.60 or higher with SLConsole version 6.70
  b. You must have either a Diagnostic cartridge ( DG ) or a Cleaning Cartridge ( CLN ) on the same side and rail as the bot you are going to test. The DG cartridge needs to be in one of the system cells. The Cleaning cartridge needs to be in a storage cell.
  c. Non-Disruptive Robot diagnostics can be run with the library online. Disruptive Robot diagnostics require the library to be in an offline state.
  d. You will not be able to run Robot Diagnostics on a robot that has failed to initialize.
  e. Once you have your cartridge positioned correctly bring up SLConsole. Under Tools select Diagnostics and open the Robot folder. You should see a screen like the one below

Robot Diagnostics Screen 1

  f. Check the Re-Init box if you would like the bot to perform a reboot after diagnostics have been run.

  g. Check the Allow Cleaning cartridge bot if a diagnostic cartridge is not available.

  h. Select the robot that you would like to run diagnostics on and the desired loop count.

  i. Click on the Run button in the top left.

  j. A successful robot diagnostic should look like the following example.

Robot Diagnostics Screen 2
Note:

a. You can increase the loop count to test for intermittent robotic issues.
b. Check the Allow Cleaning carts if you do not have diagnostic ( DG ) cartridge in the Library.
c. Disruptive test require the Library to be in an offline state.
d. Robot diagnostics can only be run on 1 robot at a time.

 If the robot diagnostic encounters a failure then open a SR against the library serial number.


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