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

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

This soft copy for use by IBM employees only.
the object class with a program such as
vi
, but be sure to copy the object class
to a safe place first should the file become inadvertently corrupted.
Also, because the SDR daemon was bypassed during this operation, it is
essential to refresh the relevant daemon (that is, the one for that partition) so
that the change can take effect. Use the
stopsrc
and
startsrc
commands, as
shown in previous examples.
The second object class that gets created is Syspar, which is a partition-specific
class (so there is one for each partition) that contains all the attributes that were
entered in the SMIT fields when the partition was customized. Run the following
commands if you have problems with a particular partition:
# export SP_NAME=<syspar name>
# SDRGetObjects Syspar
The data should match the data contained in the custom file that was created
during the customization of the partition. Ensure that the data is consistent
between the SDR and the custom file, and correct any errors. Following is the
data from the
SDRGetObjects
command for the default partition in the example:
syspar_name ip_address install_image syspar_dir code_version
spcws
9.180.6.199 default /spdata/sys1/sypar_configs/1nsb0isb
/config.8_8/layout.1/syspar.1 PSSP-2.1
The default partition is at PSSP 2.1, which is shown by the
code_version
attribute. Here is the same data for the second partition:
syspar_name ip_address install_image syspar_dir code_version
sppart2
9.180.6.198 default /spdata/sys1/sypar_configs/1nsb0isb
/config.8_8/layout.1/syspar.2 PSSP-2.1
This data is consistent with the
custom file example in the previous examples.
5.4.4 SDR Locking
Now that there is the potential to have multiple SDR daemons accessing the
same systemwide or global object classes, there is the requirement to have a
persistent locking mechanism to prevent simultaneous updates of object classes.
The lock files are created in the following directory:
/spdata/sys1/sdr/system/locks
The file that is created contains details of the node updating the SDR and the
partition to which it belongs.
Whenever the SDR daemons are started up, they check for the presence of any
lock files in case they were left behind when an update of the SDR ended
abnormally. If any are found at this point, they are removed. This is another
good reason why it is a good idea to recycle the SDR daemons when there are
apparent SDR problems.
5.4.5 The Restructured SDR
The SDR gets reorganized during the
apply stage of System Partitioning. Before
the new partitions are set up, there are some checks that are carried out by the
spapply_config
command that carries out the
apply of the partitioning. This
command verifies the following:
•
The data in the specified layout directory (see the previous section on
verifying the configuration for more details).
150
SP PD Guide