[6bone] Instability incarnate

[John Fraizer]

Serious flappage going on here...(and it ain't us!)

BGP routing table entry for 3FFE:1CED::/32, version 90420
Paths: (2 available, best #2)
  Advertised to non peer-group peers:
  2001:6E0::2 2001:768:E:5::1 3FFE:80B0:100:8000::3 3FFE:8100:102::1:9 
  3FFE:8100:200:2FFF::9 195.74.212.38 
  45328 2042 24765 13944 (history entry)
    3FFE:8100:200:2FFF::9 from 3FFE:8100:200:2FFF::9 (131.211.28.48)
      Origin IGP, localpref 100, external
      Dampinfo: penalty 7047, flapped 126 times in 07:28:28
  15589 24765 13944, (received & used)
    3FFE:8170:1:10::1 from 3FFE:8170:1:10::1 (192.168.1.12)
      Origin IGP, localpref 100, valid, external, best


BGP routing table entry for 2001:4F0::/35, version 89613
Paths: (5 available, best #5)
  Advertised to non peer-group peers:
  2001:6E0::2 2001:768:E:5::1 3FFE:80B0:100:8000::3 3FFE:8100:102::1:9 
  3FFE:8100:200:2FFF::9 195.74.212.38 
  45328 2042 24765 13944, (suppressed due to dampening), (received & used)
    3FFE:8100:200:2FFF::9 from 3FFE:8100:200:2FFF::9 (131.211.28.48)
      Origin IGP, localpref 100, valid, external
      Dampinfo: penalty 6134, flapped 128 times in 07:31:31, reuse in 00:45:30
  8379 24765 13944, (received & used)
    2001:768:E:5::1 from 2001:768:E:5::1 (195.143.108.166)
      Origin IGP, localpref 100, valid, external
  5594 13193 109 13944, (received & used)
    3FFE:8100:102::1:9 from 3FFE:8100:102::1:9 (195.154.1.6)
      Origin IGP, localpref 100, valid, external
  1849 24765 13944, (received & used)
    2001:600:4:1F1::1 from 2001:600:4:1F1::1 (158.43.131.66)
      Origin IGP, localpref 100, valid, external
  15589 24765 13944, (received & used)
    3FFE:8170:1:10::1 from 3FFE:8170:1:10::1 (192.168.1.12)
      Origin IGP, localpref 100, valid, external, best


I don't know who is flapping in the breeze in this path "45328 2042
24765" but, I'll tell ya folks right now, if you have peers like that,
it's in your best interest to de-peer.

If this is prominant on the 6bone, I now understand what the fuss is
about.  I won't keep a peer like that, period, the end.  We have one
flapper right now.  I don't know what their problem is as they haven't
replied to my emails.  It's "customer-routes:customer-routes" peering
though so, the damage is at least limited to our peering session.  If they
don't reply with a satisfactory answer as in "We found a problem and are
(contacting the vendor | replacing the hardware | firing the fool who kept
unplugging the router | upgrading the software)" I'll have no choice but
to admin-shutdown the session until they get their end fixed.

So, in summary: If your peers flap in the breeze like the above example,
find out why and fix it or drop the peering.  It's not worth it.



---
John Fraizer              | High-Security Datacenter Services |
EnterZone, Inc            | Dedicated circuits 64k - 155M OC3 |
http://www.enterzone.net/ | Virtual, Dedicated, Colocation    |