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-72-1527222.1
Update Date:2014-08-26
Keywords:

Solution Type  Problem Resolution Sure

Solution  1527222.1 :   ACSLS - L700 not fully communicating with ACSLS after MPC and MPU2 cards replaced  


Related Items
  • Sun StorageTek L700 Tape Library
  •  
  • Sun StorageTek Auto Cartridge Sys Lib SW (ACSLS)
  •  
Related Categories
  • PLA-Support>Sun Systems>TAPE>Tape Hardware>SN-TP: Tape Library Control Software
  •  




In this Document
Symptoms
Changes
Cause
Solution
References


Created from <SR 3-6714684717>

Applies to:

Sun StorageTek L700 Tape Library - Version Not Applicable to Not Applicable [Release N/A]
Sun StorageTek Auto Cartridge Sys Lib SW (ACSLS) - Version 7.1 to 8.2 [Release 7.0 to 8.0]
Information in this document applies to any platform.

Symptoms

1. The ACSLS testports utility returns "LSM becoming ready" message with error 62800.

    $ testports
     acs 0 | port 0 | /dev/mchanger0 | offline | LSM error 62800: \c LSM becoming ready

    $ smc_test /dev/mchanger0:
    ..
    Command: n
    Peripheral Type = 8
    Vendor ID = “STK”
    Product ID = “L700”
    Revision Level = “0317”
    PTP Serial Number = “MPC74001967”
    Vendor Specific ID = 005da630
    Vendor Specific ID Extn = 113085014f0

    Command: s 29
    Command error = 62800                              

    Command: t
    Command error = 62800

    Command: i
    Command error = 62800

    NOTE: Error 62800 refers to:
    SK/ASC/ASCQ 6/28/00 = 28/00 DTLPWROMAEBKVF NOT READY TO READY CHANGE, MEDIUM MAY HAVE CHANGED
    i.e., the LSM is not getting to a ready state


2. acsss_config may also show the 62800 error:

     $ acsss_config

           8. Define or Change Library Configuration

    Menu choice: 8

    Verifying database environment…
    Configure library communications? (y or n): y
    Library server data  base exists and will be overwritten, continue (y or n)? y
    Number of connections to ACS #0: 1

    Device or host – ACS #0, connection #0: /dev/mchanger0

    Checking defined ports…

    acs 0 | port 0 | /dev/mchanger0 | offline | LSM error 62800: \c
    LSM becoming ready

    Each port must be attached and communicating to a functional
    Library before the library can be configured. Exiting.

    Cannot execute program ‘$ACS_HOME/config/lib_config.sh’
    Acsss_config 1595: Error: Problems occurred running the configuration menu.
    Exiting

Changes

 After a power outage the SL700 had hardware problems and both the MPC (communication controller board) and MPU2 ( FC board ) cards were replaced.

Cause

There is a problem with the L700 MPC board.   If the OS is not able to see the L700, there may also be a problem with the MPU2 board.

Solution


1.  To verify FC connectivity to the L700, refer to <Document 1020528.1> ACSLS - Troubleshooting 'mchanger' Installation Problems

2.  If the the FC HBA on the ACSLS server is correctly configured, 'cfgadm -al'  command should show something like this output for the HBA:

       C3::500104f0005da631   med-changer     connected          configured          unkown

3.  Run the ACSLS testports utility.  If testports is successful, the output will look like this:
     $ testports
        ACS0:
        /dev/mchanger0 is communicating to an LSM: STK L700 level 0317

     Otherwise, testports will return an error. 

4.  If testports return a 62800 error, verify if the same error is returned by the smc_test utility.
     Refer to <Document 1014616.1> ACSLS - How to run smc_test.

5.  If the ACSLS utilities return the same 62800 error consistently, open a HW service request to have a field engineer
     check the library MPC and/or MPU2 cards.

6.  If another type of error is being returned by the ACSLS utilities, search the Knowledge base for known solutions or
     open a service request in My Oracle Support.

    

References


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