ACSLS - SL8500 Mounts Fail with "Serious internal error" Message

Asset ID:	1-72-1014656.1
Update Date:	2015-12-18
Keywords:

Solution Type Problem Resolution Sure

Solution 1014656.1 : ACSLS - SL8500 Mounts Fail with "Serious internal error" Message

Applies to:

Sun StorageTek Auto Cartridge Sys Lib SW (ACSLS) - Version 7.0 to 8.2 [Release 7.0 to 8.0]
Sun StorageTek SL8500 Modular Library System - Version All Versions to All Versions [Release All Releases]
Sun StorageTek SL3000 Modular Library System - Version All Versions to All Versions [Release All Releases]
All Platforms

Symptoms

All lights are green on SL8500 console
Can not ping SL8500 from network

Error messages in the acsss_event.log:
2005-12-29 15:59:07 ACSLH[0]:
1185 N Cm_ProcessRequests.C 2 685
LMU error: Cm_4400::ProcessRequests: ACS 0: port 172.22.0.43: Resetting port,
line = 685.
2005-12-29 16:02:51 ACSLH[0]:
1140 N Lm_tcpipVopen.C 1 316
Lh error: Lm_tcpip::Vopen: ACS 0: port 172.22.0.43: pending connect failed,
errno = 145.
2005-12-29 16:02:51 ACSLH[0]:
1133 N Lh_main.C 1 247
Lh error: main:ProcessPort: Serious internal error, please check event log.
2005-12-29 16:14:07 ACSLH[0]:
1133 N Lh_main.C 1 247
Lh error: main:ProcessPort: Serious internal error, please check event log.
2005-12-29 16:28:26 MOUNT[0]:
546 N cl_log_lh_er.c 1 99
mo_lh_lib_fail: LH error type = LH_ERR_LMU_FAILURE

Changes

Possible network configuration changes occurred

Cause

Network communication between ACSLS and the TCP/IP LMU is disrupted by network problems. Attempt by ACSLS to reconnect is unsuccessful due to timeout errors (errno = 145).

Solution

1. Verify from the customer if the network problem has been resolved.

2. When the network problem has been identified and resolved, verify if communication with the library has been restored.

3. If ACSLS is still unable to connect to the library after the network problem has been restored, request for library log snapshot or error warn info event log.
Open a service request (SR) or a collaboration SR with the tape hardware support group to review the logs and determine if there are library network interface problems.

4. If there is no problem with the library and the reported network issue has been fixed, dispatch a field engineer to the site so he can IPL the library. After the IPL, ACSLS may
have to be restarted in order to synchronize HLI communication with the library.

5. If there is a problem with the library's network module, this problem has to be resolved before attempting to connect ACSLS with the library.

References

<NOTE:1020070.1> - ACSLS - Validating Host Server Communication with a TCP/IP Attached Sun[TM] SorageTek Library
<NOTE:1020152.1> - ACSLS - Verify ACSLS start script completes with no error messages
<NOTE:1307534.1> - SL3000/SL8500 - How to Collect Log Snapshot From SL8500 or SL3000 Library

Attachments

This solution has no attachment