[c-nsp] Cisco BFD and NSF

[Peter Salanki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Same here, BFD in sup720 PFC/MSFC seems as crappy implemented as the  
IGP/EGP keepalive processes. BFD wouldn't even be needed, nor be  
needed to be done in hardware if cisco could build a proper scheduler  
for this platform so that a large BGP update won't interfer with IGP  
keepalives.

30 jul 2006 kl. 10.23 skrev Mikael Abrahamsson:

> On Sun, 30 Jul 2006, David J. Hughes wrote:
>
>> BFD is such a great step forwards for high availability.  It's a  
>> shame
>> that it appears to be a bit piecemeal at the moment.
>
> We've seen BFD-flaps due to high CPU load on one end, so one should  
> really
> consider the risk/benefit ration when deploying it.
>
> -- 
> Mikael Abrahamsson    email: swmike at swm.pp.se
> _______________________________________________
> 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/

Med vänliga hälsningar

Peter Salanki
Nätansvarig
Bahnhof AB (AS8473)
www.bahnhof.se
Kontor: +46855577132
Mobil: +46709174932



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (Darwin)

iD8DBQFEzHM7iQKhdiFGiogRAqo+AKCV27/3/2zA32CC5HiY6O/g1RCQEQCfZ4/S
Maj+h8zNiftRv0gw+9Z9weA=
=K3RP
-----END PGP SIGNATURE-----