This section discusses how to reconfigure your system to remove a switch and replace it with a new switch. It does not discuss how to install a switch initially into your system. For this information, refer to Chapter 2, Installing and configuring a new RS/6000 SP system or Adding a switch.
|If you need to move the switches in your system to locations other than |where the SP Switch switches were located, you will first need to perform this |procedure and place the SP Switch2 switches into the locations previously |occupied by the SP Switch switches. After this procedure is complete, |you can then delete and add frames as appropriate to change the locations of |your switches. |
|If you are removing a High Performance Switch and replacing it with |the SP Switch, you need to do the following:
Prior to removing an SP Switch and replacing it with the SP Switch2, you need to do the following:
IBM suggests that your system be configured as a single partition. If your system is a single partition, skip this step and proceed to the next step. If your system has multiple partitions, continue with this step.
Always archive the SDR before partitioning (or repartitioning) your
system. If you change your mind once you have committed a system
partition configuration, or if applying a system partition configuration
fails, you should use the archived SDR to recreate the previous system
partition configuration. (To do this, select the Restore System
Partition Configuration option from the SMIT menu.)
| If using: | Do this: |
|---|---|
| SMIT | At the System Partition Configuration menu:
|
| SDRArchive | Enter
SDRArchive |
| |
Either restore a previous single partition or set up a single
partition.
| To Restore a Single Partition: | To Set Up a Single Partition: |
|---|---|
Using SMIT
Using the command line The full path name of the sprestore_config command is: /usr/lpp/ssp/bin/sprestore_config archived_file | Using SMIT
Using the command line Issue the spapply_config command. |
To remove existing css0 device entries from the ODM, issue the following command:
dsh -a /usr/sbin/rmdev -l css0 -d
dsh -a ls -al /etc/SP/expected.top
cshutdown -G -N 3
This step may involve replacing the switch, switch adapters, switch cables, frame supervisors, and for some node types, the OCS modules. For more information regarding the instances when OCS module replacement is necessary, refer to the switch Miscellaneous Equipment Specifications (MES) that you received when you ordered the switch.
Your IBM System Engineer will perform this step for you using the instructions found in the Miscellaneous Equipment Specifications (MES) that you received when you ordered the switch.
To update the SDR switch information, issue the following command:
/usr/lpp/ssp/install/bin/hmreinit
Refer to Step 34: Update the state of the supervisor microcode for more information.
Issue the following command:
Eprimary -init
Use Eannotator to update the switch topology file's connection labels with their correct physical locations. Use the -O yes flag to store the switch topology file in the SDR. Using Eannotator makes the switch hardware easier to debug because the switch diagnostics information is based on physical locations.
For example, to annotate a two-switch or maximum 32-node system, enter:
Eannotator -F /etc/SP/expected.top.2nsb.0isb.0 \
-f /etc/SP/expected.top.annotated -O yes
SP Switch note:
If you are replacing a High Performance Switch with an SP Switch and your system has multiple partitions, you must run the Eannotator command against all switch topology files that are in use for any system partition.
If you entered Eannotator -O yes or yes previously when issuing the Eannotator command, skip this step.
Use Etopology to store the switch topology file in the SDR and make sure that it has been annotated. For example, to store a two-switch or maximum 32-node configuration, enter:
Etopology /etc/SP/expected.top.2nsb.0isb.0.annotated
SP Switch note:
If you are replacing a High Performance Switch with an SP Switch and your system has multiple partitions, you must run the Etopology command against all switch topology files that are in use for any system partition.
Frame 1, node 1 is the default primary node.
If you have an SP Switch or SP Switch2 system, the primary backup node takes over for the primary node when it detects that the primary node is no longer functional. By default, a node is selected from a frame that is different from the primary node. If no other frame exists (for example, a single frame system), a node is selected from a switch chip that is different from the primary node. If no other switch chip is available, any available node on the switch is selected. From the command line, use the Eprimary command to verify this node or change the primary or primary backup to another node. For example:
Eprimary 1 -backup 16
This command, without any parameters, returns the node number of the current primary node, the primary backup node, the oncoming primary node, and the oncoming primary backup node.
Use the Eclock command to initialize the switch's Clock Source. The Eclock command requires that you know the number of Node Switch Boards (NSBs) and Intermediate Switch Boards (ISBs) in your RS/6000 SP system.
Select the Eclock topology file from the control workstation's /etc/SP subdirectory, based on these numbers. For example, if your RS/6000 SP system has six node switch boards and four intermediate switch boards, you would select /etc/SP/Eclock.top.6nsb.4isb.0 as an Eclock topology file.
Eclock -f /etc/SP/Eclock.top.6nsb.4isb.0
This command sets the proper clock source settings on all switches within a 96-way (6 nsb, 4 isb) RS/6000 SP system.
See the PSSP: Command and Technical Reference for the Eclock topology file names.
Since there was a switch topology change, you need to install this software on all the nodes in the system. Use SMIT or issue the spbootins command to do this by changing the boot/install information for all the Node Objects in the SDR to specify a bootp response of customize.
Set the nodes to customize with the following command:
spbootins -r customize -l node_list
Power on the node using the cstartup command. For example:
cstartup -G -N 48
To verify that the switch adapters are functioning correctly, issue either of the following commands.
For the SP Switch adapter, issue:
SDRGetObjects switch_responds
For the SP Switch2 adapter, issue:
SDRGetObjects Adapter adapter_type==css0
If adapter_config_status shows other than css_ready, such as diag_fail, contact your IBM service representative.
This step initializes the optional switch. Perform this step from the command line by issuing:
Estart
Check the switchResponds (SP Switch) or the switchResponds0 (SP Switch2) indicator for each node.
Run a verification test to ensure the installation of the switch is complete. You can do this using the command line. For example:
CSS_test
If the verification test fails, see the section on "Diagnosing switch problems" in the PSSP: Diagnosis Guide.
This is an optional step to perform only if you have multiple partitions. To reapply your original system partition configuration, follow Steps 2 through 6 of "Partitioning the SP system" in the "Managing system partitions" chapter of the PSSP: Administration Guide.