[c-nsp] BFD flapping on 6509 SUP720-3BXL

[Ross Halliday]

> What software are you using? SXF is said to be terrible regarding BFD,
> SXH/SXI a little better.

Of course I forgot to include that... the SUP720s are running 12.2(33)SXI4a. The lone 7204 VXR is an NPE-G2 box with 12.4(24)T1.

> > configured with "bfd interval 50 min_rx 50 multiplier 4", yet these
> > are not experiencing the same flaps.
> 
> I think this is much too low for the Sup720. We're using "bfd interval
> 100 min_rx 100 multiplier 5" without any problems on SXI.

Okay, sort of good to hear :) Guessed as much!

> Maybe the output from "show interface GiX/Y | incl drop" and "show ibc
> |
> incl spd drop" would shed light on it.

>From the 4 routers from my previous post, note that I also included interfaces that are connected elsewhere which do not exhibit this problem (core-site_2-c6509 Gi6/2, despite the drops, has no problems)


core-site_1-c6509#sh int gig 6/1 | incl drop
  Input queue: 0/75/33/33 (size/max/drops/flushes); Total output drops: 0
core-site_1-c6509#sh int gig 7/1 | incl drop
  Input queue: 0/75/12/10 (size/max/drops/flushes); Total output drops: 115015
core-site_1-c6509#sh int gig 7/6 | incl drop
  Input queue: 0/75/4/4 (size/max/drops/flushes); Total output drops: 5943
core-site_1-c6509#sh int gig 7/13 | incl drop
  Input queue: 0/75/30/30 (size/max/drops/flushes); Total output drops: 0
core-site_1-c6509#show ibc | inc spd drop
        Potential/Actual paks copied to process level 1169099650/1167989541 (1110109 dropped, 276692 spd drops)


core-site_4-c7204#sh int gig 0/1 | inc drop
  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 212
     0 unknown protocol drops
core-site_4-c7204#sh int gig 0/2 | inc drop
  Input queue: 0/75/19/0 (size/max/drops/flushes); Total output drops: 21475
     0 unknown protocol drops


core-site_2-c6509#sh int gig 4/17 | inc drop
  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
core-site_2-c6509#sh int gig 4/19 | inc drop
  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
core-site_2-c6509#sh int gig 4/21 | inc drop
  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
core-site_2-c6509#sh int gig 5/1 | inc drop
  Input queue: 0/75/4044/0 (size/max/drops/flushes); Total output drops: 0
core-site_2-c6509#sh int gig 5/2 | inc drop
  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
core-site_2-c6509#sh int gig 6/1 | inc drop
  Input queue: 0/75/4145/0 (size/max/drops/flushes); Total output drops: 0
core-site_2-c6509#sh int gig 6/2 | inc drop
  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 75569
core-site_2-c6509#show ibc | inc spd drop
        Potential/Actual paks copied to process level 955918870/955929609 (4294956557 dropped, 693 spd drops)


core-site_3-c6513#sh int gig 7/1 | inc drop
  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
core-site_3-c6513#sh int gig 8/1 | inc drop
  Input queue: 0/75/2/0 (size/max/drops/flushes); Total output drops: 2
core-site_3-c6513#sh ibc | inc spd drop
        Potential/Actual paks copied to process level 233788359/233637166 (151193 dropped, 0 spd drops)


I don't quite understand what the IBC stuff is about. Does this indicate process-switched packets?

Thanks!

Ross