<?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 Firewalls in Active Active using Azure Internal Load balancer in VM-Series in the Public Cloud</title>
    <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/firewalls-in-active-active-using-azure-internal-load-balancer/m-p/1226318#M2363</link>
    <description>&lt;P&gt;Hi, we have deployed Palo-alto firewalls on Azure and a Standard Internal Load Balancer with single front-end IP and single backend pool, does LB maintain session state if -&lt;/P&gt;
&lt;P&gt;(1) communication is sourced from Azure VNET destined to On-premise ?&lt;/P&gt;
&lt;P&gt;(2) communication is sourced from On-premise destined to Azure VNET ?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We don't have a Virtual Network Gateway deployed instead we have a Cisco vMX SDWAN in Azure VNET that extend the connectivity to on-premise, so for on-premise communication we are routing all traffic (after firewall inspection) to Cisco vMX SDWAN which further forwards the traffic to on-premise.&lt;/P&gt;
&lt;P&gt;Currently all traffic between the Azure VNETs are routing through Azure ILB are working and no issues have been reported so far but traffic which sends outside to Azure for on-prem where we are observing asymmetric of routing causing drops on firewall intermittently specifically we observed issues for SNMP and UDP protocols so would like to understand whether this type of design supports by Palo Alto on Azure using Azure ILB&lt;/P&gt;</description>
    <pubDate>Fri, 11 Apr 2025 06:47:05 GMT</pubDate>
    <dc:creator>SShaikh647896</dc:creator>
    <dc:date>2025-04-11T06:47:05Z</dc:date>
    <item>
      <title>Firewalls in Active Active using Azure Internal Load balancer</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/firewalls-in-active-active-using-azure-internal-load-balancer/m-p/1226318#M2363</link>
      <description>&lt;P&gt;Hi, we have deployed Palo-alto firewalls on Azure and a Standard Internal Load Balancer with single front-end IP and single backend pool, does LB maintain session state if -&lt;/P&gt;
&lt;P&gt;(1) communication is sourced from Azure VNET destined to On-premise ?&lt;/P&gt;
&lt;P&gt;(2) communication is sourced from On-premise destined to Azure VNET ?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We don't have a Virtual Network Gateway deployed instead we have a Cisco vMX SDWAN in Azure VNET that extend the connectivity to on-premise, so for on-premise communication we are routing all traffic (after firewall inspection) to Cisco vMX SDWAN which further forwards the traffic to on-premise.&lt;/P&gt;
&lt;P&gt;Currently all traffic between the Azure VNETs are routing through Azure ILB are working and no issues have been reported so far but traffic which sends outside to Azure for on-prem where we are observing asymmetric of routing causing drops on firewall intermittently specifically we observed issues for SNMP and UDP protocols so would like to understand whether this type of design supports by Palo Alto on Azure using Azure ILB&lt;/P&gt;</description>
      <pubDate>Fri, 11 Apr 2025 06:47:05 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/firewalls-in-active-active-using-azure-internal-load-balancer/m-p/1226318#M2363</guid>
      <dc:creator>SShaikh647896</dc:creator>
      <dc:date>2025-04-11T06:47:05Z</dc:date>
    </item>
    <item>
      <title>Re: Firewalls in Active Active using Azure Internal Load balancer</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/firewalls-in-active-active-using-azure-internal-load-balancer/m-p/1226723#M2365</link>
      <description>&lt;P&gt;For inbound traffic like a web server you need a source and destination NAT. The internal LB is bypassed. For traffic initiated outbound the default gateway needs to be the internal LB. Most likely you are having a NAT problem causing asymmetrical routing. It bit me.&lt;/P&gt;</description>
      <pubDate>Wed, 16 Apr 2025 14:58:15 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/firewalls-in-active-active-using-azure-internal-load-balancer/m-p/1226723#M2365</guid>
      <dc:creator>Carleton</dc:creator>
      <dc:date>2025-04-16T14:58:15Z</dc:date>
    </item>
  </channel>
</rss>

