Re: monitor multiple IP address

Simon Horman <[email protected]> Thu, 2 Oct 2008 17:03:13 +1000
Newsgroups gmane.linux.highavailability.ultramonkey
Message-ID <[email protected]>
On Thu, Oct 02, 2008 at 02:07:04PM +0800, Ron wrote:
> Hi Sir,
> 
> Thank You for your reply. actually my setup is a bit confusing.
> i'm using eth0 for one service and eth1 for another.
> 
> eth1 is used to load balanced access to mysql so i used the loopback, 
> but its is not a member of the real servers.
> 
> virtual = 10.10.10.216:3306
>          service = mysql
>          real = 10.10.10.213:3306 gate
>          real = 10.10.10.214:3306 gate
>          checktype = negotiate
>          login = "mydbuser"
>          passwd = "mydbpassword"
>          database = "ldirectordb"
>          request = "SELECT * FROM connectioncheck"
>          scheduler = wrr
> 
> 
> the eth0 is not used for load balancing i am actually using it to bind 
> asterisk (voip sip) to 201.202.203.216.
> 
> what i would like to do is create a simple failover, that would get all 
> the IP address of server1 to server2.

Ok, in that case you do not need to add 201.202.203.216 to lo.

> here are the config:
> 
> -- ha.cf --
> logfacility        local0
> bcast        eth1
> mcast eth1 225.0.0.1 694 1 0
> auto_failback off
> node        db-mngr
> node        dundi-db-mngr
> respawn hacluster /usr/lib/heartbeat/ipfail
> apiauth ipfail gid=haclient uid=hacluster
> 
> 
> do i need to add eth0 on mcast as well?

Yes, that would be a good idea.

> -- haresources --
> db-mngr \
>          ldirectord::ldirectord.cf \
>          LVSSyncDaemonSwap::master \
>          IPaddr2::10.10.10.216/28/eth1/10.10.10.223
> 	IPaddr2::201.202.203.216/28/eth0/201.202.203.223
> 
> 
> thank you for your help.
> 
> regards,
> ron
> 
> 
> 
> 
> Simon Horman wrote:
> > On Thu, Oct 02, 2008 at 01:34:42PM +0800, Ron wrote:
> >> hi sir,
> >>
> >> do i need to assign the 201.202.203.216 to loopback interface as well?
> >> sorry got confused now.
> > 
> > Hi Ron,
> > 
> > That depends a little on what you are doing with your configuration.
> > But if it was neccessary to add 10.10.10.216 then it is likely
> > to also be neccessary to add 201.202.203.216.
> > 
> > Do  your linux-directors also act as real-servers. If so,
> > you'll need to add 10.10.10.216 and 201.202.203.216, and handle
> > ARP correctly. If not, you probably don't need to add either
> > address to lo.
> > 
> _______________________________________________
> Ultramonkey-users mailing list
> [email protected]
> http://lists.vergenet.net/listinfo/ultramonkey-users

-- 
Simon Horman
  VA Linux Systems Japan K.K., Sydney, Australia Satellite Office
  H: www.vergenet.net/~horms/             W: www.valinux.co.jp/en

_______________________________________________
Ultramonkey-users mailing list
[email protected]
http://lists.vergenet.net/listinfo/ultramonkey-users