[122088] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: BFD over p2p transport links

daemon@ATHENA.MIT.EDU (Tim Durack)
Fri Feb 5 10:48:05 2010

In-Reply-To: <803804.84064.qm@web53606.mail.re2.yahoo.com>
Date: Fri, 5 Feb 2010 10:47:27 -0500
From: Tim Durack <tdurack@gmail.com>
To: Serge Vautour <serge@nbnet.nb.ca>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

On Fri, Feb 5, 2010 at 9:45 AM, Serge Vautour <sergevautour@yahoo.ca> wrote=
:
> Hello,
>
> I'm being asked to look into using BFD over our P2P transport links. Is a=
nyone else doing this? Our transport links are all 10G Ethernet (LAN-PHY). =
There's no alarming inside of LAN-PHY like there is in SONET. The transport=
 side should propagate a fiber break by stopping to send light on both ends=
. This is enough to cause the router interfaces to drop and for protocols t=
o converge.

We only use BFD on L2 circuits.

Ethernet auto-neg includes limited link-fault signalling. It's not as
good as SONET, but it will detect link-failure/one-way link.

> Since LAN-PHY doesn't have any built end-end alarming, some folks believe=
 that we may encounter situations where a fiber break doesn't cause interfa=
ces do go down. Convergence would then have to wait for IGP hellos to detec=
t the problem.

Have not found GigE 10GigE to be a problem over fiber.

Have found BFD to be problematic depending on the implementation and
CPU load of your equipment.

The closer you can stay to the physical layer, the better off you are.

> Is anybody else running BFD over 10G LAN-PHY transport links? Any comment=
s around BFD for this application in general?
>
> Thanks,
> Serge
>
>
>
> =A0 =A0 =A0______________________________________________________________=
____
> Looking for the perfect gift? Give the gift of Flickr!
>
> http://www.flickr.com/gift/
>
>



--=20
Tim:>
Sent from Brooklyn, NY, United States


home help back first fref pref prev next nref lref last post