IBM RS/6000 SP, Руководство по определению проблем

Страница: 125 / 316

This soft copy for use by IBM employees only.
The system only uses these labels when reporting errors in the error log or the
css logs. If these labels are incorrect, then it will be difficult to debug problems
because the errors may be attributed to the wrong node.
Eannotator physically checks which connections it is going through (that is, the
jack socket or the switch chip connection) to get to a node or switch chip and
will update the topology file accordingly. It converts what is initially logical
information to actual physical information. For example, L06 for logical frame 6
may be converted to E8 because this may be the 8th physical frame.
After migrating to the SP Switch, it is essential to run
Eannotator
after the
hardware installation because the jack connections have changed completely
from those which were used for the High Performance Switch. The system does
not use this information during initialization, needing only the
logical data to the
left of this in the file which describes each link on the network.
Eannotator is run after the topology file has been selected as part of the
installation process.
Etopology
- Stores or reads a switch topology file into or out of the SDR.
After the switch topology file has been annotated, it will be stored to the SDR by
Etopology
during the installation process. The switch topology file stored in the
SDR can be overwritten by having an expected.top file in /etc/SP on the primary
node.
Estart
- Starts the switch
If Estart can find the file expected.top file in /etc/SP on the primary node, it will
use that to initialize the switch. Otherwise it will transfer the one stored in the
SDR on the Control Workstation to that directory on the primary node.
Estart_sw
is run on the primary to initialize all the nodes in the switch. For the High
Performance Switch this process will then clean up the topology file that was
placed in its /etc/SP directory so that a new one will get transferred at the next
Estart.
If the switch fails to initialize all nodes for any reason, always check to see if
there is a /etc/SP/expected.top file on the primary node. If there is, check to see
if it is the correct topology file, and that its contents are valid. For the High
Performance Switch the only reason one of these files should exist is if an IBM
engineer wishes to temporarily override the topology file in the SDR to assist in
the diagnosis of a possible hardware failure on the switch. Once that work has
been completed, the file should be removed and the SDR file should be used.
Check to see if any of these files exist on any of the nodes by running:
# dsh -a ls -l /etc/SP/expected.top
If one of these files exists, then check it out because if the primary is changed to
that node, it may affect the initialization of the switch.
For the SP Switch, this procedure is different. A check is made to see whether
there has been a change in the switch topology by referencing the SDR, and if
this is not the case it uses the existing topology that has been previously
Chapter 4. The Switch
105