IBM RS/6000 SP, Maintenance Information

Page: 342 / 388

MAP 0540: Switch Function
MAP 0540: Switch Function
Notes:
1. Refer to “Appendix A” in
RS/6000 SP: Maintenance Information, Volume 1 for frame-to-frame or
switch-to-switch cables. Logical frame to physical frame translation information can also be found in
this appendix.
2. Refer to "HiPS 2.0/3.0 Node Data Cables" in
IBM RS/6000 SP: Maintenance Information, Volume 3,
Locations and Service Procedures for switch connections to primary and secondary processor nodes.
3. For the LC8, refer to "HiPS-LC8 Node Data Cables" in
IBM RS/6000 SP: Maintenance Information,
Volume 3, Locations and Service Procedures.
4. Refer to "Service Position Procedures" in
IBM RS/6000 SP: Maintenance Information, Volume 3,
Locations and Service Procedures for placing or removing the high-performance switch in/from service
position.
001
Possible functional problem with switch assembly.
Note: If out.top does not match the physical switch configuration, run Eannotator. (Refer to the Installa-
tion section of IBM RS/6000 SP: Scalable POWERparallel Switch Support for the IBM PSSP for
AIX (GC23-3998).
– To complete the following procedures, you will need to have primary node root access. (Customer may
enter root password when required.)
– If either of the following two conditions is true:
Ÿ Estart has not been run by the customer
Ÿ The CE has already replaced components that might affect the switch.
then from the control workstation of the “primary” processor node, enter:
Estart
You should receive a message indicating successful initialization at the primary node. If you receive any
other message, consult the “Diagnosing High Performance Switch Problems” section of
IBM Parallel
System Support Programs for AIX: Diagnosis Guide
– Determine the primary node number. From an AIX window on the control workstation, enter:
Eprimary
– Determine the host name for this node by checking “reliable_hostname” for the node number with the
command:
splstdata -n | pg
– From the system file server, log into “primary” processor node as root using the telnet command:
telnet PrimaryNodename
– 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.
– 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:
1. Verify that the timestamp on the out.top file is current (using ls -l /var/adm/SPlogs/css/out.top).
(Step 001 continues)
1-322
RS/6000 SP MAPs