IBM RS/6000 SP - Manual (Page 38)

splstdata -n | pg
5. From the system file server, log into “primary” processor node as root using the telnet command:
telnet PrimaryNodename
6. Check errpt -a -N Worm | pg for any switch related problems. If any errors are listed, use the error
information, with this MAP, to help isolate the problem.
7. Check the functional state of the switch in the out.top file by issuing the following command on the
“primary” processor node:
pg /var/adm/SPlogs/css/out.top
Notes:
a. Verify that the timestamp on the out.top file is current (using ls -l /var/adm/SPlogs/css/out.top).
b. Refer to
″
Starting a service call (MAP 0100)
″
in RS/6000 SP: System Service Guide for information
on using the pg command.
8. Problems are indicated at the end of a text line by the following sequence:
−# ErrorMessage
Examples of error messages:
-1 uninitialized
-3 R: faulty link from VOP
9. Does /var/adm/SPlogs/css/out.top file report any problems?
v If yes, use the SPS Error Conditions table (Table 1-7 on page 1-19) to continue service.
v If no, go to “Step 0620-002”.
Step 0620-002
No functional problems found.
1. Have you replaced any components or fixed problems?
v If yes:
a. You have resolved the switch problem.
b. Go to
″
End of call (MAP 0650)
″
in RS/6000 SP: System Service Guide.
v If no, go to “Step 0620-003”.
Step 0620-003
You did not find any functional problems and you did not fix or replace anything.
1. Did Estart command start okay?
v If yes, call the next level of support.
v If no:
a. Consult the “Diagnosing Switch Problems” section of IBM RS/6000 SP: PSSP Diagnosis Guide.
b. Return to “Step 0620-001” on page 1-17.
SP Switch function (MAP 0620)
1-18 RS/6000 SP: SP Switch Service Guide