Change Hostnames and IP Addresses on SP for PSSP 2.1

This information describes the activities that the admin user needs to execute when changing the IP address or hostname for the SP nodes and control workstation (CW). Avoid making any hostname or IP address changes if possible. The tasks are numerous and in some cases require re-execution of the installation steps.

This document is intended solely for use on AIX Version 4.1.3 or later and Parallel System Support Program (PSSP) version 2.1 systems.

The changing of the hostnames and IP addresses of SP nodes affects the whole SP system. Hostnames and IP addresses are located in the System Data Repository (SDR) and require working with objects and attributes. Hostnames and IP addresses are also kept in various files that are located on the SP nodes and the CW. These changes can cause problems with Network Installation Manager (NIM), System Partition objects and configuration files on your SP system.

HI

indicates those commands that should be executed when changing either hostnames OR IP addresses.

H

indicates those commands that are to be executed when changing HOSTNAMES ONLY.

I

indicates those commands that are to be executed when changing IP ADDRESSES ONLY.

NOTE: In this document "hostname" refers to the name returned as output when the hostname command is run on the machine. "Short_hostname" refers to the portion of the machine hostname before the first period.

For example:

• Let's say the hostname command gives an output on the Control Workstation as follows:

     spcntl.aix.dfw.ibm.com 
  

  The hostname is spcntl.aix.dfw.ibm.com and the "short_hostname" is spcntl.

• Let's say the hostname command gave an output on the Control Workstation as follows:

     spcntl 
  

  The hostname is spcntl and the "short_hostname" is spcntl.

This document is intended solely for use on AIX 4.1.3 or later and Parallel System Support Program (PSSP) version 2.1 systems. If you are unsure which version of PSSP you are running, run the command lslpp -h ssp.basic. You should see the version number displayed in the output:

   PATH: /usr/lib/objrepos 
   ssp.basic 
   02.01.0000.0000 
   ****** 

The SDR objects that reference the hostname and IP address changes are as follows:

Adapters

deals with ent, css0, tr0, fi0 IP addresses and adapters.

Frame

deals with the MACN CWS attribute and works with hostnames.

Node

works with initial/reliable hostnames and uses the IP address for boot servers. Node objects are organized in system partitions.

SP

deals mostly with CW attributes, but uses hostname when working with ntp, printing, user management, and accounting.

SP_ports

deals with hostname used with hardmon and CW.

Switch_partition

works with hostname of primary node used with switch.

JM_domain,Pool

works with Resource Manager and references hostnames.

Syspar

deals with IP address and SP_NAME used with system partitions.

The following are files which contain IP Addresses, or hostnames that exist on SP nodes and CW. Look through these files when completing the procedures for changing hostnames and IP addresses for your SP system.

/.rhosts

contains hostnames used exclusively with rcmd services.

/.klogin

contains hostnames used with authentication rcmd services.

/etc/hosts

contains IP addresses and hostnames used with the SP system.

/etc/resolv.conf

contains the IP address for domain name service (Opt).

/etc/rc.net

contains alias IP addresses used with System Partitions.

/var/yp/<nis>

Network Information Service references hostname and IP address.

/etc/niminfo

works with the NIM configuration for NIM master information.

/etc/krb.conf

works with hostname for authentication server.

/etc/krb.realms

works with the hostname of SP nodes and authentication server.

/etc/krb-srvtab

provides authentication service key using hostname.

/etc/SDR_dest_info

specifies the hostname and IP address of the CW and SDR.

/etc/ssp/cw_name

specifies the IP address of the CW hostname (SP nodes).

/etc/ssp/server_name

specifies the IP address and hostname of the SP server of the boot and install adapter servers (SP nodes).

/etc/ssp/server_hostname

specifies the IP address and hostname of the SP server.

/etc/ssp/reliable_hostname

specifies the IP address and hostname of the SP node.

/etc/ntp.conf

works with the IP address of the ntp server (Optional).

/etc/filesystems

may contain the IP address or hostname of the nfs systems mainly used on /usr client systems.

/etc/jmd_config

works with hostnames for Resource Management pools (CW).

/tftpboot/<host>.config_info

contains the IP address and hostname for each SP node, and is found on CW and boot servers.

/tftpboot/<host>.install_info

contains the IP address and hostname for each SP node, and is found on CW and boot servers.

/tftpboot/<host>-new-srvtab

provides authentication service keys using hostname, and is found on CW and boot servers.

Changing the hostname or IP address for an SP node and CW will follow the same procedures, except that the Control Workstation will include additional network and SP configuration steps.

1. Update PSSP files and interfaces on the SP nodes.

2. Update the en0 network interface on each SP node that has IP address, domain, or hostname changes.

   NOTE: Know the new selected IP addresses and hostnames being used by the SP nodes, Control Workstation, and gateway servers. This is required so that the SP node will properly communicate to the Control Workstation during the reboot activity. This is a manual activity for each SP node.

3. Work on the Control Workstation and make the necessary changes to the System Data Repository (SDR). This includes:
   • Updates to reset PSSP daemons and System Partitions (syspar) files.
   • Update files on the Control Workstation to reflect the new hostnames and IP addresses. NOTE: During this activity the SP system should not be available to users. The SP system is not ready until the SP nodes reference the new IP address and hostname changes.

4. Set the boot response to "customize" and then execute a reboot for the SP nodes.

   After the SP nodes have completed the reboot and customized, verify that the files on the SP nodes reflect the new IP address and hostname changes.

   NOTE: The added Install support in AIX 4.1 for NIM requires the admin user to replace the NIM master objects. It may be necessary to update the NIM network and machine resources to match the new IP address or hostname. The NIM updates will be needed for the CWS and bootserver nodes.

   NOTE: If you had previously used System Partitioning on your SP system, it will be necessary to re-execute the System Partition steps on your system. This will allow the necessary syspar config files to reflect any changes.

5. HI: Change name resolution on the control workstation, the nodes and at any nameservers to use the new hostnames and IP addresses.

NOTE: Do not proceed until this step is completed. Many commands use name resolution to update the system.

Current mksysb images may have old name resolution data in them. To avoid accidentally restoring inaccurate name resolution data, the mksysb images should be remade after the conversion of hostnames and IP addresses on the entire system is complete.

The following SP node updates need to be made on every SP node prior to updates made to the Control Workstation (CW).

1. Update the SP node en0 Interface with the mktcpip command.

   This will update the en0 interface on each SP node to allow the proper communication paths between the SP node and the Control Workstation. The mktcpip command will allow you to:

   • Change the en0 interface to the new IP address and hostname.
   • Supply the proper gateway and route information for the en0 adapter.
   • Modify any other adapter interfaces on the SP node.

   HI: The mktcpip command can be executed through smit mktcpip or the mktcpip command on each SP node. The following are examples of using the mktcpip command.

   mktcpip -h <new node hostname> -a <new node IP addr> -m <subnet mask> 
   -i en0 -n <name server> -d <domain> -g <gateway IP addr> -t N/A " 
   

   The following will change the hostname of node k22n06 to be referenced as new node hostname k88n06 in domain ppd.pok.ibm.com.

   "/usr/sbin/mktcpip -h'k88n06.ppd.pok.ibm.com' -a'129.40.88.70' 
   -m'255.255.255.192' -i'en0' -n'129.40.70.1' -d'ppd.pok.ibm.com' 
   -g'129.40.88.126' -t'N/A'" 
   

   NOTE: Do not change the hostname via the hostname command. This only makes a temporary change. If you don't want to use mktcpip to change the hostname, then use smitty hostname to make the change permanent.

2. Update the NIM files and configuration.
   1. HI: Update the /etc/niminfo file to provide the new hostname and IP address changes for the NIM client, master, and file references.

      /etc/niminfo 
      

      Change NIM_NAME, NIM_HOSTNAME, NIM_MASTER_HOSTNAME, NIM_BOSINST_RECOVER, SPOT, NIM_CUSTOM, and NIM_HOSTS, replacing old names and addresses with the new ones.

   2. HI: If the node is a bootserver (or a NIM master), remove all NIM objects from the node. This is accomplished by executing the following:

      /usr/sbin/nim -o unconfig master 
      

      HI:

      /usr/sbin/installp -u bos.sysmgt.nim.master 
      

3. Update the following PSSP files to place the new hostname and IP address information for node and server information.
   1. I: Update the /etc/SDR_dest_info file using new CW and SDR IP addresses.

      vi /etc/SDR_dest_info 
      

      Change the IP address of the SP ethernet interface to the control workstation (keep in mind that you may need to put in one of the alias addresses depending on the partition to which this node belongs).

   2. Update the /etc/ssp/ files cw_name, server_hostname, and server_name to reference the new boot server hostname and IP address.
      • HI: Change the control workstation ethernet address.

        vi /etc/ssp/cw_name 
        

      • HI: Change the boot server hostname and IP address.

        vi /etc/ssp/server_hostname 
        

      • HI: Change the boot server hostname and IP address.

        vi /etc/server_name 
        

   3. Update the /etc/ssp/reliable_hostname file to reference the new node client hostname and IP address.

      HI: Change the node's hostname and IP address.

      vi /etc/ssp/reliable_hostname 
      

   4. HI: Make sure that the SP_NAME environment variable is blank.

      unset SP_NAME 
      

   5. HI: Execute a /usr/lpp/ssp/kerberos/bin/kdestroy to remove any active kerberos ticket-granting-tickets. You may need to update the /etc/krb.conf file to point to the correct kerberos server.

      /usr/lpp/ssp/kerberos/bin/kdestroy 
      vi /etc/krb.conf 
      

      Make sure that it has the name of the control workstation so that it can find the kerberos database.

      You should now be completed at the SP node. You need to make the changes at the Control Workstation and then reboot the SP nodes.

The following tasks need to be executed by the admin (root) user on the Control Workstation when changing the ethernet IP addresses or hostname.

1. HI: Update files on the CW that may reflect IP address or hostname changes.
   1. Update the .rhosts or .klogin files that may exist.
      • cd to home directory for each user that uses remote commands (for example, rsh).

      • vi .klogin (or .rhosts, or both).

   2. Update the /etc/filesystems and /etc/jmd_config.<SP_NAME> files for SP configuration.
      • HI: Change any mounted filesystems that may come from a host that has changed hostnames (or IP addresses) as appropriate.

        vi /etc/filesystems 
        

      • HI: Each partition will have a jmd.config file, but not the files with a date extension.

        ls /etc/jmd* 
        

      • H: Where SP_NAME is the name of each partition, change the hostnames listed in the files accordingly.

        vi /etc/jmd.config.<SP_NAME> 
        

   3. H: Check to make sure that the /tftpboot/script.cust file is updated to reflect IP address and hostname changes. Instead of hardcoding hostnames, reference the $SERVER and $CW variables.

      vi /tftpboot/script.cust 
      

2. If currently in a System Partition configuration:
   1. HI: Save the current SDR attributes by executing an archive:

      /usr/lpp/ssp/bin/SDRArchive 
      

   2. HI: Backup the current /spdata file system in case there are problems doing the IP Address and hostname changes.

      tar -cvf /dev/rmt0 /spdata 
      (provided you are backing up to tape rmt0) 
      

      You will need to reference the old and the new System Partition names (SP_NAME) and IP addresses for the following tasks.

   3. HI: Reset the SP system back into one default system partition prior to changing the IP address hostname in the SDR. Type smitty and execute the indicated actions at the appropriate screens.

      9076 SP System Management 
      9076 SP Configuration Database Management 
      Enter Database Information 
      System Partition Configuration 
      Select System Partition Configuration 
      	(select a single partition configuration - for example, config.16) 
      	press Enter to execute 
      	hit PF3 to back up one screen 
      Display Information for Given Configuration or Layout 
      	hit enter to execute 
      	verify that the output is a single partition that is a true representation of your system 
      	hit PF3 to back up one screen 
      	hit PF3 to back up one screen to the screen entitled: 
      System Partition Configuration 
      Select System Partition Layout 
      	select .../layout.1 (there should not be a layout.2, and so on) 
      	hit PF3 to back up a screen 
      Enter Customization Information for a Selected System Partition 
      	select .../layout.1/syspar.1 
      	fill in the IP address of the SP ethernet adapter on the Control Workstation 
      	select a PSSP Code Level of PSSP-2.1 
      	press Enter to execute and create the custom file 
      	hit PF3 to back up one screen 
      	hit PF3 to back up one screen to the screen entitled: 
      System Partition Configuration 
      Apply System Partition Configuration 
      

      At this point the SDR (System Data Repository) is set for a single partition. This will make it easier to change the hostname and IP addresses on the CW.

3. H: Change the SP class before stopping the SDR daemon, where <short_hostname> is the short hostname for the CW.

   SDRChangeAttrValues SP control_workstation=<short_hostname> 
   

4. HI: Stop all the PSSP daemons--sdr, hb, hr, hardmon--on the CW.

   /bin/stopsrc -g sdr 
   /bin/stopsrc -g hb 
   /bin/stopsrc -g hr 
   /bin/stopsrc -s hardmon 
   

5. HI: Remove the current source master objects for sdr, hb. and hr for each System Partition (SP_NAME) reference.

   /usr/lpp/ssp/bin/sdr -spname <SP_NAME> rmsrc 
   /usr/lpp/ssp/bin/hb  -spname <SP_NAME> rmsrc 
   /usr/lpp/ssp/bin/hr  -spname <SP_NAME> rmsrc 
   

   HI To obtain the spname for each partition to be used in each of the preceding commands, execute the following command:

   /usr/lpp/ssp/bin/SDRGetObjects Syspar_map syspar_name 
   

   Execute the preceding commands for each DIFFERENT partition name (syspar_name).

6. HI: Using mktcpip or the chdev command, specify the new IP address or hostname changes required for the CW.

   mktcpip -h <new CW hostname> -a <new CW IP addr> -m <subnet mask> 
   -i en0 -n <name server> -d <domain> -g <gateway IP addr> -t N/A " 
   

   NOTE: Do not change the hostname via the hostname command, as this makes only a temporary change. If you don't want to use mktcpip to change the hostname, then use smitty hostname to make the change permanent.

   1. HI: If multiple system partitions exist, update the /etc/rc.net file to reference the new alias addresses used for system partitions.

      vi /etc/rc.net 
      

   2. HI: Add the following command for each partition other than the default:

      /usr/sbin/ifconfig <adapter> alias <ip-address> 
      netmask <ip mask> up  \>>$LOGFILE 2>&1 
      

      <adapter> is the adapter that corresponds to the IP address returned from the hostname command, <ip-address> is the alias IP address for the partition, and <ip mask> is the netmask for that IP address. For example:

      /usr/sbin/ifconfig tr0 alias 129.40.127.101 netmask 255.255.255.0 up 
      

      Make sure you enter the above command into /etc/rc.net for each partition other than the default.

   3. HI: Execute the /etc/rc.net to configure the new alias addresses.

   4. Manually update the /etc/SDR_dest_info and /spdata/sys1/spmon/hmacls files to the new IP address and hostname used with hardmon and SDR.

      I:  vi /etc/SDR_dest_info
      H:  vi /spdata/sys1/spmon/hmacls
      

   5. HI: Move the system partition directories found at location /spdata/sys1/sdr/partitions from old IP addresses to the new IP addresses for each system partition reference.

      cd /spdata/sys1/sdr/partitions 
      /bin/mv   <OLD IP_ADDR>   <New IP_ADDR> 
      

7. Execute the setup_authent script to create authentication services for the new hostname being used.

   This should only be executed for hostname changes for the CW. It is not required for changes made to IP addresses, or with SP node updates. Reference Step 12 in the SP Installation Guide.

   H: Manually check that the authentication files /etc/krb.conf, /etc/krb.realms, and /etc/krb-srvtab reference the new hostname.

   setup_authent 
   vi /etc/krb.conf (change the hostname) 
   pg /etc/krb.realms (to see if it exists) 
   if /etc/krb.realms exists: 
   vi /etc/krb.realms (change the hostname) 
   ksrvutil list (check for new hostname in krb-srvtab) 
   

8. Create the new master resources for the sdr, hb, and hr daemons.

   HI: Execute the /usr/lpp/ssp/inst_root/ssp/inst_root/ssp.basic.post_i script to recreate and start the daemons. It is NORMAL to get errors, so do not rerun this script. Ignore the errors at at this point.

   /usr/lpp/ssp/inst_root/ssp.basic.post_i 
   /bin/lssrc -g sdr (check that an sdr for each partition is listed) 
   /bin/lssrc -g hb  (check that an hb for each partition is listed) 
   /bin/lssrc -g hr  (check that an hr for each partition is listed) 
   

9. After the sdr daemon has been properly activated on the SP system, manually execute SDRChangeAttrValues for the CW.
   • H: Change the hostname attribute using the new hostname for the SP_ports object.

     SDRChangeAttrValues SP_ports hostname=<hostname> 
     

   • H: Change the MACN attribute using the new hostname for the Frame object.

     SDRChangeAttrValues Frame MACN=<hostname>
     

     <hostname> is the hostname for the control workstation.

   • HI: Change the control_workstation attribute using the short hostname for the SP object.

     SDRChangeAttrValues Syspar syspar_name=<short_hostname> \ 
     ip_address=<New IP_addr> 
     SDRChangeAttrValues Syspar_map syspar_name= <short_hostname> 
     syspar_addr=<New IP_addr> 
     

10. HI: Remove the current Network Installation Manager (NIM) database and configuration files on the CW. Execute:

    /usr/sbin/nim -o unconfig master 
    /usr/sbin/installp -u bos.sysmgt.nim.master 
    

11. HI: Reboot the control workstation. This establishes a clean system to reflect the IP address and hostname changes.

    shutdown -Fr 
    

    HI: Verify that all PSSP daemons are getting activated from the /etc/inittab.

    ps -ef | pg 
    

    Look for sdrd, hrd, hbd, hardmon, kadmind, and xntpd.

12. Using CMI or the spsitenv command, specify any hostname changes that may be referenced for ntp, printing, and user management. Reference Step 15 in the SP Installation Guide.

    (optional) HI: Type smitty.

    9076 SP System Management 
    9076 SP Configuration Database Management 
    Enter Database Information 
    Site Environment Information 
    

    Change any necessary hostnames or IP addresses and execute.

13. H: Move the /home/<CW> directory and update the amd map as follows:

    mv /home/<old_CW_hostname> /home/<new_CW_hostname> 
    vi /etc/exports (change the exported home directory) 
    exportfs -a 
    vi /etc/amd/amd-maps/amd.u 
    

    Do a global change from the old hostname to the new hostname throughout the file as follows:

       :g/old_hostname/s//new_hostname/g 
       :wq 
    

    Now amd will function properly once supper propagates the amd.u file.

14. Update the SDR objects using commands, or by using the SMIT based 9076 SP Configuration Management Interface (CMI). You may need to execute the following activities from each system partition.
    1. HI: Using CMI or the spethernt command, specify the new ethernet IP address or hostname change required for the SP nodes. Reference Step 18 in the SP Installation Guide. Type: smitty.

          9076 SP System Management 
          9076 SP Configuration Database Management 
          Enter Database Information 
          Node Database Information 
          SP Ethernet Information 
       

       Change any necessary hostnames or IP addresses and execute.

    2. HI: Using CMI or the spadaptrs command, reset the css0 and other adapters that need to reference the new ethernet IP address and hostname that was changed. Reference step 22 in the SP Installation Guide. Type: smitty.

          9076 SP System Management 
          9076 SP Configuration Database Management 
          Enter Database Information 
          Node Database Information 
          Additional Adapter Information 
       

       Change any necessary hostnames or IP addresses and execute.

    3. HI: Using CMI or the sphostnam command, reset the initial hostname that you want to use in your system. Reference Step 23 in the SP Installation Guide(Optional). Type: smitty.

          9076 SP System Management 
          9076 SP Configuration Database Management 
          Enter Database Information 
          Node Database Information 
          Hostname Information 
       

       Change any necessary hostnames or IP addresses and execute.

    4. HI: Using CMI or the spbootins command, reset the boot install server to reference the new ethernet IP address and hostname that was changed. You will need to set bootp response to "customize" for the SP nodes. Type: smitty.

          9076 SP System Management 
          9076 SP Configuration Database Management 
          Enter Database Information 
          Node Database Information 
          Boot/Install/usr Server Information 
       

       Change any necessary hostnames or IP addresses, set the bootp response to "customize", and press Enter to execute the SMIT panel.

       The SMIT panel will execute a 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 SP nodes. This process may take approximately 30 minutes.

    5. Manually verify that the following files have been successfully updated on the boot install server after running the previous CMI steps.

       /etc/ntp.conf 
       /tftpboot/<host>.config_info 
       /tftpboot/<host>.install_info 
       /tftpboot/<host>-new-srvtab 
       

    6. HI: If ntp is set to other than "consensus", on the SP environment panel update:

       pg /etc/ntp.conf 
       

    7. HI: Also check:

       ls -la /tftpboot/<host>.config_info 
       ls -la /tftpboot/<host>.install_info 
       ls -la /tftpboot/<host>-new-srvtab 
       

       If the date and time indicate a new file was generated, it is probably safe to assume that the new hostname and IP addresses are incorporated in the files.

15. HI: If you previously converted your system to a single partition, you may want to re-execute the System Partitioning steps that are specified in Chapter 5 of the System Administrators Guide. Type smitty and perform the indicated actions at the appropriate locations.

       9076 SP System Management 
       9076 SP Configuration Database Management 
       Enter Database Information 
       System Partition Configuration 
       Select System Partition Configuration 
       	(select the proper partition configuration that you desire) 
       	press Enter to execute 
       	hit PF3 to back up one screen 
       Display Information for Given Configuration or Layout 
       	hit Enter to execute 
       	verify that the output indicates the porper partitioning that you desire 
       	hit PF3 to back up one screen 
       	hit PF3 to back up one screen to the screen entitled: 
       System Partition Configuration 
       Select System Partition Layout 
       	select the proper layout that you desire 
       	hit PF3 to back up a screen 
       Enter Customization Information for a Selected System Partition 
       	*select .../layout.?/syspar.1 
       	*fill in the IP address of the SP ethernet adapter on the Control Workstation 
       	*select the proper PSSP Code Level 
       	*press Enter to execute and create the custom file 
       	*hit PF3 to back up one screen 
       	complete the previous 5 steps (marked with an *) for each additional partition 
       	hit PF3 to back up one screen to the screen entitled: 
       System Partition Configuration 
       Apply System Partition Configuration 
    

16. Execute a reboot on each of the SP nodes, using the System Monitor GUI.

    Follow the same install sequence as for Installation, by customizing the boot servers first and then customizing the remaining SP nodes. For each bootserver node, unconfigure NIM and re-execute setup_server to create the Installation files.

    Since the SP nodes are in customize mode, most configuration files will be updated to reflect the IP address and 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 SP nodes by including them in the /tftpboot/script.cust file. These may include the /etc/resolv.conf, /.rhosts, and other SP customer-owned files.

17. HI: Set the boot install server nodes to "customize" on the control workstation (make sure that Run setup_server on the Control Workstation? is set to yes). Type: smitty server_dialog.
    1. Fill in the appropriate node numbers for the boot install servers.
    2. Put 0 as the Boot/Install Server Node Identifier.
    3. Set Response from Server to bootp Request to Customize.
    4. Set Run setup_server on the Control Workstation? to yes.
    5. Execute the SMIT panel by pressing Enter.

    The SMIT panel may run for approximately 30 minutes because NIM is being reconfigured.

18. HI: Update /tftpboot/script.cust by uncommenting and changing the hostnames for the proper name resolution files (/etc/resolv.conf or /etc/hosts, /.rhosts, or any other appropriate customer-owned files).

19. HI: Reboot the boot install server nodes either through the spmon GUI or by manually logging onto the nodes and running shutdown -Fr.

20. HI: Telnet to each of the boot install servers and unconfigure NIM.

    /usr/sbin/nim -o unconfig master 
    /usr/sbin/installp -u bos.sysmgt.nim.master 
    

21. HI: Set the nodes that are not boot install servers to "customize" on the control workstation (DO THIS FOR THE NODES THAT BELONG TO EACH BOOT INSTALL SERVER). Type: smitty server_dialog.
    1. Fill in the appropriate node numbers for the nodes that belong to a boot install server.
    2. Put the node number of the boot install server as the Boot/Install Server Node Identifier.
    3. Set Response from Server to bootp Request to Customize.
    4. Set Run setup_server on the Control Workstation? to yes.
    5. Execute the SMIT panel by pressing Enter.

    The SMIT panel may execute for approximately 30 minutes because NIM is being reconfigured.

22. HI: Update /tftpboot/script.cust by uncommenting and changing the hostnames for the proper name resolution files (/etc/resolv.conf or /etc/hosts, /.rhosts, or any other appropriate customer-owned files).

23. HI: Reboot the boot install server CLIENT nodes either through the spmon GUI or by manually logging onto the nodes and running shutdown -Fr.

The following steps need to be executed for IP address and hostname changes for both the Control Workstation and the each of the SP nodes.

1. After the reboot has completed, and SP nodes have initialized, verify that the following have the correct IP address and hostname.
   • Updated SP Ethernet address specified for the SP node
   • Updated default route is correct.
   • Hostname resolution files were updated correctly (/etc/hosts).
   • The /etc/SDR_dest_info file points to the CW and SDR addresses.
   • The acct_master hostname is updated for NFS export list directory
   • /var/adm/acct (SP Accounting)
   • Files in the directories /etc/ssp cw_name, server_hostname, server_name and reliable_hostname point to the correct IP address and hostnames.
   • The files /etc/krb.conf, /etc/krb.realms, and /etc/krb-srvtab have the correct hostnames defined.

2. Modify the following files on the SP nodes to reflect the updated IP addresses and hostname definitions.
   • /etc/filesystems
   • /etc/ntp.conf
   • /etc/resolv.conf
   • /.rhosts
   • /.klogin

   If any of the files are not correct, make the proper updates for the correct IP address or hostname manually.

3. Remove the current Network Installation Manager (NIM) database and configuration files on any PSSP 2.1 bootserver node.

   /usr/sbin/nim -o unconfig master 
   /usr/sbin/installp -u bos.sysmgt.nim.master 
   

4. Execute setup_server on the bootserver node.

5. Reboot all of the SP nodes to reflect the IP address and hostname changes.

   When the SP nodes initialize, your SP system should be activated using the new IP addresses and hostnames.