<?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>debugall &#187; Traffic Engineering</title>
	<atom:link href="http://www.debugall.co.uk/category/traffic-engineering/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.debugall.co.uk</link>
	<description></description>
	<lastBuildDate>Mon, 27 Jun 2011 06:33:20 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
		<item>
		<title>ISIS wide metrics</title>
		<link>http://www.debugall.co.uk/2009/01/02/isis-wide-metrics/</link>
		<comments>http://www.debugall.co.uk/2009/01/02/isis-wide-metrics/#comments</comments>
		<pubDate>Fri, 02 Jan 2009 05:42:16 +0000</pubDate>
		<dc:creator>zismail</dc:creator>
				<category><![CDATA[CCIE SP]]></category>
		<category><![CDATA[iPod]]></category>
		<category><![CDATA[IS-IS]]></category>
		<category><![CDATA[Traffic Engineering]]></category>
		<category><![CDATA[TE]]></category>

		<guid isPermaLink="false">http://www.debugall.co.uk/?p=551</guid>
		<description><![CDATA[Be default ISIS caps ISIS metrics greater than 63. To address this limitation a new IS-IS TLV was defined to overcome the limited 6-bit metric of 63.  This TLV known as TLV Type 135 increased the per-link metric range from to ie the new TLV has 24-bits for the ISIS metric. This new range can [...]]]></description>
		<wfw:commentRss>http://www.debugall.co.uk/2009/01/02/isis-wide-metrics/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Traffic Engineering &#8211; Fast Reroute</title>
		<link>http://www.debugall.co.uk/2008/12/02/traffic-engineering-fast-reroute/</link>
		<comments>http://www.debugall.co.uk/2008/12/02/traffic-engineering-fast-reroute/#comments</comments>
		<pubDate>Tue, 02 Dec 2008 09:59:49 +0000</pubDate>
		<dc:creator>zismail</dc:creator>
				<category><![CDATA[CCIE SP]]></category>
		<category><![CDATA[Traffic Engineering]]></category>
		<category><![CDATA[TE]]></category>

		<guid isPermaLink="false">http://www.debugall.co.uk/?p=365</guid>
		<description><![CDATA[Fast reroute (FRR) is one of the main drivers for implementing Traffic Engineering. Fast Reroute uses the concept of a backup tunnel. When the path used by the primary tunnel is detected as down, traffic is dynamically switched over to the backup tunnel. Fast reroute provides two types of protection. 1-Link Protection 2-Node Protection Lets [...]]]></description>
		<wfw:commentRss>http://www.debugall.co.uk/2008/12/02/traffic-engineering-fast-reroute/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How does TE detect a neighbor-down</title>
		<link>http://www.debugall.co.uk/2008/12/02/how-does-te-detect-a-link-down/</link>
		<comments>http://www.debugall.co.uk/2008/12/02/how-does-te-detect-a-link-down/#comments</comments>
		<pubDate>Tue, 02 Dec 2008 04:53:50 +0000</pubDate>
		<dc:creator>zismail</dc:creator>
				<category><![CDATA[CCIE SP]]></category>
		<category><![CDATA[Traffic Engineering]]></category>
		<category><![CDATA[BFD]]></category>
		<category><![CDATA[TE]]></category>

		<guid isPermaLink="false">http://www.debugall.co.uk/?p=356</guid>
		<description><![CDATA[There are three &#8220;down notifications&#8221; which cause MPLS nodes to switch traffic onto their FRR backup tunnels. 1-Interface &#8220;down notification&#8221; 2-RSVP Hello neighbor &#8220;down notification&#8221; 3-BFD neighbor &#8220;down notification&#8221; Some interfaces such as POS have very quick interface down notification ie around 50ms.  If a router detects a link down it reroutes the traffic via [...]]]></description>
		<wfw:commentRss>http://www.debugall.co.uk/2008/12/02/how-does-te-detect-a-link-down/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Configuring Traffic Engineering using the explicit path-option</title>
		<link>http://www.debugall.co.uk/2008/12/01/configuring-traffic-engineering-using-the-explicit-path-option/</link>
		<comments>http://www.debugall.co.uk/2008/12/01/configuring-traffic-engineering-using-the-explicit-path-option/#comments</comments>
		<pubDate>Mon, 01 Dec 2008 03:51:03 +0000</pubDate>
		<dc:creator>zismail</dc:creator>
				<category><![CDATA[CCIE SP]]></category>
		<category><![CDATA[Traffic Engineering]]></category>
		<category><![CDATA[TE]]></category>

		<guid isPermaLink="false">http://www.debugall.co.uk/?p=359</guid>
		<description><![CDATA[Lets start by configuring a dynamic tunnel between PE1 and PE2 using the tunnel configuration below. interface Tunnel100 ip unnumbered Loopback0 tunnel destination 3.3.3.3 tunnel mode mpls traffic-eng tunnel mpls traffic-eng priority 5 5 tunnel mpls traffic-eng bandwidth  512 tunnel mpls traffic-eng path-option 1 dynamic Now lets examine the path the tunnel takes. PE1#show mpls [...]]]></description>
		<wfw:commentRss>http://www.debugall.co.uk/2008/12/01/configuring-traffic-engineering-using-the-explicit-path-option/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Configuring Traffic Engineering</title>
		<link>http://www.debugall.co.uk/2008/11/30/configuring-traffic-engineering/</link>
		<comments>http://www.debugall.co.uk/2008/11/30/configuring-traffic-engineering/#comments</comments>
		<pubDate>Sun, 30 Nov 2008 04:41:12 +0000</pubDate>
		<dc:creator>zismail</dc:creator>
				<category><![CDATA[CCIE SP]]></category>
		<category><![CDATA[Traffic Engineering]]></category>
		<category><![CDATA[IS-IS]]></category>
		<category><![CDATA[TE]]></category>

		<guid isPermaLink="false">http://www.debugall.co.uk/?p=348</guid>
		<description><![CDATA[Consider the toplogy below. We will enable traffic engineering on the serial link between PE1 and P1 and between P1 and PE2. The first step is to enable traffic engineering globally on all three routers using the command below. mpls traffic-eng tunnels Once you have enabled traffic engineering globally, you then need to enable traffic [...]]]></description>
		<wfw:commentRss>http://www.debugall.co.uk/2008/11/30/configuring-traffic-engineering/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Traffic Engineering &#8211; IGP extensions (OSPF)</title>
		<link>http://www.debugall.co.uk/2008/11/29/traffic-engineering-igp-extensions-ospf/</link>
		<comments>http://www.debugall.co.uk/2008/11/29/traffic-engineering-igp-extensions-ospf/#comments</comments>
		<pubDate>Sat, 29 Nov 2008 05:14:56 +0000</pubDate>
		<dc:creator>zismail</dc:creator>
				<category><![CDATA[CCIE SP]]></category>
		<category><![CDATA[OSPF]]></category>
		<category><![CDATA[Traffic Engineering]]></category>
		<category><![CDATA[TE]]></category>

		<guid isPermaLink="false">http://www.debugall.co.uk/?p=343</guid>
		<description><![CDATA[OSPF has been extended using TLV and sub-TLVs in order to be used with Traffic Engineering. RFC 3630 contains details of the extensions. The OSPF TLV extension for TE is also referred to as OSPF Opaque LSA 10. This LSA has an area flooding scope. Opaque LSA 10 contains 2 top level TLVs. 1. Router [...]]]></description>
		<wfw:commentRss>http://www.debugall.co.uk/2008/11/29/traffic-engineering-igp-extensions-ospf/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Traffic Engineering &#8211; IGP extensions (IS-IS)</title>
		<link>http://www.debugall.co.uk/2008/11/29/traffic-engineering-igp-extensions-is-is/</link>
		<comments>http://www.debugall.co.uk/2008/11/29/traffic-engineering-igp-extensions-is-is/#comments</comments>
		<pubDate>Sat, 29 Nov 2008 04:46:55 +0000</pubDate>
		<dc:creator>zismail</dc:creator>
				<category><![CDATA[CCIE SP]]></category>
		<category><![CDATA[IS-IS]]></category>
		<category><![CDATA[Traffic Engineering]]></category>
		<category><![CDATA[TE]]></category>

		<guid isPermaLink="false">http://www.debugall.co.uk/?p=330</guid>
		<description><![CDATA[Some extensions were added to ISIS to provide resource information to the TE process. IS-IS Extenstions added to support TE TLVs have been defined to extend IS-IS functionality to include it amongst the protocols of choice for TE. Informational RFC 3784 details the TLVs which have been added To IS-IS to support TE.  RFC 3874 [...]]]></description>
		<wfw:commentRss>http://www.debugall.co.uk/2008/11/29/traffic-engineering-igp-extensions-is-is/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Traffic Engineering &#8211; Introduction</title>
		<link>http://www.debugall.co.uk/2008/11/29/traffic-engineering-introduction/</link>
		<comments>http://www.debugall.co.uk/2008/11/29/traffic-engineering-introduction/#comments</comments>
		<pubDate>Sat, 29 Nov 2008 03:27:20 +0000</pubDate>
		<dc:creator>zismail</dc:creator>
				<category><![CDATA[CCIE SP]]></category>
		<category><![CDATA[Traffic Engineering]]></category>
		<category><![CDATA[TE]]></category>

		<guid isPermaLink="false">http://www.debugall.co.uk/?p=326</guid>
		<description><![CDATA[Informational RFC 3272 provides an overview of Traffic Engineering. Traffic Engineering(TE) is different to network engineering in that TE is concerned about engineering/manipulating traffic flows across the network. If you think about a road system, network engineering is similar to that of building the roads themselves.  Where as TE is analogous to placing the traffic [...]]]></description>
		<wfw:commentRss>http://www.debugall.co.uk/2008/11/29/traffic-engineering-introduction/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

