Sun StorageTek Auto Cartridge Sys Lib SW (ACSLS)
 
StorageTek SL150 Modular Tape Library
 
Sun StorageTek SL500 Modular Library System
 

PLA-Support>Sun Systems>TAPE>Tape Hardware>SN-TP: Tape Library Control Software
 
_Old GCS Categories>Sun Microsystems>Storage Software>Library Software
 

Applies to:

Goal

This solution provides a means to verify if there is communication between the SCSI/Fibre attached library and the ACSLS host server.

This solution requires knowledge of the host bus adapter (HBA) card on the ACSLS server to which the SCSI/Fibre library is attached to.

SCSI/Fibre attached libraries include libraries like L700, L180, 9740, SL500, SL150, etc. This solution does not include the instructions on how to install the library and the HBA.

Solution

Validating Host Server Communication with a Sun StorageTek[TM] SCSI/Fibre attached Library

1. Verify that the library is online and all components are available
   This can be verified from the library control panel or SLConsole (if applicable).
   ACSLS requires that there is at least one CAP and one tape drive online and available, for its configuration process to succeed.
   
   
   

2. For an existing ACSLS installation, verify that the host server can still communicate with the SCSI/Fibre library through a configured mchanger device
   To verify if the ACSLS host server is able to communicate with the SCSI/FC library through the configured mchanger device, run smc_test. 
   Refer to <Document 1014616.1>  ACSLS - How to run smc_test.  
   
   If the smc_test commands are completing successfully, this implies that the mchanger device is configured correctly and ACSLS should be able to communicate successfully with the SCSI/FC
   tape library.  However,  if ACSLS fails to vary the port connection to the library in spite of  successful  smc_test  commands,  enable  the  scsilh trace utility  to  identify  what  is  causing  the  connection  failure.   Refer  to <Document 1017174.1> ACSLS - How to Turn on scsilh Tracing.
   
   If smc_test fails to complete successfully, proceed to the next step.
   
   

3. Verify that the library and the HBA are installed correctly
   The field engineer or customer who is configuring the tape library with ACSLS should have previously connected the tape library to the appropriate HBA card installed on the ACSLS host server. 
   Please refer to these solutions: 
   <Document 1020536.1> ACSLS - Verify SCSI HBA is Installed and Configured
   <Document 1020533.1> ACSLS - Verify FC HBA is Installed and Configured
   
   Additional notes on SCSI HBA's:
   Some SCSI HBAs do not have the Fcode driver that would allow probe-scsi-all to identify the devices attached to the controller.   To workaround this problem, try these steps:
   1. connect to local console or serial port console.
   2. go to the ok prompt (i.e., single-user mode)
       # init 0                                                         
   3. in the ok prompt, issue these commands:
       ok>  setenv auto-boot? false
       ok>  reset-all
       ok>  probe-scsi-all  -capture output
       ok>  setenv auto-boot? true
       ok>  reset-all                                          -this will boot you back to multi user mode
   
   
   If no tape library device is discovered by probe-scsi-all, luxadm or cfgadm command,  ACSLS will not be able to communicate with the library.  Hence,  the ACSLS library hardware configuration process will fail. Check for possible cable, switch and host port issues.
   
   References:
   1.  The following URL provides links to StorageTek[TM] Library manuals and technical documentations:
        https://docs.oracle.com/en/storage/
   2.  The following URL provides a link to the Solaris[TM] Handbook for Sun Peripherals:
        https://docs.oracle.com/cd/E19455-01/806-2219-10/806-2219-10.pdf
   3.  <Document 1004694.1> SCSI Troubleshooting on Sun Systems
   4.  <Document 1016818.1> Library Not Seen by Server
   
   
   

This solution has no attachment