ACSLS - How to Troubleshoot a Library Port Communication Reset Error

Asset ID:	1-71-2184916.1
Update Date:	2018-01-02
Keywords:

Solution Type Technical Instruction Sure

Solution 2184916.1 : ACSLS - How to Troubleshoot a Library Port Communication Reset Error

Applies to:

Sun StorageTek SL8500 Modular Library System - Version All Versions to All Versions [Release All Releases]
Sun StorageTek Auto Cartridge Sys Lib SW (ACSLS) - Version 7.0 to 8.4 [Release 7.0 to 8.0]
Information in this document applies to any platform.

Goal

How to troubleshoot port reset errors

How to troubleshoot library port communication reset errors

How to troubleshoot an problem when a port lost communication with the library

Solution

1. Determine if there is a rogue host connected to the tape library.

    a. Check from the SLConsole HLI connection tab if there is a host IP address that does not match the current ACSLS server's IP address

    b. If there is an unknown host IP address connected to the library, identify the server and if possible, shut it down.
        Then, verify if ACSLS server is running and port connection to the library is stable.

2. If the problem persists, run these tests:

a. Bring down ACSLS and make sure no other ACSLS and Postgres processes are running.

        $ acsss shutdown
        $ psacs
        $ ps -ef | grep -i post

b. Kill ACSLS and postgres processes that did not terminate completely.

c. Bring down the library.

d. Bring up the library. Make sure all components are up.

e. From the ACSLS server, run these 10 times :

$ testlmutcp chyjb1-lan1

Or, run this on the command line:

   $ for i in {1..10} ; do
         > testlmutcp chyjb1-lan1
         > done

See if there are errors returned.

f. Restart the database and set desired-state of port and ACS to offline so the server will come up but not communicate with the library.

       $ acsss db
       $ sql.sh "update porttable set port_desired_state=5 where acs=x"
       $ sql.sh "update acstable set acs_desired_state=5 where acs=x"

Note: Where "acs=x" in the above command, replace x with the appropriate acs ID number.

g. Restart ACSLS and monitor the progress of the startup process.

   $ acsss enable
       $ cd /export/home/ACSSS/log >>> it's good to open another session and monitor the messages on that session
       $ tail -f acsss_event.log

h. When ACSLS is up, vary online the port and ACS:

      $ cmd_proc -l
    $ query port all
      $ vary port x,x online
      $ query acs all
      $ vary acs 0 online

Note: Where "port x,x" in the above cmd_proc command, replace x,x with the appropriate port ID.

3. If the problem persists or if root cause needs to be determined, open an ACSLS service request.

Attachments

This solution has no attachment