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

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

In this Document

Symptoms

Changes

Cause

Solution

Created from <SR 3-6437493393>

Applies to:

Symptoms

1. testlmuctp is failing with Error 149 (Operation already in progress). However, the library is online and available. It is communicating to the mainframe hosts in one partition through port 2B.

2. ssh to the library times out; but, ping may work.

3. acsss_event.log error message during ACSLS start up:
2012-11-13 12:53:25 ACSLH[0]:
1140 N Lm_tcpipVopen.C 1 346
Lh error: Lm_tcpip::Vopen: ACS 0: port sl8500-2B: pending connect failed, errno = 145.

4. Another server on the same subnet as ACSLS and the library is able to ssh to the library.

Changes

No change known to the customer

Cause

Possible problem with the ACSLS server's interface, connection or routing to the library

 

Solution

1. Make sure the library is online and available.
    a. Check library components and verify errors in the SLC error warning info log. Reboot library if needed.
    b. Check HLI host IP connections with the library using the SLConsole Library Details HLI properties tab.
    c.  Enable monitor trace and ACSLH trace prior to recreating the problem.
    d. Check if the ACSLS server IP address appears on the HLI table and monitor trace log.
  
2. If ACSLS can connect to the library as seen on the HLI table and monitor trace, but connection drops, IPL the library.

3. If ACSLS never successfully connected to the library, isolate the problem:
    a. Is this a routing issue?
        - Ask the customer to check for static routes that would cause the connection to fail to reach the library
        - Run traceroute from the ACSLS serswitch/gateway
    b. Is this an interface issue?
        - Check the system messages file for any interface issue
        - Make sure that the library communication is going through the correct interface
        - If there is another interface port with a route to the library, try moving the library connection to that port
        - Make sure the network interface to the library is plumb'd correctly
    c. Is this a cabling or switch issue?
        - Verify cable for any damage or issues. Replace with a new cable if needed.
        - Verify if there are any issues with the switch. Ask the customer to make sure that another server attached to the switch can ssh to the library.

4. For each change made in the troubleshooting steps above, verify if the problem is resolved:
    a. Run the ACSLS testlmutcp command:
        $ testlmutcp <library-IP-address>
        or,
        $ testlmutcp  <library-IP-address>:50001
    b. ssh to the library:
        # ssh admin@<library-IP-address>
    c. Vary the port online in ACSLS:
        $ cmd_proc -l
           ACSSA> vary port online

5. If the problem persists, have the customer involve their network admin to further troubleshoot the problem.
    If customer has Solaris / SAN support, a collab SR can be opened with the SAN team.
 

This solution has no attachment