The switch topology file describes the wiring configuration for the switch. It contains node-to-switch or switch-to-switch cable information.|You choose a switch topology file based on the highest numbered |switch in your system. This usually corresponds, but not always, to the |number of switches in your system. For example, for a system that |contains four switches with switch numbers 1, 2, 3, and 5, you must use the |topology file that corresponds to a system containing five switches. |Such a situation can occur if your system has been reconfigured since the |original installation.
You can annotate connection labels onto the selected switch topology file with the Eannotator command. After you have selected and annotated the switch topology file, you store it in the SDR with the Etopology command. When you start the switch, the switch initialization code reads the switch topology file stored in the SDR.
|In a two-plane SP Switch2 configuration, you choose one switch |topology file for each switch plane. Typically, you set up the system |such that each plane is wired the same way. Then you can specify the |same topology file for each plane. You can do that either by letting |the -p flag default to all or by explicitly setting it |to all.
For more information on choosing a switch topology file, see the following:
An expected.top file in the /etc/SP directory of the primary node overrides the topology file specified in the SDR. This is used when servicing or debugging the switch. See the book IBM RS/6000 SP: System Service Guide for more information.
Before a switch topology file is stored in the SDR, you use the Eannotator command to update the switch topology file connection labels with their current physical locations. If the -O yes flag is specified, the topology file is stored in the SDR. Running the Eannotator command makes the switch hardware easier to debug because the switch diagnostics information is printed based on physical locations. The base topology files only contain logical locations. Running the Eannotator command is required to update jack information for switch diagnostics. See the Eannotator command in the book PSSP: Command and Technical Reference for more information on running the command.
After you have annotated your topology file, if any nodes get added, you need to re-annotate and store the topology in the SDR. You also need to run the Estart command in order to bring any new nodes into the switch network.
Using SMIT
Using the command line
You can annotate a switch topology file with the following form of the command:
Eannotator -F input_file -f output_file -O yes
For example, to annotate a topology file for a two-switch or maximum 32-node system:
Eannotator -F expected.top.2nsb.0isb.0 -f expected.top.2nsb.0isb.0 -O yes
You can use the Etopology command to store the topology file in the SDR in the current system partition.
Using SMIT
Using the command line
To store a topology file from the command line, use the Etopology command in the form:
Etopology topology_filename
where topology_filename is the name of the topology file that suits your configuration.
For example, to store a topology file for a two-switch or 32-node maximum configuration, run the command:
Etopology expected.top.2nsb.0isb.0
|In a two-plane SP Switch2 configuration, the named file is applied |to all switch planes unless you use the -p flag to specify |otherwise.