ACSLS - OSB Eject Request is Not Getting Executed by ACSLS

Asset ID:	1-72-2013054.1
Update Date:	2017-08-07
Keywords:

Solution Type Problem Resolution Sure

Solution 2013054.1 : ACSLS - OSB Eject Request is Not Getting Executed by ACSLS

Applies to:

Sun StorageTek Auto Cartridge Sys Lib SW (ACSLS) - Version 8.0 to 8.3 [Release 8.0]
Sun StorageTek SL3000 Modular Library System - Version All Versions and later
Information in this document applies to any platform.

Symptoms

There was an Eject request from OSB for a tape to be ejected. The tape was never ejected and it looks like ACSLS never got the request.
The tape was successfully ejected through the ACSLS cmd_proc.

OSB server logged errors like these during the eject operation:

ob> catxcr 1646
2015/05/04.12:00:54 ______________________________________________________________________
2015/05/04.12:00:54
2015/05/04.12:00:54 Transcript for job 1646 running on pbkposb1
2015/05/04.12:00:54
2015/05/04.12:00:54 Error: can't determine CAP size for cap - CAP full - operator needs to empty (SCSI library)
2015/05/04.12:00:54 Error: set_export_size failed - CAP full - operator needs to empty (SCSI library)
2015/05/04.12:00:54 Request completed

Changes

No known change in the system

Cause

OSB locks or some work files may have to be reset or cleared. Restarting OSB resolved the problem.

Not an ACSLS issue.

Solution

Enable the CSI trace to verify if ACSLS is receiving the Eject request packet from OSB.
Upload the CSi trace log named acsss_trace.log to the service request ticket in MOS and the support engineer will decode and analyze it.

If the Eject request from OSB is not found in the CSI trace, the request is not reaching ACSLS.
Try restarting the OSB services and wait for another OSB Eject job.

If the Eject request is in the CSI trace, check the acsss_event.log for any CAP issue that may have happened during the Eject process.

If the problem persists, work with the ACSLS support engineer to resolve the problem by providing additional diagnostic information:
- get an ACSLS output tarfile and upload this to the service request.
- also upload a library event log from the library console.

References

<NOTE:1013165.1> - ACSLS - How to Gather Diagnostic Logs and Information
<NOTE:1014964.1> - ACSLS - How to Get a CSI Trace.
<NOTE:1307534.1> - SL3000/SL8500 - How to Collect Log Snapshot From SL8500 or SL3000 Library

Attachments

This solution has no attachment