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-1473774.1
Update Date:2017-06-28
Keywords:

Solution Type  Technical Instruction Sure

Solution  1473774.1 :   SL150 - How to Remove/Replace the Robot CRU in a StorageTek SL150 Modular Tape Library [VCAP]  


Related Items
  • StorageTek SL150 Modular Tape Library
  •  
Related Categories
  • PLA-Support>Sun Systems>Sun_Other>Sun Collections>SN-OTH: TAPE-CAP VCAP
  •  
  • Microlearning>Video>ML-VID-VCAP
  •  




In this Document
Goal
Solution
References


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

A video presentation on how to Remove/Replace the Robot CRU in a StorageTek SL150 Modular Tape Library

Solution

 DISPATCH INSTRUCTIONS
   WHAT SKILLS ARE REQUIRED?: No special skills required, Customer Replaceable Unit (CRU) procedure
   TIME ESTIMATE: 90 minutes
   TASK COMPLEXITY: 0 (low complexity)

REMOVAL/REPLACEMENT INSTRUCTIONS:
   PROBLEM OVERVIEW: How to Remove/Replace the Robot CRU in a StorageTek SL150 Modular Tape Library
   WHAT STATE SHOULD THE SYSTEM BE IN TO BE READY TO PERFORM THE RESOLUTION ACTIVITY?: The SL150 library must be put into an offline state from the Web GUI.
   WHAT ACTIONS ARE REQUIRED?:

 

To Remove the Robot:

Caution:

The robot, front control panel, and base module chassis (the KLM card FRU would be the same as the base module chassis) are critical to maintaining the product serial number and customer settings. When a replacement is needed for any of these CRUs, you may only replace one CRU during a single power-down cycle.

Caution:

If you receive a SL150 NUC/KLP robot of P/N 7311556, 7311557, 7301827, or higher then you cannot downgrade the firmware below 2.50 because the SL150 will not boot up due to the older firmware not supporting the new NUC and KLP hardware.

 

1.Power off the library with the option enabled to prepare the robot for removal.  If the Web GUI is not available please see the How to Park the Robot Manually procedure at the bottom of this document.

Note: It is critical for the robot to be parked and latched before attempting to remove the robot CRU.

2.Reposition the robot lock. 

  • If the robot lock is the knewer knob style grasp the knob and turn it counterclockwise until the pointer is past the red, locked padlock icon.
  • If the robot lock is the type with a thumb screw, loosen the thumbscrew, remove the mechanism, rotate the mechanism 180 degrees, insert the mechanism, and tighten the thumbscrew.

Note: Make sure the locked padlock icon is visible.

3.Make sure to identify each Ethernet port and its attached cable (label the cable if necessary).

Note: The Ethernet ports might be connected to different networks. A USB cable can be connected to any port so it is not necessary to label this type of cable.

4.Remove the robot:
   a.Disconnect all cables attached to the robot module (Ethernet and module expansion).
   b.Loosen the robot module thumbscrews.
   c.Grasp the robot module thumbscrews and pull the robot approximately ten inches out of the base module.
   d.Reposition your hands near the center of the extended robot

Caution: The robot CRU weighs approximately 5 kg (11 pounds) and is long which makes it difficult to handle.

To Replace the Robot:

1.Remove the replacement robot from its packaging, and set it on an anti-static surface.
2.Grasp the robot near the center with the thumbscrews and cable jacks facing you.
3.Insert the robot into the base module aligning the tabs on the robot with the channels in the base module chassis.
4.Push the robot fully into the module.
5.Tighten the thumbscrews.

6.Reset the robot lock

  • If the robot lock is the newer knob style grasp the knob and turn it clockwise until the pointer is past the black, unlocked padlock icon.
  • If the robot lock is the type with a thumb screw, loosen the thumbscrew, remove the mechanism, rotate the mechanism 180 degrees, insert the mechanism, and tighten the thumbscrew.

Note: Make sure the unlocked padlock icon is visible.

7.Plug the expansion cable for each module into the base module connectors (a cable can be connected to any available connector).
8.Plug the Ethernet cables into the appropriate Net Mgt port.
9.Power on the SL150 library from the power button on the front of the SL150 library.


How to Park the Robot Manually:

1.Remove the top tape drive from the base module.
2.Locate the bullwheel gear above the top drive slot.
3.Place your finger in an indent on the body of the bullwheel gear.
4.Turn the gear clockwise to raise the robot.


Note: Assume that the 12 o’clock position is toward the front control panel.

5.Hold the bullwheel gear with the robot fully raised until the robot is locked.

6.Reposition the robot lock (loosen the thumbscrew, remove the mechanism, rotate the mechanism 180 degrees, insert the mechanism, and tighten the thumbscrew).

  WHAT ACTIONS ARE REQUIRED TO RETURN THE SYSTEM TO AN OPERATIONAL STATE?: The SL150 library will need to be brought to an online state from the Web GUI.

PARTS NOTE:

REFERENCE INFORMATION: Please see the attached video for a step by step procedure on how to remove/replace the robot CRU in the SL150 library.

Warning:  If the new robot CRU is older the firmware on the robot might be downlevel and so after the library initializes you will be on an older firmware version than what you were running when the robot went bad.  If so you will need to download the latest firmware and upgrade the library.  Please see Doc ID 1474172.1 which guides you on how to find and upgrade the firmware on your SL150 library.

Warning:  If there are IBM LTO7 drives installed in the library you have to be running 2.60 code.  If the robot gets replaced and has an older code then the IBM LTO7 drives will not be recognized.  If the IBM LTO7 drives are the only drive type in the library then it won't initialize due to it not having a bridge capable drive.  Please see Doc ID 2196607.1 for more information on this scenario.

 


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