<?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 Re: HA path group in Next-Generation Firewall Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/ha-path-group/m-p/580624#M2838</link>
    <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/1182974307"&gt;@BlackWater&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;Slightly confused on what your question is? What's the goal?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Path monitoring simply uses ICMP to the specified path group to ensure that your active device can actually pass traffic. So just going off of your network design you might create a path group with a failure condition of 'all' and specify the switches and the ISP equipment as destinations and trigger a failure if all of those start failing ICMP. You might have another group that simply checks the ISP gateways are reachable and fail over if all of them are down. It honestly depends on what you&amp;nbsp;&lt;EM&gt;can&amp;nbsp;&lt;/EM&gt;monitor and what your desired outcome actually is.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 15 Mar 2024 21:36:19 GMT</pubDate>
    <dc:creator>BPry</dc:creator>
    <dc:date>2024-03-15T21:36:19Z</dc:date>
    <item>
      <title>HA path group</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/ha-path-group/m-p/580623#M2837</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am trying to setup HA path group but as seen below between FW and ISP we have L2 switches. what is the optimum solution for path monitoring since L2 switch hardly goes down ? By the way Panorama manages the FW&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="EOdeh_1-1710534820057.png" style="width: 400px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/58427iB6A4871DC907C050/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="EOdeh_1-1710534820057.png" alt="EOdeh_1-1710534820057.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 15 Mar 2024 21:26:12 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/ha-path-group/m-p/580623#M2837</guid>
      <dc:creator>BlackWater</dc:creator>
      <dc:date>2024-03-15T21:26:12Z</dc:date>
    </item>
    <item>
      <title>Re: HA path group</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/ha-path-group/m-p/580624#M2838</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/1182974307"&gt;@BlackWater&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;Slightly confused on what your question is? What's the goal?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Path monitoring simply uses ICMP to the specified path group to ensure that your active device can actually pass traffic. So just going off of your network design you might create a path group with a failure condition of 'all' and specify the switches and the ISP equipment as destinations and trigger a failure if all of those start failing ICMP. You might have another group that simply checks the ISP gateways are reachable and fail over if all of them are down. It honestly depends on what you&amp;nbsp;&lt;EM&gt;can&amp;nbsp;&lt;/EM&gt;monitor and what your desired outcome actually is.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 15 Mar 2024 21:36:19 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/ha-path-group/m-p/580624#M2838</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2024-03-15T21:36:19Z</dc:date>
    </item>
  </channel>
</rss>

