Disable CMA's ip on Multi Domain Server

[Peter_Janum_Sod]

Hi CheckMates.

We are currently migrating an R77.30 Multi Domain Server to R80.20. We have chosen to use the method 'Upgrading an R7x Multi-Domain Log Server with Gradual Migration of Domain Log Servers', where we migrate one CMA at a time. To minimize risk and complexity we are re-using the same CMA ip addresses on the R80.20 MDS.

The challenge is now, that the R77.30 MDS and R80.20 MDS are on the same ip subnet. So in order to avoid ip address conflicts between the R77.30 CMA and R80.20 CMA, we need to disable the ip address for a CMA on the R77.30, and then import and start the CMA on the R80.20 MDS.

We can stop the CMA and bring down virtuel ip with the commands:

[Expert@MDS_Server:0]# mdsstop_customer Test_Server

[Expert@MDS_Server:0]# ifconfig eth0:1 down

But these do not survive reboot or mdsstop;mdsstart.

There are no interface config file in /etc/sysconfig/network-scripts/ and I cannot change ip address on the R77.30 CMA. Any suggestions from the community on how to solve this?

Thanks in advance,

Best Regards

Peter Sode

[Maarten_Sjouw]

There is no way to solve this and the ifconfig is not even needed, but there are a number of things you need to ask yourself:
How long do you want to be able to go back?
Do you want to go back?

Why do you need reboots and MDSstop/start in normal operation?

Depending on the answers above you can delete the CMA when you are happy with the new one.

Also keep in mind that when both your MDS's are behind a Cisco device, that you will need to issue a 'arping -c 4 -A -I eth0 <IP of CMA>' on the new MDS.

[Marco_Valenti]

Disable automatic start of checkpoint product from mdsconfig so even if you reboot all the cma and mdm stay down

[Tal_Paz-Fridman]

Try the following workaround:

In mdsconfig select option 8 to configure Automatic Start of Multi-Domain Server

After reboot run mdsstart -m to start only the MDS Server and then mdsstart_customer for the specific Domains you do wnat to run.

Then you will only have to disable the interface for the Domain that is down.

HTH

Tal