change IP address of server & packge

[Santosh P Karpe]

am having two rp 3410 box and diskstation in cluster .
I want to move my both servers on another network.So pls guide me how can i change IP address of both servers & packge.

Is it necessary to change IP address of PKG ?

Thanks in advance..................

[Kenan Erdey]

Hi,

after halting cluster, do ip changes in /etc/hosts and /etc/rc.config.d/netconf file. you can also setparms to change the ip. after rebooting, do changes in control and ascii files(both cluster and package files) in /etc/cmcluster. then run commands cmcheckconf and cmappyconf to create new binary cluster files. do these changes in both nodes respectively. after rebooting once again they should form the new cluster.

Kenan.

[Steven E. Protter]

Shalom,

Changing the IP address of the server is theoretically possible without bringing down SG on that node.

In practice, I've tried this many times and gotten away with it very few times.

Realism sets in and the following procedure is recommended.

Change the IP address in /etc/rc.config.d/netconf
Reboot
reconfigure the SG package as per normal procedures to its new floating IP address.

Now if its a two node cluster you can probably get away without downtime. Just fail all the packages over to the node that is not being messed with.

Necessary to change the IP address in the package? Probably yes. It depends on the scope of the change. If you are changing the nodes network, the SG floating IP address will not be compatible forcing you to change this as well using the procedure above.

SEP

[Deepak Kr]

Santosh,

>>Is it necessary to change IP address of PKG ?

It depends on the scope of change you are going to implement here.

FYI, package IPs can be in different subnets also.

As steps already explained above.

You can furnish some more info here so that we can advise you.

[Santosh P Karpe]

Dear deepak

My PKG & Servers are in single subnet.

[Ganesan R]

Hi,

We have done this using following steps.

1.Halt the cluster
2.Disable the auto-start of the cluster
3.Change the new ip and subnet. Then reboot
4.Change the new ip address on cluster conf file and package conf files
5.cmcheckconf and cmapplyconf
6.start the cluster
7.Enable auto-start of the cluster

Thanks.

[Gokul Chandola]

Hi,
Its not nessesary that you change IP Address.
Without changes IP Address you can use DMZ concept if subnet mask is same.

Regards,
Gokul Chandola

[Asif Sharif]

See the Technical knowledge base document

http://www12.itrc.hp.com/service/cki/docDisplay.do?docLocale=en&docId=emr_na-c01028229-4

Regards,
Asif Sharif

[Santosh P Karpe]

Dear Ganesan R

Actually i am new to cluster so Pls Guide me exactly
1. How to Disable the auto-start of the cluster?
2.Change the new ip address on cluster conf file and package conf files ?
3.cmcheckconf and cmapplyconf ?

Thanks.

Santosh Karpe

[Ganesan R · Accepted solution]

Hi Santhosh,

>Actually i am new to cluster so Pls Guide me exactly <
>1. How to Disable the auto-start of the cluster?<

There is a config file /etc/rc.config.d/cmcluster which will control the cluster startup during boot.
Since you are going to make modifications disable autostart of cluster by changing the value to 0 like below
AUTOSTART_CMCLD=0

so that cluster won't be started when you reboot after changing the system ip address as per step3.

>2.Change the new ip address on cluster conf file and package conf files ?<

We have to get cluster config file and package config file from existing cluster binary file using cmgetconf. Once you have these files you need to modify the cluster config ascii file with new system ip address and subnet and package config file with new subnet. Also note that you need modify the package control script with new ip address and subnet. control script will be available on /etc/cmcluster/ directory. modify on both nodes
Ex:
# cmgetconf -c /tmp/cluster.config

# cmgetconf -p /tmp/pkg.config

>3.cmcheckconf and cmapplyconf ?<

Once you modified the above files you need to check the files for any syntax errors and create the new cluster binary file.

To check for any errors use cmcheckconf command.
Ex:
#cmcheckconf -v -C /tmp/cluster.config
-P /tmp/pkg.config

Fix the errors if any. otherwise apply the configuration using cmapplyconf command

Ex:
#cmapplyconf -v -C /tmp/cluster.config
-P /tmp/pkg.config

Then start the cluster using cmruncl

also enable auto start again.

Hope this helps