[j-nsp] bfd = busted failure detection :)

[Nilesh Khambal]

Hi Richard,

Just talking from this router perspective, it looks like the remote end
router has problem receiving BFD packets from this router. It signaled the
BFD session down because of that.

You can start by looking at egress stats at the on the local router. See if
there are any ttp queue drops (software queue drops) in "show pfe statistics
traffic" any queuing drops on the egress interface.


On 11/21/09 12:22 PM, "Richard A Steenbergen" <ras at e-gerbil.net> wrote:

> Is there a way to see stats on bfd sessions, such as the number of
> probes lost? I'm trying to figure out why I can't reliably keep bfd
> running between two Juniper's without getting a ton of false positives,
> even with very high detection thresholds. Nothing useful in "show bfd
> session extensive" (below), and I'm not seeing anything obvious in the
> pfe shell for bfd stats (I'm running ppm delegate, wondering if there
> are possible issues there).
> 
>                                                   Detect   Transmit
> Address                  State     Interface      Time     Interval
> Multiplier
> x.x.x.x                  Up        xe-7/0/0.0     5.000     0.500        10
>  Client ISIS L2, TX interval 0.500, RX interval 0.500
>  Session up time 00:12:13, previous down time 00:00:17
>  Local diagnostic NbrSignal, remote diagnostic CtlExpire
>  Remote state Up, version 1
>  Replicated 
>  Min async interval 0.500, min slow interval 1.000
>  Adaptive async TX interval 0.500, RX interval 0.500
>  Local min TX interval 0.500, minimum RX interval 0.500, multiplier 10
>  Remote min TX interval 0.500, min RX interval 0.500, multiplier 10
>  Local discriminator 174, remote discriminator 84
>  Echo mode disabled/inactive
>  Remote is control-plane independent