<?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 Uplink configuration between EXOS stack 5320 and VOSS cluster in ExtremeSwitching (EXOS/Switch Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/uplink-configuration-between-exos-stack-5320-and-voss-cluster/m-p/119978#M23070</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Can someone please confirm whether the uplink configuration between a &lt;STRONG&gt;VOSS cluster&lt;/STRONG&gt; and an &lt;STRONG&gt;EXOS 5320 stack&lt;/STRONG&gt; is correct? (See attached diagram.)&lt;/P&gt;&lt;P&gt;For &lt;STRONG&gt;EXOS-to-EXOS&lt;/STRONG&gt;, how should the uplinks be configured when they connect to a &lt;STRONG&gt;5520 cluster used for VPEX&lt;/STRONG&gt;?&lt;/P&gt;&lt;P&gt;During a production test of the &lt;STRONG&gt;VOSS cluster ↔ EXOS&lt;/STRONG&gt; connection, we saw &lt;STRONG&gt;Centreon&lt;/STRONG&gt; alerts indicating that some switches became unreachable, which forced us to disconnect the link. Our environment is large and mixed, with &lt;STRONG&gt;VOSS, EXOS, and ERS&lt;/STRONG&gt; switches (&lt;STRONG&gt;SPB, MLT, SLT&lt;/STRONG&gt;…).&lt;/P&gt;&lt;P&gt;Could this be related to the configuration&amp;nbsp;&lt;STRONG&gt;spanning tree settings&lt;/STRONG&gt;? If so, what are the &lt;STRONG&gt;best practices for spanning tree&lt;/STRONG&gt; in this scenario?&lt;BR /&gt;Also, what &lt;STRONG&gt;troubleshooting steps&lt;/STRONG&gt; would you recommend to isolate the issue?&lt;/P&gt;&lt;P&gt;Thanks for your help!&lt;/P&gt;</description>
    <pubDate>Wed, 13 Aug 2025 19:10:36 GMT</pubDate>
    <dc:creator>Tamaya</dc:creator>
    <dc:date>2025-08-13T19:10:36Z</dc:date>
    <item>
      <title>Uplink configuration between EXOS stack 5320 and VOSS cluster</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/uplink-configuration-between-exos-stack-5320-and-voss-cluster/m-p/119978#M23070</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Can someone please confirm whether the uplink configuration between a &lt;STRONG&gt;VOSS cluster&lt;/STRONG&gt; and an &lt;STRONG&gt;EXOS 5320 stack&lt;/STRONG&gt; is correct? (See attached diagram.)&lt;/P&gt;&lt;P&gt;For &lt;STRONG&gt;EXOS-to-EXOS&lt;/STRONG&gt;, how should the uplinks be configured when they connect to a &lt;STRONG&gt;5520 cluster used for VPEX&lt;/STRONG&gt;?&lt;/P&gt;&lt;P&gt;During a production test of the &lt;STRONG&gt;VOSS cluster ↔ EXOS&lt;/STRONG&gt; connection, we saw &lt;STRONG&gt;Centreon&lt;/STRONG&gt; alerts indicating that some switches became unreachable, which forced us to disconnect the link. Our environment is large and mixed, with &lt;STRONG&gt;VOSS, EXOS, and ERS&lt;/STRONG&gt; switches (&lt;STRONG&gt;SPB, MLT, SLT&lt;/STRONG&gt;…).&lt;/P&gt;&lt;P&gt;Could this be related to the configuration&amp;nbsp;&lt;STRONG&gt;spanning tree settings&lt;/STRONG&gt;? If so, what are the &lt;STRONG&gt;best practices for spanning tree&lt;/STRONG&gt; in this scenario?&lt;BR /&gt;Also, what &lt;STRONG&gt;troubleshooting steps&lt;/STRONG&gt; would you recommend to isolate the issue?&lt;/P&gt;&lt;P&gt;Thanks for your help!&lt;/P&gt;</description>
      <pubDate>Wed, 13 Aug 2025 19:10:36 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/uplink-configuration-between-exos-stack-5320-and-voss-cluster/m-p/119978#M23070</guid>
      <dc:creator>Tamaya</dc:creator>
      <dc:date>2025-08-13T19:10:36Z</dc:date>
    </item>
    <item>
      <title>Re: Uplink configuration between EXOS stack 5320 and VOSS cluster</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/uplink-configuration-between-exos-stack-5320-and-voss-cluster/m-p/119997#M23072</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;one thing I saw in your diagram: You had set LACP timer to short interval on VOSS.&lt;BR /&gt;The timer should be the same on both ends of the link.&amp;nbsp;&lt;BR /&gt;So on EXOS "configure sharing 1:53 lacp timeout short" has to be set, too.&lt;BR /&gt;Or leave defaults on both ends.&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Christoph&lt;/P&gt;</description>
      <pubDate>Thu, 14 Aug 2025 14:24:36 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/uplink-configuration-between-exos-stack-5320-and-voss-cluster/m-p/119997#M23072</guid>
      <dc:creator>Christoph</dc:creator>
      <dc:date>2025-08-14T14:24:36Z</dc:date>
    </item>
    <item>
      <title>Re: Uplink configuration between EXOS stack 5320 and VOSS cluster</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/uplink-configuration-between-exos-stack-5320-and-voss-cluster/m-p/119999#M23073</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;Christoph,&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Thanks for your message. I have read that in a Fabric Attach environment, there is no need to configure uplinks on the EXOS side, as they are handled automatically by the fabric.&lt;BR /&gt;&lt;A href="https://documentation.extremenetworks.com/exos_32.5/GUID-F140CBF4-6E25-4DA7-92EC-DD5B645E1218.shtml" target="_blank" rel="noopener"&gt;https://documentation.extremenetworks.com/exos_32.5/GUID-F140CBF4-6E25-4DA7-92EC-DD5B645E1218.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;</description>
      <pubDate>Thu, 14 Aug 2025 23:18:34 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/uplink-configuration-between-exos-stack-5320-and-voss-cluster/m-p/119999#M23073</guid>
      <dc:creator>Tamaya</dc:creator>
      <dc:date>2025-08-14T23:18:34Z</dc:date>
    </item>
  </channel>
</rss>

