<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic multiple TE path-options vs protect path-option in MPLS</title>
    <link>https://community.cisco.com/t5/mpls/multiple-te-path-options-vs-protect-path-option/m-p/1807018#M16632</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Sherif,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You are correct. Like link/node protection, protected path now provided end to end protetction to the destination. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This cannot be dynamic and so we explicitly need to specify a path which is totally diverse from the primary one. On cofiguring the protected path, as you said, it will be signalled will be used if primary LSP goes down.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH,&lt;/P&gt;&lt;P&gt;Nagendra&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 16 Nov 2011 02:24:22 GMT</pubDate>
    <dc:creator>Nagendra Kumar Nainar</dc:creator>
    <dc:date>2011-11-16T02:24:22Z</dc:date>
    <item>
      <title>multiple TE path-options vs protect path-option</title>
      <link>https://community.cisco.com/t5/mpls/multiple-te-path-options-vs-protect-path-option/m-p/1807017#M16631</link>
      <description>&lt;P&gt;Dear all&lt;/P&gt;&lt;P&gt;I would like your assistance plz in below&lt;/P&gt;&lt;P&gt;what is the difference between having multiple TE path-options &amp;amp; protected path-option &lt;/P&gt;&lt;P&gt;i.e&lt;/P&gt;&lt;P&gt;multiple "tunnel mpls traffic-eng path-option" and "tunnel mpls traffic-eng path-option protect" ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I believe for 1st one, is used to define several static paths but key point is that they wont be signalled (bw reservations) untill primary path is down&lt;/P&gt;&lt;P&gt;however for second one, protected path is signalled and bw reservations are done in advance , i.e before primary path is down&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Correct ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Many Thanks&lt;/P&gt;&lt;P&gt;Sherif Ismail&lt;/P&gt;</description>
      <pubDate>Wed, 16 Nov 2011 00:18:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/mpls/multiple-te-path-options-vs-protect-path-option/m-p/1807017#M16631</guid>
      <dc:creator>Sherif Atef Ahmed Ismail</dc:creator>
      <dc:date>2011-11-16T00:18:29Z</dc:date>
    </item>
    <item>
      <title>multiple TE path-options vs protect path-option</title>
      <link>https://community.cisco.com/t5/mpls/multiple-te-path-options-vs-protect-path-option/m-p/1807018#M16632</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Sherif,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You are correct. Like link/node protection, protected path now provided end to end protetction to the destination. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This cannot be dynamic and so we explicitly need to specify a path which is totally diverse from the primary one. On cofiguring the protected path, as you said, it will be signalled will be used if primary LSP goes down.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH,&lt;/P&gt;&lt;P&gt;Nagendra&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 Nov 2011 02:24:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/mpls/multiple-te-path-options-vs-protect-path-option/m-p/1807018#M16632</guid>
      <dc:creator>Nagendra Kumar Nainar</dc:creator>
      <dc:date>2011-11-16T02:24:22Z</dc:date>
    </item>
    <item>
      <title>multiple TE path-options vs protect path-option</title>
      <link>https://community.cisco.com/t5/mpls/multiple-te-path-options-vs-protect-path-option/m-p/1807019#M16633</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Thanks Nagendra &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/4.5.4/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 Nov 2011 09:17:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/mpls/multiple-te-path-options-vs-protect-path-option/m-p/1807019#M16633</guid>
      <dc:creator>Sherif Ismail</dc:creator>
      <dc:date>2011-11-16T09:17:47Z</dc:date>
    </item>
    <item>
      <title>Re: multiple TE path-options vs protect path-option</title>
      <link>https://community.cisco.com/t5/mpls/multiple-te-path-options-vs-protect-path-option/m-p/1807020#M16634</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear Nagendra&lt;/P&gt;&lt;P&gt;Can you plz check my post about Multihoming VPLS in below URL&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" href="https://community.cisco.com/thread/2115232"&gt;https://supportforums.cisco.com/thread/2115232&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 Nov 2011 14:38:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/mpls/multiple-te-path-options-vs-protect-path-option/m-p/1807020#M16634</guid>
      <dc:creator>Sherif Atef Ahmed Ismail</dc:creator>
      <dc:date>2011-11-18T14:38:59Z</dc:date>
    </item>
  </channel>
</rss>

