<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>djerk.nl &#187; mtu</title>
	<atom:link href="http://www.djerk.nl/wordpress/tag/mtu/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>Mon, 26 Jul 2010 04:45:00 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Inter-AS MPLS and MTU</title>
		<link>http://www.djerk.nl/wordpress/2009/inter-as-mpls-and-mtu</link>
		<comments>http://www.djerk.nl/wordpress/2009/inter-as-mpls-and-mtu#comments</comments>
		<pubDate>Tue, 02 Jun 2009 14:18:33 +0000</pubDate>
		<dc:creator>Djerk</dc:creator>
				<category><![CDATA[Networking]]></category>
		<category><![CDATA[3600]]></category>
		<category><![CDATA[7600]]></category>
		<category><![CDATA[cisco]]></category>
		<category><![CDATA[IP]]></category>
		<category><![CDATA[linkedin]]></category>
		<category><![CDATA[MP-eBGP]]></category>
		<category><![CDATA[mpls]]></category>
		<category><![CDATA[mtu]]></category>

		<guid isPermaLink="false">http://www.djerk.nl/wordpress/?p=220</guid>
		<description><![CDATA[Type-2 interconnects are fun, but mtu issues are not. When faced with migrating subnets  from one MPLS cloud to another -different AS numbers you see- the three common inter-AS types were taken off the shelf and dusted off&#8230;
A quick refresh for all:

PE physical link(s), ties one VRF to another using one subnet for each VRF. [...]]]></description>
			<content:encoded><![CDATA[<p>Type-2 interconnects are fun, but mtu issues are not. When faced with migrating subnets  from one MPLS cloud to another -different AS numbers you see- the three common inter-AS types were taken off the shelf and dusted off&#8230;<span id="more-220"></span></p>
<p>A quick refresh for all:</p>
<ol>
<li>PE physical link(s), ties one VRF to another using one subnet for each VRF. Commonly deployed using vlans across a DOT1q trunk (anyone still using ISL? ok, ok a tagged trunk but don&#8217;t tell me I&#8217;m not allowed to say &#8220;trunk&#8221;). Possible to use routing protocols between each individual VRF, most commonly staticly routed as it&#8217;s the safest model, the other side isn&#8217;t trusted&#8230;</li>
<li>PE MP-eBGP, ties the two MPLS clouds together exchanging VPN labels. BGP can be used to exchange the vpn labels, no need for tag-switching of IP traffic. Requires the inter- link to be known in both IGPs as the next-hop changes, <strong>only</strong> the vpn label is preserved end-to-end.</li>
<li>P tag-switching, joins the two domains together at the lowest level. The inter-link can be between P devices all labels are preserved end-to-end. Even the IGPs must have &#8216;full&#8217; connectivity, of course I mean PE-to-PE&#8230;</li>
</ol>
<p>Type-2 seemed to make most sense due to the amount of vrfs involved, no need to go for type-3 and type-1 would add way too much complexity to be able to support a multi month long migration.</p>
<p>Now for the MTU issue. The old MPLS cloud uses 3600&#8217;s as PE&#8217;s in the relevant sites and the new network uses 7600&#8217;s. Admittedly a bit slow on the ball -mind you I was not the original designer- we implemented an mtu of 1536 on the sup720 GE based infrastructure links on the new network. However the vpn label on the 4 FE inter-AS/MP-eBGP links was forgotten untill a service using TCP keepalives was partially migrated. Sessions flapped due to the keepalives being 1500 bytes in size and having their df-bit set. I wonder why they used TCP but as of yet I&#8217;m left guessing.</p>
<p>The moment we noticed the error of our ways we found that IOS threw us a few curve balls:</p>
<ol>
<li>A 3600 running 12.3 doesn&#8217;t accept anything over 1500 as mtu on a FastEthernet interface</li>
<li>A 7600 with 6748-GE (LAN interfaces) doesn&#8217;t allow a larger than 1500 mtu size either (routed interface)</li>
</ol>
<p>The short answers are the following:</p>
<ol>
<li>On the 3600: tag switching mtu 1508</li>
<li>On the 7600: mpls mtu 1508</li>
</ol>
<p>fyi, 1504 would have done fine as an mpls label is just 4 bytes we just threw in another 4 bytes for luck <img src='http://www.djerk.nl/wordpress/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Some links to back things up:</p>
<ul>
<li><a title="External link to cisco.com" href="http://www.cisco.com/en/US/docs/routers/7600/ios/12.2SR/configuration/guide/intrface.html#wp1059164" target="_blank">Cisco MTU config for 7600 12.2SR &amp; layer3 ports</a></li>
<li><a title="External link to blog.ioshints.info" href="http://blog.ioshints.info/2007/10/tale-of-three-mtus.html" target="_blank">Cisco IOS hints and tricks: The tale of three MTUs</a></li>
<li>You&#8217;ll have to take my word for this quote from Cisco: &#8220;I can confirm that using tag-switching mtu at 1508 on the 3600 should resolve the issue from that side&#8221; (despite not being able to set the interface mtu higher than 1500)</li>
</ul>
<p>Command to verity mpls mtu:</p>
<pre>sh mpls [intf] det</pre>
]]></content:encoded>
			<wfw:commentRss>http://www.djerk.nl/wordpress/2009/inter-as-mpls-and-mtu/feed</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
	</channel>
</rss>
