Asset ID: |
1-72-1495225.1 |
Update Date: | 2017-09-27 |
Keywords: | |
Solution Type
Problem Resolution Sure
Solution
1495225.1
:
SL3000 - LTO Upside-Down Cartridge Behaviour
Related Items |
- Sun StorageTek SL3000 Modular Library System
|
Related Categories |
- PLA-Support>Sun Systems>TAPE>Tape Hardware>SN-TP: SL3000-8500 Library
|
In this Document
Oracle Confidential PARTNER - Available to partners (SUN).
Reason: Confidential for service personnel
Created from <SR 3-5936620031>
Applies to:
Sun StorageTek SL3000 Modular Library System - Version Not Applicable to Not Applicable [Release N/A]
Information in this document applies to any platform.
Symptoms
SL3000 with code 3.00 direct attached to NBU 7.1 over FC Interface.
Expectation was that the SL3000 would detect this and media would remain in CAP, But Library imported them into the slots.
-----SL3000 Event Logs
2012-07-17T13:52:42.318 1,0,0,0,0 root default internal 0 error 3314 Cartridge found upside down address=1,1,5,2,6 volumeLabel=T00008L5K</resultText></resultStatus></result></response>
Cause
Tapes were entered upside down by Library operator.
Library Operator accidentally inserted LTO5 cartridges upside down from CAP.
Solution
The library detects the upside down cartridge condition correctly and reports it back to the host if it is HLI attached.
The library managers manage the CAP activity and the library just does as it is told for the most part.
With ACSLS or HSC when this is reported to the library manager they eject the cartridge from the CAP. We could only follow up if the SL3000 is attached to ACSLS or HSC.
In this case, it is managed by a third party via the Fibre interface like NBU, the issue must be addressed by NBU.
CAUTION :
Possible Media Damage : Insertion of upside-down cartridges should never be attempted, especially for Oracle StorageTek cartridges.
For LTOs, the CAP design does allow placing cartridge upside-down but such attempts should not be made.
Also avoid entering any media with missing or damaged Barcode. This can create problems during Library Audit and are seen as #UREAD labels in the event logs.
References
@inputs from Bruce McDonald
Attachments
This solution has no attachment