<?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: AWS Availability Zones in VM-Series in the Public Cloud</title>
    <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/aws-availability-zones/m-p/298618#M711</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I was investigating this issue. my problem is that I need cross AZ .&amp;nbsp; VPN+NAT&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;AWS speaking, I could move the EIP of the Trust interface to an ENI on another AZ. And then, update the route tables pointing to the second ENI. This will be with some downtime, which is acceptable as this is based on AZ failure, the other system behind my nat need to recover as well.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;On paper, looks good. I'm wondering if there's a way to know with an external tool about the failure and initiate the failover process? and when the route is considered being down? no more ping? how about the WAN down and not the router?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
    <pubDate>Thu, 14 Nov 2019 18:24:33 GMT</pubDate>
    <dc:creator>nronica</dc:creator>
    <dc:date>2019-11-14T18:24:33Z</dc:date>
    <item>
      <title>AWS Availability Zones</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/aws-availability-zones/m-p/153672#M40</link>
      <description>&lt;P&gt;For background, here is the scenario:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Initially we were looking at a high availability setup with 2 VM appliances, however, there is a restriction to a single AZ in that approach because of how the “floating IP / ENI” works.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;However, this environment will span multiple AZ’s for redundancy and there is a published Palo Alto video on how they do this: &lt;A href="https://www.youtube.com/watch?time_continue=130&amp;amp;v=xiPZHzdNRmI" target="_blank"&gt;https://www.youtube.com/watch?time_continue=130&amp;amp;v=xiPZHzdNRmI&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I’m re-watching it again, but based on my setup of the initial PA devices here is what I think I’m seeing:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;It looks like the configuration is being sync’d not through native PA HA config sync features, but through the cloud formation (CF) template and scripting&lt;/LI&gt;&lt;LI&gt;It looks like they may be using CF to set the necessary AWS routing to support egress filtering&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I just want to confirm this is the case so we roughly have an understanding of how we’ll how to build this out.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;</description>
      <pubDate>Fri, 21 Apr 2017 18:18:27 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/aws-availability-zones/m-p/153672#M40</guid>
      <dc:creator>nrobison</dc:creator>
      <dc:date>2017-04-21T18:18:27Z</dc:date>
    </item>
    <item>
      <title>Re: AWS Availability Zones</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/aws-availability-zones/m-p/153675#M41</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You are correct, our PAN-OS stateful failover solution requires an interface move which cannot happen between subnets and subnets do not span AZs.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;For AZ redundancy, we recommend the load balancer sandwhich covered in the video you referenced. &amp;nbsp;It doesn't track state between AZs but AZ failure is very rare and session restablishment for web based applications is usually transparent for the user.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Make sure you are using the latest template for the auto scaling solution:&amp;nbsp;&lt;A href="https://github.com/PaloAltoNetworks/aws-elb-autoscaling/tree/master/Version-1.2" target="_blank"&gt;https://github.com/PaloAltoNetworks/aws-elb-autoscaling/tree/master/Version-1.2&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;HTH,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Warby&lt;/P&gt;</description>
      <pubDate>Fri, 21 Apr 2017 18:29:39 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/aws-availability-zones/m-p/153675#M41</guid>
      <dc:creator>Warby</dc:creator>
      <dc:date>2017-04-21T18:29:39Z</dc:date>
    </item>
    <item>
      <title>Re: AWS Availability Zones</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/aws-availability-zones/m-p/298618#M711</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I was investigating this issue. my problem is that I need cross AZ .&amp;nbsp; VPN+NAT&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;AWS speaking, I could move the EIP of the Trust interface to an ENI on another AZ. And then, update the route tables pointing to the second ENI. This will be with some downtime, which is acceptable as this is based on AZ failure, the other system behind my nat need to recover as well.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;On paper, looks good. I'm wondering if there's a way to know with an external tool about the failure and initiate the failover process? and when the route is considered being down? no more ping? how about the WAN down and not the router?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Thu, 14 Nov 2019 18:24:33 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/aws-availability-zones/m-p/298618#M711</guid>
      <dc:creator>nronica</dc:creator>
      <dc:date>2019-11-14T18:24:33Z</dc:date>
    </item>
    <item>
      <title>Re: AWS Availability Zones</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/aws-availability-zones/m-p/298641#M712</link>
      <description>&lt;P&gt;Please have a look at our reference architecture for AWS.&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.paloaltonetworks.com/resources/guides/intelligent-architectures-aws-reference-architecture" target="_blank"&gt;https://www.paloaltonetworks.com/resources/guides/intelligent-architectures-aws-reference-architecture&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have several approaches to Fault Tolerance, most recently including the Transit Gateway.&lt;/P&gt;</description>
      <pubDate>Thu, 14 Nov 2019 18:46:24 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/aws-availability-zones/m-p/298641#M712</guid>
      <dc:creator>jmeurer</dc:creator>
      <dc:date>2019-11-14T18:46:24Z</dc:date>
    </item>
  </channel>
</rss>

