Sun StorageTek SL500 Modular Library System
 

GCS>Sun Microsystems>Storage - Tape>Libraries - SL-Series
 

Applies to:

Goal

Solution

 Prior to turning the SL500 over to the customer, perform this procedure.

1.1  Power on library after fully installing in rack unit.

1.2  Connect CSE laptop PC to CLI port - right hand RJ45 connector.

-   For Oracle/STK Service Personal, user ID would normally be"service"

-   For Service Partners ID would be "OEM"

Example:

Welcome.  Tue Sep 21  2004 14:07:48

green23 login: service

Password: xyz1234

 Note:

Diagnostic commands can be found in Section 3 of manual 96153 SL500 Diagnostic manual. 

1.4   Diagnostic self-test (run from CLI prompt) � requires DG_xxx cartridge in one of the reserved cells

diagselftest

 This command:

1.  Performs the library basic health diagnostic.

2.  Does get/put operations from the src address to random empty slots in the library.

3.  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

 Run diagselftest using one of the highest available cell (e.g. 0,1,1,1) and then again using one of the lowest cells (e.g. in a 3 module system, 0,3,7,8). This will ensure that the robot can reach the extreme corners of the library.

 1.5   CAP diagnostic (run from CLI prompt)

 CAP Configures a specified module's CAP as I/O or as storage slots

1.6             Door diagnostic

diagdoor

 This interactive command is used to determine if the door sensor and LED are functioning.

Example: diagdoor

 1.7  Run DEMO for 200 loop count.

 diagdemo

This command moves any cartridge from a random source to a random destination. The two mode values are silent and non-silent.

- Silent mode returns only the ending status.

Example: diagdemo 10 silent

- Non-silent mode returns the current (loop) count value.

Example: diagdemo 100 nonsilent

 1.8  Verify host connectivity to library

Two options:

1. You can connect the cable to your PC and run SCSI/Fiber tool box diagnostics (until Tools has a SL500 option use of L700 has worked for basic function testing).  

2. You can connect to the host server, have customer install the ISV application software and attempt to run using the application program.

1.9   Verify host connectivity to drives

 Three options: Drive connectivity can be tested via

1. Toolbox

2. The OEM Vendor Diagnostic program

3. Using the ISV backup application.

2.0     Capture logs from CLI, "print log all"        

print log   

 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.

 Example:

> print log all

            log_error:    

 2004-09-20T19:21:45.636,      0.0.0.0.0, 3200, interface-manager, (null), error, 3000, 3312, "(request id = Diagnostic/0x100b0878) IfmMove::commonMoveCommand(): FETCH request failed:"

2004-09-20T19:21:45.644,     0.0.0.0.0, 3670,  diag, (null),  error, 3683, 3312, "(request id = Service/0x1009f6e8) DiagGetPut()Diagnostic Get/Put  ...completionCode==1 "

2004-09-21T10:57:11.902,     0.0.0.0.0, 3670,  diag, (null),  error, 3683, 3302, "(request id = Service/0x100a02c8) DiagGetPut()Diagnostic Get/Put  ...completionCode==1 "

2004-09-21T11:00:31.311,     0.0.0.0.0, 3670,  diag, (null),  error, 3683, 3302, "(request

 2.1   Turn over to customer and monitor as/if your service area procedures require.

This solution has no attachment