1 message in net.nether.puck.cisco-nsp[c-nsp] Persistent Convergence Oscill...
FromSent OnAttachments
Brian FeenyJan 7, 2005 4:55 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:[c-nsp] Persistent Convergence Oscillation in BGP ConfederationsActions...
From:Brian Feeny (sig@shreve.net)
Date:Jan 7, 2005 4:55:54 pm
List:net.nether.puck.cisco-nsp

I was wondering if anyone with experience in dealing with PCO in a Confederation, can share what they have done to mitigate it. I realize there are many ways to handle this, and I have read RFC 3345 as well as alot of stuff out there, but knowing what others have used in a actual operational environment would be interesting.

I plan to use a hub-spoke topology from a logical point of view for connecting sub-AS's. Also all the transit goes into the backbone/hub sub-AS (at least for now). I believe that alone would stop type II churn if I read correctly. It would seem you almost always need to raise the inter-sub-AS IGP metric above the intra-sub-AS IGP metric to ensure loop free topology.

Brian

------------------------------------------------------------------------