Beruflich Dokumente
Kultur Dokumente
Crash Kit;
300-1357 - Sony 670 Watt Power Supply
501-5539 - 450MHz UltraSPARC II Module
501-5168 - System Board, 0MB FRU
1.3 Login using the login user ID and password. (Or one time password
if 1st time)
- For 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 m
anual. (Rev 1 Sept 2004). Later revisions may change.
1.4 Diagnostic self-test (run from CLI prompt) ? requires DG_xxx ca
rtridge in one of the reserved cells
diagselftest
<diagselftest> <src address> <loop count> <mode>
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 lib
rary
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 the
n 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 <module#> <io|storage> Configures a specified module's CAP as I/O or as sto
rage slots
1.6 Door diagnostic
diagdoor
<diagdoor>
This interactive command is used to determine if the door sensor and LED are fu
nctioning.
Example: diagdoor
1.7 Run DEMO for 200 loop count.
diagdemo
<diagdemo> <count> <mode>
This command moves any cartridge from a random source to a random destination. T
he two mode values are silent and nonsilent.
- 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 fu
nction testing). Or 2) you can connect to the host server, have customer insta
ll 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 or 2) the OEM Ve
ndor Diagnostic program or 3) by using the ISV backup application.
2.0 Capture logs from CLI, ?print log all?
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 th
e desired log.
2.1 Turn over to customer and monitor as/if your service area proced
ures require.
User IDs
To log in to the SL Console, you must have a valid, active user ID. Each user ID
must be
assigned a password.
There are a fixed set of user IDs at a site. The user IDs include admin (custome
r
administrator), service (Sun Customer Services Engineer), and oem (third-party f
ield
service technician). When you log in successfully, the SL Console displays your
user ID
in the status bar of the screen.
Only one user at a time can be logged in to the local operator panel, but any nu
mber of
users can connect to a library through the standalone SL Console or Web-launched
SL Console.
Activation Password
Before any users at your site can use the SL Console for the first time, your li
brary
administrator must activate the admin userid with a special activation password.
Your Sun support representative provides your administrator with the activation
password, which is valid for one-time use only.
After logging in with the activation password, the administrator must change the
admin user ID password to ensure system security.
For details about this process, see the appropriate library Installation Guide.