IBM RS/6000 SP, Problem Determination Manual

Page: 298 / 316

This soft copy for use by IBM employees only.
a. Using CMI or the
spethernt
command, specify the new Ethernet IP
address or hostname change required for the RS/6000 SP nodes.
Reference Step 18 in the RS/6000 SP Installation Guide.
b. Using CMI or the spadaptrs command, reset the “css0” and other
adapters that need to reference the new Ethernet IP address/hostname
that was changed. Reference step 22 in the RS/6000 SP Installation
Guide.
c. Using CMI or the
sphostnam
command, reset the initial hostname that you
want to use in your system. Reference Step 23 in the RS/6000 SP
Installation Guide. (This is optional.)
d. Using CMI or the
spbootins
command, reset the boot install server to
reference the new Ethernet IP address/hostname that was changed. You
will need to set bootp response to “customize” for the RS/6000 SP
nodes.
The spbootins will execute the
setup_server
command, which will create all
the NIM-based files and resources required for installation. It will also
create the authentication principals for the new RS/6000 SP nodes.
You may want to manually verify that the following files have been
successfully updated after running the previously CMI steps:
/etc/ntp.conf
/tftpboot/<host>.config_info
/tftpboot/<host>.install_info
/tftpboot/<host>-new-srvtab
13. You may want to re-execute the system partitioning steps that are specified
in Chapter 5 of the System Administrators Guide. Update other files on the
CW that may reflect IP address or hostname changes.
a. Update any files that are involved with hostname resolution. The files
are /etc/hosts, /etc/resolv.conf (dns), and /var/yp/* (nis).
b. Update the .rhosts or .klogin files that may exist.
c. Update the /etc/filesystems and / e t c / j m d _ c o n f i g . < S P _ N A M E > files for
your RS/6000 SP configuration.
d. You should also check to make sure your /tftpboot/script.cust file is
updated to reflect IP address/hostname changes. Instead of hardcoding
hostnames, you may reference the $SERVER and $CW variables.
14. You can now execute a “reboot” on each of the RS/6000 SP nodes. This can
be accomplished using the System Monitor GUI. Follow the same install
sequence as during installation: customize the boot servers first, and then
customize the remaining RS/6000 SP nodes. For each bootserver node you
will need to unconfigure NIM and re-execute
setup_server to create the
Installation files. Since the RS/6000 SP nodes are in customize mode, most
configuration files will be updated to reflect the IP address/hostname
changes.
Some files will not be updated on the nodes during the customization. You may
want to “rcp” these files from the CW to the RS/6000 SP nodes by including them
in the /tftpboot/script.cust file. These may include the /etc/resolv.conf, /.rhosts,
and other RS/6000 SP customer-owned files.
278
SP PD Guide