<?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 Asymmetric Routing - Palo Edge Firewall Active/Passive to Nexus Core in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/asymmetric-routing-palo-edge-firewall-active-passive-to-nexus/m-p/1245935#M125865</link>
    <description>&lt;P&gt;We have (2) equal cost L3 links from our Nexus core switches to an upstream Palo edge firewall HA pair, active/passive. On the firewall, this is an aggregation ethernet with layer 3 subinterfaces defined.&amp;nbsp; There is an SVI on each Nexus switch for routing with a layer 2 port-channel to a breakout switch in between the firewall and core, and we are using OSPF.&amp;nbsp; We suspect there may be some asymmetric routing issues where we see flows such as TCP non-syn in global counters incrementing on the firewall, and due to some application throughput issues.&amp;nbsp; We want to influence path selection so that the primary L3 link is always used. I have attached a high-level diagram of the topology.&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We are planning to adjust cost on the Palo by changing the OSPF metric to a higher metric on the secondary link, and also adjusting the cost on the Nexus switch SVI for the secondary link to a higher cost.&amp;nbsp; Currently, we do not have ECMP enabled.&amp;nbsp; Has anyone experienced a similar issue and resolve it by adjusting the OSPF metric, or by enabling ECMP?&lt;/P&gt;</description>
    <pubDate>Tue, 20 Jan 2026 02:46:51 GMT</pubDate>
    <dc:creator>A.Watson129832</dc:creator>
    <dc:date>2026-01-20T02:46:51Z</dc:date>
    <item>
      <title>Asymmetric Routing - Palo Edge Firewall Active/Passive to Nexus Core</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/asymmetric-routing-palo-edge-firewall-active-passive-to-nexus/m-p/1245935#M125865</link>
      <description>&lt;P&gt;We have (2) equal cost L3 links from our Nexus core switches to an upstream Palo edge firewall HA pair, active/passive. On the firewall, this is an aggregation ethernet with layer 3 subinterfaces defined.&amp;nbsp; There is an SVI on each Nexus switch for routing with a layer 2 port-channel to a breakout switch in between the firewall and core, and we are using OSPF.&amp;nbsp; We suspect there may be some asymmetric routing issues where we see flows such as TCP non-syn in global counters incrementing on the firewall, and due to some application throughput issues.&amp;nbsp; We want to influence path selection so that the primary L3 link is always used. I have attached a high-level diagram of the topology.&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We are planning to adjust cost on the Palo by changing the OSPF metric to a higher metric on the secondary link, and also adjusting the cost on the Nexus switch SVI for the secondary link to a higher cost.&amp;nbsp; Currently, we do not have ECMP enabled.&amp;nbsp; Has anyone experienced a similar issue and resolve it by adjusting the OSPF metric, or by enabling ECMP?&lt;/P&gt;</description>
      <pubDate>Tue, 20 Jan 2026 02:46:51 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/asymmetric-routing-palo-edge-firewall-active-passive-to-nexus/m-p/1245935#M125865</guid>
      <dc:creator>A.Watson129832</dc:creator>
      <dc:date>2026-01-20T02:46:51Z</dc:date>
    </item>
    <item>
      <title>Re: Asymmetric Routing - Palo Edge Firewall Active/Passive to Nexus Core</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/asymmetric-routing-palo-edge-firewall-active-passive-to-nexus/m-p/1246116#M125872</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;We had the same problem once. I'm not sure we are in the same situation here but i m pretty sure the solution you said will be ok.&lt;/P&gt;
&lt;P&gt;Shortly : indeed u have to change the ospf cost.&lt;/P&gt;
&lt;P&gt;We put an OSPF cost higher on the nexus backup link and a higher metric on our ospf links on the palo alto connected to this nexus. All of this was related to the nexus doing a hashing thing... We had some&amp;nbsp;asymetric packets and some others not.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope it helps !&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 21 Jan 2026 10:10:02 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/asymmetric-routing-palo-edge-firewall-active-passive-to-nexus/m-p/1246116#M125872</guid>
      <dc:creator>RomainSalmon</dc:creator>
      <dc:date>2026-01-21T10:10:02Z</dc:date>
    </item>
    <item>
      <title>Re: Asymmetric Routing - Palo Edge Firewall Active/Passive to Nexus Core</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/asymmetric-routing-palo-edge-firewall-active-passive-to-nexus/m-p/1246118#M125873</link>
      <description>&lt;P&gt;For the ecmp answer : i don't know at all. I m currently working on migrating these links for ebgp links with ECMP but one sentence scared me :&amp;nbsp;&lt;A href="https://docs.paloaltonetworks.com/ngfw/networking/ecmp" target="_blank"&gt;https://docs.paloaltonetworks.com/ngfw/networking/ecmp&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;'ECMP is supported on all Palo Alto Networks&lt;/SPAN&gt;&lt;SUP class="ph sup"&gt;®&lt;/SUP&gt;&lt;SPAN&gt;&amp;nbsp;firewall models, also with hardware forwarding support on the PA-7000 Series, PA-5200 Series, and PA-3200 Series. VM-Series firewalls support ECMP through software only. &lt;STRONG&gt;Performance is affected for sessions that cannot be hardware offloaded. '&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 21 Jan 2026 09:50:50 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/asymmetric-routing-palo-edge-firewall-active-passive-to-nexus/m-p/1246118#M125873</guid>
      <dc:creator>RomainSalmon</dc:creator>
      <dc:date>2026-01-21T09:50:50Z</dc:date>
    </item>
    <item>
      <title>Re: Asymmetric Routing - Palo Edge Firewall Active/Passive to Nexus Core</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/asymmetric-routing-palo-edge-firewall-active-passive-to-nexus/m-p/1246471#M125898</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;I agree with changing the cost metric. I use high numbers for the metric like 10000. That way the algorhythm will always chose the path I want.&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="OtakarKlier_0-1769197243306.png" style="width: 400px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/70447iBA0DF66D5423E206/image-size/medium?v=v2&amp;amp;px=400" role="button" title="OtakarKlier_0-1769197243306.png" alt="OtakarKlier_0-1769197243306.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;</description>
      <pubDate>Fri, 23 Jan 2026 19:40:52 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/asymmetric-routing-palo-edge-firewall-active-passive-to-nexus/m-p/1246471#M125898</guid>
      <dc:creator>OtakarKlier</dc:creator>
      <dc:date>2026-01-23T19:40:52Z</dc:date>
    </item>
  </channel>
</rss>

