Sun StorageTek SL8500 Modular Library System
 

PLA-Support>Sun Systems>TAPE>Tape Hardware>SN-TP: SL3000-8500 Library
 

In this Document

Symptoms

Changes

Cause

Solution

References

Oracle Confidential PARTNER - Available to partners (SUN).
Reason: adding new knowledge
Created from <SR 3-17566352432>

Applies to:

Symptoms

Both robots on the same rail are in a offline not ready error state.

The supplied log snapshot shows the following for both bots on rail 3..

2018-05-25T05:41:10.440, 4.3.0.1.0, root, default, internal, 0, error, 1301, "Device response time-out", request=<request sequence="21499160"><command>healthCheck</command><requestId>internalActivity</requestId><parms><watchdogTimeout>182</watchdogTimeout></parms></request>
2018-05-25T05:41:25.460, 4.3.0.2.0, root, default, internal, 0, error, 1301, "Device response time-out", request=<request sequence="21499161"><command>healthCheck</command><requestId>internalActivity</requestId><parms><watchdogTimeout>182</watchdogTimeout></parms></request>
2018-05-25T05:42:10.740, 4.3.0.1.0, root, default, internal, 0, error, 1301, "Device response time-out", request=<request sequence="21499180"><command>healthCheck</command><requestId>internalActivity</requestId><parms><watchdogTimeout>212</watchdogTimeout></parms></request>
2018-05-25T05:42:25.750, 4.3.0.2.0, root, default, internal, 0, error, 1301, "Device response time-out", request=<request sequence="21499186"><command>healthCheck</command><requestId>internalActivity</requestId><parms><watchdogTimeout>212</watchdogTimeout></parms></request>
2018-05-25T05:43:10.480, 4.3.0.1.0, root, default, internal, 0, error, 1301, "Device response time-out", request=<request sequence="21499203"><command>healthCheck</command><requestId>internalActivity</requestId><parms><watchdogTimeout>212</watchdogTimeout></parms></request>
2018-05-25T05:43:25.490, 4.3.0.2.0, root, default, internal, 0, error, 1301, "Device response time-out", request=<request sequence="21499204"><command>healthCheck</command><requestId>internalActivity</requestId><parms><watchdogTimeout>212</watchdogTimeout></parms></request>

Device.db shows both robots in a error not communicating state.

4,3,0,1,0 HBB 74028905 HBB 74028905 false false false Error NULL 4,3,-10,1,0
4,3,0,2,0 HBB 74029092 HBB 74029092 false false false Error NULL 4,3,-6,1,1

Changes

Cause

Device.db shows both robots in a error not communicating state.

4,3,0,1,0 HBB 74028905 HBB 74028905 false false false Error NULL 4,3,-10,1,0
4,3,0,2,0 HBB 74029092 HBB 74029092 false false false Error NULL 4,3,-6,1,1

You will not see any HBB logs for these bots due to the fact that they are in a error state and not communicating with the HBC.

Solution

1. Create HW onsite task for HBS card power cycle.
    a. Open the library rear doors.
    b. Set the circuit breaker to the down/off position for the HBS card on rail 3.
    c. Wait 30 seconds and set the Circuit Breaker to the up/on position.
    d. Verify that the greed LED indicating Power is on and the red (fault) LED is off.     Note: The remaining LED's may flicker as the HandBots send and receive commands.
2. If you do not see any green LED on and/or remaining LED's indicating sending and receiving commands proceed to step 3.
3. Replace HBS card... See sl8500 - How to Remove and Replace a Defective HBS card in a sl8500(Doc ID 2232646.1)

References

This solution has no attachment