[j-nsp] VRRP tracking problem

[hani ibrahim]

Hi Howard,

thanks for your feed back , but in my design  i cannot use two routing
instance i need only one with two next hops if the 1st next-hop  failed
switch over to the next one .....

NOT: the load balancer (LB) it foundry

BR,
Hany

On Sun, Jan 8, 2012 at 11:08 PM, Howard Hart <Howard.Hart at ooma.com> wrote:

> This is a complete shot in the dark and probably wrong since I've never
> played with Juniper Load Balancing, but what if you split Cache-LB into two
> routing instances, one for next-hop route, Cache-LB-next and one for the
> qualified-next-hop route, Cache-LB-qualified, then applied tracking to the
> vrrp instances like so
>
> set interfaces irb unit 202 family inet address 10.10.10.27/29 vrrp-group
> 1 track route routing-instance Cache-LB-qualified priority cost N1
> set interfaces irb unit 202 family inet address 10.10.10.147/29vrrp-group 2 track route routing-instance Cache-LB-next priority cost N2
>
> where cost N1 and cost N2 need to be set to a number that, when subtracted
> from the vrrp instance priority, drops the cost below the cost of the other
> vrrp instance.
>
> Howard Hart
> ________________________________________
> From: juniper-nsp-bounces at puck.nether.net [
> juniper-nsp-bounces at puck.nether.net] on behalf of hani ibrahim [
> hani.ibrahim.aswn at gmail.com]
> Sent: Saturday, January 07, 2012 11:25 PM
> To: juniper-nsp at puck.nether.net
> Subject: [j-nsp] VRRP tracking problem
>
> Dear All,
>
> kindly i need your help ,
>
> i have VRRP issue between  My router and Loadbalancer , how can the router
> detect the primary VIP get down to switch the traffic to the qualified next
> hop ?
>
> edit interfaces irb unit 202]
>
>
> Mx480-re0#
> show
>
> description MX-to-Cache-LB;
> family inet {
>    address 10.10.10.27/29 {
>        vrrp-group 1 {
>            virtual-address 10.10.10.29;
>            priority 50;
>            fast-interval 300;
>            accept-data;
>        }
>    }
>
>    address 10.10.10.147/29 {
>        vrrp-group 2 {
>            virtual-address 10.10.10.149;
>            priority 150;
>            fast-interval 300;
>            accept-data;
>        }
>    }
> }
>
>
>
> {master}[edit]
> Mx480-re0## show interfaces ae0
> description "Connected to  EX4200";
> vlan-tagging;
> encapsulation flexible-ethernet-services;
> aggregated-ether-options {
>    minimum-links 1;
>    link-speed 10g;
> }
>
> }
> unit 202 {
>    description "LB";
>    encapsulation vlan-bridge;
>    vlan-id 202;
> }
>
> Mx480-re0# show bridge-domains
> Cache-Filter-LB {
>    domain-type bridge;
>    vlan-id 202;
>    interface ae0.202;
>    interface ae3.202;
>    routing-interface irb.202;
> }
>
> Mx480-re0# show routing-instances
> Cache-LB {
>    instance-type forwarding;
>    routing-options {
>        static {
>            route 0.0.0.0/0 {
>                next-hop 10.10.10.150;---------------------------->primary
> LB VIP add
>                qualified-next-hop 10.10.10.30 {--------------->-sec LB VIP
> add
>                    preference 6;
>                }
>            }
>        }
>    }
>
> Thanks,
> Hany
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>