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

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

This soft copy for use by IBM employees only.
•
The host listed in each of the custom files has the same interface as the
hostname of the Control Workstation.
•
The SDR is up and can answer a call.
• There is exactly one default partition whose name is the same as that stated
in the SP object class (that is, host name of the Control Workstation).
• The existing SDR is consistent by calling the spchk_syspars command before
setting up the new partitions.
• The command generates a list of affected and unaffected nodes based on the
current configuration and the data for the new partitions in the
syspar
directories.
•
The VSDs will not span the new partitions by running the
verparvsd
command.
If any errors are generated from these checks, then the
spapply_config
command will quit there and report an error. All of the issues have been
discussed previously, so run back through the details to rectify the situation.
When all these checks have been completed without error, the
spapply_config
command begins the reorganization of the SDR and daemons as follows:
• Deletes heartbeat and host_responds daemons for partitions that will not
exist in the new partitioned environment (as partitioning may previously have
been set up on the system).
•
Creates the new partitions using the
SDRAddSyspar
command, which creates
the new SDR directories, object classes, and SDR daemons.
•
Moves data from the original Node, Adapter, host_responds and
switch_responds to the newly-created ones, but only for the affected nodes.
•
Opens a custom file in the syspar directory to get the data to put into the
Syspar object class.
•
Updates Syspar_map object class with new information for the affected nodes
such as the syspar_name and syspar_addr.
•
After obtaining the code level of the partition, it makes and starts the new
heartbeat daemon (as the heartbeat may be in compatibility mode for an AIX
Version 3.2.5 partition).
• Makes and starts the new host_responds daemon.
•
Adds the path to the layout directory in the SP object class.
• Runs the partitionVSDdata command to restructure the VSD data (if it exists).
•
Deletes any partitions that no longer exist in the newly-partitioned system by
running the
SDRRemoveSyspar command, which deletes the SDR daemon and
SDR data associated with the partition.
• Sets up the switch in each partition by running Eprimary, Eannotator, and
Etopology
. This loads the new topology file into the SDR, which is then ready
to run the
Estart
command when the nodes are available.
•
Verifies that the data in the SDR is correct by running the command
spverify_config
, which checks against the original data supplied in the
syspar directory.
If there are any errors, then check manually in the relevant SDR object classes.
Check that the newly-created data was copied from the syspar directory without
any errors, and similarly, that the data got moved from the existing object
Chapter 5. System Partitioning
151