Resource Manager 8.15 wont start with IP takeover mechanism

[naviat]

Hi all,

I have a problem with RM and IP Takeover mechanism. RM (memberid=1) is primary, and memberid=2 is backup server . the first, memberid =1 with VIP starts, memberid=2 stop but when i'm switchover or stop RM primary, Server cannot move VIP to RM backup. This is RM primary and backup option:

-------------------- Primary-----------------------
[cluster]
electiontimer=3000
failoverscript=$InstallationRoot$/bin/NLB.bat
ha-mode=active-active
heartbeattimer=2000
hotstandby=true
initial-electiontimer=10000
member.1=<IP RM primary>:port
member.2=<IP RM backup>:port
members=1 2
[color=red]mymemberid=1[/color]
networkrecoverytime=5000
virtual-ip=<Virtual IP>
virtual-ip-in-via=true

-------------------- Backup-----------------------

[cluster]
electiontimer=3000
failoverscript=$InstallationRoot$/bin/NLB.bat
ha-mode=active-active
heartbeattimer=2000
hotstandby=true
initial-electiontimer=10000
member.1=<IP RM primary>:port
member.2=<IP RM backup>:port
members=1 2
[color=red]mymemberid=2[/color]
networkrecoverytime=5000
virtual-ip=<Virtual IP>
virtual-ip-in-via=true

Thanks dudes

[Kubig]

I very recommend you to use bonding mechanism instead IP takeover for RM ha cluster. I know, that bonding mechanism with one eth interface does not make a sense, but from real-life and real-experience, it works more better. Next thing is, that primary RM in HA cluster got to have memberid=2 (member with higher ID is always primary, if is running). So, at first correct the configuration, think about bonding and look at the RM logs, if the VIP script was fired and what happened during "failover".

[naviat]

Thanks Kubig

I dont known you mean bonding mechanism. With each server, i just have 1 eth, when i config bonding for backup server, i have an error: bonding device bond0 does not seem to be present. How to do it ?

[smile]

you need to configure bonding driver on each server. then bond interface will contain only one eth interface. thus it looks like "alias" for one physical eth interface, but add one level of abstraction to application. procedure for configuring bonding driver is clearly described in deployment guide.