IBM RS/6000 SP Problem Determination Manual page 164

Hide thumbs Also See for RS/6000 SP:
Table of Contents

Advertisement

4. The SDR is not up or is not responding.
5. The current data in the SDR that relates to the partitioning has
Check and correct any problems associated with points 1, 2, and 3. If everything
is correct in these areas, then proceed to the next section to find out how to
resolve problems with the SDR.
5.3.6 Applying the System Partitioning
The key step at this point is to ensure that all affected nodes are shutdown. This
is critical to the health of these nodes in the newly-partitioned environment.
Shutting them down is the best way to guarantee that all the daemons and files
will be configured correctly in the new partitions. Shut the nodes down in the
correct manner according to the normal working procedures on the system (that
is, in the correct order from the spmon GUI or the command line).
When the
tasks are carried out:
If the apply fails, then record the error message that appears on the SMIT
screen. In order to debug this further, read the following sections about the SDR
and heartbeat subsystems.
5.3.7 Validating the Partitions and Restoring the SDR
The option remains to restore the SDR that was archived earlier in the
procedure, but it is worth understanding why the apply failed in case the same
problem occurs the next time you attempt to implement System Partitioning.
To restore the SDR, go to the SMIT menu Restore System Partition
Configuration, list the archived files, and select the appropriate backup or
archive to restore. This will run the following command:
# /usr/lpp/ssp/bin/sprestore_config
This script restores the original SDR and reverses the actions carried out in the
apply of the partitions. For example, it will stop and remove the multiple
daemons.
Even if the apply was successful, it is still a good idea to run the following
command to verify that the partitioning configuration is good in the SDR before
the affected nodes are rebooted:
# splstdata -p
The
the SDR was updated correctly, but it can be run manually from the command
line as a final check.
144
SP PD Guide
inconsistencies or is incorrect.
spapply_config
The SDR is restructured for the partitions and the multiple daemons are
created and started.
The heartbeat and host_responds are restructured and the multiple daemons
are created and started.
The switch gets configured according to the new partitions (if there is one
installed).
Validates that the VSD configuration is consistent with the partition being set
up.
spapply_config
command calls the
This soft copy for use by IBM employees only.
command is run (without the
spverify_config
-v
flag), the following
command to check that

Advertisement

Table of Contents
loading

Table of Contents