ats – library engineering sl500 fault...

ATS – Library EngineeringSL500 Fault Isolation

Version v1.1

Sun Microsystems Inc. Confidential: Need To Know

SL500 Fault Isolation Sun Microsystems Inc. Confidential: Need To Know

Document Control Information

Document File Name PATTLNK_10182006_1738-SL500 Fault Isolation GuideFI_1_05.2.doc

Document Published Location <location of published document – in Livelink?>

Date of Last Modification 10/11/2006 04:12:59 PM

Revision Level v1.1

Document Owner Brian L. Plomondon

Document Classification Protected

Organization Automated Tape Solutions – Library Engineering

Group SL500 Library

Review Distribution Chris West, Chris Clos, Stephen Hamada, Brian Plomondon, MarkRoget, Jon Allen, Rob Schmidt

Modification History

Rev Date Intls Modification

1.00 03/21/05 BLP Changes from Chris Clos were accepted for Chapter 7

1.1 08/29/06 BLP Added all new result codes since last update

1.1 10/11/06 BLP Added review updates – Added new drive types

- Removed “If HP” from any result code indicating IBM

(result codes: 6430, 6444, 6445, 6446)

ii Sun Microsystems Inc. Confidential: Need To Know

SL500 Fault Isolation

Table Of Contents

Chapter 1: Introduction ........................................................................................................................................ 1

Chapter 2: Suspect FRU List ............................................................................................................................... 2

2.1 FRU List, SL500 ......................................................................................................................................... 2

2.2 FRU List, Drives, SL500 ........................................................................................................................... 2

2.3 HP Specific ............................................................................................................................................... 3

Chapter 3: SCSI Errors ........................................................................................................................................ 4

Chapter 4: IFM Errors .......................................................................................................................................... 8

Chapter 5: DIAGNOSTIC Errors ....................................................................................................................... 22

Chapter 6: LIBRARY Miscellaneous ................................................................................................................. 43

Chapter 7: SNMP ............................................................................................................................................. 49

Chapter 8: Service ............................................................................................................................................. 51

Chapter 9: ROBOT ............................................................................................................................................ 55

9.1 SRV_MECH Errors .................................................................................................................................. 55

9.2 SCAN Errors ........................................................................................................................................... 74

9.3 TARGET Errors ........................................................................................................................................ 77

9.4 CMO Errors ............................................................................................................................................. 79

Chapter 10: DRIVE Errors ................................................................................................................................. 87

Chapter 11: Sensor Manager ......................................................................................................................... 105

Chapter 12: CLI Service Commands ............................................................................................................. 108

iii Sun Microsystems Inc. Confidential: Need To Know


Chapter 1:Introduction

The intended purpose of this document is to facilitate the isolation of a library fault and its repair. Libraryreason codes taken from logs or diagnostics are used as the starting point for fault isolation. Once a reasoncode is determined, the code can be referenced here. The isolation procedures provide the actions to take toisolate the fault. Any library commands referenced in this document are CLI commands from the Servicelogon.

1 Sun Microsystems Inc. Confidential: Need To Know


Chapter 2:Suspect FRU List

See the SL500 REPLACEABLE PARTS CATALOG PN 96120 for specifics.

2.1 FRU List, SL500PWA MPU2 (HP)

PWA MPW (STK)

PWA RLJ - Base unit 4U motherboard

PWA RLC – Robot Controller Proc.

PWA RLE – Drive Expansion unit motherboard

PWA RLM – Base unit motherboard

Fan Assy, 5VDC AXIAL

PS, AC/DC, 490W, ATX MOD

OPERATOR PANEL, FRU ASSY

ROBOT ASSY, STK

2.2 FRU List, Drives, SL500HP LTO2, SCSI, FRU ASSY

HP LTO2, FC 2GB, FRU ASSY

IBM LTO2, SCSI, FRU ASSY

IBM LTO2, FC 2GB, FRU ASSY

IBM LTO2, FC AS4, FRU ASSY

HP LTO3, SCSI, FRU ASSY



IBM LTO3, SCSI, FRU ASSY



QUANTUM SDLT 320, SCSI, FRU ASSY

QUANTUM SDLT 600, SCSI, FRU ASSY

QUANTUM SDLT 600, FC 2GB, FRU ASSY

QUANTUM DLT-S4, SCSI, FRU ASSY

PWA RLD

FAN ASSY, 5VDC AXIAL



2.3 HP Specific IM – Interface Controller

IC – Interface Controller (HarpoonIII)

The Suspect FRU List consists of the most likely FRUs that would fix the problem.



Chapter 3:SCSI Errors

1100=SCSI_NOOP

"Requested action not needed"

SFL: No FRU

Isolation Procedure: No Isolation Procedure

1101=SCSI_FAILED

"Requested action failed"

FIBRE SFL: 1) software 2) MPU2 (STK)

LVD SFL: 1) software 2) MPW (STK)

SIPP: SFL: 1) software 2) Harpoon (HP) 3) Montana (HP)

Isolation Procedure:

FIBRE

1. Issue LUN reset task management function (from host)

2. Reset transport layer from the host, retry operation

3. Unplug and plug in FIBRE cable

4. Reboot library

5. If persists, MPU2 card (for STK) at fault. Replace MPU2 card

LVD



3. Reboot library

4. If persists, MPW card (for STK) at fault. Replace MPW card

SIPP



3. Reboot library

4. If persists, Harpoon or Montana card (for HP) at fault. Replace appropriate card



1102=SCSI_DRIVER_ERROR

"Error executing driver request"

FIBRE SFL: 1) software 2) MPU2 (STK)

LVD SFL: 1) software 2) MPW (STK)

SIPP: SFL: 1) software 2) Harpoon (HP) 3) Montana (HP)


FIBRE


2. Unplug and plug in FIBRE cable

3. Reboot library

4. If persists, MPU2 card (for STK) at fault. Replace MPU2 card

LVD


2. Reboot library

3. If persists, MPW card (for STK) at fault. Replace MPW card.

SIPP


2. Reboot library

3. If persists, Harpoon or Montana card (for HP) at fault. Replace appropriate card

1103=SCSI_SYSTEM_ERROR

"System error occurred - application, hardware configuration, or os."

SFL: 1) Hardware configuration, Hardware, Software


1. Check for heterogeneous hardware

Invalid configuration would be FIBRE and SCSI together.

Or no cards at all (STK only)

2. Verify all cards are seated.

3. If error persists, replace MPU2 (STK) or MPW (STK).

1104=SCSI_PROGRAM_ERROR



"Encountered a situation which should never occur"

SFL: 1) Software


1. Collect logs

2. Create pinnacle

1105=SCSI_TASK_ABORTE D

"Task was aborted"

SFL: No FRU


No Isolation Procedure

1106=SCSI_REJECTED

"Requested action from host rejected"

SFL: 1) Host software

Isolation Procedure: No (library) Isolation Procedure. Host software is attempting an unsupported taskmanagement function.

1107=SCSI_RESTART_INTERFACE

"Interface needs to be restarted"

SFL: 1) software 2) MPU2 (STK) or MPW (STK), Harpoon (HP), Montana (HP)


1. Collect logs (including kernel logs)

2. Reboot library

3. If problem persists after reboot, hardware at fault

4. Replace MPU2 (STK) or MPW (STK), Harpoon (HP), Montana (HP)

1108=SCSI_TASK_COMPLETED

"Task completed"

SFL: No FRU

Isolation Procedure: No isolation procedure required, normal operation



1109=SCSI_NOT_ALLOWED

""Requested action not allowed

SFL: No FRU

Isolation Procedure: No isolation procedure required, normal operation



Chapter 4:IFM Errors

3300=IFM_UNKNOWN

"Unexpected error"

SFL: 1) Firmware

Isolation Procedure

1. Collect logs

print log <all>

2. Reboot library

reboot

3301=IFM_RESOURCE_FAIL

"User command could not be sent"

SFL: 1) Robotics 2) Firmware

Isolation Procedure

1. Collect logs

print log <all>

2. Reboot library

reboot

3302=IFM_CONTENT_FAIL

"Content failure for a request or function call"

SFL: 1) No FRU – Check media


1. Collect logs

print log <all>

2. Reboot library

reboot



3303=IFM_NON_EXISTENT_SOURCE_DRIVE

"Source drive requested is not configured"

SFL: 1) No FRU– Check source drive address

Isolation Procedure: See result code 3304 for Action Require.

3304=IFM_NON_EXISTENT_DEST_DRIVE

"Destination drive requested is not configured"

SFL: 1) No FRU – Check destination drive address


1. Check address of drive, if correct continue

2. Visibly check for drive, if present continue

3. Visibly check that drive bezel is still in place, if present continue

4. Initialize drive

If HP drive issue drive reset command - drive <addr> reset

If not HP drive, pull drive out, wait 10 seconds, put it back in. Note: In fully populated library thewait could be up to 20 seconds.

5. Issue drive state command

drive <addr> state

If problem persist, continue

6. Insert a different drive

7. Issue drive status command

drive <addr> state

If problem goes away, replace drive

If problem persists, replace robotic assy

3305=IFM_INOP

"Encountered inop condition"


Isolation Procedure

1. Collect logs

2. Scan for error IFM_INOP

3. Once error is found, look back in time for INOP indication.

4. Once INOP condition is found, determine source of INOP condition and attempt to clear.

5. Reboot library



3306=IFM_USER_REQUEST_FAIL

"User command request failed to get sent"

SFL: Firmware

Isolation Procedure: None, result code is not used.

3307=IFM_USER_RESPONSE_FAIL

"User command response returned failure"

SFL: 1) Firmware

Isolation Procedure

1. Collect logs

print log <all>

2. Reboot library

reboot

3308=IFM_MOVE_NON_EXISTENT_SOURCE

"Source address does not exist"

SFL: 1) No FRU

Isolation Procedure: See result code 3309 for Isolation Procedure.

3309=IFM_MOVE_SOURCE_EMPTY

"Source location is empty"

SFL: 1) No FRU


1. Check source addressNote: If SCSI address, addresses are shifted by number of reserved cells.

2. If address is correct, collect traces and reboot

3310=IFM_MOVE_NON_EXISTENT_DESTINATION

"Destination address does not exist"

SFL: 1) No FRU




3311=IFM_MOVE_DESTINATION_FULL

"Destination address is occupied"

SFL: No FRU

Isolation Procedure

1. Check destination addressNote: If SCSI address, addresses are shifted by number of reserved cells.

2. If address is correct, collect traces and reboot

3312=IFM_MOVE_GET_FAIL

"Get failed"

SFL: Unknown


1. Collect logs

print log <all>

2. Find the result code IFM_MOVE_GET_FAIL in the logs and get the failing address

3. Turn on diagnostic traces

trace diag on

4. Issue diagnostic command diaggetput using the address retrieved from the logs in the sourceaddress of the diagnostic command.

diaggetput cellToCell <source addr> <destination addr> 5 nonsilent

5. If diagnostic pass, collect logs and write a pinnacle. If diagnostics fail, use the diagnostic error codeto continue the investigation

print log <all>

3313=IFM_MOVE_PUT_FAIL

"Put failed"

SFL: Unknown


1. Collect logs

print log <all>

2. Find the result code IFM_MOVE_PUT_FAIL in the logs and get the failing address


trace diag on






print log <all>

3314=IFM_MOVE_LOAD_FAIL

"Drive load failed"

SFL: 1) Drive 2) Firmware


1. Collect logs

print log <all>

2. Find the result code IFM_MOVE_LOAD_FAIL in the logs and get the failing address


trace diag on




print log <all>

3315=IFM_MOVE_UNLOAD_FAIL

"Drive unload failed"



1. Check cartridge visibly. Did the cartridge eject past the cartridge present sensor?

If it did, try pushing cartridge back into drive.

Issue get status command and check for cartridge seated & present

2. If cartridge is not seated & present, replace drive



3316=IFM_MOVE_DRIVE_NOT_PRESENT

"Drive not present"

SFL: 1) Drive 2) RLC 3) Firmware


1. Check address of drive, if correct continue

2. Visibly check for drive, if present continue

3. Visibly check that drive bezel is still in place, if present continue

4. Activate traces for the drive in question

trace drive–tti-xx on (xx is the drive id)

trace tti-dbg-xx on (xx is the drive id)

5. Initialize drive


If not HP drive, pull drive out, wait 10 seconds, put it back in. Note: In fullypopulated library the wait could be up to 20 seconds.

6. Issue command to get drive state

drive <addr> state

7. If command fails, insert a different drive


drive <addr> state

9. If problem goes away, drive was bad

If problem persists, replace RLC

3317=IFM_MOVE_BAD_DRIVE_STATE

"Bad drive state for move"

SFL: 1) Drive Assy 2) Firmware





2. Initialize drive


If not HP drive, pull drive out, wait 10 seconds, put it back in. Note: In fullypopulated library the wait could be up to 20 seconds.

3. Issue command to get drive state, if command fails replace drive

drive <addr> state



3318=IFM_MOVE_MEDIA_ERROR

"Media error"

SFL: 1) Media 2) Drive 3) Firmware


1. Move cartridge to another drive

move <source addr> <dest addr>

2. If problem persists, replace the cartridge, else continue

3. Issue command drive get status and check to see if drive needs cleaning

drive <addr> state

4. Clean drive if indicated

5. Try another cartridge in original drive, if problem persists, replace drive

3319=IFM_MOVE_SOURCE_CAP_OPEN

"Source location cap open"

SFL: 1) No FRU – Close CAP door 2) CAP Sensor


1. Visually check CAP doors for an open door.

If CAP door was open, close it and retry operation.

2. Press each CAP door

If you here a click the door was not closed. Retry operation.

If you don’t here a click, continue to Step 3.

3. Run CAP diagnostics

diagcaps

If diagnostics fail, then replace the CAP sensor indicated

If diagnostics don’t fail, collect logs and write a pinnacle

3320=IFM_MOVE_DESTINATION_CAP_OPEN

"Destination location cap open"

SFL: 1) No FRU – Close CAP door 2) CAP Sensor


1. Visually check CAP doors for an open door.

If CAP door was open, close it and retry operation.

2. Press each CAP door



If you here a click the door was not closed. Retry operation.

If you don’t here a click, continue to Step 3.

3. Run CAP diagnostics

diagcaps

If diagnostics fail, then replace the CAP sensor indicated

If diagnostics don’t fail, collect logs and write a pinnacle

3321=IFM_MOVE_RESERVE_FAIL

"Failure during reservation"

SFL: 1) Firmware


1. Check address

2. Visibly verify that there is really a conflict

If no conflict recheck address, remember to take reserved cells into account when addressis SCSI

If still no conflict, collect traces, continue

If conflict continue

3. Issue reboot command

reboot

3322=IFM_MOVE_CART_IN_HAND

"Cartridge in hand"



1. Collect logs

2. Scan for error IFM_MOVE_CART_IN_HAND

3. Once error is found, look back in time for INOP indication.

4. Once INOP condition is found, determine source of INOP condition and attempt to clear .

3323=IFM_MOVE_SOURCE_CAP_MAGAZINE_MISSING

"Source location cap magazine missing"

SFL: 1) CAP Magazine


1. Open all CAP doors configured as I/O

2. Verify visually all CAP magazines are present.



If all are present, replace CAP magazine indicated as missing.

If one or more CAP magazines in missing, insert missing magazines

3324=IFM_MOVE_DESTINATION_CAP_MAGAZINE_MISSING

"Destination location cap magazine missing"

SFL: 1) CAP Magazine


1. Open all CAP doors configured as I/O

2. Verify visually all CAP magazines are present.

If all are present, replace CAP magazine indicated as missing.

If one or more CAP magazines in missing, insert missing magazines

3325=IFM_SOURCE_DRIVE_NOT_AVAILABLE

"Source drive requested is not available"

SFL: 1) Drive 2) Robotic (serial port)

Isolation Procedure: See result code 3326 for Isolation Procedure

3326=IFM_DEST_DRIVE_NOT_AVAILABLE

"Destination drive requested is not available"

SFL: 1) Drive 2) Robotic (serial port)





2. Initialize drive


If not HP drive, pull drive out, wait 10 seconds, put it back in. Note: In fully populated library thewait could be up to 20 seconds.


drive <addr> state

4. Issue command to get drive info, if command fails replace drive

drive <addr> info

5. Issue command to get drive config, if command fails replace drive

drive <addr> getconfig



6. Issue command to set drive config, if command fails replace drive

drive <addr> setconfig

7. Issue command to load drive, if command fails replace drive


8. Deactivate traces for the drive in question

trace drive–tti-xx off (xx is the drive id)

trace tti-dbg-xx off (xx is the drive id)

9. If problem persists replace robotic assy

3327=IFM_DIAG__NO_CARTRIDGE_AVAILABLE

"No cartridge available for diagnostic use"

SFL: 1) Tape Cartridge 2) Firmware


1. Check for cartridge

2. Issue cartridge print command

cartridge print

3. If cartridge list is empty, insert cartridge

4. Reissue diagnostic command.

5. If error re-occurs, Firmware at fault

6. Collect logs, write pinnacle

3328=IFM_DIAG__NO_DIAGNOSTIC_CARTRIDGE_AVAILABLE

"No diagnostic cartridge available or not in reserved cell location"



1. Check for diagnostically labeled cartridge


cartridge print

3. Verify diagnostically labeled tape is present

If not present, enter diagnostic cartridge and retry diagnostic.

If present, continue to Step 4.

4. Verify diagnostic tape is in reserved cell location. Issue reserved print command to show library’scurrent reserved cell count.

reserved print

5. Verify diagnostic tape is in the reserved cell location.



If the diagnostic tape is not within the reserved cell locations, then move it to an emptyreserved cell location and retry the diagnostic.

If the diagnostic tape is within the reserved cell location collect the logs, write a pinnacle

3329=IFM_DIAG__CARTRIDGE_IS_NOT_DIAGNOSTIC_CARTRIDGE

"Not a diagnostic cartridge or not in reserved cell location"



1. Check for diagnostically labeled cartridge


cartridge print

3. Verify diagnostically labeled tape is present

If not present, enter diagnostic cartridge and retry diagnostic. Or choose a diagnosticcartridge and retry diagnostic

If present, continue to Step 4.

4. Verify diagnostic tape is in reserved cell location. Issue reserved print command to show library’scurrent reserved cell count.

reserved print

5. Verify diagnostic tape is in the reserved cell location.

If the diagnostic tape is not within the reserved cell locations, then move it to an empty reservedcell location and retry the diagnostic.

If the diagnostic tape is within the reserved cell location collect the logs, write a pinnacle

3330=IFM_DIAG__NO_CARTRIDGE_AT_THIS_LOCATION

"No cartridge at this location"



1. Check for cartridge at location specified in diagnostic command


cartridge print

3. Verify tape cartridge is present at location specified

If not present, choose another cartridge from cartridge list generated in Step 2.

If present collect logs and write a pinnacle.



3331=IFM_DIAG__CARTRIDGE_IS_NOT_CORRECT_TYPE (HP only)

"Cartridge is not correct type"



1. Verify cartridge selected in not a cleaning cartridge

2. Issue “cartridge print” command

cartridge print

If cartridge is a cleaning cartridge then select another

If cartridge selected in not a cleaning cartridge collect the logs and write a pinnacle.

3332=IFM_DIAG__NO_EMPTY_DESTINATION_CELL_FOUND

"No empty destination cell found"

SFL: 1) No empty cell available 2) Firmware


1. Remove a cartridge from the library

2. Retry diagnostic. If error persists, collect logs and write pinnacle

3333=IFM_DRIVE_GET_CONFIG_FAILED

"Get Drive Configuration Failed"

SFL: 1) Drive Assy 2) Firmware



“trace drive –tti-xx” (xx is the drive id)

“trace tti-dbg-xx (xx is the drive id)

2. Issue “drive <addr> state”

If the drive state command fails then issue drive <addr> reset

3. Once reset, issue the “drive <addr> state” command again

If the drive state command fails then pull the drive out and put in back into the library.

4. Issue “drive <addr> state” again

If command fails then replace the drive assembly.

If command succeeds no further Isolation required

3334=IFM_INCOMPATIBLE_CART_FOR_DRIVE

"Source cartridge is incompatible with destination drive"



SFL: No FRU

Isolation Procedure: Verify cartridge and drive type.

3335=IFM_DRIVE_CLEANING

"This drive is currently executing a drive clean"

SFL: No FRU

Isolation Procedure: Retry operation after drive cleaning is complete.

3336=IFM_INCOMPATIBLE_CART_FOR_MOVE

"Cartridge move is restricted for this cartridge type."

SFL: No FRU


1. Check cartridge type

2. If type is correct for desired move, collect traces and escalate.

3. Otherwise use different cartridge for move

3337=IFM_NO_CAPATIBLE_CLEAN_CARTRIDGE

"No compatible cleaning cartridge for this drive type."

SFL: No FRU

Isolation Procedure: Add compatible cleaning cartridge to library

3338=IFM_CLEAN_CARTRIDGE_EXPIRED

"Cleaning cartridge has expired."

SFL: 1) Cleaning cartridge

Isolation Procedure: Replace cleaning cartidge

3339=IFM_EMPTY_CAP_CELL_NOT_FOUND

"No empty CAP cells remain."

SFL: No FRU

Isolation Procedure: Remove cartridges from load port



3340=IFM_CART_IS_NOT_CLN_OR_DIAG

"Selected cartridge is not a cleaning or diagnostic cartridge."

SFL: No FRU

Isolation Procedure: Select a cleaning or diagnostic cartridge and retry command

3341=IFM_DIAG__ONE_OR_MORE_CORNERS_SKIPPED (Sun Only)

"Corners Test Failed One Or More Corners Occupied"

SFL: No FRU

Isolation Procedure: No action required. The diagnostic passed but, is indicating that one or more cornerscontains a cartridge and the diagnostic cartridge cannot be moved to the occupied corner(s).

3342=IFM_DIAG__CAP_CELL_SKIPPED (Sun Only)

"All CAP Cells Occupied, Skipped Test"

SFL: No FRU

Isolation Procedure: No action required. The diagnostic passed but is indicating that it could not move adiagnostic cartridge to a CAP location.

3343=IFM_DIAG__ONE_OR_MORE_DRIVES_SKIPPED (Sun Only)

"All Drives Test Failed One Or More Drives Occupied"

SFL: No FRU

Isolation Procedure: No action required. The diagnostic passed but is indicating that one or more of thedrives contains a cartridge and cannot participate in the test.



Chapter 5:DIAGNOSTIC Errors

Note: Any diagnostic failure will leave the library in the maintenance mode. Only a successful diagnosticcompletion (from any diagnostic) will clear the maintenance mode library state.

3500=DIAGNOSTIC_FAILED

"Unexpected error"

SFL: 1) Firmware


1. Collect logs

2. Rerun the diagnostics

If diagnostics fail as before, reboot

If diagnostics pass, transient error condition

3501=DIAGNOSTIC_ODS_INVALID_INSTANTIATION

"Diagnostic InProgress object invalid"

SFL: 1) Firmware


1. Collect logs




3502=DIAGNOSTIC_ALREADY_INPROGRESS

"Diagnostic already in progress"

SFL: 1) Firmware (only if condition persists)


1. Diagnostic may already be in progress from another login

2. Issue diagstop if you suspect another diagnostic is in progress. Or wait twenty to thirty minutesbefore re-issuing the diagnostic command.

Note: The diagstop command only terminates a diagnostic at the end of a diagnostic iteration.The diagnostic self test may take a long time to finish a diagnostic iteration as all drives aretested.

3. If the error persists, collect the logs and reboot the library.



3503=DIAGNOSTIC_UNABLE_TO_GET_OBJECT

"Unable to get diagnostic InProgress object"

SFL: 1) Firmware


1. Collect logs




3504=DIAGNOSTIC_UNABLE_TO_CHANGE_LIBRARY_STATE

"Unable to put library into maintenance mode"

SFL: Unknown


1. Collect logs




3505=DIAGNOSTIC_THREAD_CREATION_FAILED

"Diagnostic thread creation failed"

SFL: 1) Firmware


1. Collect logs

2. Reboot library.

3506=DIAGNOSTIC_PROC_FILE_OPEN_FAILURE

"Unable to open file in proc filesystem"

SFL: 1) Power Supply 2) RLC 3) Firmware

Isolation Procedure: See result code 3512

3507=DIAGNOSTIC_PROC_SERVO_FAILED

"Proc file indicates servo failure"



SFL: No FRU

Isolation Procedure: None, result code no longer used.

3508=DIAGNOSTIC_PROC_SERVO_CNTL_STATUS_FAILED

"Proc file indicates servo control status failure"

SFL: No FRU


3509=DIAGNOSTIC_PROC_DRIVE_FAILURE

"Proc file indicates drive failure"

SFL: No FRU


3510=DIAGNOSTIC_PROC_RTC_FAILED

"Proc file indicates real time clock battery failure"

SFL: 1) Battery 2) Firmware


1. Replace the battery

2. Execute the diagnostic command “diagquery basicHealth 1 nonsilent”

If the diagnostic fails with the same result code, proceed to Step 3

If the diagnostic fails with a different result code, go to the Isolation Procedure for that resultcode.

If the diagnostic passes, problem resolved

3. Collect the traces

4. Reboot library

5. Rerun the diagnostic command “diagquery basicHealth 1 nonsilent”

If problem persists, try another battery

If diagnostic passes, problem resolved.

3511=DIAGNOSTIC_PROC_FPGA_FAILURE

"Proc file indicates FPGA failure"

SFL: No FRU




3512=DIAGNOSTIC_PROC_FILE_EMPTY

"Reading the proc file returned a NULL"

SFL: 1) Power Supply 2) RLC 3) Firmware


1. Verify all Library Modules have power.

Note: All modules must have power at boot up.

2. If one (or modules) does not have power, replace the failed power supply(s), reboot and rerun thediagnostic

If problem persists, go to Step 3

If diagnostic passes, problem resolved

3. Replace RLC, reboot library, rerun diagnostic

If problem persists, escalate


3513=DIAGNOSTIC_PROC_FILE_TOKEN_MISSING

"NULL returned when token was expected"

SFL: 1) Firmware


1. Collect traces

2. Rerun diagnostics

If problem persists, reboot

If diagnostics pass, intermittent problem encountered.

3. Reboot library



If diagnostics pass, intermittent problem encountered.

3514=DIAGNOSTIC_SYSTEM_MODULE_NOT_PRESENT

"System module not found"

SFL: 1) Firmware, RLM, RLC


1. Retry the diagnostic



If diagnostic passes, transient failure, your done.

If diagnostic fails, continue

2. Reboot the library

3. Retry the diagnostic, if failure persists, replace the RLC

4. Reboot the library

5. Retry the diagnostic, if failure persists, replace the RLM

3515=DIAGNOSTIC_ROBOT_NOT_PRESENT

"Robot not present"

SFL: 1) Robot 2) RLC 3) Firmware


1. Collect logs

2. Visually check for Robot presence

If robot is missing, replace

If robot is there, replace RLC

3. Reboot library

4. Rerun diagnostic

If diagnostic fails, collect traces, escalate

If diagnostic pass, problem resolved

3516=DIAGNOSTIC_IDCARD_NOT_PRESENT

"IDCARD not present"

SFL: 1) IDCARD 2) RLC 3) Firmware


1. Visually check for IDCARD

If IDCARD is missing, replace

If IDCARD is there, replace RLC

2. Reboot library

3. Rerun diagnostic

If diagnostic fails, collect traces, escalate


3517=DIAGNOSTIC_RLC_MASTER_ENABLE_ERROR

"RLC master enable error detected"



SFL: 1) RLC 2) Firmware


1. Collect logs

2. Reboot library

3. Rerun diagnostic

If diagnostic fails, collect traces, replace RLC


4. Reboot library

5. Rerun diagnostic

If diagnostic fails, escalate


3518=DIAGNOSTIC_BRAKE_FAULT_DETECTED

"Control Status: brake fault detected"

SFL: 1) RLC 2) Robot 3) RLM


3519=DIAGNOSTIC_12V_POWER_NOT_OK

"Control Status: 12v Power not ok"



3520=DIAGNOSTIC_SERVO_VOLTAGE_LOW

"Control Status: servo voltage low"



3521=DIAGNOSTIC_CABLE_SLACK

"Control Status: cable slack"





3522=DIAGNOSTIC_REACH_SAFE

"Control Status: reach safe error"



3523=DIAGNOSTIC_PROX_DETECT

"Control Status: proc detect error"



3524=DIAGNOSTIC_GRIP_FAULT

"Grip fault detected"



3525=DIAGNOSTIC_GRIP_PHASE_ERROR

"Grip phase error detected"



3526=DIAGNOSTIC_GRIP_HALL_ERROR

"Grip phase error detected"



3527=DIAGNOSTIC_GRIP_AMP_ENABLE_ERROR

"Grip amp enable error detected"





3528=DIAGNOSTIC_WRIST_FAULT

"Wrist fault detected"



3529=DIAGNOSTIC_WRIST_PHASE_ERROR

"Wrist phase error detected"



3530=DIAGNOSTIC_WRIST_HALL_ERROR

"Wrist phase error detected"



3531=DIAGNOSTIC_WRIST_AMP_ENABLE_ERROR

"Wrist amp enable error detected"



3532=DIAGNOSTIC_REACH_FAULT

"Reach fault detected"



3533=DIAGNOSTIC_REACH_PHASE_ERROR

"Reach phase error detected"



3534=DIAGNOSTIC_REACH_HALL_ERROR



"Reach phase error detected"



3535=DIAGNOSTIC_REACH_AMP_ENABLE_ERROR

"Reach amp enable error detected"



3536=DIAGNOSTIC_TRACK_FAULT

"Track fault detected"



3537=DIAGNOSTIC_TRACK_PHASE_ERROR

"Track phase error detected"



3538=DIAGNOSTIC_TRACK_HALL_ERROR

"Track phase error detected"



3539=DIAGNOSTIC_TRACK_AMP_ENABLE_ERROR

"Track amp enable error detected"



3540=DIAGNOSTIC_Z_FAULT



"Z fault detected"



3541=DIAGNOSTIC_Z_PHASE_ERROR

"Z phase error detected"



3542=DIAGNOSTIC_Z_HALL_ERROR

"Z phase error detected"



3543=DIAGNOSTIC_Z_AMP_ENABLE_ERROR

"Z amp enable error detected"



1. Collect logs

2. Find the diagnostic result code in the Log Error log file.

Once found, scan backwards in the log looking for a 5XXX result code

If a 5XXX result code is found, use the 5XXX isolation procedure

If no 5XXX result code is found continue with the procedure below.

3. Rerun the diagnostic

If diagnostic fails, reboot library (step 3)

If diagnostic passes, intermittent problem

4. Reboot library


If diagnostic fails, replace RLC


6. Reboot


If diagnostic fails, put original RLC back into library, replace Robot




8. Reboot


If diagnostic fails, put original Robot back into lilbrary, replace RLM


10. Reboot


If diagnostic fails, escalate


3544=DIAGNOSTIC_DRIVE_NOT_PRESENT

"Drive not present"

SFL: 1) Drive 2) RLC 3) RLM


1. Collect logs

2. Verify drive is present visibly.

If drive present, reboot

If drive is missing, replace drive, reboot

3. Rerun diagnostic

If problem persists, put back original drive into library and replace RLC


4. Reboot.

5. Rerun diagnostic

If problem persists, put back original RLC into library and replace RLM


6. Reboot.

7. Rerun diagnostic



3545=DIAGNOSTIC_DRIVE_FAN_FAILURE

"Drive fan failure detected"

SFL: 1) DRIVE 2) RLC 3) RLM




1. Collect logs

2. Verify fan has failed visibly

3. If fan has stopped, replace Drive assy.

Note: Fan maybe running below threshold

4. If fan is running, rerun the diagnostic

If problem persists, replace drive assy

If diagnostics pass, problem resolved

5. Reboot


If problem persists, put original drive assy into library, replace RLC


7. Reboot


If problem persists, put original RLC into library, replace RLM


9. Reboot




11. Collect logs

3546=DIAGNOSTIC_DRIVE_FAULT_LED_ACTIVE

"Drive fault LED active"

SFL: 1) Drive Assy 2) RLC 3) Firmware


1. Verify drive fault LED is active

If LED is active, replace drive

IF LED is not active, check drive state

2. Issue drive <addr> state command

If state indicates a fault or not present condition, replace the drive

If state is online, reboot the library.

3. Reboot library

4. Verify drive fault LED is off

If fault LED is on, replace the drive

If fault LED is off, rerun diagnostic – if diagnostic fails then escalate.



3547=DIAGNOSTIC_NO_FUNCTIONAL_DRIVE_FOUND

"No functional drive found"



1. Verify visibly that all drives have their fault light active.

If one or more drives do not have there fault LEDs on, continue to Step 2

If all drives have their fault LEDs active, replace Drive(s), continue to Step 2

2. Reboot library

3. Rerun diagnostic



3548=DIAGNOSTIC_DOOR_SENSOR_FAILURE_DOOR_OPEN

"Door sensor failure: Door open"

SFL: 1) Door Sensor 2) RLC 3) Firmware


1. Verify Door state (open/closed)

If closed, replace door sensor

If open, close door and wait for audit to complete.

2. Rerun diagnostic (The diagdoor diagnostic may have timed out waiting for the door to be closed)



3549=DIAGNOSTIC_DOOR_SENSOR_FAILURE_DOOR_CLOSED

"Door sensor failure: Door closed"

SFL: 1) Door Sensor 2) RLC 3) Firmware


1. Verify Door state (open/closed

If open, replace door sensor

If closed, rerun diagnostic (The diagdoor diagnostic may have timed out waiting for the door tobe opened.)

2. Rerun diagnostic





3550=DIAGNOSTIC_DOOR_OPEN_LED_FAILURE_LED_SHOULD_BE_ON

"Door Open LED Failure: LED should be on"

SFL: 1) Door LED 2) RLC 3) Firmware


3551=DIAGNOSTIC_DOOR_OPEN_LED_FAILURE_LED_SHOULD_BE_OFF

"Door Open LED Failure: LED should be off"

SFL: 1) RLC 2) Firmware


1. Rerun diagnostic

If problem persists, go to Step 2

If diagnostic passes, problem resolved (diagnostic may have timed out on original run)

2. Reboot library

3. Rerun diagnostic

If problem persists, replace RLC, go to Step 4


4. Reboot

5. Rerun diagnostic



3552=DIAGNOSTIC_DOOR_OPEN_LED_FAILURE_LED_NOT_ON_OR_FLASHING"Door Open LED Failure: LED should be on or flashing"



3553=DIAGNOSTIC_DOOR_OPEN_LED_FAILURE_LED_NOT_FLASHING

"Door Open LED Failure: LED should be flashing"



1. Rerun diagnostic

If problem persists, replace door LED



If diagnostic passes, problem resolved (diagnostic may have timed out on original run)

2. Reboot library

3. Rerun diagnostic



4. Reboot

5. Rerun diagnostic



3554=DIAGNOSTIC_UNABLE_TO_RETURN_LIBRARY_TO_READY

"Unable to return library to ready state."

SFL: 1) Firmware


1. Collect logs

2. Reboot library

3. Rerun diagnostic (any diagnostic)



3555=DIAGNOSTIC_UNABLE_TO_CLEAR_DIAG_IN_PROGRESS_FLAG

"Unable to clear the diagnostic in progress flag."

SFL: 1) Firmware


1. Collect logs

2. Reboot library

3. Rerun diagnostic (any diagnostic)



3556=DIAGNOSTIC_TIME_OUT

"Diagnostic Timed Out."

SFL: No FRU



Isolation Procedure: Result code not used.

3557=DIAGNOSTIC_CAP_SENSOR_FAILURE_CAP_OPEN

"CAP sensor failure: CAP open"

SFL: Not used


3558=DIAGNOSTIC_CAP_SENSOR_FAILURE_CAP_CLOSED

"CAP sensor failure: CAP closed"

SFL: Not used

3559=DIAGNOSTIC_CAP_OPEN_LED_FAILURE_LED_SHOULD_BE_ON

"CAP Open LED Failure: LED should be on"

SFL: CAP Sensors, Load Port latch, RLC


1. Collect logs


3. If diagnostics fail, verify that at least 1 load port is configured for I/O

If no load ports are configured for I/O, configure at least one load port for I/O, retry diagnostic

If there is at least one load port configured for I/O. Watch the robot open the load port. Doesthe load port open? If not check load port latch. If the load port opens, replace the RLC.

3560=DIAGNOSTIC_CAP_OPEN_LED_FAILURE_LED_SHOULD_BE_OFF

"CAP Open LED Failure: LED should be off"

SFL: CAP Sensors, RLC


1. Verify all load ports are closed.

If one or more load ports is not closed, please close load ports and rerun the diagnostic

If all load ports are closed, continue


If diagnostics fail as before, replace CAP sensor.


If error persists, replace the RLC



3561=DIAGNOSTIC_CAP_OPEN_LED_FAILURE_LED_NOT_ON_OR_FLASHING"CAP Open LED Failure: LED should be on or flashing"

SFL: CAP Sensors, LED, RLC


1. Collect logs


3. If diagnostics fail, verify that at least 1 load port is configured for I/O


If there is at least one load port configured for I/O. Watch the robot open the load port. Doesthe load port open? If not check load port latch. If the load port opens, replace the RLC.

3562=DIAGNOSTIC_CAP_OPEN_LED_FAILURE_LED_NOT_FLASHING

"CAP Open LED Failure: LED should be flashing"

SFL: CAP Sensor, LED, RLC


1. Collect logs


If diagnostics fail, verify that at least 1 load port is configured for I/O


If there is at least one load port configured for I/O. Watch the robot open the load port. Does theload port open? If not check load port latch. If the load port opens, replace the RLC.

3563=DIAGNOSTIC_CAP_INFO_UNAVAILABLE

"CAP Info Unavailable to Diagnostics"

SFL: Firmware


1. Collect logs



3. Rerun diagnostic, If error persists, escalate.

3564=DIAGNOSTIC_CAP_SENSOR_FAILURE_CAP_1_OPEN



"CAP sensor failure: CAP 1 open"

Note: See result code 3569















SFL: 1) CAP Sensor 2) Firmware


1. Verify all CAP doors are closed.

If one or more CAP doors is open then close all open CAP doors and wait for audit to finish

If all CAP doors are closed, replace CAP sensor for door indicated


If diagnostics pass (with new sensor), your done.

If diagnostics pass, (without new sensor) transient error condition. (CAP door may have been leftopen to long during test.)

If diagnostics fail with message – “CAP Door State is not closed, diagnostics will not start. Oneor more CAP doors is open or CAP Audit is in progress.” If an audit is in progress, please waituntil audit is done and retry command. If an audit is not in progress, replace the sensor indicated.

3570=DIAGNOSTIC_CAP_SENSOR_FAILURE_CAP_1_CLOSED

"CAP sensor failure: CAP 1 closed"


















SFL: 1) CAP sensor 2) Firmware


1. Rerun the diagnostic (make sure none of the CAP doors are obstructed.)

If diagnostic passes, your done

If diagnostic fails, continue

2. Verify CAP door indicated is closed.

If the indicated CAP door is closed then check the door latch. If it is to stiff, replace or adjust it.

If the indicated CAP door is open, replace the sensor.


If diagnostics pass (with new sensor), your done.

If diagnostics pass, (with adjusting/replacing the latch) your done

If diagnostics fails, collect traces

3576=DIAGNOSTIC_POWER_SUPPLY_MODULE_1_SUPPLY_1_FAILED

"Power Supply Failure: Module 1, Supply 1"



SFL: 1) Power Supply 2) Power Cord 3) Firmware


1. Verify power supply cord is seated properly

If cord is not seated properly then connect power cord and verify power supply is active

If cord is seated properly then replace power supply indicated by result code and verify powersupply is active.















































3588=DIAGNOSTIC_POWER_SUPPLY_MODULE_4_SUPPLY_1_DEGRADED

"Power Supply Degraded: Module 4, Supply 1"



3589=DIAGNOSTIC_POWER_SUPPLY_MODULE_4_SUPPLY_2_DEGRADED

"Power Supply Degraded: Module 4, Supply 2"





Chapter 6:LIBRARY Miscellaneous

3700=LIBRARY_SYSTEM_RESOURCE_FAILURE

"Library system resource failed"

SFL: 1) Firmware


1. Collect traces

2. Reboot library

3701=LIBRARY_UNABLE_TO_MOVE_CARTRIDGE_TO_SOURCE

"Library unable to move cartridge to source"

SFL: 1) Robot Assy 2) Missing CAP Magazine 3) Firmware


1. Open door

2. Check the hand

3. If destination is magazine, verify magazine is correctly seated

4. If destination is drive, check drive bezel, replace if fallen off

5. Check cartridge

If well in hand, close door and reboot

If cartridge is not well in hand, remove cartridge

6. reboot

3702=LIBRARY_CARTRIDGE_IN_HAND

"Library cartridge in hand"

SFL: 1) Robot Assy 2) Magazine (not sitting correctly) 3) Firmware


1. Open door

2. If destination is magazine, verify magazine is correctly seated

3. If destination is drive, check drive bezel, replace if fallen off

4. Check cartridge

If well in hand, close door and reboot



If cartridge is not well in hand, remove cartridge

5. reboot

3703=LIBRARY_THREAD_FAILED

"Library thread failed"

SFL: 1) Firmware


3704=LIBRARY_THREAD_WAIT_FAILED

"Library thread wait failed"

SFL: 1) Firmware


3705=LIBRARY_THREAD_CREATION_FAILED

"Library thread creation failed"

SFL: 1) Firmware


1. Collect traces

2. Reboot library

3706=LIBRARY_UNABLE_TO_PARK_ROBOT

"Library unable to park robot"

SFL: Robot


1. Open door

2. Look for obstruction

Cartridge may be to far out

Cartridge may be loose in the hand (remove)

3. Reboot

3707=LIBRARY_INIT_FAILED__MESSAGE_TO_DIRECTOR_FAILED

"Library initialization failed to send message to Director "

SFL: 1) Firmware




1. Collect traces

2. Reboot

3708=LIBRARY_INIT_FAILED__DIRECTOR_RESPONSE

"Library initialization failed, Director response unsuccessful"

SFL: 1) Robot


1. Open door

2. Look for obstruction


Cartridge may be loose in the hand (remove)

3. Reboot

3709=LIBRARY_INIT_FAILED__MODIFYING_ELEMENT_MAP

"Library initialization failed modifying element map"

SFL: 1) Firmware


1. Collect traces

2. Reboot

3710=LIBRARY_INIT_FAILED__INIT_OF_CELLDB_FAILED

"Library initialization failed, CELLDB init failed"

SFL: 1) Firmware


1. Verify SCSI/FIBRE interface is configured correctly

2. Collect traces

3. Reboot

3711=LIBRARY_INIT_FAILED__MESSAGE_TO_HOST_PROCESS

"Library initialization failed, message to host process failed"

SFL: 1) Interface card 2) Firmware




1. Verify SCSI/FIBRE interface is configured correctly

2. Verify interface card is seated

3. Collect traces

4. Reboot

3712=LIBRARY_INIT_FAILED__AUDIT_FAILED

"Library initialization failed, audit failed"

SFL: 1) Robot 2) Missing Magazine


1. Open door

2. Verify that every CAP configure as storage has a magazine

3. Visually check for obstructions


Foreign object may be on floor

4. Check error logs for indication of missing magazine

5. Watch audit

If camera light is continuously on, replace robotic assy

If camera light is continuously off, replace robotic assy

If camera light blinks erratically, replace robotic assy

6. Collect logs

7. Reboot

3713=LIBRARY_INIT_FAILED__CONFIGURATION_VERIFICATION_FAILED"Library initialization failed, configuration failed"

SFL: 1) Power Supply 2) Cables


1. Open door

2. Verify no obstructions

3. Verify all power supplies are active ( No module should be without power)

4. Verify all cables are connected correctly

5. Reboot

3714=LIBRARY_INIT_FAILED__OPEN_CAPS



"Library initialization failed, open CAPS"

SFL: 1) CAP Magazine 2) Firmware


1. Open CAP doors

2. Insert CAP magazine

3. Reboot

3715=LIBRARY_INIT_FAILED__HARPOON_COUNT

"Library initialization failed, incorrect Harpoon card count"

SFL: 1) Harpoon 2) IM Card 3) Firmware


1. Verify all Harpoon cards are plugged in & powered

2. Verify you have enough Harpoon cards. One Harpoon per 4 drives.

3716=LIBRARY_INIT_FAILED__HAND_STILL_FULL

"Library initialization failed, hand still full"

SFL: No FRU


1. Verify an empty cell in a CAP magazine is available

If none available, create one, reboot

2. Check robotics, get cartridge out of hand if possible, reboot

3717=LIBRARY_INIT_FAILED__ROBOT_INIT_FAILED

"Robot initialization failed"

SFL: Robot


1. Reboot the library, if error continues then replace the robot.

3718=LIBRARY_INIT_FAILED__LAST_ROW_POSITION_ACCESS

"Robot initialization failed"

SFL: 1) Robot




1. Verify result code was output as an ERROR, if so proceed

2. Check library for obstructions

3. Verify tray is level

4. Verify library is level

5. Verify tray reaches bottom of library (verify tray does not catch or snag on way down)

6. If all of above conditions are good, replace robot

3719=LIBRARY_INIT_FAILED__PROCFS_REBUILD_FAILED

"Rebuild of System Module portion of Proc File System failed"

SFL: 1) Power Supply 2) rlc 3) firmware


1. Verify that all modules have power.

2. If any modules are not powered, then either add a power supply or replace the failed power supply.

3. Reboot,

4. If condition persists, then collect logs and escalate.

3720=LIBRARY_INIT_FAILED__SENSORMGR_COMM_FAILED

"Unable to communicate with Sensor Manager"

SFL: 1) firmware


1. Reboot

2. If problem persists then collect traces and escalate

3721=LIBRARY_FILE_SYSTEM_MOUNT_FAILED

"Mount Failed: All saved data and passwords may be lost"

SFL: 1) RLC 2) RLM


1. Replace RLC

2. Reboot

3. If problem persists replace RLM

4. Replace RLC with original

5. Reboot



6. If problem persists replace RLC (both RLM & RLC are now replaced)

7. Reboot

8. If problem persists then collect traces and escalate.



Chapter 7:SNMP

Note: This chapter does not apply to HP

3800=VSNMP_SOCKET_COMMAND_FAILURE

"VSnmp Socket Command Failure"

SFL: 1) Firmware


1. Reboot

2. If condition persists then collect traces and escalate

3801=VSNMP_BIND_COMMAND_FAILURE

"VSnmp Bind Command Failure"

SFL: 1) Firmware


1. Reboot


3802=VSNMP_LISTEN_COMMAND_FAILURE

"VSnmp Listen Command Failure"

SFL: 1) Firmware


1. Reboot


3803=VSNMP_CONNECT_COMMAND_FAILURE

"VSnmp Connect Command Failure"

SFL: 1) Firmware


1. Reboot




3804=VSNMP_SEND_COMMAND_FAILURE

"VSnmp SEND Command Failure"

SFL: 1) Firmware


1. Reboot


3805=VSNMP_RECV_COMMAND_FAILURE

"VSnmp RECV Command Failure"

SFL: 1) Firmware


1. Reboot


3806=VSNMP_SOCKET_UNAVAILABLE

"VSnmp Socket Not Available"

SFL: 1) -

Isolation Procedure: Not Used

3807=VSNMP_RESPONSE_NOT_FOUND

"VSnmp Response Not Available"

SFL: 1) -




Chapter 8:Service

Note: This chapter does not apply to HP

3900=SERVICE_INVALID_OP_CODE

"Service Invalid Op Code "

SFL: -


1. Invoke help for desired command

2. Verify syntax

3. Retry command

3901=SERVICE_MISSING_PARAMETER

"Service Missing Parameter "

SFL: -

Isolation Procedure: Retry command with missing parameter included.

3902=SERVICE_BAD_PARAMETER

"Service Bad Parameter "

SFL: -

Isolation Procedure: Retry command with correct parameter.

3903=SERVICE_COMMUNICATION_FAILURE

"Service Communication Failure "

SFL: 1) Firmware


1. Log off

2. Log on

3. Retry command

4. If condition persists, collect traces and escalate



3904=SERVICE_INVALID_RESP_SEQ_NUMBER

"Service Invalid Response Sequence Number "

SFL: 1) -

Isolation Procedure: Not used

3905=SERVICE_INVALID_COMMAND_IN_RESPONSE

"Service Invalid Command In Response "

SFL: 1) Firmware


1. Retry command


3906=SERVICE_RESPONSE_TIMEOUT

"Service Response From Server Timeout "

SFL: 1) Firmware


1. Retry command


3907=SERVICE_SOCKET_ERROR

"Service DCI Socket Broken "

SFL: 1) Firmware


1. Retry command

2. If condition persists, then logoff, logon, retry command

3. If condition persists, then collect traces and escalate

3908=SERVICE_INTERNAL_SW_ERROR

"Service Internal Software Error "

SFL: 1) -




3909=SERVICE_RESP_CONTENT_FAILURE

"Service Content Failure In Response String "

SFL: 1) -


3910=SERVICE_RECEIVE_CLI_SOCKET_FAILURE

"Service Receive From CLI Socket Failure "

SFL: 1) Firmware


1. Retry command



3911=SERVICE_SEND_CLI_SOCKET_FAILURE

"Service Send To CLI Socket Failure "

SFL: 1) Firmware


1. Retry command



3912=SERVICE_CLI_SOCKET_UNAVAILABLE

"Service CLI Socket Unavailable "

SFL: 1) Firmware


1. Retry command



3913=SERVICE_CLI_SNMP_RESULT_FAILURE

"Service CLI Result Failure "



SFL: 1) Firmware


1. Retry command



3914=SERVICE_PROCESS_NOT_AVAILABLE

"Service Process Not Available "

SFL: 1) -




Chapter 9:ROBOT

9.1 SRV_MECH Errors

5000=SRV_MECH_STALLED

"Mechanism stalled unexpectedly"

SFL: -

Isolation Procedure: Reason Code Not Used

5001=SRV_MECH_STALLED_ON_INIT

"Mechanism stalled unexpectedly - during initialization"

SFL: -

Isolation Procedure: Internal Software error. Should not cause INOP condition. If it does:

1. Reboot Library

2. Retry Operation

3. If error persists, check for code update

5002=SRV_MECH_OUTSIDE_STOPLOCK

"Mechanism travelled outside of it's stoplock range"

SFL: -


5003=SRV_ISR_LOGICAL_FAILURE

"The servo isr shut down due to a logical/software fault"

SFL: -


5004=ERR_SRV_UNKNOWN_REQUEST_TYPE

"An unknown type of request was received by Servo"

SFL: -




1. Reboot Library

2. Retry Operation


5005=ERR_SRV_UNEXPECTED_SYS_ERROR_RET

"Kernel/OS fault - An unexpected system return code was received by Servo"

SFL: -


5006=ERR_SRV_BAD_CHK_MOVE_CALC

"An error was encountered in performing a quick initialization move"

SFL: -


5007=ERR_SRV_DEST_OUTSIDE_OPER_RANGE

"The requested destination is not within the allowable operating range"

SFL: robot assy


1. Open door


3. Clear any obstructions found

4. Reboot library

5. If error persists, replace robot.

5008=ERR_SRV_ILLEGAL_PROFILE_TYPE

"An undefined profile type was requested"

SFL: -

Isolation Procedure: Internal software error. Does not propagate.

5009=ERR_SRV_OVERCURRENT



"An overcurrent fault was detected by the hardware"

SFL: robot assy

Isolation Procedure: This error will be intermittent to start and then happen more frequently.

1. Reboot library


5010=ERR_SRV_EXCESSIVE_POSITION_ERROR

"An excessive position error was detected during motion"

SFL: - robot assy


1. Open door



4. Reboot library


5011=ERR_SRV_TACH_PHASE_ERROR

"A tachometer phase error was detected"

SFL: robot assy

Isolation Procedure: This error will be intermittent to start and then happen more frequently.

1. Reboot library


5012=ERR_SRV_CANT_START__NOT_IN_STOPLOCK

"The requested motion cannot start because the mechanism is not in stoplock"

SFL: robot assy


1. Reboot library

2. Retry operation


5013=ERR_SRV_ISR_REENTERED

"The servo interrupt service routine was re-entered before exiting"



SFL: -


1. Reboot Library

2. Retry Operation


5014=ERR_SRV_SATURATION_CURRENT_REQUESTED_TOO_LONG

"The max or min current was requested an excessive amount of times"

SFL: robot assy


1. Open door


3. Remove any obstructions found

4. Reboot library

5. Execute diagquery basicHealth

6. If basic health good, retry operation


5015=ERR_SRV_MECH_DROPPED_OUT_OF_STOPLOCK

"The mechanism has fallen outside the allowable stoplock range"

SFL: robot assy


1. Reboot library

2. Retry operation


5016=ERR_SRV_MECH_FAILED_TO_SETTLE_INTO_STOPLOCK

"The mechanism was unable to settle into the desired stoplock window"

SFL: robot assy


1. Open door





4. Reboot library




5017=ERR_SRV_OPERATING_RANGE_OUT_OF_SPEC

"The range of motion on initialization is not within specification"

SFL: robot assy


1. Open door



4. Reboot library


5018=ERR_SRV_INVALID_THETA_Z_RANGE_COMBO

"The range of motion on arm init does not match a valid combination"

SFL: -


5019=ERR_SRV_REDEFINED_LIB_CONFIG

"The operating ranges found at arm initialization don't indicate known hardware"

SFL: - robot assy


1. Open door



4. Make sure Z mechanism flex cable is the proper length

5. Reboot library




5020=ERR_SRV_BAD_MECH_ID_IN_ISR

"The servo interrupt received a bad mechanism identifier"

SFL: -


1. Reboot Library

2. Retry Operation


5021=ERR_SRV_ILLEGAL_REQUEST_OPTION

"An illegal request option for servo was requested"

SFL: -


1. Reboot Library

2. Retry Operation


5022=ERR_SRV_FAILED_TO_ENCOUNTER_CARTRIDGE

"The hand failed to encounter a cartridge"

SFL: -


5023=ERR_SRV_FAILED_TO_DISENGAGE_CARTRIDGE

"The hand failed to dis-enagage a cartridge"

SFL: -


5024=ERR_SRV_FAILED_TO_SEAT_CARTRIDGE



"The cartridge seat sensor didn't report true after a fetch"

SFL: -


5025=ERR_SRV_FAILED_TO_UNSEAT_CARTRIDGE

"The cartridge seat sensor didn't report false after a put"

SFL: -


5026=ERR_SRV_REQUEST_ALREADY_ACTIVE_AGAINST_MECHANISM

"Motion is already active against mechanism"

SFL: -


1. Reboot Library

2. Retry Operation


5027=ERR_SRV_CANT_MOVE_ARM__HAND_IS_ACTIVE

"Arm Request rejected - hand is currently active"

SFL: -


1. Reboot Library

2. Retry Operation


5028=ERR_SRV_CANT_MOVE_HAND__ARM_IS_ACTIVE

"Hand Request rejected - arm is currently active"

SFL: -


1. Reboot Library



2. Retry Operation


5029=ERR_SRV_UNEXPECTED_RESP_AT_DISPATCHER

"The servo dispacter received an invalid response"

SFL: -


1. Reboot Library

2. Retry Operation


5030=ERR_SRV_CANT_GET_WITH_HAND_FULL

"Fetch request rejected - hand is already full"

SFL: -

Isolation Procedure: This error may be indicative of hand sensor problems

If hand has a cartridge in it

1. There may have been a prior error

2. Remove cartridge from hand, replace in cell

3. Reboot library

4. Retry operation

5. Replace robot if error persists

If hand is empty:

1. Rebot library

2. Retry operation


5031=ERR_SRV_CANT_PUT_WITH_HAND_EMPTY

"Put request rejected - hand is empty"

SFL: robot assy


If hand has a cartridge in it



1. There may have been a prior error

2. Remove cartridge from hand, replace in cell

3. Reboot library

4. Retry operation


If hand is empty:

1. Rebot library

2. Retry operation


5032=ERR_SRV_MOVE_ABORTED

"The request ended in failure due to an abort request"

SFL: -

Isolation Procedure: Not a failure. An abort was requested and the robot should still be operational.

5033=ERR_SRV_HAND_NOT_SAFE__HAND_IS_INOPERATIVE

"Hand is not safe - the hand is not operative"

SFL: robot assy


1. Open door



4. Check for cartridge in hand

5. Remove cartridge from hand if found

6. Reboot library




5034=ERR_SRV_HAND_NOT_SAFE__REACH_NOT_RETRACTED

"Hand is not safe - reach is not retracted"

SFL: robot assy




1. Open door





6. Reboot library




5035=ERR_SRV_HAND_NOT_SAFE__CARTRIDGE_IS_UNSEATED_IN_GRIP

"Hand is not safe - a cartridge is unseated in the grip"

SFL: -


1. Reboot Library

2. Retry Operation


5036=ERR_SRV_MECHANISM_NOT_INITIALIZED

"Mechanism must be initialized prior to accepting a motion command"

SFL: robot assy


1. Reboot library

2. Retry operation


5037=ERR_SRV_MECHANISM_SHUTDOWN

"Mechanism has been shut down and requires re-initialization"

SFL: robot assy


1. Check for obstructions

2. Reboot library



3. Retry operation


5038=ERR_SRV_MECHANISM_NOT_OPERATIONAL

"The mechanism is not operational"

SFL: -

Isolation Procedure: No action required. Reason code may appear prior to recovery code being invoked.

5039=ERR_SRV_USER_REQ_THETA_MOVE_FOR_SCAN

"A Z scan was requested with a theta motion too large"

SFL: -


5040=ERR_SRV_CANT_CLEAR_AMP_ENABLE

"Could not clear a bit in the amp enable register during fault processing"

SFL: robot assy


1. Power cycle the library

2. Retry operation


5041=ERR_SRV_SATURATION_CURRENT_READ_TOO_LONG

"The max or min current was read an excessive amount of times by the ADC"

SFL: robot assy


1. Open door



4. Reboot library


5042=ERR_SRV_MINIMUM_INIT_MOVE_NOT_DETECTED

"No motion detected by tachometer during mechanism initialization"



SFL: robot assy



2. Retry operation


5043=ERR_SRV_REACH_SAFE_SENSOR_FAIL

"Reach safe sensor did not report an encountered level"

SFL: robot assy



2. Retry operation


5044=ERR_SRV_REACH_GRIP_OVERCURRENT

"Overcurrent detected on gripper"

SFL: -


5045=ERR_SRV_AMP_ENABLE_FAIL

"The mechanism amplifier could not be enabled"

SFL: robot assy



2. Retry operation


5046=ERR_SRV_FAILED_STALL

"The mechanism stall point was outside of allowable tolerances"

SFL: robot assy




1. Open door





6. Reboot library




5047=ERR_SRV_FAILED_STALL__OBSTRUCTED

"The hand stall point was too close to the hand to assure good operating range"

SFL: -


5048=ERR_SRV_DEST_OUTSIDE_OPER_RANGE_ADJUSTED

"The requested destination is not within the allowable operating range"

SFL: - robot assy

Note: Non-fatal error (warning). The error if it propagates, will be fatal


1. Reboot

2. If error persists, replace robot

5049=ERR_SRV_NOT_RESPONSE_DISCARDED

"A srv_response msg was expected, but another type of msg was recvd & discarded"

SFL: -


5050=ERR_SRV_CANT_FIND_REACH_DEPTH

"Reach and touch rejected - hand is full"

SFL: -




5051=ERR_SRV_POWER_LOW_ERROR

"A low voltage condition has been detected on the servo motor power"

SFL: Door Sensor, Cabling

Note: Error occurs when software detects a door open condition.


1. Verify library door is closed

2. Reboot library

3. Retry operation

4. If error persists, check door sensors/cabling for damage. Replace as needed.

5052=ERR_SRV_REQUEST_QUEUED_TIMEOUT

"The servo module timed out waiting for a request to be queued"

SFL: -


1. Reboot Library

2. Retry Operation


5053=ERR_SRV_REQUEST_ACTIVE_TIMEOUT

"The servo module timed out waiting for a request to complete"

SFL: -


1. Reboot Library

2. Retry Operation


5054=ERR_SRV_BAD_MECH_ID_IN_COORD

"The servo coordinator received a bad mechanism identifier"

SFL: -




1. Reboot Library

2. Retry Operation


5055=ERR_SRV_SYS_MSG_ALLOC_FAIL

"Servo could not allocate a sys message"

SFL: -


1. Reboot Library

2. Retry Operation


5056=ERR_SRV_SYS_MSG_SEND_FAIL

"Servo could not send a sys message"

SFL: -


1. Reboot Library

2. Retry Operation


5057=ERR_SRV_SYS_MSG_RECV_FAIL

"Servo could not receive a sys message"

SFL: -


1. Reboot Library

2. Retry Operation


5058=ERR_SRV_SYS_MSG_BAD_SIZE



"Servo failed to validate the size of a received sys message"

SFL: -


1. Reboot Library

2. Retry Operation


5059=ERR_SRV_SYS_MSG_GET_CONTENT_FAIL

"Servo could not get the content of a received sys message"

SFL: -


5060=ERR_SRV_SYS_MSG_SET_CONTENT_FAIL

"Servo could not set the content of a allocated sys message"

SFL: -


1. Reboot Library

2. Retry Operation


5061=ERR_SRV_SYS_MSG_RELEASE_FAIL

"Servo could not release a allocated sys message"

SFL: -


1. Reboot Library

2. Retry Operation


5062=ERR_SRV_HAND_NOT_SAFE



"Hand is not safe"

SFL: -


1. Open door





6. Reboot library




5063=ERR_SRV_HAND_INIT_FAIL_NOT_EMPTY

"Could not sweep reach/grip - hand not empty"

SFL: -


5064=ERR_SRV_COORD_SEND_MECH_REQUEST_FAILED

"The servo coordinator received a bad mechanism identifier"

SFL: -


1. Reboot Library

2. Retry Operation


5065=ERR_SRV_HALL_ERROR

"A motor hall error was detected"

SFL: robot assy

Isolation Procedure: : This error will be intermittent to start and then happen more frequently.

1. Reboot library




5066=ERR_SRV_HDW_OVER_CURRENT_ERROR

"A hardware overcurrent error was detected"

SFL: robot assy


1. Power cycle library

2. Retry operation


5067=ERR_SRV_HDW_UNKNOWN_ERROR

"Hardware driver returned an unknown error"

SFL: -


1. Reboot Library

2. Retry Operation


5068=ERR_SRV_EXCESSIVE_MOTOR_HEATING

"The current in the motor is causing excessive heating"

SFL: - robot assy

Note: Non-fatal error (warning). The error if it propagates, will be fatal


1. Reboot library

2. If error persists, replace robot

5069=ERR_SRV_SAT_CURRENT_REQ_TOO_LONG_STALL_MIN_NOT_REACHED"The max or min current was requested an excessive amount of times during a stall move with a minimumposition not reached"

SFL: -


1. Check for improperly installed cartridges, arrays, cables to tight, and drives and remedy if necessary

2. Reboot library



3. Retry operation


5070=ERR_SRV_EXCESSIVE_TRACK_STRACK_RELATIVE_ERROR

"Exceeded maximum allowed position error between the track motors. Possible gear slip occurred."

SFL: -


5071=ERR_SRV_DOOR_OPEN_ERROR

"A door open condition has been detected. Amps are shutdown."

SFL: 1) Door Sensor


1. If the door is closed, check the door sensor connections. If connected then replace door sensor.

2. If door is open, then close door and retry command.

5072=ERR_SRV_COORD_SEQUENCING_FAILED

"The servo coordinator could not perform necessary move sequencing"

SFL: -




9.2 SCAN Errors

5400=SCAN_FAULT_OPEN_FAILURE

"Failure opening scanner channel"

SFL: firmware


1. Update firmware.

5401=SCAN_FAULT_POWER_UP_FAILURE

"Failed to power up scanner"

SFL: robot




5402=SCAN_FAULT_INITIALIZATION_FAILURE

"Failed to init scanner, could not get version string"

SFL: -

Isolation Procedure: Reason Code only used in unit test.

5403=SCAN_APP_RECEIVED_NO_MESSAGES

"Scanner application received no messages from driver"

SFL: -

Isolation Procedure: Not an error. Used to communicate that the scanner could not find a target/label wheninstructed to read one.

5404=SCAN_APP_TO_DRIVER_READ_TIMEOUT

"Scanner application timed out while trying to read from driver"

SFL: robot






5405=SCAN_APP_TO_DRIVER_WRITE_TIMEOUT

"Scanner application timed out while trying to write to driver”/

SFL: robot




5406=SCAN_APP_RECEIVED_LLF_NAK_FN

"Scanner returned NAK on the outgoing packet's frame number"

SFL: robot




5407=SCAN_APP_RECEIVED_LLF_NAK_CHKSUM

"Scanner returned NAK on the outgoing packet's checksum"

SFL: robot




5408=SCAN_APP_RECEIVED_LLF_BUSY

"Scanner returned message indicating packets received are being ignored"

SFL: robot




5409=SCAN_APP_RECEIVED_PACKET_WITH_BAD_CHKSUM

"Scanner application received a packet with a bad checksum"

SFL: robot






5410=SCAN_APP_RECEIVED_NR

"Scanner application received a packet with NR<CR> when expecting a label"

SFL: -

Isolation Procedure: Not an error. Reason code is returned when the scanner does not see a label whenasked to read one.

5411=SCAN_APP_BAD_STATUS

"Scanner application failed to return valid status"

SFL: robot




5412=SCAN_APP_PACKET_SIZE_TOO_LARGE

"Scanner application attempted to return too large of packet"

SFL: robot




5413=SCAN_APP_ASCII_TO_INT_PARSE_FAILURE

"Scanner application tried failed while trying to parse target data"

SFL: -


5414=SCAN_APP_LOOKING_FOR_TARGET_GOT_BARCODE

"Scanner returned a barcode but the application was looking for a target"

SFL: -




5415=SCAN_APP_RECEIVED_LINE_STATUS_ERROR_INDICATION

"Line status (Overrrun,Framing,Break,or RxFIFO) error on scanner serial channel"

SFL: robot




5416=SCAN_APP_TARGETING_DATA_TOO_SHORT

"Targeting packet received from scanner too short to contain valid data"

SFL: - robot


1. Inspect library for obstruction(s), remove if found.



Isolation Procedure: Not an error. Used to communicate that the scanner couldn’t find a target/label wheninstructed to read one.

5417=SCAN_FIRMWARE_DOWNLOAD_FAILURE

"A firmware download of the scan engine failed"

SFL: - 1) Robot

Isolation Procedure: Reboot the library, if error persists then replace the robot.

9.3 TARGET Errors

5500=BURNIN_FAULT_BAD_REQU

"The burnin module received a bad IPC message"

SFL: -




5500=TARGET_EXCEEDED_MAX_ALLOWABLE_BARS

"The camera reported more bars than are allowed in the array"

SFL: -


5501=TARGET_NOT_RECOGNIZED

"No valid target found in the target scan data from the camera"

SFL: - Isolation Procedure:

1. Check for obstructions

2. Reboot library

5502=TARGET_OFFSET_INVALID

"Target offset checking found an invalid value"

SFL: robot


1. Verify target hardware to ensure it is properly installed.



5504=TARGET_FAILED_TO_CALIBRATE_SCANNER

"The calibration of the camera for targeting failed (possible no target present as well)"

SFL: -




9.4 CMO Errors

5600=CMO_FAILED_CARTESIAN_LOOKUP_AUDIT

"Failure getting cartesian coordinate data for audit"

SFL: -


1. Reboot Library

2. Retry Operation


5601=CMO_FAILED_CARTESIAN_LOOKUP_FETCH

"Failure getting cartesian coordinate data for fetch"

SFL: -


1. Reboot Library

2. Retry Operation


5602=CMO_FAILED_CARTESIAN_LOOKUP_PUT

"Failure getting cartesian coordinate data for put"

SFL: -


1. Reboot Library

2. Retry Operation


5603=CMO_FAILED_CARTESIAN_LOOKUP_TARGET

"Failure getting cartesian coordinate data for targeting"

SFL: -




1. Reboot Library

2. Retry Operation


5604=CMO_FAILED_CARTESIAN_LOOKUP_NOMINAL

"Failure getting cartesian coordinate data for nominal move"

SFL: -


1. Reboot Library

2. Retry Operation


5605=CMO_COULD_NOT_STORE_TARGET_CALIBRATION

"Failure storing target calibration data in the database"

SFL: -


1. Reboot Library

2. Retry Operation


5606=CMO_REACH_NOT_SAFE_DETECTED

"Reach safe sensor reports not safe"

SFL: robot, sensors


1. Check for obstructions.

2. Verify that cartridge is properly in hand. If not attempt to return to original cell location

3. Perform reboot or open and close the library door.

4. Retry operation




5607=CMO_HAND_EMPTY_DETECTED

"Cartridge present sensor reports no cartridge"

SFL: robot, sensors



2. Check for cartridge not properly in hand.


4. Retry operation


5608=CMO_HAND_FULL_DETECTED

"Cartridge present sensor reports a cartridge"

SFL: robot, sensors



2. Check for cartridge in hand. If so attempt to return to original cell location


4. Retry operation


5609=CMO_FAILED_TARGET_CALIBRATION

"The camera failed to find a target"

SFL: robot


1. Check for properly installed robot


3. Retry operation


5610=CMO_FETCH_RETRY_PERFORMED

"A retry was needed to perform a fetch"

SFL: robot




1. Occurs occasionally as part of operation. Do nothing unless it occurs in large numbers

2. If reason code occurs in large numbers, replace robot after checking hardware (drives, arrays,CAPs) for defects.

5611=CMO_PUT_RETRY_PERFORMED

"A retry was needed to perform a put"

SFL: robot



2. If reason code occurs in large numbers, replace robot after checking hardware (drives, arrays,CAPs) for defects.

5612=CMO_CART_LABEL_MISCOMPARE

"The cartridge label or media type did not match the one from the controller"

SFL: cartridge


1. Verify cartridge is labeled correctly. Correct label if found to be in error.

2. If labeled correctly, verify Host information.

5613=CMO_CELL_FULL_DETECTED

"Proximity sensor reports a full cell"

SFL: -

Isolation Procedure: Does not exist on SL500

5614=CMO_CELL_EMPTY_DETECTED

"Proximity sensor reports an empty cell"

SFL: -


5615=CMO_END_OF_RAIL_ID_FAILURE

"Failed to read the End of Rail ID"

SFL: -




5616=CMO_INIT_FAILURE

"Failed initialization"

SFL: robot assy


1. Check library for obstructions. Clear obstruction if found

2. Make sure robot flex cable is extracted from robot chassis to the proper length. Not too short, not toolong.

3. Reboot the library or open and close the library door.

4. If problem persists, replace robot.

5617=CMO_FAILED_CARTESIAN_LOOKUP_PROX

"Failure getting cartesian coordinate data for audit"

SFL: -


5618=CMO_FAILED_PROX_READ

"Received a failure status when attempting to read prox sensor"

SFL: -


5619=CMO_MOVE_RETRY_PERFORMED

"A retry was needed to complete the move-arm request"

SFL: robot



2. If reason code occurs in large numbers, replace robot after checking hardware for defects andproper installation.

5620=CMO_INCONSISTENT_SUCCESS_ON_FETCH

"At the end of a fetch, success was false even though the hand had a cartridge"

SFL: robot





2. If reason code occurs in large numbers, replace robot after checking hardware for defects andimproper installation.

5621=CMO_INCONSISTENT_SUCCESS_ON_PUT

"At the end of a put, success was false even though the hand was empty"

SFL: robot



2. If reason code occurs in large numbers, replace robot after checking hardware for defects.

5622=CMO_CELL_SCAN_USED_FOR_AUDIT

"The normal audit failed to find a label so cell scan was used as a retry"

SFL: -


1. Reboot Library

2. Retry Operation


5623=CMO_DEPRECATED_POSITION_USED_TO_TARGET

"Calibration had to use a deprecated position to find a target"

SFL: -

Isolation Procedure: Not used.

5624=CMO_USED_INITIAL_TARGETED_LOCATION

"Calibration had to use the initial targeted location because the retarget at cal position failed"

SFL: robot






5625=CMO_AUDIT_LABEL_MIN_LENGTH_NOT_MET

"Audit read a label but the minimum label length of six characters was not met"

SFL: labels, robot


1. If occurs frequently, check for damaged labels. Replace label(s) if damaged one’s are found.

2. If labels look good, replace robot.

5626=CMO_FAILED_UNSET_TARGET_CALIBRATION

"Failed to unset target calibration"

SFL: -


5627=CMO_RECOVER_FOR_FETCH_PUTBACK_NOT_ATTEMPTED

"Conditions of current location and/or a non-operational robot prevented a putback"

SFL: -


5628=CMO_RECOVER_FOR_FETCH_SRV_RECOVERED_CART

"SRV recover hand for fetch succeeded in recovering cartridge"

SFL: -


5629=CMO_FAILED_HANDBOT_RANGE_GET

"Failed to get a mech's range (range not set, mech not initialized)"

SFL: -


5630=CMO_CALIBRATION_RETRY_PERFORMED

"A retry was needed to perform a calibration"

SFL: robot






5631=CMO_ROBOT_Z_RANGE_IS_SHORT

"The sweep range of Z is to short to reach all locations"

SFL: -


5632=CMO_ROBOT_TRACK_RANGE_IS_SHORT

"The sweep range of TRACK is to short to reach all locations"

SFL: -


5633=CMO_ROBOT_WRIST_RANGE_IS_SHORT

"The sweep range of WRIST is to short to reach all locations"

SFL: -


5634=CMO_INVALID_ADDRESS

"The address for a cmo operation is not valid"

SFL: -




Chapter 10:DRIVE Errors

6400=TTI_RESULT_DRIVE_CONDITION

"Drive condition"

SFL: 1) Drive Assy

Isolation Procedure: Follow procedure for result code 6408

6401=TTI_RESULT_DRIVE_BUSY

"Drive busy"

SFL: 1) Drive Assy – Only if Drive is continuously busy


6402=TTI_RESULT_COMMAND_NOT_SUPPORTED

"Drive command not supported"

SFL: No FRU


1. Collect traces

6403=TTI_RESULT_FAIL_STATUS_COMMAND

"Drive failed status command"

SFL: 1) Drive Assy


6404=TTI_RESULT_UPPER_RETRY_EXCEEDED

"Upper retry limit exceeded"

SFL: 1) Drive Assy


6405=TTI_RESULT_RETRY_EXCEEDED

"Retries exceeded"

SFL: 1) Drive Assy


6406=TTI_RESULT_READ_TIMEOUT

"A TTI read timeout occurred"



SFL: 1) Drive Assy


6407=TTI_RESULT_COMM_ERROR

"Communication error occurred with the drive"

SFL: 1) Drive Assy


6408=TTI_RESULT_NO_DRIVE_ERROR

"No drive"

SFL: 1) Drive Assy





2. Initialize drive


If not HP drive, pull drive out, wait 10 seconds, put it back in.

Note: In fully populated library the wait could be up to 20 seconds.


drive <addr> state


drive <addr> info










9. Drive is ok.



6409=TTI_RESULT_WRONG_PORT_NUM

"Port number received in the response does not match the one in the request"

SFL: 1) Software





2. Initialize drive




3. Issue command to get drive state, if command fails, collect traces, replace drive

drive <addr> state




6410=TTI_RESULT_WRONG_PACKET_SIZE

"Response packet size doesn't match the packet length specified"

SFL: 1) Drive Firmware 2) Drive Assy 3) Software


1. Collect traces

2. If problem persists, reboot

6411=TTI_RESULT_FAIL_DETERMINE_INSTALLED_DRIVE

"Failed to determine what type of drive is installed"

SFL: 1) Drive Assy 2) Software


6412=TTI_RESULT_FAIL_TO_SET_HOLDOFF_LOAD

"Failed to set the drive to holdoff load mode"

SFL: 1) Drive Assy




6413=TTI_RESULT_FAIL_TO_SET_FILE_PROTECT

"Failed to set the drive to file protect mode"

SFL: 1) Drive Assy


6414=TTI_RESULT_UNKNOWN_DRIVE

"Request failed because the drive is unknown"






2. On an HP library, verify the LED associated with the Drive Fibre Channel cable is on.

If the LED is off, verify the cable is plugged in

If the LED is on, continue below.

3. Initialize drive





drive <addr> state


drive <addr> info










10. Drive is ok.

6415=TTI_RESULT_LOAD_FAIL_CART_PRESENT



"The load failed and the cartridge is still present"

SFL: 1) Drive Assy 2) Hand (robot)



drive <addr> state

2. If drive state results indicate cartridge present then issue load command

drive <addr> load

3. If load fails, open door, attempt to push cartridge in

4. Issue drive load command again

drive <addr> load

5. If load fails, attempt to manually load different cartridge


drive <addr> state

7. If drive state indicates cartridge present, issue a load command

drive <addr> load

8. If load fails, replace the drive

6416=TTI_RESULT_LOAD_FAIL_NO_CARTRIDGE

"The load failed because there is no cartridge present"



1. Open door

2. Determine where the cartridge is (Drive or Hand ?)

Cartridge in drive

a. Issue drive state command

drive <addr> state

b. Do results indicate that cartridge is not presentIBM Drive

1. Open the door, attempt to push cartridge in all the way

2. Issue drive state command

drive <addr> state

3. If results indicate that cartridge is present, replace the driveHP Drive1. If the cartridge is sitting in the throat of the drive, replace the drive (sensor is not functional)



Cartridge not in drivea. If cartridge is not in the throat, check the robotic hand

b. Manually extract it from the hand

c. Issue move from cell to drive

Move <source addr> <dest addr>

d. If cartridge doesn’t load, issue drive state command

drive <addr> state

e. If results indicate that cartridge is not present, check the hand, if cartridge is in the hand thenreplace the robot assy

f. If cartridge loads, problem resolved

6417=TTI_RESULT_DRIVE_INTERFACE_TYPE_UNKNOWN

"Drive configuration was tried, but the interface type is unknown"

SFL: 1) Drive Assy 2) Drive Firmware 3) Software





2. Initialize drive




3. Issue command drive state, if command fails

drive <addr> state

If drive is HP, repeat steps 2 & 3, but pull the drive instead of resetting it (If drive state commandfalls a second time, replace it.)

If drive is IBM, replace drive




Note: The log_error trace file should have an entry for Incompatible Drive Type.

6418=TTI_RESULT_DRIVE_UNKNOWN_CART_POSITION



"The drive tried to load the cart, but failed. Cart position in drive unknown"



1. Open door

2. Check position of cartridge visually

If stuck, try removing

If unable to remove, remove drive and remove cartridge manually

3. Issue load to drive, if load fails, replace the robot assy

drive <addr> load

4. Issue rewindunload

drive <addr> rewindunload

5. If can’t rewindunload, replace drive

6419=TTI_RESULT_INVALID_RESPONSE_PACKET

"The response packet was invalid."

SFL: 1) Drive Assy 2) Drive Firmware


1. Check drive firmware for correct version of STK variant firmware

drive <addr> info




3. Issue drive command “info” and check drive type

drive <addr> info

4. If problem persists update firmware

5. If drive is a new type (it may not be supported by the software yet), replace drive

6420=TTI_RESULT_IBM_LTO_COOLING_ERROR

"The IBM LTO Drive reported a COOLING error."

SFL: 1) Drive Assy


1. Replace drive

6421=TTI_RESULT_IBM_LTO_POWER_ERROR



"The IBM LTO Drive reported a POWER error."

SFL: 1) Drive Assy


1. Replace drive

6422=TTI_RESULT_IBM_LTO_CODE_ERROR

"The IBM LTO Drive reported a MICROCODE error."

SFL: 1) Drive Firmware


1. Replace drive

6423=TTI_RESULT_IBM_LTO_CODE_OR_DRIVE_ERROR

"The IBM LTO Drive reported a MICROCODE or DRIVE Hardware error."

SFL: 1) Drive Firmware 2) Drive Assy


1. Replace drive

6424=TTI_RESULT_IBM_LTO_DRIVE_FAILURE

"The IBM LTO Drive reported DRIVE FAILURE."

SFL: 1) Drive Assy


1. Replace drive

6425=TTI_RESULT_IBM_LTO_DRIVE_OR_MEDIA_ERROR

"The IBM LTO Drive reported a DRIVE or MEDIA error."

SFL: 1) Media 2) Drive Assy


1. Replace drive

6426=TTI_RESULT_CARTRIDGE_MEDIA_ERROR

"The Drive reported a Cartridge MEDIA ERROR. This can occur on load or unload."

SFL: 1) Media 2) Drive




1. Move cartridge to another drive


2. If problem persists, replace cartridge

3. If problem disappears, issue drive state command

drive <addr> state

4. Determine if drive needs cleaning from drive state command

If cleaning is require, do it

If cleaning is not required continue to step 5.

5. Move a different cartridge to the original drive,

If error persists, replace drive

6427=TTI_RESULT_IBM_LTO_SCSI_OR_FIBRE_ERROR

"The IBM LTO Drive reported a SCSI or FIBRE Channel error."

SFL: 1) Drive Assy 2) Fibre/SCSI Connector 3) Cable


6428=TTI_RESULT_IBM_LTO_RS_422_ERROR

"The IBM LTO Drive reported an RS422 error."

SFL: 1) Drive Assy 2) RLC


6429=TTI_RESULT_IBM_LTO_DRIVE_ERROR

"The IBM LTO Drive reported a recoverable DRIVE error."

SFL: 1) Drive Assy


6430=TTI_RESULT_IBM_LTO_FIBRE_PORT_OFFLINE

"The IBM LTO Drive reported that the FIBRE PORT is OFFLINE."

SFL: 1) Drive Assy 2) Cable 3) Switch







2. Initialize drive

Pull drive out, wait 10 seconds, put it back in.


3. Issue command drive state

drive <addr> state

If command fails, replace drive




6431=TTI_RESULT_IBM_LTO_FIBRE_NO_LIGHT_DETECTED

"The IBM LTO Drive reported NO LIGHT DETETCTED on the FIBRE PORT. Fibre cable might not beconnected."

SFL: 1) Drive Assy 2) Cable 3) Switch Port


1. Reseat cable, if problem persists continue

2. Try other port, if problem persists continue

3. Try different switch port, if problem persists, replace drive

6432=TTI_RESULT_IBM_LTO_FIBRE_AL_PA_CONFLICT

"The IBM LTO Drive reported an AL_PA conflict. Two ports have the same AL_PA"

SFL: 1) Configuration 2) Drive Assy


1. Try different loop id, if problem persists continue

2. Set to soft ID, if problem persists, replace drive

6433=TTI_RESULT_INCORRECT_SEQUENCE_NUMBER

"The Response Sequence Number Does Not Match the Request Sequence Number"

SFL: 1) Software







2. Initialize drive





drive <addr> state






6434=TTI_RESULT_UNIT_CHECK_CONDITION

"The Drive Returned a Unit Check Condition in the Response"

SFL: 1) Drive


1. Check command

2. Reissue command

3. If condition persists, replace drive

6435=TTI_RESULT_SURROGATE_SCSI_TASK_ABORTED

"The Drive Received an Abort Message While Processing a Surrogate SCSI Command"

SFL: 1) Software





2. Re issue command




4. Collect traces, escalate



6436=TTI_RESULT_UNKNOWN_STATUS

"The Drive Returned an Unknown Status in the Response"






2. Initialize drive





drive <addr> state






6437=TTI_RESULT_DRIVE_NEEDS_CLEANING

"The Drive has indicated it needs to be cleaned"

SFL: 1) No FRU – Clean the drive


1. Clean Drive

6438=TTI_RESULT_FAIL_TO_RESET_HOLDOFF_LOAD

"Failed to reset the drive holdoff load mode"

SFL: 1) Drive Assy


1. Maybe a bad cartridge, move cartridge to another drive


2. If problem persists, replace cartridge

3. If problem disappears, move a different cartridge to original drive




4. If problem persists, replace drive

6439=TTI_RESULT_DRV_EMPTY_POSSIBLE_OVEREJECT

"Drive is empty on rewindUnload: possible overeject"

SFL: 1) Drive Assy


1. Open door

2. Visually inspect cartridge

3. Re insert cartridge into drive manually

4. If cartridge doesn’t load, replace drive

5. If cartridge loads, issue rewind/unload


6. If conditions persists, replace drive

6440=TTI_RESULT_LOAD_TIMEOUT

"The Drive failed to load within the alotted time"

SFL: 1) Drive Assy 2) Media


1. Maybe a bad cartridge, move cartridge to another drive


2. If cartridge doesn’t load, replace cartridge

3. If cartridge does load, move a different cartridge to original drive


4. If problem persists, replace drive

6441=TTI_RESULT_UNLOAD_TIMEOUT

"The Drive failed to unload within the allotted time"

SFL: 1) Drive Assy 2) Media


1. Maybe stuck cartridge

2. Open door

3. Visually check cartridge

4. If not stuck, replace drive



5. If stuck, issue rewindunload


6. If cartridge remains stuck, remove drive and manually eject cartridge

7. Replace drive

6442=TTI_RESULT_HP_TIMEOUT

"A HP LTO Drive command Timeout occurred"

SFL: 1) Drive Assy 2) Drive Firmware 3) Software





2. Initialize drive





drive <addr> state






6443=TTI_IBM_NACK_RECEIVED

"The IBM LTO drive returned a NAK to the last command"

SFL: 1) Drive Assy


6444=TTI_IBM_SNACK_RECEIVED

"The IBM LTO drive returned a SNAK to the last command"

SFL: 1) Drive Assy







2. Initialize drive




drive <addr> state If command fails replace drive



6445=TTI_IBM_NO_ETX_VALUE

"The IBM LTO drive didn't return an ETX value."

SFL: 1) Software 2) Drive Assy





2. Initialize drive




drive <addr> state


4. (originally, statement was check drive firmware, if problem persists, replace drive)




6446=TTI_IBM_IMPROPERLY_STUFFED_RESPONSE

"The data packed contained an improperly stuffed response."








2. Initialize drive




drive <addr> state


4. (originally, statement was check drive firmware, if problem persists, replace drive)




6447=TTI_RESULT_PREVENT_MEDIA_REMOVAL

"The Drive reported prevent media removal set"

SFL: 1) Software





2. Initialize drive





drive <addr> state



4. Issue drive rewind/unload command


5. If fails to unload, remove cartridge manually

6. if problem persists, replace drive






6448=TTI_HP_OFF_BUS

"The Hp LTO drive has gone off the bus"

SFL: 1) Software 2) Drive Assy


Action Require:

1. Check SCSI/FIBRE cables

2. Issue drive set config (enabling ports)


3. Initialize drive




4. Issue command to get drive config


5. Check for port enabled from getconfig results

If condition persists, (and cable is FIBRE) move cable to Port B, check for port enabled (asabove)

If condition persists, (and cable is SCSI) try another cable, check for port enabled (as above)

If condition persists, (and cable is FIBRE) try another switch port, check for port enabled (asabove)

6. If condition persists, replace drive

6449=TTI_RESULT_IBM_DRIVE_POST_PROCESSING

"The IBM LTO Drive is in POST Processing."

SFL: -

Isolation Procedure: No action required – informational only

6450=TTI_RESULT_DRIVETRAY_FAILURE SL8500 ONLY – Does not apply to SL500

"The driveTray is NotPresent or PoweredOff."

SFL: 1) -

Isolation Procedure: -



6451=TTI_RESULT_HP_VARIANT_DRIVE_IN_NON_HP_LIB SL8500 ONLY – Does not apply to SL500

"There is an HP variant drive in a non HP library"

SFL: -


6452=TTI_RESULT_IBM_UNLOAD_RETRY_WARNING

"An IBM drive unload failed, but the retry succeeded"

SFL: -

Isolation Procedure: No action required – informational only

6453=TTI_RESULT_CLEANING_CARTRIDGE_EXPIRED

"Load failed due to expired cleaning cartridge."

SFL: 1) Cleaning Cartridge


1. Replace cleaning cartridge

2. Retry drive cleaning

6454=TTI_RESULT_LOAD_FAIL_T10K_MISBUCKLE SL8500 ONLY – Does not apply to SL500

"Load failed due to mis-buckle error."

SFL: -


Notes: Reset time for drives may be longer than ten 10s for fully populated library (20 seconds)



Chapter 11: Sensor Manager

Enviromentals for power supplies

8000=SM_MODULE_POWER_SUPPLY_INSTALLED

"Module power supply installed"

SFL: -

Isolation Procedure: No action required – informational

8001=SM_MODULE_POWER_SUPPLY_REMOVED

"Module power supply removed"

SFL: -

Isolation Procedure: No action required - informational

8002=SM_MODULE_POWER_SUPPLY_WORKING

"Module power supply working"

SFL: -


8003=SM_MODULE_POWER_SUPPLY_FAILED

"Module power supply failed"

SFL: 1) Power Supply, Firmware


1. Replace failed drive

// Environmentals for fans

8010=SM_MODULE_FAN_WORKING

"Module fan working"

SFL: -


8011=SM_MODULE_FAN_FAILED



"Module fan failed"

SFL: 1) Module Fan


1. Replace failed module fan

8012=SM_DRIVE_FAN_WORKING

"Drive fan working"

SFL: -


8013=SM_DRIVE_FAN_FAILED

"Drive fan failed"

SFL: 1) Drive Assy, 2) Firmware


1. Replaced failed Drive Assy

// Environmentals for temperature sensors

8020=SM_MODULE_TEMP_WARNING_LEVEL

"Module temperature sensor has exceed the warning level"

SFL: 1)Module Fan


1. Verify Module fans are spinning

2. Check logs for indications of module fan failure

3. Replace any module fan indicated as failed

4. Verify library environment is within normal operating parameters

8021=SM_MODULE_TEMP_SHUTDOWN_LEVEL

"Module temperature sensor has reached the shutdown level"

SFL: 1) Module Fans


1. Verify Module fans are spinning



2. Check logs for indications of module fan failure

3. Replace any module fan indicated as failed

4. Verify library environment is within normal operating parameters

8022=SM_DRIVE_TEMP_WARNING_LEVEL

"Drive temperature sensor has exceed the warning level"

SFL: 1) Drive Assy


1. Verify drive fan is spinning, if not spinning then replace drive assy

2. Check logs for indications of drive fan failure

3. Replace drive assy if drive fan is indicated as failed

4. If condition persists, verify library environment is within normal operating parameters

8023=SM_DRIVE_TEMP_SHUTDOWN_LEVEL

"Drive temperature sensor has reached the shutdown level"

SFL: 1) Drive Assy


1. Verify drive fan is spinning, if not spinning replace

2. Check logs for indications of drive fan failure

3. Replace drive assy if drive fan is indicated as failed

4. If condition persists, verify library environment is within normal operating parameters



Chapter 12: CLI Service Commands

SERVICE>> help all

cap <module#> <io|storage>

Configure the specified module's CAP as I/O or as storage cells.

cartridge print

Show location, volser, and media type for all cartridges.

codeload 'filename'

Load in new code image.

date <print> | <mm/dd/yyyy>

Print or set the library's date value. Takes the library off of

network time if set.

diagcaps

Diagnose the CAPs.

diagdemo

<diagdemo> <count> <mode>

Moves any cartridge from a random source to a random destination.

Example: diagdemo 10 silent

Example: diagdemo 100 nonsilent

diagdoor

Diagnose the Door.

diaggetput

<diaggetput> <diag type> <source addr> <destination addr> <count> <mode>

Moves the diagnostic cartridge from the specified or random source

to the specified or random destination.

Example: diaggetput cellToCell 0,1,2,1 0,1,3,3 10 silent

Example: diaggetput cellToCell 0,1,2,1 0,1,5,2 5 nonsilent

Example: diaggetput cellToDrive 0,1,2,1 0,1,2,9 5 nonsilent

Example: diaggetput cellToDrive 0,1,3,2 all 5 silent



diagquery

<diagquery> <diag type> <count> <mode>

Example: diagquery basicHealth 10 silent

Example: diagquery basicHealth 10 nonsilent

diagselftest <src address> <loop count> <mode>

Performs library basic health diagnostic. Then does get/put

operations from the src address to random empty cells in the

library. Then performs mounts from the src address to all drives

attached to the library.

Example: diagselftest 0,1,1,2 2 silent

Example: diagselftest 0,2,1,1 10 nonsilent

diagstop

Stop the 'Diag' operation.


Show the specified drive's fibre channel or SCSI configuration.

drive <addr> gettime

Show the specified drive's Time-of-Day (TOD) clock setting.

drive <addr> info

Show the specified drive's information.


Set the specified drive's fibre channel or SCSI configuration.

drive <addr> settime

Set the specified drive's Time-of-Day (TOD) clock.

drive <addr> state

Show the specified drive's operational state.

frameinfo print

Show the library's frame information (i.e, frame serial number,

World Wide Name (WWN)) and the Vendor.

lib getconfig

Show library configuration.

lib setconfig

Set the specified library's fibre channel or SCSI configuration.

libstate print

Shows the state and location of all mechanisms


move the cartridge from the specified source to the specified



destination.

network ip <IP address>

Set the library's IP address to the specified IP address.

network mask <IP address>

Set the library's subnet mask to the specified IP address.

network name <machine network name>

Set the library's machine name to the specified host ID.

network gateway <IP address | none>

Set the gateway IP address. (optional)

network print

Print the library's network settings.

network restart

Restart the library's network interface.

IMPORTANT REMINDER: All network parameters should be configured before

issuing the 'network restart' command.

print log <all> | <error> | <warning> | <info> | <trace> | <diag> | <config>

Print one or all of the library's diagnostic logs. To create a

text file of the log using Hyperterminal, enable text capture to a

local file before printing the desired log.

put <dest addr>

Place the cartridge from the robot hand into the specified address

range < track | z | wrist | reach | grip >

Show the range of motion (in tach counts) of the mech.

reboot

Restart the operating system wich initiates library initialization.

reserved print

Show the library's current reserved cell count.

reserved <number of cells>

Set the maximum number of reserved(playground) library storage cells

in the library.

resetpw <admin> | <oem> | <service> | <all>

Places the specified login password back to the -needs activated-

state. This is used to recover forgotten passwords.

statistics < reset | print >

Show or reset the total number of get/put operations and retries.



time <print> | <network> | <hh:mm:ss> | <hh:mm>

Print or set the library's time value. Takes the library off of

network time if set. The network option re-enables network time.

Depending on the network, it may take several minutes to revert

back to network time.

trace <trace type> on/off

Example: trace tti-dbg-01 on

Turns tti debug log trace on for drive id 1

Example: trace tti-dbg-18 off

Turns tti debug log trace off for drive id 18

Example: trace interface manager-debug on

Turns IFM debug log trace on

List of Trace Type Strings That Can Be Used With Trace:

tti-dbg-xx ( xx is the drive id )

drive-tti-xx ( xx is the drive id )

scsi

scsi-engine

scsi-server

interface-manager

interface-manager-debug

diag

event-manager

OpPanel

service-interface

VMonitor

object-data-store

access-manager

sensor-manager

opel-server

move-sequence

lms

version print

Show all library version information


ats – library engineering sl500 fault...

Documents