[prev in list] [next in list] [prev in thread] [next in thread] 

List:       keepalived-devel
Subject:    [Keepalived-devel] Monitoring redundant interfaces
From:       Bjørnar_Ness <bjornar.ness () gmail ! com>
Date:       2014-08-11 19:49:55
Message-ID: CAJO99T=DMb7883u9PwUY5FN9c9F9bKjo8b+bdGH4O4KqeX91BA () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


I have the following setup:

sfp0/sfp1/eth0

eth0 is internet side, and spf* is OSPF ECMP internal side.

sfp0 has 10.1 and sfp1 10.2 and 172.16.0.1/32 is announced on both
interfaces.

What I want to accomplish is:

have a vrrp_group that monitors eth0 (this is standard), but also, I want
to monitor is either spf0 _or_ spf1 is down.

Any way to accomplish this?

I could perhaps do unicast to my neighbors 172.16.0.2 and 172.16.0.3 from
src unicast 172.16.0.1 ?

-- 
Bj(/)rnar

[Attachment #5 (text/html)]

<div dir="ltr"><div><div>I have the following \
setup:<br><br></div>sfp0/sfp1/eth0<br><br></div><div>eth0 is internet side, and spf* \
is OSPF ECMP internal side.<br><br></div><div>sfp0 has 10.1 and sfp1 10.2 and <a \
href="http://172.16.0.1/32">172.16.0.1/32</a> is announced on both interfaces.<br> \
<br></div><div>What I want to accomplish is:<br><br></div><div>have a vrrp_group that \
monitors eth0 (this is standard), but also, I want<br></div><div>to monitor is either \
spf0 _or_ spf1 is down.<br><br></div><div>Any way to accomplish this?<br> \
<br></div><div>I could perhaps do unicast to my neighbors 172.16.0.2 and 172.16.0.3 \
from<br>src unicast 172.16.0.1 ?<br></div><div><div><div><div><br>-- <br>Bj(/)rnar \
</div></div></div></div></div>



------------------------------------------------------------------------------


_______________________________________________
Keepalived-devel mailing list
Keepalived-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/keepalived-devel


[prev in list] [next in list] [prev in thread] [next in thread]