[j-nsp] VRRP VIP route not accepted as contributing route to AGGREGATE
Alexander Marhold
alexander.marhold at gmx.at
Tue Jan 26 15:49:25 EST 2016
Thanks, Vincent that solution also works for me.
However theoretically the original plan should also work,
Regards
Alexander
-----Ursprüngliche Nachricht-----
Von: juniper-nsp [mailto:juniper-nsp-bounces at puck.nether.net] Im Auftrag von Vincent Bernat
Gesendet: Dienstag, 26. Januar 2016 20:38
An: 'Juniper List'
Betreff: Re: [j-nsp] VRRP VIP route not accepted as contributing route to AGGREGATE
❦ 26 janvier 2016 18:15 +0100, "Alexander Marhold" <alexander.marhold at gmx.at> :
> We want to have an aggregate only announced when the VRRP vip route is
> active on the local BGP speaker
I had the exact same problem. I solved by using a conditional route instead.
policy-options {
policy-statement v4-PRIVATE-2-BGP {
term 10 {
from protocol aggregate;
then accept;
}
term 20 {
from {
protocol direct;
route-filter 192.168.96.0/19 exact;
condition got-oob-vrrp;
}
then accept;
}
}
condition got-oob-vrrp {
if-route-exists {
192.168.96.1/32;
table private.inet.0;
}
}
}
--
Write clearly - don't sacrifice clarity for "efficiency".
- The Elements of Programming Style (Kernighan & Plauger) _______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
More information about the juniper-nsp
mailing list