IP and subnet change.

[brian_31]

We have a SG environment where the subnets and ip's are going to be changed. What would i have to do so that the SG works fine..Here is what i think

1. change the ip of the system using set_parms and reboot
2. now edit the existing pkg ascii file under /etc/cmlcuster for the subnet and heartbeat information.
3. change the line staring with IP in the pkg script file
run checkconf and then if it is OK run applyconf..

Is this correct? Please advise.

Thanks

Brian

[MarkSyder]

I've done and documented this:

1. Amend the ip address in /etc/hosts. If using NIS, add entry for slave server to /etc/hosts.

2. Amend /etc/rc.config.d/netconf - change to new ip address and change the ROUTE_GATEWAY to the new subnet.

3. Amend the YPBIND entry in /etc/rc.config.d/namesvrs to -ypset and set YPSET_ADDR to the address of the slave server.

4. Shut the server down.

5. Ask the network administrator to change the port.

6. Change the ip address on the NIS server's hosts file.

7. Change the entries in DNS.

8. When the server comes back up log in and check access to other servers.

9. Amend the file /etc/rc.config.d/namesvrs to remove the -ypset and ip address (leaving them in is a security risk). Run the following commands: (if using NIS)

/sbin/init.d/nis.client stop
/sbin/init.d/nis.client start

10. Check that networked filesystems are available. If necessary run the following commands:

/sbin/init.d/nfs.client stop
/sbin/init.d/nfs.client start

If this server exports filesystems to other servers/workstations you will also have to stop and start nfs.server.

Mark Syder (like the drink but spelt different)

[A. Clay Stephenson]

You should start by halting the packages and the cluster otherwise you are on the correct course. The other thing to consider is than VLAN's will probably be changed so that there will be switch and router configurations to change. Normally, I make certain that all of the external networking changes have been done before I apply the changes to the cluster.

You also just mention the package ascii file but you are going to have to make equivalent changes in the cluster IP ascii file as well because it appears that you stationary IP addresses are changing as well as possibly your heartbeat IP's.

[yulianto piyut]

1. before you change ip address, halt your package, node, and then your cluster
2. make sure to change your cluster configuration file (under /etc/cmcluster, depend on your cluster configurations)
3. make sure to change your /etc/hosts, /etc/rc.config.d/netconf (automatically changed if you change the ip address via SAM)
4. check your cluster (cmcheckconf)
5. start your cluster (cmruncl)


-yut-