<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: BGP</title>
	<atom:link href="http://www.djerk.nl/wordpress/ccie-rs/things-to-know-lab/bgp/feed" rel="self" type="application/rss+xml" />
	<link>http://www.djerk.nl/wordpress</link>
	<description>Anything related to Djerk Geurts may be found here (either locally or linked)</description>
	<lastBuildDate>Sat, 07 Nov 2009 19:05:09 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: Djerk</title>
		<link>http://www.djerk.nl/wordpress/ccie-rs/things-to-know-lab/bgp/comment-page-1#comment-5590</link>
		<dc:creator>Djerk</dc:creator>
		<pubDate>Wed, 11 Feb 2009 09:24:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.djerk.nl/wordpress/ccie-rs/things-to-know-lab/bgp/#comment-5590</guid>
		<description>MD,

Glad to see you find my site of use! I&#039;ll definitely keep up the good work, though not studying at the moment and permanently being contracted out to a customer don&#039;t help. I&#039;m having to be very discreet with announcing what I&#039;m working on, though sadly I&#039;m not working on anything majorly exciting at the moment.

With regards to your question about choosing an IGP when eBGP is involved on an ASBR. That really depends on what is required. EIGRP and most other link state protocols have faster convergence while (i)BGP carries things like communities and supports MPLS very well. So if I had to give a definitive answer without more input I&#039;d advise EIGRP if you need fast convergence. If however redistribution between EIGRP and BGP was required -beyond a simple default-route- and convergence wasn&#039;t so much of an issue I&#039;d prefer BGP as it&#039;s best to avoid redistribution if possible.

Some overly generic real life info from my experience for you: SMB mainly use EIGRP or OSPF as IGP, EGP is whatever they get offered by their ISP and as such mostly redistributed statics. Enterprises mainly use OSPF as IGP and BGP as EGP, the larger ones prefer to use more than one ISP (multihoming) and will most likely be using iBGP and different ASs for the different branches and holdings. Enterprises are also more and more deploying MPLS (MP-iBGP), e.g. the holding provides the MPLS cloud and the branches are the MPLS customers with their own IGPs. ISPs use either ISIS and/or OSPF overlaid with MP-iBGP (MPLS) and obviously peer with eBGP and sometimes MP-eBGP.</description>
		<content:encoded><![CDATA[<p>MD,</p>
<p>Glad to see you find my site of use! I&#8217;ll definitely keep up the good work, though not studying at the moment and permanently being contracted out to a customer don&#8217;t help. I&#8217;m having to be very discreet with announcing what I&#8217;m working on, though sadly I&#8217;m not working on anything majorly exciting at the moment.</p>
<p>With regards to your question about choosing an IGP when eBGP is involved on an ASBR. That really depends on what is required. EIGRP and most other link state protocols have faster convergence while (i)BGP carries things like communities and supports MPLS very well. So if I had to give a definitive answer without more input I&#8217;d advise EIGRP if you need fast convergence. If however redistribution between EIGRP and BGP was required -beyond a simple default-route- and convergence wasn&#8217;t so much of an issue I&#8217;d prefer BGP as it&#8217;s best to avoid redistribution if possible.</p>
<p>Some overly generic real life info from my experience for you: SMB mainly use EIGRP or OSPF as IGP, EGP is whatever they get offered by their ISP and as such mostly redistributed statics. Enterprises mainly use OSPF as IGP and BGP as EGP, the larger ones prefer to use more than one ISP (multihoming) and will most likely be using iBGP and different ASs for the different branches and holdings. Enterprises are also more and more deploying MPLS (MP-iBGP), e.g. the holding provides the MPLS cloud and the branches are the MPLS customers with their own IGPs. ISPs use either ISIS and/or OSPF overlaid with MP-iBGP (MPLS) and obviously peer with eBGP and sometimes MP-eBGP.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MD</title>
		<link>http://www.djerk.nl/wordpress/ccie-rs/things-to-know-lab/bgp/comment-page-1#comment-5589</link>
		<dc:creator>MD</dc:creator>
		<pubDate>Wed, 11 Feb 2009 02:36:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.djerk.nl/wordpress/ccie-rs/things-to-know-lab/bgp/#comment-5589</guid>
		<description>hey, the good djerk! good job in the ibgp to BGP default route redistribution method, the ip prefix method. it saved the day for me! Thanks.

keep up the good work!

you see, many information and articles available but not all to the point with a practical use just like the one you posted. I Have one question if possible, would you use ibgp where you have two border routers to Internet and at the bottom of the network, have a 300 MB SONET ring to anothet site? or just use eigrp in site one, site 2 and just BGP (or eBGP) to the Internet?

Regards,

MD</description>
		<content:encoded><![CDATA[<p>hey, the good djerk! good job in the ibgp to BGP default route redistribution method, the ip prefix method. it saved the day for me! Thanks.</p>
<p>keep up the good work!</p>
<p>you see, many information and articles available but not all to the point with a practical use just like the one you posted. I Have one question if possible, would you use ibgp where you have two border routers to Internet and at the bottom of the network, have a 300 MB SONET ring to anothet site? or just use eigrp in site one, site 2 and just BGP (or eBGP) to the Internet?</p>
<p>Regards,</p>
<p>MD</p>
]]></content:encoded>
	</item>
</channel>
</rss>

