<?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 Connectivity loss in hybrid Fabric/MSTP loop during link failover (VOSS &amp;amp; Cisco) in ExtremeSwitching (VSP/Fabric Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/connectivity-loss-in-hybrid-fabric-mstp-loop-during-link/m-p/121770#M3203</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I am currently migrating a Cisco environment to Extreme VOSS (Fabric Engine/Fabric Connect).&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Topology Setup:&lt;/STRONG&gt; The physical loop is as follows: Cisco-01 &amp;lt;--&amp;gt; Cisco-02 &amp;lt;--&amp;gt; Extreme-02 &amp;lt;--&amp;gt; Cisco-03 &amp;lt;--&amp;gt; Extreme-01 &amp;lt;--&amp;gt; Cisco-01&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Cisco Side:&lt;/STRONG&gt; 3x switches&amp;nbsp;&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Extreme Side:&lt;/STRONG&gt; 2x VOSS switches&amp;nbsp;&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;STRONG&gt;The Issue:&lt;/STRONG&gt; Connectivity is stable in the normal state. However, Cisco ports initially showed Bound(RSTP) when connected to VOSS on certain interfaces. To resolve this, I used the command "no spanning-tree mstp force-port-state enable" on the Extreme interfaces connected to the Cisco switches. This successfully forced the ports to p2p mode, and everything works fine when the loop is fully connected.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;The Redundancy Problem:&lt;/STRONG&gt; When I unplug a link to test redundancy, connectivity drops and does not recover, even though a valid redundant path exists.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Observations:&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Port Status:&lt;/STRONG&gt; Cisco ports correctly show p2p when connected to VOSS.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Root Bridge Conflict:&lt;/STRONG&gt; &lt;STRONG&gt;Cisco-03&lt;/STRONG&gt; appears to be isolated; it claims to be the &lt;STRONG&gt;Root Bridge&lt;/STRONG&gt;, while all other switches see &lt;STRONG&gt;Cisco-01&lt;/STRONG&gt; as the Root.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;BPDU Statistics:&lt;/STRONG&gt; On VOSS, show spanning-tree mstp port statistics reveals highly asymmetric Rx/Tx BPDU counts (e.g., very high Rx but near-zero Tx on some ports).&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Configuration Constraint:&lt;/STRONG&gt; VOSS is NOT the Root Bridge (&lt;STRONG&gt;Cisco-01&lt;/STRONG&gt; is the designated Root). My management currently refuses to change the Bridge Priority on the Extreme switches.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;</description>
    <pubDate>Tue, 12 May 2026 08:50:22 GMT</pubDate>
    <dc:creator>Dragonfly</dc:creator>
    <dc:date>2026-05-12T08:50:22Z</dc:date>
    <item>
      <title>Connectivity loss in hybrid Fabric/MSTP loop during link failover (VOSS &amp; Cisco)</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/connectivity-loss-in-hybrid-fabric-mstp-loop-during-link/m-p/121770#M3203</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I am currently migrating a Cisco environment to Extreme VOSS (Fabric Engine/Fabric Connect).&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Topology Setup:&lt;/STRONG&gt; The physical loop is as follows: Cisco-01 &amp;lt;--&amp;gt; Cisco-02 &amp;lt;--&amp;gt; Extreme-02 &amp;lt;--&amp;gt; Cisco-03 &amp;lt;--&amp;gt; Extreme-01 &amp;lt;--&amp;gt; Cisco-01&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Cisco Side:&lt;/STRONG&gt; 3x switches&amp;nbsp;&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Extreme Side:&lt;/STRONG&gt; 2x VOSS switches&amp;nbsp;&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;STRONG&gt;The Issue:&lt;/STRONG&gt; Connectivity is stable in the normal state. However, Cisco ports initially showed Bound(RSTP) when connected to VOSS on certain interfaces. To resolve this, I used the command "no spanning-tree mstp force-port-state enable" on the Extreme interfaces connected to the Cisco switches. This successfully forced the ports to p2p mode, and everything works fine when the loop is fully connected.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;The Redundancy Problem:&lt;/STRONG&gt; When I unplug a link to test redundancy, connectivity drops and does not recover, even though a valid redundant path exists.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Observations:&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Port Status:&lt;/STRONG&gt; Cisco ports correctly show p2p when connected to VOSS.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Root Bridge Conflict:&lt;/STRONG&gt; &lt;STRONG&gt;Cisco-03&lt;/STRONG&gt; appears to be isolated; it claims to be the &lt;STRONG&gt;Root Bridge&lt;/STRONG&gt;, while all other switches see &lt;STRONG&gt;Cisco-01&lt;/STRONG&gt; as the Root.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;BPDU Statistics:&lt;/STRONG&gt; On VOSS, show spanning-tree mstp port statistics reveals highly asymmetric Rx/Tx BPDU counts (e.g., very high Rx but near-zero Tx on some ports).&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Configuration Constraint:&lt;/STRONG&gt; VOSS is NOT the Root Bridge (&lt;STRONG&gt;Cisco-01&lt;/STRONG&gt; is the designated Root). My management currently refuses to change the Bridge Priority on the Extreme switches.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;</description>
      <pubDate>Tue, 12 May 2026 08:50:22 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/connectivity-loss-in-hybrid-fabric-mstp-loop-during-link/m-p/121770#M3203</guid>
      <dc:creator>Dragonfly</dc:creator>
      <dc:date>2026-05-12T08:50:22Z</dc:date>
    </item>
    <item>
      <title>Re: Connectivity loss in hybrid Fabric/MSTP loop during link failover (VOSS &amp; Cisco)</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/connectivity-loss-in-hybrid-fabric-mstp-loop-during-link/m-p/121780#M3204</link>
      <description>&lt;P&gt;Maybe this link can help&lt;/P&gt;&lt;P&gt;&lt;A href="https://extreme-networks.my.site.com/ExtrArticleDetail?an=000082836&amp;amp;q=how%20to%20connect%20SPBM-FC%20to%20MSTP" target="_blank"&gt;https://extreme-networks.my.site.com/ExtrArticleDetail?an=000082836&amp;amp;q=how%20to%20connect%20SPBM-FC%20to%20MSTP&lt;/A&gt;&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;&lt;P&gt;WillyHe&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 12 May 2026 21:21:33 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/connectivity-loss-in-hybrid-fabric-mstp-loop-during-link/m-p/121780#M3204</guid>
      <dc:creator>WillyHe</dc:creator>
      <dc:date>2026-05-12T21:21:33Z</dc:date>
    </item>
  </channel>
</rss>

