[nsp] connected flaps?

From: bmanning@ISI.EDU
Date: Fri Aug 14 1998 - 11:55:47 EDT


Ok, I'm at ropes end....

>sh ip route 198.32.64.12
Routing entry for 198.32.64.0/24
  Known via "connected", distance 0, metric 0 (connected)
  Redistributing via bgp 4555
  Advertised by bgp 4555 metric 50 weight 3500
  Routing Descriptor Blocks:
  * directly connected, via FastEthernet2/0
      Route metric is 0, traffic share count is 1
>sh ip bgp 198.32.64.12
BGP routing table entry for 198.32.64.0/24, version 1618391
Paths: (1 available, best #1, advertised over EBGP)
  Local
    0.0.0.0
      Origin IGP, localpref 100, weight 32768, valid, sourced, local, best
>sh ip bgp sum
...
198.32.146.10 4 226 785093 20878 1617928 0 0 1w4d 51493
...

from 198.32.146.10
>sh ip route 198.32.64.12
% Network not in table
>sh ip bgp 198.32.64.12
BGP routing table entry for 198.32.64.0/24, version 14990982
Paths: (1 available, no best path, advertised over IBGP, EBGP)
  4555 (history entry)
    198.32.146.11 from 198.32.146.11 (192.0.2.10)
      Origin IGP, metric 1, external
      Dampinfo: penalty 11024, flapped 331 times in 04:21:30
>

Any pointers on why the cisco code might think this route is "flapping"?

--bill



This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:13:13 EDT