IBM RS/6000 SP, Problem Determination Manual

Page: 144 / 316

This soft copy for use by IBM employees only.
4.8 Additional Problem Determination
The following sections discuss determining additional system problems.
4.8.1 Debugging Scripts
If a problem could not be determined by the log files, it is useful to debug the
command which fails by itself. Several commands used for SP Switchs are shell
scripts or perl scripts.
Shell scripts could be debugged by inserting
set -x
in the beginning of a script.
It should be inserted in a new line right after
#!/bin/ksh
.
Perl scripts could be debugged by inserting
-d
flag just in the first line of the
script.
#!/usr/lpp/ssp/perl/bin/perl -d
•
Run the commands:
# script <filename>
# <name of perl script>
−
From within the perl script enter:
-
″
t
″ (
to turn trace on)
-
″
c
″ (
to continue)
−
Then run:
# exit (to stop the script command)
4.8.2 AIX Error Logging
In addition to the log files, there is always a possibility of errors being recorded
in the error log (/var/adm/ras/errlog). These errors can be read by using the
error report command
errpt
. It is important to note the time of the failure in
order to correlate messages in error report errpt to the error. There are also
many normal, informational switch messages that you will see in the error
report. For instance, when you issue an
Estart , you will see a switch fault in the
error report.
Expect one of each of these messages for each
Estart
command.
ERROR_ID TIMESTAMP T CL Res Name ERROR_Description
34FFBE83 0502140496 T H Worm HPS Fault - detected by switch chip
C3189234 0502135796 T H Worm HPS Fault - not isolated
Figure 57. Message i n Error Report w h i l e Estart Has B e e n Executed
To get some error reports specific to the switch, you can use
dsh -a errpt -a -N
css
or
dsh -a errpt -a -N Worm
. You can also run diags if you suspect a
hardware problem on the switch:
diag -c -d css0
or
diag -A -d css0
.
124
SP PD Guide