<?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 STP Loop Protect in ExtremeSwitching (EXOS/Switch Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/stp-loop-protect/m-p/90010#M21203</link>
    <description>&lt;P&gt;I was studying STP from the User guide , I came to this part of loop protect. My problem is that i don`t understand that part. i feel lost when i read this part.&lt;BR /&gt;Can anyone clarify that part for me and make it more simpler ?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;“Loop Protect protects the network from loops. The Loop Protect feature is achieved by ports receiving&lt;BR /&gt;BPDUs (RSTP/MSTP only) on point-to-point ISLs before their states are allowed to become forwarding.&lt;BR /&gt;Further, if a BPDU timeout occurs on a port, its state becomes listening until a new BPDU is received. In&lt;BR /&gt;this way, both upstream and downstream facing ports are protected. When a root or alternate port&lt;BR /&gt;loses its path to the root bridge, due to message age expiration, it takes on the role of designated port&lt;BR /&gt;and will not forward traffic until a BPDU is received. When a port is intended to be the designated port&lt;BR /&gt;in an ISL, it constantly proposes and will not forward until a BPDU is received. It will revert to listening if&lt;BR /&gt;it stops getting a response. Loop Protect also overrides the port admin setting. This protects against&lt;BR /&gt;misconfiguration (such as disabling STP on a port) and protocol failure by the connected bridge.&lt;BR /&gt;Loop Protect has the capability to&lt;BR /&gt;• Control port forwarding state based on reception of agreement BPDUs&lt;BR /&gt;• Control port forwarding state based on reception of disputed BPDUs&lt;/P&gt;&lt;P&gt;“&lt;/P&gt;</description>
    <pubDate>Thu, 22 Apr 2021 14:31:57 GMT</pubDate>
    <dc:creator>Maghraby</dc:creator>
    <dc:date>2021-04-22T14:31:57Z</dc:date>
    <item>
      <title>STP Loop Protect</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/stp-loop-protect/m-p/90010#M21203</link>
      <description>&lt;P&gt;I was studying STP from the User guide , I came to this part of loop protect. My problem is that i don`t understand that part. i feel lost when i read this part.&lt;BR /&gt;Can anyone clarify that part for me and make it more simpler ?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;“Loop Protect protects the network from loops. The Loop Protect feature is achieved by ports receiving&lt;BR /&gt;BPDUs (RSTP/MSTP only) on point-to-point ISLs before their states are allowed to become forwarding.&lt;BR /&gt;Further, if a BPDU timeout occurs on a port, its state becomes listening until a new BPDU is received. In&lt;BR /&gt;this way, both upstream and downstream facing ports are protected. When a root or alternate port&lt;BR /&gt;loses its path to the root bridge, due to message age expiration, it takes on the role of designated port&lt;BR /&gt;and will not forward traffic until a BPDU is received. When a port is intended to be the designated port&lt;BR /&gt;in an ISL, it constantly proposes and will not forward until a BPDU is received. It will revert to listening if&lt;BR /&gt;it stops getting a response. Loop Protect also overrides the port admin setting. This protects against&lt;BR /&gt;misconfiguration (such as disabling STP on a port) and protocol failure by the connected bridge.&lt;BR /&gt;Loop Protect has the capability to&lt;BR /&gt;• Control port forwarding state based on reception of agreement BPDUs&lt;BR /&gt;• Control port forwarding state based on reception of disputed BPDUs&lt;/P&gt;&lt;P&gt;“&lt;/P&gt;</description>
      <pubDate>Thu, 22 Apr 2021 14:31:57 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/stp-loop-protect/m-p/90010#M21203</guid>
      <dc:creator>Maghraby</dc:creator>
      <dc:date>2021-04-22T14:31:57Z</dc:date>
    </item>
  </channel>
</rss>

