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
 

Applies to:

Purpose

This document provides a means to assist in troubleshooting 'mchanger' installation problems.

Troubleshooting Steps

Please validate that each troubleshooting step below is true for your environment.  Each step will provide instructions or link to a document in order to eliminate possible causes and take corrective action as necessary.  The steps are ordered in the most appropriate sequence to isolate the issue and identify the proper resolution.  Please do not skip a step.

1.  Verify that the HBA is installed and functional on the ACSLS host server
     The ACSLS server needs a Host-Bus Adapter (HBA) that is compatible to the interface card in the  SCSI/Fibre tape library.
     Thus, the HBA could either be a Fibre Channel or a SCSI card depending on whether the library is configured with the Fibre
     Channel feature or not.  The HBA would need a compatible device driver to be functional.

     For Fibre Channel HBAs, refer to <Document 1020533.1> ACSLS - Verify FC HBA is Installed and Configured

     For SCSI HBAs, refer to <Document 1020536.1> ACSLS - Verify SCSI HBA is Installed and Configured

     If the appropriate HBA and HBA driver are not installed correctly, make sure that the issue is resolved prior to
     performing the next step.

     If necessary, open a case with the Oracle support center regarding installation and configuration of HBA and/or HBA driver
     needed to communicate with the StorageTek[TM] Tape Library.


2.  Verify that the OS can see the library that is connected to the HBA
     The following commands can be used to verify if the OS can see the connected tape library through the HBA device:

     For Fibre Channel connection
     a.  With the FC HBA and driver installed, run this command to get the HBA port world-wide name:
           #   fcinfo hba-port
                  HBA Port WWN: 210000e08b86b991
                  OS Device Name: /dev/cfg/c3
                  Manufacturer: Qlogic Corp.
                  Model: QLE2460
                  Type: L-port
                  State: online
                  Supported Speeds: 1Gb 2Gb 4Gb
                  Current Speed: 1Gb
                  Node WWN: 20000e08b86b991
                 
     b.  Using the HBA port WWN discovered above, verify if the host OS can see the connected tape library:
          #  fcinfo remote-port -slp 210000e08b86b991
               Remote Port WWN: 500104f000411932
                                      Active FC4 Types:
                                      SCSI Target: yes
                                      Node WWN: 500104f000411846
                                      Link Error Statistics:
                                                          Link  Failure  Count: 0
                                                          Loss of Sync Count: 0
                                                          Loss of Signal Count: 0
                                                          Primitive Seq Protocol Error Count: 0
                                                          Invalid Tx Word Count: 0
                                                          Invalid CRC Count: 0
                                      LUN: 0
                                      Vendor: STK
                                      Product: L180
                                      OS Device Name: Unknown

          This display confirms functionality of all the steps listed above:
          - the Leadville driver modules (qlc, fp, fctl, and fcp) are loaded and functional;
          - the QLogic HBA is functional and is seen by the Solaris[TM] system;
          - the HBA is properly bound to the 'qlc' driver; and,
          - a StorageTek library is successfully communicating via the fibre connection.

     For SCSI Connection (and FC connections without the Leadville driver installed)
     Refer to <Document 1020069.1> ACSLS - Validating Host Server Communication with SCSI/Fibre Attached Sun StorageTek Tape Library.

3. Verify the mchanger installation process runs successfully
    The SCSI Media Changer (also called mchanger) is the SCSI/Fibre attached library device driver that makes
    it possible for ACSLS to communicate with the SCSI/Fibre attached library.

    A mchanger device must be created for each SCSI/Fibre library attached to the ACSLS server. Adding a
    mchanger device is part of the installation process when install.sh is run.

    There may be times when a new SCSI library has to be added to an existing ACSLS configuration. For this
    purpose, the script install_scsi_sol.sh, can be run. (For ACSLS running on AIX, run install_scsi_aix.sh.)

    For Solaris mchanger installation problems, refer to <Document 1020620.1>  ACSLS - Troubleshooting install_scsi_sol.sh Problems

    For AIX mchanger installation problems, refer to <Document 1020638.1>   ACSLS - Troubleshooting install_scsi_aix.sh Problems


4. Confirm that the tape library responds as an mchanger device using any of these ACSLS utilities
    a. probescsi.sh
        Example:
          $ probescsi.sh /dev/mchanger0
          /dev/mchanger is communicating to an LSM: STK L180 level 0311

    b. smc_test
        Example:      
          $ smc_test /dev/mchanger0
        The smc_test utility allows ACSLS to send SCSI commands to the library.Refer to <Document 1014616.1> ACSLS - How to Run smc_test

5. At this point, if you validated that each of the troubleshooting step above is true for your environment, and the issue still exists,
    further troubleshooting is required. If there are unresolved errors from the preceding troubleshooting steps, gather the ACSLS
    diagnostic logs - <Document 1013165.1> . Then, open a service request and submit all pertinent documentation related to the
    problem ( including, but not limited to, screenshot images of error messages resulting from running commands from the
    troubleshooting steps above).

         

This solution has no attachment