<?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 RE: portenable in ExtremeSwitching (EOS)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-eos/portenable/m-p/59984#M1806</link>
    <description>It is also recommended in this article outlining some best practises for getting started with L2 config, in case this is useful for you ..&lt;BR /&gt;
&lt;BR /&gt;
Browser  View: &lt;A href="https://gtacknowledge.extremenetworks.com/articles/How_To/EOS-Basic-Switch-Layer-2-Configuration-Best-Practices" target="_blank" rel="nofollow noreferrer noopener"&gt;https://gtacknowledge.extremenetworks.com/articles/How_To/EOS-Basic-Switch-Layer-2-Configuration-Best-Practices&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;
    Mobile View:  &lt;A href="https://gtacknowledge.extremenetworks.com/pkb_mobile#article/How_To/kA134000000LymfCAC/s" target="_blank" rel="nofollow noreferrer noopener"&gt;https://gtacknowledge.extremenetworks.com/pkb_mobile#article/How_To/kA134000000LymfCAC/s&lt;/A&gt;  &lt;BR /&gt;
&lt;BR /&gt;
    Please let  us know if this article was helpful by submitting article feedback. Thanks!  &lt;BR /&gt;
&lt;BR /&gt;
Best Regards&lt;BR /&gt;
&lt;BR /&gt;
Glyn&lt;BR /&gt;
&lt;BR /&gt;</description>
    <pubDate>Tue, 18 Aug 2015 15:36:00 GMT</pubDate>
    <dc:creator>Straw__Glyn</dc:creator>
    <dc:date>2015-08-18T15:36:00Z</dc:date>
    <item>
      <title>portenable</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-eos/portenable/m-p/59977#M1799</link>
      <description>Can someone elaborate on the following command?  Below is all that I can find in the documentation.  i  know portadmin determines  if a port processes  BDBPs but what does portenable do?   &lt;BR /&gt;
&lt;BR /&gt;
set spantree portenable  &lt;BR /&gt;
&lt;BR /&gt;
Use this command to set the port status on one or more Spanning Tree ports.</description>
      <pubDate>Fri, 14 Aug 2015 22:42:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-eos/portenable/m-p/59977#M1799</guid>
      <dc:creator>Curtis_Parish1</dc:creator>
      <dc:date>2015-08-14T22:42:00Z</dc:date>
    </item>
    <item>
      <title>RE: portenable</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-eos/portenable/m-p/59978#M1800</link>
      <description>The following information is from a legacy KB article, and is being ported to a new GTAC Knowledge article. These commands operate on the 7100/S/N/K-Series products.&lt;BR /&gt;
&lt;BR /&gt;
The 'set spantree portadmin  {enable | disable}' command will enable/disable the Spanning Tree protocol on a per-port basis as long as STP is globally enabled (this is the default). If per-port spantree portadmin is disabled, any received BPDUs will be discarded and no BPDUs will be transmitted out this port. This command has no effect if STP is globally disabled ('set spantree stpmode none').&lt;BR /&gt;
&lt;BR /&gt;
The 'set spantree portenable  {enable | disable}' command will prohibit data traffic from being switched. However, operMAC will stay up and the port will still indicate link. Higher layer entities can still process traffic; but the traffic won't be learned/forwarded. If you want to shut the port down completely, you would instead use 'set port disable'. &lt;BR /&gt;
Note: There is no practical application that isn't met equally well using the 'set port disable' command, which engages the ifMIB to disable the interface. The spanning tree command is an artifact of an earlier time.</description>
      <pubDate>Fri, 14 Aug 2015 22:53:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-eos/portenable/m-p/59978#M1800</guid>
      <dc:creator>Paul_Poyant</dc:creator>
      <dc:date>2015-08-14T22:53:00Z</dc:date>
    </item>
    <item>
      <title>RE: portenable</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-eos/portenable/m-p/59979#M1801</link>
      <description>Captured in GTAC Knowledge, at &lt;A href="https://gtacknowledge.extremenetworks.com/articles/Q_A/Difference-between-EOS-Spanning-Tree-portadmin-and-portenable-commands" target="_blank" rel="nofollow noreferrer noopener"&gt;https://gtacknowledge.extremenetworks.com/articles/Q_A/Difference-between-EOS-Spanning-Tree-portadmin-and-portenable-commands&lt;/A&gt;.</description>
      <pubDate>Fri, 14 Aug 2015 23:39:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-eos/portenable/m-p/59979#M1801</guid>
      <dc:creator>Paul_Poyant</dc:creator>
      <dc:date>2015-08-14T23:39:00Z</dc:date>
    </item>
    <item>
      <title>RE: portenable</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-eos/portenable/m-p/59980#M1802</link>
      <description>"disables Spanning Tree on that port while also preventing traffic from being transmitted - &lt;I&gt;but not preventing it from being received&lt;/I&gt;. "   &lt;BR /&gt;
&lt;BR /&gt;
Thanks, that is one unusual command.  It bit me when I unintentionally  used portenable instead of portadmin.</description>
      <pubDate>Fri, 14 Aug 2015 23:55:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-eos/portenable/m-p/59980#M1802</guid>
      <dc:creator>Curtis_Parish1</dc:creator>
      <dc:date>2015-08-14T23:55:00Z</dc:date>
    </item>
    <item>
      <title>RE: portenable</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-eos/portenable/m-p/59981#M1803</link>
      <description>The command does have a practical use ( set spantree portenable  disable ). &lt;BR /&gt;
&lt;BR /&gt;
It is often used for Lag member ports to ensure that only the lag logical port (lag,0.1) can forward. The member ports will be set portenable disable so that they cannot forward independently of the lag. &lt;BR /&gt;
&lt;BR /&gt;
Thus if there are connectivity issues and lacp protocol cannot maintain the lag, the member ports will never forward independently of the lag. The is prevents possibility of loops if protocols are failing. It also means clean failover to whatever other redundant path there is. &lt;BR /&gt;
&lt;BR /&gt;
Hope this helps&lt;BR /&gt;
Glyn</description>
      <pubDate>Tue, 18 Aug 2015 15:33:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-eos/portenable/m-p/59981#M1803</guid>
      <dc:creator>Straw__Glyn</dc:creator>
      <dc:date>2015-08-18T15:33:00Z</dc:date>
    </item>
    <item>
      <title>RE: portenable</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-eos/portenable/m-p/59982#M1804</link>
      <description>Very useful information that needs to be included in the configuration guide.   Not sure why it is under spanning tree though.  Sounds like it should be in the LACP config tree.</description>
      <pubDate>Tue, 18 Aug 2015 15:33:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-eos/portenable/m-p/59982#M1804</guid>
      <dc:creator>Curtis_Parish1</dc:creator>
      <dc:date>2015-08-18T15:33:00Z</dc:date>
    </item>
    <item>
      <title>RE: portenable</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-eos/portenable/m-p/59983#M1805</link>
      <description>yes , the positioning under spanning tree can be a little misleading. I think this is a historical thing but i agree we should look at getting this into the config guide if customers are not seeing it. &lt;BR /&gt;
&lt;BR /&gt;
Thanks for the feedback&lt;BR /&gt;
Best Regards&lt;BR /&gt;
Glyn</description>
      <pubDate>Tue, 18 Aug 2015 15:33:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-eos/portenable/m-p/59983#M1805</guid>
      <dc:creator>Straw__Glyn</dc:creator>
      <dc:date>2015-08-18T15:33:00Z</dc:date>
    </item>
    <item>
      <title>RE: portenable</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-eos/portenable/m-p/59984#M1806</link>
      <description>It is also recommended in this article outlining some best practises for getting started with L2 config, in case this is useful for you ..&lt;BR /&gt;
&lt;BR /&gt;
Browser  View: &lt;A href="https://gtacknowledge.extremenetworks.com/articles/How_To/EOS-Basic-Switch-Layer-2-Configuration-Best-Practices" target="_blank" rel="nofollow noreferrer noopener"&gt;https://gtacknowledge.extremenetworks.com/articles/How_To/EOS-Basic-Switch-Layer-2-Configuration-Best-Practices&lt;/A&gt;&lt;BR /&gt;
&lt;BR /&gt;
    Mobile View:  &lt;A href="https://gtacknowledge.extremenetworks.com/pkb_mobile#article/How_To/kA134000000LymfCAC/s" target="_blank" rel="nofollow noreferrer noopener"&gt;https://gtacknowledge.extremenetworks.com/pkb_mobile#article/How_To/kA134000000LymfCAC/s&lt;/A&gt;  &lt;BR /&gt;
&lt;BR /&gt;
    Please let  us know if this article was helpful by submitting article feedback. Thanks!  &lt;BR /&gt;
&lt;BR /&gt;
Best Regards&lt;BR /&gt;
&lt;BR /&gt;
Glyn&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Tue, 18 Aug 2015 15:36:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-eos/portenable/m-p/59984#M1806</guid>
      <dc:creator>Straw__Glyn</dc:creator>
      <dc:date>2015-08-18T15:36:00Z</dc:date>
    </item>
  </channel>
</rss>

