[j-nsp] juniper-nsp Digest, Vol 62, Issue 18
alaerte vidali
alaertevidali at gmail.com
Sat Jan 12 11:15:39 EST 2008
Hi
Have you used it in production networks?
I am wondering how it scale with the values you are using (50 and 3 for
minimum interval and multiplier)
tks,
Alaerte
>
>
> Message: 1
> Date: Thu, 10 Jan 2008 21:24:59 +0100
> From: "Gard Undheim" <gard at ipnett.no>
> Subject: Re: [j-nsp] BFD over RSVP LSPs with teardown as action
> To: "Piotr Marecki" <peter at mareccy.org>, <juniper-nsp at puck.nether.net>
> Message-ID: <65582C6D4E704640B5E76948D06C27B9D6BF63 at pompel.ipnett.com>
> Content-Type: text/plain; charset="us-ascii"
>
> Worked like a charm, thanks a lot
>
> Regards,
> Gard
>
> -----Original Message-----
> From: Piotr Marecki [mailto:peter at mareccy.org]
> Sent: 10. januar 2008 20:31
> To: Gard Undheim; juniper-nsp at puck.nether.net
> Subject: Re: [j-nsp] BFD over RSVP LSPs with teardown as action
>
> Just quick shot :
> Since BFD for LSP uses mpls lsp ping as an bootstrap/periodic control
> plane
> verification , it probably needs 127.0.0.1/32 address to be configured
> on
> both routers lo0 interfaces.
> So , add 127.0.0.1/32 to your lo0 stanzas
>
>
>
> Piotr Marecki
>
> ----- Original Message -----
> From: "Gard Undheim" <gard at ipnett.no>
> To: <juniper-nsp at puck.nether.net>
> Sent: Thursday, January 10, 2008 3:00 PM
> Subject: [j-nsp] BFD over RSVP LSPs with teardown as action
>
>
> > Hi
> >
> > I am currently trying to test the new functionality in Junos 8.5 which
> > enables BFD to tear down lsps. I am currently running a simple MPLS
> > setup between two routers with one lsp with a primary and standby
> > secondary path.
> >
> > I have never setup BFD before, and when I try I can not get the
> > BFD session up and running. Anyone have any suggestions?
> >
> > Below are the configuration on the egress/ingress MPLS routers,
> > the LSPs are up and running. No log entries regarding BFD are
> > found in the messages on any of the routers.
> >
> > Best Regards,
> > Gard
> >
> >
> > Config:
> >
> > Router1:
> >
> > label-switched-path to_38 {
> > to 192.168.1.38;
> > oam {
> > bfd-liveness-detection {
> > minimum-interval 50;
> > multiplier 3;
> > failure-action teardown;
> > }
> > }
> > primary via_38;
> > secondary via_37 {
> > standby;
> > }
> > }
> > label-switched-path to_37 {
> > to 192.168.1.37;
> > primary via_37;
> > secondary via_38 {
> > standby;
> > }
> > }
> > path via_37 {
> > 192.168.1.37 strict;
> > }
> > path via_38 {
> > 192.168.1.38 strict;
> > }
> >
> >
> > Router2:
> >
> > label-switched-path to_36 {
> > to 192.168.1.36;
> > oam {
> > bfd-liveness-detection {
> > minimum-interval 50;
> > multiplier 3;
> > failure-action teardown;
> > }
> > }
> > primary via_36;
> > secondary via_37 {
> > standby;
> > }
> > }
> > path via_37 {
> > 192.168.1.37;
> > }
> > path via_36 {
> > 192.168.1.36;
> > }
> >
> > BFD session output:
> >
> > Router1:
> >
> > Transmit
> > Address State Interface Detect Time Interval
> > Multiplier
> > 127.0.0.1 Init fe-0/1/0.0 3.000 1.000
> > 3
> > Client RSVP-OAM, TX interval 0.050, RX interval 0.050
> > Local diagnostic NbrSignal, remote diagnostic None
> > Remote state Down, version 1
> > Transmit
> > Address State Interface Detect Time Interval
> > Multiplier
> > 127.0.0.1 Init fe-0/1/1.0 3.000 1.000
> > 3
> > Client RSVP-OAM, TX interval 0.050, RX interval 0.050
> > Local diagnostic NbrSignal, remote diagnostic None
> > Remote state Down, version 1
> > Transmit
> > Address State Interface Detect Time Interval
> > Multiplier
> > 192.168.1.38 Down 0.000 1.000
> > 3
> > Client RSVP-OAM, TX interval 0.050, RX interval 0.050
> > Local diagnostic None, remote diagnostic None
> > Remote state AdminDown, version 1
> > Transmit
> > Address State Interface Detect Time Interval
> > Multiplier
> > 192.168.1.38 Down 0.000 1.000
> > 3
> > Client RSVP-OAM, TX interval 0.050, RX interval 0.050
> > Local diagnostic None, remote diagnostic None
> > Remote state AdminDown, version 1
> >
> > 4 sessions, 4 clients
> > Cumulative transmit rate 4.0 pps, cumulative receive rate 2.0 pps
> >
> >
> > Router2:
> >
> > Transmit
> > Address State Interface Detect Time Interval
> > Multiplier
> > 127.0.0.1 Init fe-0/3/0.0 3.000 1.000
> > 3
> > Client RSVP-OAM, TX interval 0.050, RX interval 0.050
> > Local diagnostic NbrSignal, remote diagnostic None
> > Remote state Down, version 1
> > Transmit
> > Address State Interface Detect Time Interval
> > Multiplier
> > 127.0.0.1 Init fe-0/3/1.0 3.000 1.000
> > 3
> > Client RSVP-OAM, TX interval 0.050, RX interval 0.050
> > Local diagnostic NbrSignal, remote diagnostic None
> > Remote state Down, version 1
> > Transmit
> > Address State Interface Detect Time Interval
> > Multiplier
> > 192.168.1.36 Down 0.000 1.000
> > 3
> > Client RSVP-OAM, TX interval 0.050, RX interval 0.050
> > Local diagnostic None, remote diagnostic None
> > Remote state AdminDown, version 1
> > Transmit
> > Address State Interface Detect Time Interval
> > Multiplier
> > 192.168.1.36 Down 0.000 1.000
> > 3
> > Client RSVP-OAM, TX interval 0.050, RX interval 0.050
> > Local diagnostic None, remote diagnostic None
> > Remote state AdminDown, version 1
> >
> > 4 sessions, 4 clients
> > Cumulative transmit rate 4.0 pps, cumulative receive rate 2.0 pps
> >
> >
> >
> > _______________________________________________
> > 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