Sun StorageTek Auto Cartridge Sys Lib SW (ACSLS)
 
Sun StorageTek SL3000 Modular Library System
 
Sun StorageTek SL8500 Modular Library System
 

PLA-Support>Sun Systems>TAPE>Tape Hardware>SN-TP: Tape Library Control Software
 

Applies to:

Symptoms

Any of the following problems may be occurring:

1.  CAP in Automatic mode does not put away tapes during Enter operation

2.  "Place cartridges in CAP" or "Remove cartridges from CAP" message in ACSLS event log 
     repeats every 2 minutes

3.  CAP is stuck in Enter mode.

4.  CAP is stuck in Eject mode.

5.  enter operation works only when CAP is in manual mode.

6.  CAP is not locking.

7.  CAP is not unlocking.

8.  The message "CAP is already reserved" always occurs when a CAP operation is started.

Changes

Library maintenance activity caused the LSM to go offline 

Cause

Any of the following events may have occurred while an Enter or Eject operation is in progress:
1. The library was reset
2. The main access door was opened causing the LSM to go offline
3. A port communication reset error occurred
4. The ACSLS acscm process terminated unexpectedly
5. Defective connector pin in the CAP assembly

Solution

Follow these steps to free up the CAP and/or stop the repeated eject or enter messages:

1.  Verify CAP reservation error messages in the acsss_event.log.  Verify if any of these documents
     resolve the CAP reservation problem:

     a.  Hung reservation on the SL8500 after installation or reconfiguration:
     <Document: 1140893.1>  ACSLS - CAP is already reserved in partition 999 by host 99

     b.  Invalid CAP priority setting in ACSLS
     <Document: 1016649.1>  ACSLS - Cannot Vary CAP Online, Robotics Failure on SL8500

     c.  There are tapes stuck in the CAP
     <Document: 1014655.1>  ACSLS - Cannot enter tapes into SL8500 CAP


2.  Verify if a defunct Enter or Eject process is running. (Use the Unix ps command to verify) 
     A defunct enter or eject process would have a start time (STIME) around the time
     the repeated eject or enter message was first logged in the acsss_event.log.
 
     If existing, kill the defunct process.  Then,  check if the repeated messages are no longer
     being logged to the acsss_event.log.


3.  If no defunct Enter (or Eject) process is running but the CAP messages continue to be logged
     every two minutes, it is likely that the ACSLS Cartridge Manager, acscm,  process terminated
     unexpectedly.  

     As a result of the acscm abnormal termination,  the ACSLS Library Manager,  acslm,  process
     never got notified that a CAP request has terminated.  If this is the case,  try to  issue a vary
     command with the force option to offline the CAP:
                ACSSA>   vary CAP <capID> offline force
     Then, vary the CAP online:
                ACSSA>  vary CAP <capID> online

     If the vary commands fail,  ACSLS may have to be cycled.   Refer to <Document: 1014909.1>
     on how to cycle ACSLS.


4.  If the CAP problem concerns a CAP that cannot be unlocked or a CAP that is not putting away
     tapes, attempt to unlock the CAP by doing the following steps:

     a.  kill the hung eject (or enter) process, if existing;
     b.  vary the CAP offline with force option; then, vary the CAP online;
     c.  if vary fails to unlock the CAP, set CAP to manual mode;  then, set CAP to auto mode
     d.  if the CAP remains locked, reboot the CAP from the SLConsole
     e.  if the CAP remains locked, cycle ACSLS

  If the CAP continues to remain unlocked or locked,  verify if there is a physical problem with the
  CAP.  The latch assembly at the top of the CAP has a shoulder bolt which can come loose and prevent  
  the CAP assembly from locking properly. If the CAP does not lock, the library controller will not attempt
  any gets or puts to the Cap.  There could also be CAP motor issues that would prevent the CAP from
  opening or closing. 

  If the library is newly installed and the CAP will not unlock, i.e., the CAP led light never lit up, ask the
  field engineer to check connectors (related to the CAP assembly) for any pushed/defective pins. If so,
  have the field engineer repair the connector and test the CAP operations again.

5.  If the CAP problem persists even after trying all of the above steps,  open a service request (SR) and attach
     the following files to the SR:
     a.  ACSLS diagnostic log bundle
          Refer to these knowledge articles for procedures on how to capture diagnostic log and trace files:
              <Document: 1013165.1>  ACSLS - How to Gather Diagnostics Information 
              <Document: 1018346.1>  ACSLS - How To Gather Advanced Diagnostic Data 
     b.  Output of "query cap all" 
     c.  Output of CAP Details from the SLConsole
     d.  ACSLH trace (acslh.log), if existing
     e.  Library event log, if available.  
          The tape library error warn info event log can be downloaded from the SLConsole.
          Refer to this knowledge document for procedure on how to capture the library event log:
               <Document: 1933727.1> SL500/SL3000/SL8500 – How to Collect Information Using SL Console (Doc ID 1933727.1)
   

This solution has no attachment