ACSLS connection to LMU is unstable, and continually re-connects, and then resets.
(Doc ID 2740365.1)
Last updated on JANUARY 04, 2021
Applies to:
Sun StorageTek Auto Cartridge Sys Lib SW (ACSLS) - Version 8.4 and laterInformation in this document applies to any platform.
The ACSLS server would not start. All components started, except the acsls component, which would eventually timeout, causing the ACSLS startup to terminate.
Symptoms
The $ acsss enable command terminates when attempting to start the acsls component.
The ~acsss/log/acsss_event log showed the following errors:
2020-12-28 04:41:00 ACSLH[0]:
2266 I Cm_ProcessRequests.C 2 896
Cm_4400::ProcessRequests: ACS 0: port <SL8500 IP address>: Port successfully
re-opened.
2020-12-28 04:41:02 ACSLM[0]:
37 N lm_msg_hdlr.c 1 1079
lm_msg_hdlr: LMU READY received for ACS Identifier 0
2020-12-28 04:41:05 ACSLH[0]:
2017 N Lm_tcpipVprocess.C 1 178
LC/LMU error: Lm_tcpip:Vprocess: ACS 0: Port <SL8500 IP address> not responding,
retrying port, line = 178.
2020-12-28 04:41:05 ACSLH[0]:
1185 N Cm_ProcessRequests.C 2 870
LC/LMU error: Cm_4400::ProcessRequests: ACS 0: port <SL8500 IP address>: Resetting
port, line = 870.
With the above 4 messages repeating every minute, until $ acsss enable timed out.
The ACSLS server was able to successfully ping and traceroute the <SL8500 IP address>.
Also, the command:
$ testlmutcp <SL8500 IP address>
correctly returned:
LMU Responded, compat level 23.
Changes
There were no SL8500, ACSLS, or network changes.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |