Sei sulla pagina 1di 117

ATS – Library Engineering SL500 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 Guide

FI_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, Mark Roget, 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 Added all new result codes since last update Added review updates – Added new drive types - Removed “If HP” from any result code indicating IBM (result codes: 6430, 6444, 6445, 6446)

1.1

08/29/06

BLP

1.1

10/11/06

BLP

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

SL500 Fault Isolation

Chapter 1:Introduction

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

SL500 Fault Isolation

Chapter 2:Suspect FRU List

See the SL500 REPLACEABLE PARTS CATALOG PN 96120 for specifics.

2.1 FRU List, SL500

PWA 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, SL500

HP 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

HP LTO3, FC 2GB, FRU ASSY

HP LTO3, FC 4GB, FRU ASSY

IBM LTO3, SCSI, FRU ASSY

IBM LTO3, FC 2GB, FRU ASSY

IBM LTO3, FC 4GB, 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)

SL500 Fault Isolation

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

SL500 Fault Isolation

1100=SCSI_NOOP

"Requested action not needed" SFL: No FRU

Chapter 3:SCSI Errors

Isolation Procedure: No Isolation Procedure

1101=SCSI_FAILED

"Requested action failed" FIBRE SFL: 1) software

LVD

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

2) MPU2 (STK) 2) MPW (STK)

SFL: 1) software

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

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

2. Reset transport layer from the host, retry operation

3. Reboot library

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

SIPP

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

2. Reset transport layer from the host, retry operation

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

LVD

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

2) MPU2 (STK) 2) MPW (STK)

SFL: 1) software

Isolation Procedure:

SL500 Fault Isolation

FIBRE

1. Reset transport layer from the host, retry operation

2. Unplug and plug in FIBRE cable

3. Reboot library

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

LVD

1. Reset transport layer from the host, retry operation

2. Reboot library

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

SIPP

1. Reset transport layer from the host, retry operation

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

Isolation Procedure:

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

SL500 Fault Isolation

"Encountered a situation which should never occur"

SFL: 1) Software

Isolation Procedure:

1. Collect logs

2. Create pinnacle

1105=SCSI_TASK_ABORTED

"Task was aborted"

SFL: No FRU

Isolation Procedure:

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 task management function.

1107=SCSI_RESTART_INTERFACE

"Interface needs to be restarted"

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

Isolation Procedure:

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

SL500 Fault Isolation

Isolation Procedure: No isolation procedure required, normal operation

SL500 Fault Isolation

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

Chapter 4:IFM Errors

3302=IFM_CONTENT_FAIL

"Content failure for a request or function call" SFL: 1) No FRU – Check media

Isolation Procedure:

1. Collect logs

2.

print log <all> Reboot library

reboot

3303=IFM_NON_EXISTENT_SOURCE_DRIVE

"Source drive requested is not configured"

SFL: 1) No FRU– Check source drive address

SL500 Fault Isolation

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

Isolation Procedure:

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. wait could be up to 20 seconds.

Note: In fully populated library the

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"

SFL: 1) Robotics 2) Firmware

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

SL500 Fault Isolation

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

2.

print log <all> 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

Isolation Procedure:

1. Check source address

Note: 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

Isolation Procedure: See result code 3311 for Isolation Procedure.

3311=IFM_MOVE_DESTINATION_FULL

"Destination address is occupied"

SFL: No FRU

Isolation Procedure

1. Check destination address

SL500 Fault Isolation

Note: 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

Isolation Procedure:

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 source address 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 code to continue the investigation

print log <all>

3313=IFM_MOVE_PUT_FAIL

"Put failed"

SFL: Unknown

Isolation Procedure:

1. Collect logs

print log <all>

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

3. Turn on diagnostic traces

trace diag on

SL500 Fault Isolation

4. Issue diagnostic command diaggetput using the address retrieved from the logs in the source address 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 code to continue the investigation

print log <all>

3314=IFM_MOVE_LOAD_FAIL

"Drive load failed"

SFL: 1) Drive

2) Firmware

Isolation Procedure:

1. Collect logs

print log <all>

2. Find the result code IFM_MOVE_LOAD_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 source address 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 code to continue the investigation

print log <all>

3315=IFM_MOVE_UNLOAD_FAIL

"Drive unload failed"

SFL: 1) Drive 2) Firmware

Isolation Procedure:

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

Isolation Procedure:

SL500 Fault Isolation

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 HP drive issue drive reset command - drive <addr> reset

 

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

Note: In fully

6. Issue command to get drive state

drive <addr> state

7. If command fails, insert a different drive

 

8. Issue command to get drive state

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

Isolation Procedure:

1. 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)

2. 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. populated library the wait could be up to 20 seconds.

Note: In fully

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

drive <addr> state

SL500 Fault Isolation

3318=IFM_MOVE_MEDIA_ERROR

"Media error"

SFL: 1) Media

2) Drive

3) Firmware

Isolation Procedure:

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

Isolation Procedure:

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

Isolation Procedure:

1. Visually check CAP doors for an open door. If CAP door was open, close it and retry operation.

2. Press each CAP door

SL500 Fault Isolation

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

Isolation Procedure:

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 address is 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"

SFL: 1) Robotics 2) Firmware

Isolation Procedure:

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

Isolation Procedure:

1. Open all CAP doors configured as I/O

2. Verify visually all CAP magazines are present.

SL500 Fault Isolation

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

Isolation Procedure:

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)

Isolation Procedure:

1.

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)

2.

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. wait could be up to 20 seconds.

Note: In fully populated library the

3.

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

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

SL500 Fault Isolation

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

move <source addr> <dest addr>

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

Isolation Procedure:

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"

SFL: 1) Tape Cartridge

2) Firmware

Isolation Procedure:

1. Check for diagnostically labeled cartridge

2. Issue cartridge print command

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’s current reserved cell count.

reserved print

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

SL500 Fault Isolation

If the diagnostic tape is not within the reserved cell locations, then move it to an empty reserved 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"

SFL: 1) Tape Cartridge

2) Firmware

Isolation Procedure:

1.

Check for diagnostically labeled cartridge

2.

Issue cartridge print command

cartridge print

3.

Verify diagnostically labeled tape is present

If not present, enter diagnostic cartridge and retry diagnostic. Or choose a 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’s current 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 reserved cell 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"

SFL: 1) Tape Cartridge

2) Firmware

Isolation Procedure:

1. Check for cartridge at location specified in diagnostic command

2. Issue cartridge print 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.

SL500 Fault Isolation

3331=IFM_DIAG

CARTRIDGE_IS_NOT_CORRECT_TYPE

(HP only)

"Cartridge is not correct type"

SFL: 1) Tape Cartridge

2) Firmware

Isolation Procedure:

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

Isolation Procedure:

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

Isolation Procedure:

1. Activate traces for the drive in question “trace drive –tti-xx” (xx is the drive id)

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

2. Issue “drive <addr> stateIf 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"

SL500 Fault Isolation

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

Isolation Procedure:

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

SL500 Fault Isolation

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 corners contains 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 a diagnostic 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 the drives contains a cartridge and cannot participate in the test.

SL500 Fault Isolation

Chapter 5:DIAGNOSTIC Errors

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

3500=DIAGNOSTIC_FAILED

"Unexpected error"

SFL: 1) Firmware

Isolation Procedure:

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

Isolation Procedure:

1. Collect logs

2. Rerun the diagnostics

If diagnostics fail as before, reboot

If diagnostics pass, transient error condition

3502=DIAGNOSTIC_ALREADY_INPROGRESS

"Diagnostic already in progress"

SFL: 1) Firmware (only if condition persists)

Isolation Procedure:

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 minutes before 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 are tested.

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

Isolation Procedure:

1. Collect logs

2. Rerun the diagnostics If diagnostics fail as before, reboot If diagnostics pass, transient error condition

SL500 Fault Isolation

3504=DIAGNOSTIC_UNABLE_TO_CHANGE_LIBRARY_STATE

"Unable to put library into maintenance mode" SFL: Unknown

Isolation Procedure:

1. Collect logs

2. Rerun the diagnostics If diagnostics fail as before, reboot If diagnostics pass, transient error condition

3505=DIAGNOSTIC_THREAD_CREATION_FAILED

"Diagnostic thread creation failed" SFL: 1) Firmware

Isolation Procedure:

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"

SL500 Fault Isolation

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

Isolation Procedure: None, result code no longer used.

3509=DIAGNOSTIC_PROC_DRIVE_FAILURE

"Proc file indicates drive failure"

SFL: No FRU

Isolation Procedure: None, result code no longer used.

3510=DIAGNOSTIC_PROC_RTC_FAILED

"Proc file indicates real time clock battery failure"

SFL: 1) Battery

2) Firmware

Isolation Procedure:

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 result code.

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

Isolation Procedure: None, result code no longer used.

3512=DIAGNOSTIC_PROC_FILE_EMPTY

"Reading the proc file returned a NULL"

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

Isolation Procedure:

1. Verify all Library Modules have power.

Note: All modules must have power at boot up.

SL500 Fault Isolation

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

If problem persists, go to Step 3

If diagnostic passes, problem resolved

3. Replace RLC, reboot library, rerun diagnostic

If problem persists, escalate

If diagnostic passes, problem resolved

3513=DIAGNOSTIC_PROC_FILE_TOKEN_MISSING

"NULL returned when token was expected"

SFL: 1) Firmware

Isolation Procedure:

1. Collect traces

2. Rerun diagnostics

If problem persists, reboot

If diagnostics pass, intermittent problem encountered.

3. Reboot library

4. Rerun diagnostics

If problem persists, escalate

If diagnostics pass, intermittent problem encountered.

3514=DIAGNOSTIC_SYSTEM_MODULE_NOT_PRESENT

"System module not found"

SFL: 1) Firmware, RLM, RLC

Isolation Procedure:

1. Retry the diagnostic

SL500 Fault Isolation

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

Isolation Procedure:

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

Isolation Procedure:

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

If diagnostic pass, problem resolved

3517=DIAGNOSTIC_RLC_MASTER_ENABLE_ERROR

"RLC master enable error detected"

SFL: 1) RLC

2) Firmware

Isolation Procedure:

1. Collect logs

2. Reboot library

3. Rerun diagnostic If diagnostic fails, collect traces, replace RLC If diagnostic pass, problem resolved

4. Reboot library

5. Rerun diagnostic

If diagnostic fails, escalate If diagnostic passes, problem resolved.

3518=DIAGNOSTIC_BRAKE_FAULT_DETECTED

"Control Status: brake fault detected"

SFL: 1) RLC

2) Robot

3) RLM

Isolation Procedure: See result code 3543

3519=DIAGNOSTIC_12V_POWER_NOT_OK

"Control Status: 12v Power not ok"

SFL: 1) RLC

2) Robot

3) RLM

Isolation Procedure: See result code 3543

3520=DIAGNOSTIC_SERVO_VOLTAGE_LOW

"Control Status: servo voltage low"

SFL: 1) RLC

2) Robot

3) RLM

Isolation Procedure: See result code 3543

3521=DIAGNOSTIC_CABLE_SLACK

"Control Status: cable slack"

SFL: 1) RLC

2) Robot

3) RLM

Isolation Procedure: See result code 3543

SL500 Fault Isolation

SL500 Fault Isolation

3522=DIAGNOSTIC_REACH_SAFE

"Control Status: reach safe error"

SFL: 1) RLC

2) Robot

3) RLM

Isolation Procedure: See result code 3543

3523=DIAGNOSTIC_PROX_DETECT

"Control Status: proc detect error"

SFL: 1) RLC

2) Robot

3) RLM

Isolation Procedure: See result code 3543

3524=DIAGNOSTIC_GRIP_FAULT

"Grip fault detected"

SFL: 1) RLC

2) Robot

3) RLM

Isolation Procedure: See result code 3543

3525=DIAGNOSTIC_GRIP_PHASE_ERROR

"Grip phase error detected"

SFL: 1) RLC

2) Robot

3) RLM

Isolation Procedure: See result code 3543

3526=DIAGNOSTIC_GRIP_HALL_ERROR

"Grip phase error detected"

SFL: 1) RLC

2) Robot

3) RLM

Isolation Procedure: See result code 3543

3527=DIAGNOSTIC_GRIP_AMP_ENABLE_ERROR

"Grip amp enable error detected"

SFL: 1) RLC

2) Robot

3) RLM

Isolation Procedure: See result code 3543

3528=DIAGNOSTIC_WRIST_FAULT

"Wrist fault detected"

SFL: 1) RLC

2) Robot

3) RLM

Isolation Procedure: See result code 3543

3529=DIAGNOSTIC_WRIST_PHASE_ERROR

"Wrist phase error detected"

SFL: 1) RLC

2) Robot

3) RLM

Isolation Procedure: See result code 3543

3530=DIAGNOSTIC_WRIST_HALL_ERROR

"Wrist phase error detected"

SFL: 1) RLC

2) Robot

3) RLM

Isolation Procedure: See result code 3543

3531=DIAGNOSTIC_WRIST_AMP_ENABLE_ERROR

"Wrist amp enable error detected"

SFL: 1) RLC

2) Robot

3) RLM

Isolation Procedure: See result code 3543

3532=DIAGNOSTIC_REACH_FAULT

"Reach fault detected"

SFL: 1) RLC

2) Robot

3) RLM

Isolation Procedure: See result code 3543

3533=DIAGNOSTIC_REACH_PHASE_ERROR

"Reach phase error detected"

SFL: 1) RLC

2) Robot

3) RLM

Isolation Procedure: See result code 3543

3534=DIAGNOSTIC_REACH_HALL_ERROR

SL500 Fault Isolation

SL500 Fault Isolation

"Reach phase error detected"

SFL: 1) RLC

2) Robot

3) RLM

Isolation Procedure: See result code 3543

3535=DIAGNOSTIC_REACH_AMP_ENABLE_ERROR

"Reach amp enable error detected"

SFL: 1) RLC

2) Robot

3) RLM

Isolation Procedure: See result code 3543

3536=DIAGNOSTIC_TRACK_FAULT

"Track fault detected"

SFL: 1) RLC

2) Robot

3) RLM

Isolation Procedure: See result code 3543

3537=DIAGNOSTIC_TRACK_PHASE_ERROR

"Track phase error detected"

SFL: 1) RLC

2) Robot

3) RLM

Isolation Procedure: See result code 3543

3538=DIAGNOSTIC_TRACK_HALL_ERROR

"Track phase error detected"

SFL: 1) RLC

2) Robot

3) RLM

Isolation Procedure: See result code 3543

3539=DIAGNOSTIC_TRACK_AMP_ENABLE_ERROR

"Track amp enable error detected"

SFL: 1) RLC

2) Robot

3) RLM

Isolation Procedure: See result code 3543

3540=DIAGNOSTIC_Z_FAULT

"Z fault detected"

SFL: 1) RLC

2) Robot

3) RLM

Isolation Procedure: See result code 3543

3541=DIAGNOSTIC_Z_PHASE_ERROR

"Z phase error detected"

SFL: 1) RLC

2) Robot

3) RLM

Isolation Procedure: See result code 3543

3542=DIAGNOSTIC_Z_HALL_ERROR

"Z phase error detected"

SFL: 1) RLC

2) Robot

3) RLM

Isolation Procedure: See result code 3543

3543=DIAGNOSTIC_Z_AMP_ENABLE_ERROR

"Z amp enable error detected"

SFL: 1) RLC

2) Robot

3) RLM

Isolation Procedure:

1. Collect logs

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

SL500 Fault Isolation

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

5. Rerun diagnostics

If diagnostic fails, replace RLC If diagnostic passes, problem resolved

6. Reboot

7. Rerun diagnostics If diagnostic fails, put original RLC back into library, replace Robot

SL500 Fault Isolation

If diagnostic passes, problem resolved

8. Reboot

9. Rerun diagnostics If diagnostic fails, put original Robot back into lilbrary, replace RLM If diagnostic passes, problem resolved

10. Reboot

11. Rerun diagnostics If diagnostic fails, escalate If diagnostic passes, problem resolved

3544=DIAGNOSTIC_DRIVE_NOT_PRESENT

"Drive not present"

SFL: 1) Drive

2) RLC

3) RLM

Isolation Procedure:

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

If diagnostic passes, problem resolved

4. Reboot.

5. Rerun diagnostic

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

6. Reboot.

7. Rerun diagnostic

If problem persists, escalate If diagnostic passes, problem resolved

3545=DIAGNOSTIC_DRIVE_FAN_FAILURE

"Drive fan failure detected"

SFL: 1) DRIVE

2) RLC

3) RLM

Isolation Procedure:

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

6. Rerun diagnostics If problem persists, put original drive assy into library, replace RLC If diagnostics pass, problem resolved

7. Reboot

8. Rerun diagnostics If problem persists, put original RLC into library, replace RLM If diagnostics pass, problem resolved

9. Reboot

10. Rerun diagnostics If problem persists, escalate If diagnostics pass, problem resolved

11. Collect logs

3546=DIAGNOSTIC_DRIVE_FAULT_LED_ACTIVE

"Drive fault LED active"

SFL: 1) Drive Assy

2) RLC

3) Firmware

Isolation Procedure:

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.

SL500 Fault Isolation

SL500 Fault Isolation

3547=DIAGNOSTIC_NO_FUNCTIONAL_DRIVE_FOUND

"No functional drive found"

SFL: 1) Drive

2) Firmware

Isolation Procedure:

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

If problem persists, escalate

If diagnostic passes, problem resolved.

3548=DIAGNOSTIC_DOOR_SENSOR_FAILURE_DOOR_OPEN

"Door sensor failure: Door open"

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

Isolation Procedure:

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)

If problem persists, replace RLC

If diagnostic passes, problem resolved

3549=DIAGNOSTIC_DOOR_SENSOR_FAILURE_DOOR_CLOSED

"Door sensor failure: Door closed"

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

Isolation Procedure:

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 to be opened.)

2. Rerun diagnostic

If problem persists, replace RLC

If diagnostic passes, problem resolved

SL500 Fault Isolation

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

Isolation Procedure: See result code 3553 for Isolation Procedure.

3551=DIAGNOSTIC_DOOR_OPEN_LED_FAILURE_LED_SHOULD_BE_OFF

"Door Open LED Failure: LED should be off" SFL: 1) RLC 2) Firmware

Isolation Procedure:

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 If diagnostic passes, problem resolved

4. Reboot

5. Rerun diagnostic

If problem persists, escalate If diagnostic passes, problem resolved

3552=DIAGNOSTIC_DOOR_OPEN_LED_FAILURE_LED_NOT_ON_OR_FLASHING

"Door Open LED Failure: LED should be on or flashing" SFL: 1) Door LED 2) RLC 3) Firmware

Isolation Procedure: See result code 3553 for Isolation Procedure

3553=DIAGNOSTIC_DOOR_OPEN_LED_FAILURE_LED_NOT_FLASHING

"Door Open LED Failure: LED should be flashing" SFL: 1) Door LED 2) RLC 3) Firmware

Isolation Procedure:

1.

Rerun diagnostic If problem persists, replace door LED

SL500 Fault Isolation

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

2. Reboot library

3. Rerun diagnostic

If problem persists, replace RLC If diagnostic passes, problem resolved

4. Reboot

5. Rerun diagnostic If problem persists, escalate If diagnostic passes, problem resolved

3554=DIAGNOSTIC_UNABLE_TO_RETURN_LIBRARY_TO_READY

"Unable to return library to ready state." SFL: 1) Firmware

Isolation Procedure:

1. Collect logs

2. Reboot library

3. Rerun diagnostic (any diagnostic) If problem persists, escalate If diagnostic passes, problem resolved

3555=DIAGNOSTIC_UNABLE_TO_CLEAR_DIAG_IN_PROGRESS_FLAG

"Unable to clear the diagnostic in progress flag." SFL: 1) Firmware

Isolation Procedure:

1. Collect logs

2. Reboot library

3. Rerun diagnostic (any diagnostic) If problem persists, escalate If diagnostic passes, problem resolved

3556=DIAGNOSTIC_TIME_OUT

"Diagnostic Timed Out." SFL: No FRU

Isolation Procedure: Result code not used.

SL500 Fault Isolation

3557=DIAGNOSTIC_CAP_SENSOR_FAILURE_CAP_OPEN

"CAP sensor failure: CAP open"

SFL: Not used

Isolation Procedure: No Isolation Procedure

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

Isolation Procedure: No Isolation Procedure

1. Collect logs

2. Rerun the diagnostic

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. Does the 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

Isolation Procedure:

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

2. Rerun the diagnostics

If diagnostics fail as before, replace CAP sensor.

3. Rerun the diagnostics

If error persists, replace the RLC

SL500 Fault Isolation

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

Isolation Procedure: No Isolation Procedure

1. Collect logs

2. Rerun the diagnostic

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. Does the 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

Isolation Procedure:

1. Collect logs

2. Rerun the diagnostic

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. Does the load 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

Isolation Procedure:

1. Collect logs

2. Rerun the diagnostics

If diagnostics fail as before, reboot

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

SL500 Fault Isolation

3565=DIAGNOSTIC_CAP_SENSOR_FAILURE_CAP_2_OPEN

"CAP sensor failure: CAP 2 open"

Note: See result code 3569

3566=DIAGNOSTIC_CAP_SENSOR_FAILURE_CAP_3_OPEN

"CAP sensor failure: CAP 3 open"

Note: See result code 3569

3567=DIAGNOSTIC_CAP_SENSOR_FAILURE_CAP_4_OPEN

"CAP sensor failure: CAP 4 open"

Note: See result code 3569

3568=DIAGNOSTIC_CAP_SENSOR_FAILURE_CAP_5_OPEN

"CAP sensor failure: CAP 5 open"

Note: See result code 3569

3569=DIAGNOSTIC_CAP_SENSOR_FAILURE_CAP_6_OPEN

"CAP sensor failure: CAP 6 open"

SFL: 1) CAP Sensor

2) Firmware

Isolation Procedure:

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

2. Rerun the diagnostics

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

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

If diagnostics fail with message – “CAP Door State is not closed, diagnostics will not start. One or more CAP doors is open or CAP Audit is in progress.” If an audit is in progress, please wait until 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"

SL500 Fault Isolation

Note: See result code 3575

3571=DIAGNOSTIC_CAP_SENSOR_FAILURE_CAP_2_CLOSED

"CAP sensor failure: CAP 2 closed" Note: See result code 3575

3572=DIAGNOSTIC_CAP_SENSOR_FAILURE_CAP_3_CLOSED

"CAP sensor failure: CAP 3 closed" Note: See result code 3575

3573=DIAGNOSTIC_CAP_SENSOR_FAILURE_CAP_4_CLOSED

"CAP sensor failure: CAP 4 closed" Note: See result code 3575

3574=DIAGNOSTIC_CAP_SENSOR_FAILURE_CAP_5_CLOSED

"CAP sensor failure: CAP 5 closed" Note: See result code 3575

3575=DIAGNOSTIC_CAP_SENSOR_FAILURE_CAP_6_CLOSED

"CAP sensor failure: CAP 6 closed"

SFL: 1) CAP sensor

2) Firmware

Isolation Procedure:

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.

3. Rerun the diagnostics

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

Isolation Procedure:

2) Power Cord

3) Firmware

1. Verify power supply cord is seated properly

SL500 Fault Isolation

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 power supply is active.

3577=DIAGNOSTIC_POWER_SUPPLY_MODULE_1_SUPPLY_2_FAILED

"Power Supply Failure: Module 1, Supply 2"

Isolation Procedure:

Note: See result code 3576

3578=DIAGNOSTIC_POWER_SUPPLY_MODULE_2_SUPPLY_1_FAILED

"Power Supply Failure: Module 2, Supply 1"

Isolation Procedure:

Note: See result code 3576

3579=DIAGNOSTIC_POWER_SUPPLY_MODULE_2_SUPPLY_2_FAILED

"Power Supply Failure: Module 2, Supply 2"

Isolation Procedure:

Note: See result code 3576

3580=DIAGNOSTIC_POWER_SUPPLY_MODULE_3_SUPPLY_1_FAILED

"Power Supply Failure: Module 3, Supply 1"

Isolation Procedure:

Note: See result code 3576

3581=DIAGNOSTIC_POWER_SUPPLY_MODULE_3_SUPPLY_2_FAILED

"Power Supply Failure: Module 3, Supply 2"

Isolation Procedure:

Note: See result code 3576

3582=DIAGNOSTIC_POWER_SUPPLY_MODULE_4_SUPPLY_1_FAILED

"Power Supply Failure: Module 4, Supply 1"

Isolation Procedure:

SL500 Fault Isolation

Note: See result code 3576

3583=DIAGNOSTIC_POWER_SUPPLY_MODULE_4_SUPPLY_2_FAILED

"Power Supply Failure: Module 4, Supply 2" Isolation Procedure:

Note: See result code 3576

3584=DIAGNOSTIC_POWER_SUPPLY_MODULE_5_SUPPLY_1_FAILED

"Power Supply Failure: Module 5, Supply 1" Isolation Procedure:

Note: See result code 3576

3585=DIAGNOSTIC_POWER_SUPPLY_MODULE_5_SUPPLY_2_FAILED

"Power Supply Failure: Module 5, Supply 2" Isolation Procedure:

Note: See result code 3576

3586=DIAGNOSTIC_POWER_SUPPLY_MODULE_6_SUPPLY_1_FAILED

"Power Supply Failure: Module 6, Supply 1" Isolation Procedure:

Note: See result code 3576

3587=DIAGNOSTIC_POWER_SUPPLY_MODULE_6_SUPPLY_2_FAILED

"Power Supply Failure: Module 6, Supply 2" Isolation Procedure:

Note: See result code 3576

3588=DIAGNOSTIC_POWER_SUPPLY_MODULE_4_SUPPLY_1_DEGRADED

"Power Supply Degraded: Module 4, Supply 1" Isolation Procedure:

Note: See result code 3576

3589=DIAGNOSTIC_POWER_SUPPLY_MODULE_4_SUPPLY_2_DEGRADED

"Power Supply Degraded: Module 4, Supply 2" Isolation Procedure:

Note: See result code 3576

SL500 Fault Isolation

SL500 Fault Isolation

Chapter 6:LIBRARY Miscellaneous

3700=LIBRARY_SYSTEM_RESOURCE_FAILURE

"Library system resource failed" SFL: 1) Firmware

Isolation Procedure:

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

Isolation Procedure:

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

Isolation Procedure:

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

SL500 Fault Isolation

Isolation Procedure: See result code 3705 for Isolation Procedure

3704=LIBRARY_THREAD_WAIT_FAILED

"Library thread wait failed" SFL: 1) Firmware

Isolation Procedure: See result code 3705 for Isolation Procedure

3705=LIBRARY_THREAD_CREATION_FAILED

"Library thread creation failed" SFL: 1) Firmware

Isolation Procedure:

1. Collect traces

2. Reboot library

3706=LIBRARY_UNABLE_TO_PARK_ROBOT

"Library unable to park robot" SFL: Robot

Isolation Procedure:

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

SL500 Fault Isolation

Isolation Procedure:

1. Collect traces

2. Reboot

3708=LIBRARY_INIT_FAILED

DIRECTOR_RESPONSE

"Library initialization failed, Director response unsuccessful" SFL: 1) Robot

Isolation Procedure:

1. Open door

2. Look for obstruction Cartridge may be to far out 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

Isolation Procedure:

1. Collect traces

2. Reboot

3710=LIBRARY_INIT_FAILED

INIT_OF_CELLDB_FAILED

"Library initialization failed, CELLDB init failed" SFL: 1) Firmware

Isolation Procedure:

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

Isolation Procedure:

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

Isolation Procedure:

SL500 Fault Isolation

1. Open door

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

3. Visually check for obstructions

Cartridge may be to far out 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

Isolation Procedure:

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

SL500 Fault Isolation

"Library initialization failed, open CAPS" SFL: 1) CAP Magazine 2) Firmware

Isolation Procedure:

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

Isolation Procedure:

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

Isolation Procedure:

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

Isolation Procedure:

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

Isolation Procedure:

SL500 Fault Isolation

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

Isolation Procedure:

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

Isolation Procedure:

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

Isolation Procedure:

1. Replace RLC

2. Reboot

3. If problem persists replace RLM

4. Replace RLC with original

5. Reboot

SL500 Fault Isolation

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

Isolation Procedure:

1. Reboot

2. If condition persists then collect traces and escalate

3801=VSNMP_BIND_COMMAND_FAILURE

"VSnmp Bind Command Failure" SFL: 1) Firmware

Isolation Procedure:

1. Reboot

2. If condition persists then collect traces and escalate

3802=VSNMP_LISTEN_COMMAND_FAILURE

"VSnmp Listen Command Failure" SFL: 1) Firmware

Isolation Procedure:

1. Reboot

2. If condition persists then collect traces and escalate

3803=VSNMP_CONNECT_COMMAND_FAILURE

"VSnmp Connect Command Failure" SFL: 1) Firmware

Isolation Procedure:

1. Reboot

2. If condition persists then collect traces and escalate

SL500 Fault Isolation

SL500 Fault Isolation

3804=VSNMP_SEND_COMMAND_FAILURE

"VSnmp SEND Command Failure" SFL: 1) Firmware

Isolation Procedure:

1. Reboot

2. If condition persists then collect traces and escalate

3805=VSNMP_RECV_COMMAND_FAILURE

"VSnmp RECV Command Failure" SFL: 1) Firmware

Isolation Procedure:

1. Reboot

2. If condition persists then collect traces and escalate

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) -

Isolation Procedure: Not Used

Chapter 8:Service

Note: This chapter does not apply to HP

3900=SERVICE_INVALID_OP_CODE

"Service Invalid Op Code " SFL: -

Isolation Procedure:

1. Invoke help for desired command

2. Verify syntax

3. Retry command

3901=SERVICE_MISSING_PARAMETER

"Service Missing Parameter " SFL: -

SL500 Fault Isolation

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

Isolation Procedure:

1. Log off

2. Log on

3. Retry command

4. If condition persists, collect traces and escalate

SL500 Fault Isolation

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

Isolation Procedure:

1. Retry command

2. If condition persists, collect traces and escalate

3906=SERVICE_RESPONSE_TIMEOUT

"Service Response From Server Timeout " SFL: 1) Firmware

Isolation Procedure:

1. Retry command

2. If condition persists, collect traces and escalate

3907=SERVICE_SOCKET_ERROR

"Service DCI Socket Broken " SFL: 1) Firmware

Isolation Procedure:

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) -

Isolation Procedure: Not Used

3909=SERVICE_RESP_CONTENT_FAILURE

"Service Content Failure In Response String " SFL: 1) -

Isolation Procedure: Not Used

3910=SERVICE_RECEIVE_CLI_SOCKET_FAILURE

"Service Receive From CLI Socket Failure " SFL: 1) Firmware

Isolation Procedure:

1. Retry command

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

3. If condition persists, then collect traces and escalate

3911=SERVICE_SEND_CLI_SOCKET_FAILURE

"Service Send To CLI Socket Failure " SFL: 1) Firmware

Isolation Procedure:

1. Retry command

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

3. If condition persists, then collect traces and escalate

3912=SERVICE_CLI_SOCKET_UNAVAILABLE

"Service CLI Socket Unavailable " SFL: 1) Firmware

Isolation Procedure:

1. Retry command

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

3. If condition persists, then collect traces and escalate

3913=SERVICE_CLI_SNMP_RESULT_FAILURE

"Service CLI Result Failure "

SL500 Fault Isolation

SL500 Fault Isolation

SFL: 1) Firmware

Isolation Procedure:

1. Retry command

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

3. If condition persists, then collect traces and escalate

3914=SERVICE_PROCESS_NOT_AVAILABLE

"Service Process Not Available " SFL: 1) -

Isolation Procedure: Not Used

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: -

SL500 Fault Isolation

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: -

Isolation Procedure: Reason Code Not Used

5003=SRV_ISR_LOGICAL_FAILURE

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

Isolation Procedure: Reason Code Not Used

5004=ERR_SRV_UNKNOWN_REQUEST_TYPE

"An unknown type of request was received by Servo" SFL: -

SL500 Fault Isolation

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

5005=ERR_SRV_UNEXPECTED_SYS_ERROR_RET

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

Isolation Procedure: Reason Code Not Used

5006=ERR_SRV_BAD_CHK_MOVE_CALC

"An error was encountered in performing a quick initialization move" SFL: -

Isolation Procedure: Reason Code Not Used

5007=ERR_SRV_DEST_OUTSIDE_OPER_RANGE

"The requested destination is not within the allowable operating range" SFL: robot assy

Isolation Procedure:

1. Open door

2. Visually check for obstructions

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

SL500 Fault Isolation

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

1. Reboot library

2. If error persists, replace robot.

5010=ERR_SRV_EXCESSIVE_POSITION_ERROR

"An excessive position error was detected during motion" SFL: - robot assy

Isolation Procedure:

1. Open door

2. Visually check for obstructions

3. Clear any obstructions found

4. Reboot library

5. If error persists, replace robot.

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

2. If error persists, replace robot.

5012=ERR_SRV_CANT_START

NOT_IN_STOPLOCK

"The requested motion cannot start because the mechanism is not in stoplock" SFL: robot assy

Isolation Procedure:

1. Reboot library

2. Retry operation

3. If error persists, replace robot.

5013=ERR_SRV_ISR_REENTERED

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

SL500 Fault Isolation

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

5014=ERR_SRV_SATURATION_CURRENT_REQUESTED_TOO_LONG

"The max or min current was requested an excessive amount of times" SFL: robot assy

Isolation Procedure:

1. Open door

2. Visually check for obstructions

3. Remove any obstructions found

4. Reboot library

5. Execute diagquery basicHealth

6. If basic health good, retry operation

7. If error persists, replace robot.

5015=ERR_SRV_MECH_DROPPED_OUT_OF_STOPLOCK

"The mechanism has fallen outside the allowable stoplock range" SFL: robot assy

Isolation Procedure:

1. Reboot library

2. Retry operation

3. If error persists, replace robot.

5016=ERR_SRV_MECH_FAILED_TO_SETTLE_INTO_STOPLOCK

"The mechanism was unable to settle into the desired stoplock window" SFL: robot assy

Isolation Procedure:

1. Open door

2. Visually check for obstructions

3. Remove any obstructions found

4. Reboot library

5. Execute diagquery basicHealth

6. If basic health good, retry operation

7. If error persists, replace robot.

SL500 Fault Isolation

5017=ERR_SRV_OPERATING_RANGE_OUT_OF_SPEC

"The range of motion on initialization is not within specification" SFL: robot assy

Isolation Procedure:

1. Open door

2. Visually check for obstructions

3. Clear any obstructions found

4. Reboot library

5. If error persists, replace robot.

5018=ERR_SRV_INVALID_THETA_Z_RANGE_COMBO

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

Isolation Procedure: Reason Code Not Used

5019=ERR_SRV_REDEFINED_LIB_CONFIG

"The operating ranges found at arm initialization don't indicate known hardware" SFL: - robot assy

Isolation Procedure:

1. Open door

2. Visually check for obstructions

3. Clear any obstructions found

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

5. Reboot library

6. If error persists, replace robot.

SL500 Fault Isolation

5020=ERR_SRV_BAD_MECH_ID_IN_ISR

"The servo interrupt received a bad mechanism identifier" SFL: -

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