<?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 flow redirect - priority in ExtremeSwitching (EXOS/Switch Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/flow-redirect-priority/m-p/92381#M21437</link>
    <description>&lt;P&gt;I’m not able to mock up a lab right now but need to deploy flow redirect for remote site HA.&amp;nbsp; Primary is fiber circuit and secondary is VPN off the our FW.&amp;nbsp; The routes on the core are static and default gw is the FW.&lt;/P&gt; &lt;P&gt;I understand I’ll need to create 2 static routes&lt;/P&gt; &lt;P&gt;One for the next hop traffic - direct connected and one pointed to the FW with a higher weight&lt;/P&gt; &lt;P&gt;Then configure the ACL statement match traffic then flow-redirect policy and apply to the vlans&lt;/P&gt; &lt;P&gt;The part I’m unsure of is when creating the flow redirect should the primary path have higher priority or lower then the other one (FW) that its tracking?&amp;nbsp; I’m not finding this in any documentation.&lt;/P&gt; &lt;P&gt;&amp;nbsp;&lt;/P&gt; &lt;P&gt;Thank you,&lt;/P&gt; &lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sat, 18 Apr 2020 04:03:07 GMT</pubDate>
    <dc:creator>treese</dc:creator>
    <dc:date>2020-04-18T04:03:07Z</dc:date>
    <item>
      <title>flow redirect - priority</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/flow-redirect-priority/m-p/92381#M21437</link>
      <description>&lt;P&gt;I’m not able to mock up a lab right now but need to deploy flow redirect for remote site HA.&amp;nbsp; Primary is fiber circuit and secondary is VPN off the our FW.&amp;nbsp; The routes on the core are static and default gw is the FW.&lt;/P&gt; &lt;P&gt;I understand I’ll need to create 2 static routes&lt;/P&gt; &lt;P&gt;One for the next hop traffic - direct connected and one pointed to the FW with a higher weight&lt;/P&gt; &lt;P&gt;Then configure the ACL statement match traffic then flow-redirect policy and apply to the vlans&lt;/P&gt; &lt;P&gt;The part I’m unsure of is when creating the flow redirect should the primary path have higher priority or lower then the other one (FW) that its tracking?&amp;nbsp; I’m not finding this in any documentation.&lt;/P&gt; &lt;P&gt;&amp;nbsp;&lt;/P&gt; &lt;P&gt;Thank you,&lt;/P&gt; &lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 18 Apr 2020 04:03:07 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/flow-redirect-priority/m-p/92381#M21437</guid>
      <dc:creator>treese</dc:creator>
      <dc:date>2020-04-18T04:03:07Z</dc:date>
    </item>
  </channel>
</rss>

