<?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 BFD on Static Route between Fabric Engine and Alcatel in ExtremeSwitching (VSP/Fabric Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/bfd-on-static-route-between-fabric-engine-and-alcatel/m-p/116219#M2702</link>
    <description>&lt;P&gt;Reaching here but wondering if anyone has this setup:&lt;BR /&gt;My Switch - Universal 5520 48T Running Fabric Engine&lt;BR /&gt;Vendor Switch - Alcatel Omniswitch 6860&lt;BR /&gt;Goal - Enable BFD Session on a static route for sub second failover&lt;/P&gt;&lt;P&gt;The vendor is being unhelpful and claiming a compatibility issue although I'm not buying it as BFD is a standard not a proprietary protocol.&amp;nbsp; I do the following 3 things on the Fabric Engine switch side:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Enable BFD Globally (router bfd enable)&lt;/LI&gt;&lt;LI&gt;Enabled BFD on the VLAN interface (ip bfd enable under interface context)&lt;/LI&gt;&lt;LI&gt;Enable BFD on the static route (ip route bfd x.x.x.x)&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;I see the Packet_Out counter incrementing when I run "show ip bfd stats" but nothing for the Packet_In counter.&amp;nbsp;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Any ideas how I can prove this is the vendors issue and misconfiguration on their end?&amp;nbsp; I also want to state that I've tested this thoroughly between two Fabric Engine switches and it works flawlessly.&amp;nbsp;&lt;/P&gt;&lt;P&gt;It's tough for me to prove its an issue on their end without any visibility plus it seems like you can't mirror BFD packets to a SPAN port either.&amp;nbsp; Is my only hope to put a FW in between to get extra visibility?&amp;nbsp; Thoughts on this one?&lt;/P&gt;</description>
    <pubDate>Fri, 18 Oct 2024 14:39:42 GMT</pubDate>
    <dc:creator>Configterminal</dc:creator>
    <dc:date>2024-10-18T14:39:42Z</dc:date>
    <item>
      <title>BFD on Static Route between Fabric Engine and Alcatel</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/bfd-on-static-route-between-fabric-engine-and-alcatel/m-p/116219#M2702</link>
      <description>&lt;P&gt;Reaching here but wondering if anyone has this setup:&lt;BR /&gt;My Switch - Universal 5520 48T Running Fabric Engine&lt;BR /&gt;Vendor Switch - Alcatel Omniswitch 6860&lt;BR /&gt;Goal - Enable BFD Session on a static route for sub second failover&lt;/P&gt;&lt;P&gt;The vendor is being unhelpful and claiming a compatibility issue although I'm not buying it as BFD is a standard not a proprietary protocol.&amp;nbsp; I do the following 3 things on the Fabric Engine switch side:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Enable BFD Globally (router bfd enable)&lt;/LI&gt;&lt;LI&gt;Enabled BFD on the VLAN interface (ip bfd enable under interface context)&lt;/LI&gt;&lt;LI&gt;Enable BFD on the static route (ip route bfd x.x.x.x)&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;I see the Packet_Out counter incrementing when I run "show ip bfd stats" but nothing for the Packet_In counter.&amp;nbsp;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Any ideas how I can prove this is the vendors issue and misconfiguration on their end?&amp;nbsp; I also want to state that I've tested this thoroughly between two Fabric Engine switches and it works flawlessly.&amp;nbsp;&lt;/P&gt;&lt;P&gt;It's tough for me to prove its an issue on their end without any visibility plus it seems like you can't mirror BFD packets to a SPAN port either.&amp;nbsp; Is my only hope to put a FW in between to get extra visibility?&amp;nbsp; Thoughts on this one?&lt;/P&gt;</description>
      <pubDate>Fri, 18 Oct 2024 14:39:42 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/bfd-on-static-route-between-fabric-engine-and-alcatel/m-p/116219#M2702</guid>
      <dc:creator>Configterminal</dc:creator>
      <dc:date>2024-10-18T14:39:42Z</dc:date>
    </item>
  </channel>
</rss>

