Re: VRRP Help
"Andres E. Rodriguez Lazo" <[email protected]> Tue, 31 Mar 2009 11:22:27 -0500
| Newsgroups | gmane.linux.keepalived.announce |
|---|---|
| Message-ID | <[email protected]> |
--===============6036879287736698749==
Content-Type: multipart/alternative; boundary=0015175ce1bedfa97304666c9a55
--0015175ce1bedfa97304666c9a55
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Thanks all for your suggestions.
Marcos.
Actually I have another connection to the network through eth0. Anyways,
what I was actually trying to do is to make eth1 (the crossover) the
interface where keepalived sent its healthcheck as the primary link, but in
case there is a failure with eth1, it could use eth2, since their are
connected to the same network in both nodes. This way, i will provide fault
tolerance by having an alternate path for healthchecking in case the primary
failed, without using bonding.
The diagrmas is something like this:
---------------
---------------
---node1--- eth1-----------crossover link-----------eth1---node2---
---------------
---------------
|eth2 |
eth2
| internal network, VIP |
-------------------------------------------------------------------------
|
|
Clients
So, eth1 will server as healthcheking interfaces exclusively, but in case
eth1 fails, keepalived should start healthchecking through eth2.
Best regards,
On Tue, Mar 31, 2009 at 11:12 AM, Marcos Hack <[email protected]> wrote:
> Hi Andres,
>
> Being eth2 the only connection to the network (eth1 is only a backend
> between the nodes, right?) why don't you use only this interface in
> the VRRP group? Because I think that if eth2 fails it doesn't matter
> if eth1 is up or not, you have to do the failover to keep VIP
> reachable, right?
>
> It would be useful if you send a simple diagram explaining your
> environment.
>
> Regards,
> Marcos Hack.
>
>
> On Mon, Mar 30, 2009 at 8:15 PM, Andres E. Rodriguez Lazo
> <[email protected]> wrote:
> > Hi All,
> >
> > I was wondering if anyone can help me with my keepalived configuration.
> >
> > What I actually want to know is how to configure keepalived to healthchek
> > over multiple interfaces. For example, I have two interfaces on each
> node
> > (2 node config). Both nodes have eth1 and eth2 interfaces. eth1 is a
> > crossover link between the nodes, and eth2 its for the network. I want to
> > make keepalived healthcheck with both interfaces so that if eth1 fails...
> it
> > won't failover because eth2 link is still up, and the VIP won't have to
> be
> > failovered two the BACKUP server. The only case where it should failover
> is
> > if both interfaces, eth1 and eth2 go down. Is this possible to do?
> >
> > My actual configuration is:
> >
> > vrrp_sync_group VG1 {
> > group {
> > VI_1
> > }
> >
> > # to MASTER transition
> > notify_master "/usr/local/bin/change_status master"
> >
> > # to BACKUP transition
> > notify_backup "/usr/local/bin/change_status backup"
> >
> > # FAULT transition
> > notify_fault "/usr/local/bin/change_status fault"
> > }
> >
> > vrrp_instance VI_1 {
> > state MASTER # (BACKUP for the secondary node)
> > interface eth1
> > virtual_router_id 49
> > priority 99
> > advert_int 1
> > authentication {
> > auth_type PASS
> > auth_pass 1234
> > }
> > virtual_ipaddress {
> > 192.168.10.100/24 brd 192.168.10.255 dev eth2
> > }
> > }
> >
> >
> > If you can see, it will healthcheck only through eth1. How can I make it
> > healthcheck over eth2 aswell?
> >
> > Thanks for the help, it will be very much appreciated.
> >
> > --
> > Andres E. Rodriguez Lazo (4nDr3s - RoAkSoAx)
> > Ubuntu Counter Project - User # 17582
> >
> >
> ------------------------------------------------------------------------------
> >
> > _______________________________________________
> > Keepalived-announce mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/keepalived-announce
> >
> >
>
--
Andres E. Rodriguez Lazo (4nDr3s - RoAkSoAx)
Ubuntu Counter Project - User # 17582
--0015175ce1bedfa97304666c9a55
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Thanks all for your suggestions.<br><br>Marcos.<br><br>Actually I have
another connection to the network through eth0. Anyways, what I was
actually trying to do is to make eth1 (the crossover) the interface
where keepalived sent its healthcheck as the primary link, but in case
there is a failure with eth1, it could use eth2, since their are
connected to the same network in both nodes. This way, i will provide
fault tolerance by having an alternate path for healthchecking in case
the primary failed, without using bonding.<div><span id=3D"q_1205d64ba929a7=
ea_1" class=3D"h4"><br>The diagrmas is something like this:<br><br>--------=
-------=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 </span><span id=3D"q_1205d64ba929a7ea_1" =
class=3D"h4">---------------</span><span id=3D"q_1205d64ba929a7ea_1" class=
=3D"h4">=C2=A0 <br>
---node1--- eth1-----------crossover link-----------eth1---node2---<br>----=
-----------=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 </span><span id=3D"q_1205d64ba929a7ea_=
1" class=3D"h4">---------------</span><span id=3D"q_1205d64ba929a7ea_1" cla=
ss=3D"h4"> <br>
=C2=A0=C2=A0=C2=A0=C2=A0 |eth2=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 | eth2<br>=C2=A0=C2=A0=C2=A0=C2=A0 |=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 inter=
nal network, VIP =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0 |<br></span></div>=C2=A0=C2=A0=C2=A0=C2=A0 ----=
---------------------------------------------------------------------<br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 |<=
br>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
|<br>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Clients<br><br>So, e=
th1 will server as healthcheking interfaces exclusively, but in case eth1 f=
ails, keepalived should start healthchecking through eth2.<br>
<br>Best regards,<br>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 <br><div class=3D"gmail_quote">On Tue, Mar 3=
1, 2009 at 11:12 AM, Marcos Hack <span dir=3D"ltr"><<a href=3D"mailto:ma=
[email protected]">[email protected]</a>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi Andres,<br>
<br>
Being eth2 the only connection to the network (eth1 is only a backend<br>
between the nodes, right?) why don't you use only this interface in<br>
the VRRP group? Because I think that if eth2 fails it doesn't matter<br=
>
if eth1 is up or not, you have to do the failover to keep VIP<br>
reachable, right?<br>
<br>
It would be useful if you send a simple diagram explaining your environment=
.<br>
<br>
Regards,<br>
<font color=3D"#888888">Marcos Hack.<br>
</font><div><div></div><div class=3D"h5"><br>
<br>
On Mon, Mar 30, 2009 at 8:15 PM, Andres E. Rodriguez Lazo<br>
<<a href=3D"mailto:[email protected]">[email protected]</a>> wrot=
e:<br>
> Hi All,<br>
><br>
> I was wondering if anyone can help me with my keepalived configuration=
.<br>
><br>
> What I actually want to know is how to configure keepalived to healthc=
hek<br>
> over multiple interfaces.=C2=A0 For example, I have two interfaces on =
each node<br>
> (2 node config). Both nodes have eth1 and eth2 interfaces. eth1 is a<b=
r>
> crossover link between the nodes, and eth2 its for the network. I want=
to<br>
> make keepalived healthcheck with both interfaces so that if eth1 fails=
... it<br>
> won't failover because eth2 link is still up, and the VIP won'=
t have to be<br>
> failovered two the BACKUP server. The only case where it should failov=
er is<br>
> if both interfaces, eth1 and eth2 go down. Is this possible to do?<br>
><br>
> My actual configuration is:<br>
><br>
> vrrp_sync_group VG1 {<br>
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 group {<br>
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 VI_1<br>
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 }<br>
><br>
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 # to MASTER transition<br>
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 notify_master "/usr/lo=
cal/bin/change_status master"<br>
><br>
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 # to BACKUP transition<br>
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 notify_backup "/usr/lo=
cal/bin/change_status backup"<br>
><br>
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 # FAULT transition<br>
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 notify_fault "/usr/loc=
al/bin/change_status fault"<br>
> }<br>
><br>
> vrrp_instance VI_1 {<br>
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 state MASTER # (BACKUP for =
the secondary node)<br>
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 interface eth1<br>
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 virtual_router_id 49<br>
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 priority 99<br>
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 advert_int 1<br>
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 authentication {<br>
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 auth_type PASS<br>
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 auth_pass 1234<br>
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 }<br>
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 virtual_ipaddress {<br>
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 <a href=3D"http://192.168.10.100/24" target=3D"_blank=
">192.168.10.100/24</a> brd 192.168.10.255 dev eth2<br>
> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 }<br>
> }<br>
><br>
><br>
> If you can see, it will healthcheck only through eth1. How can I make =
it<br>
> healthcheck over eth2 aswell?<br>
><br>
> Thanks for the help, it will be very much appreciated.<br>
><br>
> --<br>
> Andres E. Rodriguez Lazo (4nDr3s - RoAkSoAx)<br>
> Ubuntu Counter Project - User # 17582<br>
><br>
</div></div>> ----------------------------------------------------------=
--------------------<br>
<div><div></div><div class=3D"h5">><br>
> _______________________________________________<br>
> Keepalived-announce mailing list<br>
> <a href=3D"mailto:[email protected]">Keepalive=
[email protected]</a><br>
> <a href=3D"https://lists.sourceforge.net/lists/listinfo/keepalived-ann=
ounce" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/keepa=
lived-announce</a><br>
><br>
><br>
</div></div></blockquote></div><br><br clear=3D"all"><br>-- <br>Andres E. R=
odriguez Lazo (4nDr3s - RoAkSoAx)<br>Ubuntu Counter Project - User # 17582<=
br>
--0015175ce1bedfa97304666c9a55--
--===============6036879287736698749==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
------------------------------------------------------------------------------
--===============6036879287736698749==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
Keepalived-announce mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/keepalived-announce
--===============6036879287736698749==--