IBM RS/6000 SP, Problem Determination Manual

Page: 163 / 316

This soft copy for use by IBM employees only.
Apply System Partition Configuration
Type or select values in entry fields.
Press Enter AFTER making all desired changes.
[Entry Fields]
System Partition Apply Option Verify only. +
Correct VSD configuration? No. Discontinue +
System Partition Path config.8_8/layout.1
F1=Help F2=Refresh F3=Cancel F4=List
Esc+5=Reset F6=Command F7=Edit F8=Image
F9=Shell F10=Exit Enter=Do
Figure 66. Example of SMIT Screen for Verifying the Configuration
Be particularly careful at this menu because the default for the first field System
Partition Apply Option is to
apply this configuration. Toggle to the Verify only
option using the tab key which will run the
spapply_config
command with the
-v
flag and will not actually run the
apply.
The second field, Correct VSD configuration, can be left at the default No.
Discontinue unless you want to correct any inconsistencies that may be apparent
in the VSD setup in relation to the new partitions. The fundamental issue is
often that the VSDs are spanning more than a single partition. Resolve these
issues before you begin System Partitioning, because only
non-fatal errors can
be corrected by using this option that passes the -F to the verparvsd command.
By choosing No. Discontinue, the
verparvsd
which gets called from
spapply_config
will exit if any non-fatal errors are encountered.
A common error that is generated by running verify details the fact that the
nodes are still up. This is merely a warning at this stage to remind you that the
affected nodes should be shutdown prior to the apply. Here is an example of this
message:
spapply_config: 0022-149 Warning: node: 1 in system partition spcws
has host_responds value of:
1 .
The
host_responds value of 1 indicates that the node is up. A value of 0
indicates that the node has lost connectivity across the en0 interface and could
therefore be down.
If the verify fails, then rerun the customize operation and try again. If it
persistently fails, it is likely to be for one of the following reasons:
1. The layout.desc file does not exist in the layout directory.
2. One of the nodelist, custom, or topology files does not exist in one of the
syspar directories.
3. The data in the custom file cannot be read, is incorrect, or is inconsistent.
Chapter 5. System Partitioning
143