8.2 Changing an IP Address on the Public LAN

This section explains how to change the IP address setting if the IP address of a public LAN or administrative LAN changes after the PRIMECLUSTER system is installed. Note that when you change an IP address, do not change the host name.

Operation Procedure:

Execute the following command on one of the cluster nodes to stop RMS operation:
```
# hvshut -a
```
Execute the following command on each cluster node to stop the shutdown facility:
```
# sdtool -e
```
If you use the shutdown facility to change an IP address when you change the public or administrative LAN, you must decide whether the /etc/opt/SMAW/SMAWsf/rcsd.cfg file must be changed on each cluster node. The file does not need to be changed if the host name registered to /etc/inet/hosts is defined in "admIP" of the rcsd.cfg file. The file must be changed if an IP address is defined in "admIP." In this case, change the "admIP" definition.
For details about the rcsd.cfg file, see the rcsd.cfg(4M) manual page.
To change the IP address of either the remote console connection unit or the XSCF when you change the public or administrative LAN, correct the /etc/inet/hosts file of each node.
To change the IP address of either the remote console connection unit or the XSCF when you change the public or administrative LAN, execute the following command in any cluster node and determine whether the IP address of either the remote console connection unit or the XSCF used by the shutdown facility must be changed. The IP address does not need to be changed if the host name registered to /etc/inet/hosts is displayed in the "IP-address" field of the command output
The IP address must be changed if an IP address is displayed in the "IP address" field.
```
# /etc/opt/FJSVcluster/bin/clrccusetup -l
```
Example: In the following example, the IP address must be changed.
```
# /etc/opt/FJSVcluster/bin/clrccusetup -l
device-name cluster-host-name  IP-address      host-name      user-name
-------------------------------------------------------------------------
xscf        narcissus          10.10.10.11     -              user01
xscf        sweetpea           10.10.10.12     -              user02
```
If in Step 5 you determined that the IP address must be changed, execute the following command in each cluster node to change the IP address of the either remote console connection unit or the XSCF.
For IP-address, specify the IP address or host name of the remote console connection unit or XSCF.
```
# /etc/opt/FJSVcluster/bin/clrccusetup -m -i IP-address
```
Example: In the following example, the IP address of either the remote console connection unit or the XSCF is changed to 10.10.10.21.
```
# /etc/opt/FJSVcluster/bin/clrccusetup -m -i 10.10.10.21
```
Execute the following command in all nodes to start the system in single-user mode:
```
# /usr/sbin/shutdown -y -g0 -i0
     :
ok> boot -s
```
Execute the following command in all nodes to mount the file system:
```
# /usr/sbin/mountall -l
```
Edit the /etc/inet/hosts file, and change the IP address of each node.
On each node, change the IP address of the public LAN used by Web-Based Admin View.
See
For details, see "7.1 Network address," "7.3 Management server," and "7.5 Multi-network between server and client by classified use" in the "PRIMECLUSTER Web-Based Admin View Operation Guide."
If a takeover IP address must be changed, correct the IP address being used as the takeover IP address in the "/etc/inet/hosts" file of each node.
If you used the userApplication Configuration Wizard to create an Ipaddress resource, edit the "/opt/SMAW/SMAWRrms/bin/hvenv.local" file on each cluster node as shown below to disable RMS automatic startup during system restart.
```
# vi /opt/SMAW/SMAWRrms/bin/hvenv.local <Return>
```
```
export HV_RCSTART=0
```
Restart the system on all nodes.
```
# /usr/sbin/shutdown -y -g0 -i6
```
If you used the userApplication Configuration Wizard to set up an Ipaddress resource, take the following steps to change the takeover IP address in the resource database.
1. Identify the takeover IP address resource to be changed in the resource database.
  Execute the "clgettree(1)" command on one of the cluster nodes. The takeover IP address resource has the resource class name for IP addresses.
  Example) In the following example, the resources with resource IDs 56 and 57 are the takeover IP address resources.
```
 # /etc/opt/FJSVcluster/bin/clgettree
 Cluster 1 cluster
      Domain 2 RC2
              Shared 7 SHD_RC2
                      SHD_Host 58 config_Ipaddress0_ip1 UNKNOWN
                              IP_Address 56 hme0:1 UNKNOWN narcissus
                              IP_Address 57 hme0:1 UNKNOWN sweetpea
              Node 3 narcissus ON
                      Ethernet 21 hme0 UNKNOWN
                              IP_Address 56 hme0:1 UNKNOWN
                      Application 31 proc1 UNKNOWN
                      DISK 19 c0t0d0 UNKNOWN
              Node 5 sweetpea ON
                      Ethernet 22 hme0 UNKNOWN
                              IP_Address 57 hme0:1 UNKNOWN
                      Application 32 proc1 UNKNOWN
                      DISK 20 c0t0d0 UNKNOWN
```
2. Identify the shared resources of the takeover IP address.
  To identify the shared resources, execute the "clgettree(1)" command on one cluster node.
  The shared resources of the takeover IP address are resources that have the SHD_Host resource class name.
  Example) For the example shown in Step 1), the resource that has resource ID 58 is the shared resource of the takeover IP address.
3. Change the takeover IP address.
  To change the address, execute the "clsetrsc(1M)" command. The takeover IP address is defined in the attributes of the shared resource for the takeover IP address that was identified in Step 2.
  On each cluster node, execute the "clsetrsc(1M)" command with the following format.
```
# /etc/opt/FJSVcluster/sys/clsetrsc -A ip_addr=new-IP-address resource-ID-of-shared-resource-having-IP-address
```
  Example) To change the takeover IP address of a shared resource (resource with resource ID=58) to 10.10.10.10
```
# /etc/opt/FJSVcluster/sys/clsetrsc -A ip_addr=10.10.10.10 58
```
4. Execute the "clgetrsc(1)" command to check that the takeover IP address was changed.
  Using the command format below, execute the "clgetrsc(1)" command on one of the cluster nodes and check that the takeover IP address was changed.
```
# /etc/opt/FJSVcluster/sys/clgetrsc -a ip_addr resource-ID-of-shared-resource-having-IP-address
```
  Example) If the takeover IP address of a shared resource (resource with resource ID=58) was changed to 10.10.10.10
```
# /etc/opt/FJSVcluster/sys/clgetrsc -a ip_addr 58
ip_addr 10.10.10.10
```
If you edited the /opt/SMAW/SMAWRrms/bin/hvenv.local file in Step 12, return the file to its previous setting.

Note

An interface or IP address to which MAC address takeover has already been configured cannot be used in Web-Based Admin View.
If a takeover IP address has been defined by GLS and if the takeover IP address is specified directly with an IP address value, not a host name, in the GLS environment settings and the Gls resource settings, first delete the Gls resource. Then change /etc/inet/hosts and the GLS environment settings, and register the Gls resource.
For details, see "8.8.3 Supplement on Cluster Application and Resource Deletion," "6.1.1 GLS Setup," and "6.6.1.4 Creating Gls Resources."
When the connection to XSCF is SSH connection, check that user inquiries of the first SSH connection (such as generation of the RSA key) have completed by connecting to XSCF from the cluster nodes via SSH using the log in user account for the shutdown facility after changing the IP address.