Hi
You could try this steps below:
Changing the IP on a LAN adapter has a potentially major effect on
ServiceGuard. Although online cluster reconfiguration is a ServiceGuard
feature, it does not allow IP changes to be done with the cluster running.
Cluster downtime should be scheduled to accommodate the IP modification if it
affects the cluster.
1) Determine whether downtime is necessary by using the following sort of
command:
# cmviewconf | grep 10.126.0.17 (OLD IP)
ip address: 10.126.0.17
If the "ip address:" line appears, then the IP is embedded in the cluster
binary, and it influences the actions of the cluster. This means the cluster
binary must be updated with the new IP in order for the cluster to operate
properly. If the subnet changes along with the IP, packages that depend on
that subnet must be updated as well.
If the cluster binary must be updated, it is necessary to perform the IP
changes before updating the cluster. Do this before proceeding with the
rest of this document.
2) With the LAN IP updated, create a current cluster configuration ASCII file
in /etc/cmcluster:
# cd /etc/cmcluster
# cmgetconf CONF
Edit the file, locate the lines containing the old IP and update the IP. The
lines will look something like this:
NETWORK_INTERFACE lan0
HEARTBEAT_IP 10.126.0.17
NETWORK_INTERFACE lan1
NETWORK_INTERFACE lan2
HEARTBEAT_IP 192.168.0.1
3) If the subnet for that LAN adapter changed, it is necessary to determine if
package-related subnet parameters must be updated as well.
# cmviewconf | grep -e "package name" -e "package subnet"
package name: clk
package subnet: 10.126.0.0 <--- HERE
If the subnet needs to be modified, locate the package configuration file
that references the subnet:
In /etc/cmcluster:
# grep 10.126.0.0 */*
PKG_1/pkg.config:SUBNET 10.126.0.0
PKG_1/pkg.ctrl:SUBNET[0]="10.126.0.0"
In the above case, only one package was affected and it's files will have to
be updated to reflect the new subnet. It may also require replacing old
relocatable IPs with new ones, and registering them on the name
server.
4) After updating the affected files, apply the updates to the cluster binary:
# cmapplyconf -C CONF [ -P ]
When completed successfully, start the new cluster:
# cmruncl
Finally, test the package startup and shutdown on each server to be
confident the change was performed properly.
Best Regards,
Ramesh
