[c-nsp] BFD expectations

Oliver Eyre oliver.eyre at cirruscomms.com.au
Thu Sep 23 02:38:16 EDT 2010


While on the subject, does anyone know if BFD for SVIs has been fixed yet?


Oliver 

-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Chris Evans
Sent: Thursday, 23 September 2010 2:20 PM
To: Pete Lumbis
Cc: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] BFD expectations

Yes. This is what I was referring to. This is centralized on the 6500 even
tho it can be implemented with distributed forwarding cards. You also need
to enable "no ip redirects" on the interfaces to reduce CPU load.

As I mentioned we tested with Cisco ECATS and our htts team with sxi3. We
tested 450ms intervals with up to 35 ebgp neighbors then pounded the CPU and
had no issues.   Centralized bfd platforms are not recommended to have low
interval timers exactly for the false positive issue.

The me3600 and 7300 are CPU based bfd I believe so there will be issues.

Chris
On Sep 22, 2010 10:11 PM, "Pete Lumbis" <alumbis at gmail.com> wrote:

> The forwarding on the 6k can be decentralized but as of today I believe
> that BFD is still a centralized process. That is, it is punted to the CPU
> and control plane issues can give false positives as Phil mentioned.
>
> I think there are plans to make BFD distributed in the future but I have
no
> idea what that time line is.
>
> -Pete
>
>
>
> On Wed, Sep 22, 2010 at 7:19 PM, Chris Evans <chrisccnpspam2 at gmail.com>
> wrote:
> >
> > Phil you bring ...
>
_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/



More information about the cisco-nsp mailing list