ACSLS - Unexpected resource type code 86

Asset ID:	1-72-1529585.1
Update Date:	2016-06-07
Keywords:

Solution Type Problem Resolution Sure

Solution 1529585.1 : ACSLS - Unexpected resource type code 86 - STATUS_LIBRARY_FAILURE

Applies to:

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

Symptoms

Repeated error messages in the acsss_event.log:

013-02-08 16:31:12 MOUNT[0]:
546 N cl_log_lh_er.c 1 99
mo_lh_lib_fail: LH error type = LH_ERR_CANCEL_PENDING

2013-02-08 16:31:12 ACSMON process[0]:
528 N cl_addr_to_id.c 1 212
cl_addr_to_id: Invalid type 68868

2013-02-08 16:31:12 ACSMON process[0]:
2283 E mon_clmon_request.c 2 988
st_mon_unsolicit_msg: Unexpected resource type code 86 and resource status
STATUS_LIBRARY_FAILURE
2013-02-08 16:10:50 MOUNT[0]:
546 N cl_log_lh_er.c 1 99
mo_lh_lib_fail: LH error type = LH_ERR_CANCEL_PENDING

The parsed ACSLH trace log may show the following:
Priority: 25 01662 REQUEST Mount S06360 type L4=LTO-800G, format Unknown/Unknown
from Cell 00,34,21,01 to Drive 00,01,12 use normal cell addressing + verify domain and type, bypass VOLSER check

This may be followed by a number of Catalog subpanel requests.

In some cases, you may see errors like these in the ACSLS event log:

2016-04-27 01:00:09 DISMOUNT[0]:
546 N cl_log_lh_er.c 1 99
dm_lh_lib_fail: LH error type = LH_ERR_LSM_OFFLINE_MTCE

2016-04-27 01:00:09 ACSMON process[0]:
528 N cl_addr_to_id.c 1 212
cl_addr_to_id: Invalid type 0

2016-04-27 01:00:09 ACSMON process[0]:
2283 E mon_clmon_request.c 2 988
st_mon_unsolicit_msg: Unexpected resource type code 87 and resource status
STATUS_LIBRARY_FAILURE

2016-04-27 01:00:09 ACSSA[0]:
1431 N sa_demux.c 1 296
code 87 no format for TYPE_code 87: Library error, LSM offline maintenance

Changes

No known change

Cause

There is a library hardware problem that is causing the Mount (or Dismount) operation to fail.
ACSLS is not correctly interpreting the return code it is getting from the library.

When ACSLS encounters unexpected conditions during mounts and dismounts, like empty cells or drives or unexpected cartridges,
ACSLS will catalog the source cells or drives. In some of these cases, the results are processed by Mount (or Dismount) error handling code. The error
handling code sometimes interprets Catalog responses as Error responses.

ACSLS 8.4 includes a fix to better handle the unexpected resource type error.

Solution

1. Enable the ACSLH trace in ACSLS

$ start_logging.sh acslh

2. Enable the SLConsole monitor trace, if possible
Refer to the SL8500 Users Guide section on Monitoring Library Events on how to enable monitor trace.

3. Recreate the problem (or wait for the error messages to show up in the acsss_event.log)

4. Disable the trace tools

$ stop_logging.sh acslh

    To disable the SLConsole monitor trace, refer to the SL8500 Users Guide. ( Refer to link above. )

5. Open a service request in My Oracle Support and upload the following logs:

    ACSLS logs
      - ACSLS output tarfile ( <Document: 1013165.1> )
      - ~acsss/log/acslh.log

    Tape library logs
      - Saved event monitor data
      - Library log snapshot ( <Document: 1933727.1> )

Notes for the tape support engineer:

1. Upload the ACSLS logs and tape library logs to SPLAT

2. Review the ACSLH log and match the Mount (or Dismount) error timestamps with the acsss_event.log timestamps to determine the drive and volume IDs
of the failing Mount (or Dismount) operation.

3. Match the Mount (or Dismount) error timestamps and drive/volume IDs with the library events in the Error Warn Info Event log.

4. Determine which library component is failing or generating the unexpected resource errors.
Fix the failing library component.

5. If the problem persists, open a collab SR to ACSLS or Library HW level 2 engineer

Please note that ACSLS 8.4 includes a fix to better handle the unexpected resource type error.
Upgrading the library firmware to the latest code may also resolve the "unexpected resource type code 86" error.

References

<BUG:15690888> - SUNBT7011286 CODE 87 NO FORMAT FOR TYPE_CODE 87: LIBRARY ERROR, LSM OFFLINE MAIN

Attachments

This solution has no attachment