| Asset ID: |
1-72-1463428.1 |
| Update Date: | 2017-09-21 |
| Keywords: | |
Solution Type
Problem Resolution Sure
Solution
1463428.1
:
SL8500/SL3000 - Device response time-out
| Related Items |
- Sun StorageTek SL3000 Modular Library System
- Sun StorageTek SL8500 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-5769911451>
Applies to:
Sun StorageTek SL3000 Modular Library System - Version All Versions to All Versions [Release All Releases]
Sun StorageTek SL8500 Modular Library System - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.
Symptoms
robot lost power and needed to reinitialize:
=====================
2012-05-30T16:00:05.915, 1.1.1.1.1, root, hli0, move,62151401, error, 3955, "Error from device Code: 603 - Drive cartridge is present", Data=<response sequence="3632469" final="true"><command>load</command><result identifier="1"><resultStatus><resultSeverity>error</resultSeverity><resultCode>6415</resultCode><resultText><!|CDATA|drive 1,1,1,1,1: load Failed with unitCheck 5530, CartLabel = MV27210R FSC: 5530||></resultText><operationalState>603</operationalState></resultStatus><currentCleanUsage>0</currentCleanUsage><maxCleanUsage>0</maxCleanUsage><faultSymptomCode>5530</faultSymptomCode></result></response>
2012-05-30T16:05:26.442, 1.1.2.1.1, root, hli0, move,62152201, error, 3955, "Error from device Code: 603 - Drive cartridge is present", Data=<response sequence="3632519" final="true"><command>load</command><result identifier="1"><resultStatus><resultSeverity>error</resultSeverity><resultCode>6415</resultCode><resultText><!|CDATA|drive 1,1,2,1,1: load Failed with unitCheck 5530, CartLabel = MV27210R FSC: 5530||></resultText><operationalState>603</operationalState></resultStatus><currentCleanUsage>0</currentCleanUsage><maxCleanUsage>0</maxCleanUsage><faultSymptomCode>5530</faultSymptomCode></result></response>
2012-05-30T16:15:55.965, 1.1.0.1.0, root, hli0, move,62152801, error, 1301, "Device response time-out", request=<request sequence="3632560"><command>fetchCartridge</command><requestId>internalActivity</requestId><parms><address>1,1,-17,2,42</address><cartType>StkHalfInch</cartType><safeColumn>-7</safeColumn></parms></request>
2012-05-30T16:15:55.994, 1.1.0.1.0, root, hli0, move,62152801, error, 1319, "Robot operation failed - robot in fetch", volumeLabel=MV2735~R hliLsm=0
2012-05-30T16:16:11.017, 1.1.0.1.0, root, default, internal, 0, error, 1301, "Device response time-out", request=<request sequence="3632569"><command>healthCheck</command><requestId>internalActivity</requestId><parms><watchdogTimeout>0</watchdogTimeout></parms></request>
2012-05-30T16:16:11.031, 1.0.0.0.0, root, default, internal, 0, error, 3215, "Robot initialization error - Data: 2012-05-30T16:16:11.029, 1.0.0.0.0, root, default, internal, 0, error, 3987, "Device io exception""
2012-05-30T16:16:11.029, 1.0.0.0.0, root, default, internal, 0, error, 3987, "Device io exception"
'network stat' and 'ifconfig' on the library server show dropped communication packets on the rail interfaces.
Changes
no known changes
Cause
Possible brush wear and rail debris build up
Solution
To bring the robot back online, reboot the robot.
Schedule a maintenance window with the customer to inspect and clean the rails.
Refer to Doc 1457018.1 : SL8500 - Procedure to Manually Clean Copper Rails in Library:ATR:1457018.1:2
Attachments
This solution has no attachment
