<?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 Spanning-tree Best practices with vPC in Switching</title>
    <link>https://community.cisco.com/t5/switching/spanning-tree-best-practices-with-vpc/m-p/2153283#M247798</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am looking for best practices for spanning-tree features in an entire vPC network, read a cisco doc where it says to do not use bridge assurance in a vPC environment. Is there any other spanning-tree feature that we need to look further before applying with vPC, like loopguard or root-guard. Should I take care before applying those features with or without peer-switch vPC feature&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance&lt;/P&gt;</description>
    <pubDate>Thu, 07 Mar 2019 20:24:39 GMT</pubDate>
    <dc:creator>j.eduardog</dc:creator>
    <dc:date>2019-03-07T20:24:39Z</dc:date>
    <item>
      <title>Spanning-tree Best practices with vPC</title>
      <link>https://community.cisco.com/t5/switching/spanning-tree-best-practices-with-vpc/m-p/2153283#M247798</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am looking for best practices for spanning-tree features in an entire vPC network, read a cisco doc where it says to do not use bridge assurance in a vPC environment. Is there any other spanning-tree feature that we need to look further before applying with vPC, like loopguard or root-guard. Should I take care before applying those features with or without peer-switch vPC feature&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance&lt;/P&gt;</description>
      <pubDate>Thu, 07 Mar 2019 20:24:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/spanning-tree-best-practices-with-vpc/m-p/2153283#M247798</guid>
      <dc:creator>j.eduardog</dc:creator>
      <dc:date>2019-03-07T20:24:39Z</dc:date>
    </item>
    <item>
      <title>Re: Spanning-tree Best practices with vPC</title>
      <link>https://community.cisco.com/t5/switching/spanning-tree-best-practices-with-vpc/m-p/2153284#M247799</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yes, there specific recommendation when using spanning-tree with VPC.&lt;/P&gt;&lt;P&gt;Have a look at this link under:&lt;/P&gt;&lt;P dir="ltr" style="font-size: 17.8112px; font-family: sans-serif; left: 174.272px; top: 258.295px; transform: scale(0.997358, 1); transform-origin: 0% 0% 0px;"&gt;Special Considerations for Spanning Tree with vPCs&lt;/P&gt;&lt;P dir="ltr"&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9670/C07-572834-00_STDG_NX-OS_vPC_DG.pdf" rel="nofollow"&gt;http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9670/C07-572834-00_STDG_NX-OS_vPC_DG.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 Mar 2013 21:18:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/spanning-tree-best-practices-with-vpc/m-p/2153284#M247799</guid>
      <dc:creator>Reza Sharifi</dc:creator>
      <dc:date>2013-03-21T21:18:41Z</dc:date>
    </item>
    <item>
      <title>Re: Spanning-tree Best practices with vPC</title>
      <link>https://community.cisco.com/t5/switching/spanning-tree-best-practices-with-vpc/m-p/2153285#M247800</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Reza,&lt;/P&gt;&lt;P&gt;Is there any impact on hardware resources on switches if I enable RSTP in an environment?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 Mar 2013 21:21:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/spanning-tree-best-practices-with-vpc/m-p/2153285#M247800</guid>
      <dc:creator>sajid_m123</dc:creator>
      <dc:date>2013-03-21T21:21:31Z</dc:date>
    </item>
    <item>
      <title>Spanning-tree Best practices with vPC</title>
      <link>https://community.cisco.com/t5/switching/spanning-tree-best-practices-with-vpc/m-p/2153286#M247801</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;For the Nexus Series, the default is Rapid PVST+.&amp;nbsp; If you don't have a whole a lot of vlans, I would stay with RSTP.&amp;nbsp; If you have a lots of vlans, then MST probably scales better.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P dir="ltr" style="font-size: 16.0688px; font-family: sans-serif; left: 174.272px; top: 671.711px; transform: scale(1.00315, 1); transform-origin: 0% 0% 0px;"&gt;MST Compared to Rapid PVST+&lt;/P&gt;&lt;P dir="ltr"&gt;&lt;/P&gt;&lt;P dir="ltr" style="font-size: 14.52px; font-family: sans-serif; left: 174.272px; top: 696.492px; transform: scale(0.999059, 1); transform-origin: 0% 0% 0px;"&gt;MST allows you to assign two or more VLANs to a spanning&lt;/P&gt;&lt;P dir="ltr" style="font-size: 14.52px; font-family: sans-serif; left: 560.391px; top: 696.492px; transform: scale(0.967032, 1); transform-origin: 0% 0% 0px;"&gt;-&lt;/P&gt;&lt;P dir="ltr" style="font-size: 14.52px; font-family: sans-serif; left: 565.038px; top: 696.492px; transform: scale(1.0009, 1); transform-origin: 0% 0% 0px;"&gt;tree instance. MST is not the default spanning&lt;/P&gt;&lt;P dir="ltr" style="font-size: 14.52px; font-family: sans-serif; left: 860.713px; top: 696.492px; transform: scale(0.967032, 1); transform-origin: 0% 0% 0px;"&gt;-&lt;/P&gt;&lt;P dir="ltr" style="font-size: 14.52px; font-family: sans-serif; left: 865.553px; top: 696.492px; transform: scale(0.999377, 1); transform-origin: 0% 0% 0px;"&gt;tree &lt;/P&gt;&lt;P dir="ltr" style="font-size: 14.52px; font-family: sans-serif; left: 174.272px; top: 719.143px; transform: scale(0.990327, 1); transform-origin: 0% 0% 0px;"&gt;mode; Rapid PVST+ is the default mode on Cisco&lt;/P&gt;&lt;P dir="ltr" style="font-size: 9.68px; font-family: sans-serif; left: 494.535px; top: 716.627px; transform: scale(1.01917, 1); transform-origin: 0% 0% 0px;"&gt;®&lt;/P&gt;&lt;P dir="ltr"&gt;&lt;/P&gt;&lt;P dir="ltr" style="font-size: 14.52px; font-family: sans-serif; left: 505.57px; top: 719.143px; transform: scale(0.963706, 1); transform-origin: 0% 0% 0px;"&gt;switches.&lt;/P&gt;&lt;P dir="ltr"&gt;&lt;/P&gt;&lt;P dir="ltr" style="font-size: 14.52px; font-family: sans-serif; left: 174.272px; top: 752.83px; transform: scale(0.987879, 1); transform-origin: 0% 0% 0px;"&gt;MST instances with the same &lt;/P&gt;&lt;P dir="ltr" style="font-size: 14.52px; font-family: sans-serif; left: 367.921px; top: 752.83px; transform: scale(1.00841, 1); transform-origin: 0% 0% 0px;"&gt;name, revision number, and VLAN&lt;/P&gt;&lt;P dir="ltr" style="font-size: 14.52px; font-family: sans-serif; left: 590.012px; top: 752.83px; transform: scale(0.967032, 1); transform-origin: 0% 0% 0px;"&gt;-&lt;/P&gt;&lt;P dir="ltr" style="font-size: 14.52px; font-family: sans-serif; left: 594.852px; top: 752.83px; transform: scale(1.01398, 1); transform-origin: 0% 0% 0px;"&gt;to&lt;/P&gt;&lt;P dir="ltr" style="font-size: 14.52px; font-family: sans-serif; left: 607.049px; top: 752.83px; transform: scale(0.967032, 1); transform-origin: 0% 0% 0px;"&gt;-&lt;/P&gt;&lt;P dir="ltr" style="font-size: 14.52px; font-family: sans-serif; left: 611.889px; top: 752.83px; transform: scale(0.990336, 1); transform-origin: 0% 0% 0px;"&gt;instance mapping combine to form an MST &lt;/P&gt;&lt;P dir="ltr" style="font-size: 14.52px; font-family: sans-serif; left: 174.272px; top: 775.675px; transform: scale(1.00166, 1); transform-origin: 0% 0% 0px;"&gt;region. The MST region appears as a single bridge to spanning&lt;/P&gt;&lt;P dir="ltr" style="font-size: 14.52px; font-family: sans-serif; left: 580.526px; top: 775.675px; transform: scale(0.967032, 1); transform-origin: 0% 0% 0px;"&gt;-&lt;/P&gt;&lt;P dir="ltr" style="font-size: 14.52px; font-family: sans-serif; left: 585.366px; top: 775.675px; transform: scale(0.998833, 1); transform-origin: 0% 0% 0px;"&gt;tree configurations outside the region.&lt;/P&gt;&lt;P dir="ltr"&gt;&lt;/P&gt;&lt;P dir="ltr" style="font-size: 14.52px; font-family: sans-serif; left: 174.272px; top: 809.555px; transform: scale(0.997797, 1); transform-origin: 0% 0% 0px;"&gt;The advantages of MST over Rapid PVST+ are as follows:&lt;/P&gt;&lt;P dir="ltr"&gt;&lt;/P&gt;&lt;P dir="ltr" style="font-size: 11.2288px; font-family: sans-serif; left: 203.312px; top: 845.758px; transform: scale(0.968885, 1); transform-origin: 0% 0% 0px;"&gt;●&lt;/P&gt;&lt;P dir="ltr"&gt;&lt;/P&gt;&lt;P dir="ltr" style="font-size: 14.52px; font-family: sans-serif; left: 220.736px; top: 843.241px; transform: scale(1.00961, 1); transform-origin: 0% 0% 0px;"&gt;MST is an IEE&lt;/P&gt;&lt;P dir="ltr" style="font-size: 14.52px; font-family: sans-serif; left: 313.713px; top: 843.241px; transform: scale(0.989877, 1); transform-origin: 0% 0% 0px;"&gt;E standard.&lt;/P&gt;&lt;P dir="ltr"&gt;&lt;/P&gt;&lt;P dir="ltr" style="font-size: 11.2288px; font-family: sans-serif; left: 203.312px; top: 873.249px; transform: scale(0.968885, 1); transform-origin: 0% 0% 0px;"&gt;●&lt;/P&gt;&lt;P dir="ltr"&gt;&lt;/P&gt;&lt;P dir="ltr" style="font-size: 14.52px; font-family: sans-serif; left: 220.736px; top: 870.732px; transform: scale(0.99722, 1); transform-origin: 0% 0% 0px;"&gt;MST is more resource efficient. In particular, the number of BPDUs transmitted by MST does not depend on &lt;/P&gt;&lt;P dir="ltr" style="font-size: 14.52px; font-family: sans-serif; left: 220.736px; top: 893.19px; transform: scale(0.997253, 1); transform-origin: 0% 0% 0px;"&gt;the number of VLANs, as Rapid PVST+ does.&lt;/P&gt;&lt;P dir="ltr"&gt;&lt;/P&gt;&lt;P dir="ltr" style="font-size: 11.2288px; font-family: sans-serif; left: 203.312px; top: 923.198px; transform: scale(0.968885, 1); transform-origin: 0% 0% 0px;"&gt;●&lt;/P&gt;&lt;P dir="ltr"&gt;&lt;/P&gt;&lt;P dir="ltr" style="font-size: 14.52px; font-family: sans-serif; left: 220.736px; top: 920.681px; transform: scale(1.00558, 1); transform-origin: 0% 0% 0px;"&gt;MST decouples the creation of VLANs from the definition for forwarding the topology.&lt;/P&gt;&lt;P dir="ltr"&gt;&lt;/P&gt;&lt;P dir="ltr" style="font-size: 11.2288px; font-family: sans-serif; left: 203.312px; top: 950.737px; transform: scale(0.968885, 1); transform-origin: 0% 0% 0px;"&gt;●&lt;/P&gt;&lt;P dir="ltr"&gt;&lt;/P&gt;&lt;P dir="ltr" style="font-size: 14.52px; font-family: sans-serif; left: 220.736px; top: 948.221px; transform: scale(1.00014, 1); transform-origin: 0% 0% 0px;"&gt;MST simplifies the depl&lt;/P&gt;&lt;P dir="ltr" style="font-size: 14.52px; font-family: sans-serif; left: 371.018px; top: 948.221px; transform: scale(0.995611, 1); transform-origin: 0% 0% 0px;"&gt;oyment of stretched Layer 2 networks, because of its ability to define regions.&lt;/P&gt;&lt;P dir="ltr"&gt;&lt;/P&gt;&lt;P dir="ltr" style="font-size: 14.52px; font-family: sans-serif; left: 174.272px; top: 975.712px; transform: scale(0.995613, 1); transform-origin: 0% 0% 0px;"&gt;For all these reasons, it is advisable for many deployments to migrate to an MST&lt;/P&gt;&lt;P dir="ltr" style="font-size: 14.52px; font-family: sans-serif; left: 691.459px; top: 975.712px; transform: scale(0.967032, 1); transform-origin: 0% 0% 0px;"&gt;-&lt;/P&gt;&lt;P dir="ltr" style="font-size: 14.52px; font-family: sans-serif; left: 696.299px; top: 975.712px; transform: scale(1.01626, 1); transform-origin: 0% 0% 0px;"&gt;based topology.&lt;/P&gt;&lt;P dir="ltr"&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9670/C07-572834-00_STDG_NX-OS_vPC_DG.pdf"&gt;http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9670/C07-572834-00_STDG_NX-OS_vPC_DG.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 Mar 2013 21:35:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/spanning-tree-best-practices-with-vpc/m-p/2153286#M247801</guid>
      <dc:creator>Reza Sharifi</dc:creator>
      <dc:date>2013-03-21T21:35:08Z</dc:date>
    </item>
    <item>
      <title>Re: Spanning-tree Best practices with vPC</title>
      <link>https://community.cisco.com/t5/switching/spanning-tree-best-practices-with-vpc/m-p/2153287#M247802</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Reza,&lt;/P&gt;&lt;P&gt;Thanks for the good info. My question is that is there any impact on network performance due resource consumption if I enable RSTP on all the switches in a network?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 Mar 2013 21:39:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/spanning-tree-best-practices-with-vpc/m-p/2153287#M247802</guid>
      <dc:creator>sajid_m123</dc:creator>
      <dc:date>2013-03-21T21:39:12Z</dc:date>
    </item>
    <item>
      <title>Spanning-tree Best practices with vPC</title>
      <link>https://community.cisco.com/t5/switching/spanning-tree-best-practices-with-vpc/m-p/2153288#M247803</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Usually, there is not, but how large is the network?&amp;nbsp; What type of devices are you using and how many vlans?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 Mar 2013 21:44:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/spanning-tree-best-practices-with-vpc/m-p/2153288#M247803</guid>
      <dc:creator>Reza Sharifi</dc:creator>
      <dc:date>2013-03-21T21:44:06Z</dc:date>
    </item>
    <item>
      <title>Re: Spanning-tree Best practices with vPC</title>
      <link>https://community.cisco.com/t5/switching/spanning-tree-best-practices-with-vpc/m-p/2153289#M247804</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Around 50 Vlans with overall 60 switches. Switches range from 3550, 3560, 3750, 3760, 4500, 6500&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 Mar 2013 21:49:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/spanning-tree-best-practices-with-vpc/m-p/2153289#M247804</guid>
      <dc:creator>sajid_m123</dc:creator>
      <dc:date>2013-03-21T21:49:58Z</dc:date>
    </item>
    <item>
      <title>Re: Spanning-tree Best practices with vPC</title>
      <link>https://community.cisco.com/t5/switching/spanning-tree-best-practices-with-vpc/m-p/2153290#M247805</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Better open another topic for you sir, thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 Mar 2013 21:58:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/spanning-tree-best-practices-with-vpc/m-p/2153290#M247805</guid>
      <dc:creator>j.eduardog</dc:creator>
      <dc:date>2013-03-21T21:58:07Z</dc:date>
    </item>
    <item>
      <title>Spanning-tree Best practices with vPC</title>
      <link>https://community.cisco.com/t5/switching/spanning-tree-best-practices-with-vpc/m-p/2153291#M247806</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P style="background-color: #ffffff; border-collapse: collapse; font-size: 12px; list-style: none; font-family: Arial, verdana, sans-serif;"&gt;Thanks for the link you provided, but what about using or not using loopguard in the access switches, is that a best practice using it even with vPC or no need to use it?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="background-color: #ffffff; border-collapse: collapse; font-size: 12px; list-style: none; font-family: Arial, verdana, sans-serif;"&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 Mar 2013 21:59:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/spanning-tree-best-practices-with-vpc/m-p/2153291#M247806</guid>
      <dc:creator>j.eduardog</dc:creator>
      <dc:date>2013-03-21T21:59:26Z</dc:date>
    </item>
    <item>
      <title>Spanning-tree Best practices with vPC</title>
      <link>https://community.cisco.com/t5/switching/spanning-tree-best-practices-with-vpc/m-p/2153292#M247807</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It is usually a good practice to enable loop guard on both sides of your link:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;H3&gt; Loop Guard &lt;/H3&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;A name="wp873716"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt; Loop Guard provides additional protection against Layer 2 forwarding&amp;nbsp; loops. Loop Guard should be enabled on root and alternate ports in the&amp;nbsp; spanning tree topology. When Loop Guard detects that BPDUs are no longer&amp;nbsp; being received on a non-designated port, the port is moved into a&amp;nbsp; loop-inconsistent state instead of transitioning to the&amp;nbsp; listening/learning/forwarding state. This prevents a Layer 2 loop from&amp;nbsp; occurring in the event that a link becomes unidirectional or a node&amp;nbsp; stops transmitting BPDUs for some reason. Loop Guard may also be&amp;nbsp; configured globally, but port-specific configuration is preferred to&amp;nbsp; ensure that it is only enabled where specifically necessary. An&amp;nbsp; illustration of where to enable Loop Guard, Root Guard, and BPDU Guard&amp;nbsp; spanning tree enhancements is shown in &lt;A href="http://www.cisco.com/en/US/docs/solutions/Enterprise/Data_Center/nx_7000_dc.html#wp873723"&gt;Figure 6&lt;/A&gt;. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;more info here:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/docs/solutions/Enterprise/Data_Center/nx_7000_dc.html"&gt;http://www.cisco.com/en/US/docs/solutions/Enterprise/Data_Center/nx_7000_dc.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 Mar 2013 22:16:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/spanning-tree-best-practices-with-vpc/m-p/2153292#M247807</guid>
      <dc:creator>Reza Sharifi</dc:creator>
      <dc:date>2013-03-21T22:16:54Z</dc:date>
    </item>
    <item>
      <title>Spanning-tree Best practices with vPC</title>
      <link>https://community.cisco.com/t5/switching/spanning-tree-best-practices-with-vpc/m-p/2153293#M247808</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There is no specific recommendation about STP features with a full vPC environment in those links&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks anyway&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 22 Mar 2013 01:07:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/spanning-tree-best-practices-with-vpc/m-p/2153293#M247808</guid>
      <dc:creator>j.eduardog</dc:creator>
      <dc:date>2013-03-22T01:07:04Z</dc:date>
    </item>
  </channel>
</rss>

