<?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 GWLB AWS - HA what to do if both appliances go down? in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/gwlb-aws-ha-what-to-do-if-both-appliances-go-down/m-p/449846#M100983</link>
    <description>&lt;P&gt;We are deploying two PA on AWS using GWLB and we are wondering what would happen if for any reason both aplliances go down , since all traffic (inbound , outbound and inter-vpc) is going through the FWs , do you know a quick bypass or fail-open solution to this? I configured a couple of linux2 machines with hairpining nat so they can send the traffic back to the gwlb in case of failure , using a secondary target group with these "bypass machines" but i dont know if you have any other idea or better design?&lt;/P&gt;</description>
    <pubDate>Mon, 29 Nov 2021 05:48:16 GMT</pubDate>
    <dc:creator>Cgca1620</dc:creator>
    <dc:date>2021-11-29T05:48:16Z</dc:date>
    <item>
      <title>GWLB AWS - HA what to do if both appliances go down?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/gwlb-aws-ha-what-to-do-if-both-appliances-go-down/m-p/449846#M100983</link>
      <description>&lt;P&gt;We are deploying two PA on AWS using GWLB and we are wondering what would happen if for any reason both aplliances go down , since all traffic (inbound , outbound and inter-vpc) is going through the FWs , do you know a quick bypass or fail-open solution to this? I configured a couple of linux2 machines with hairpining nat so they can send the traffic back to the gwlb in case of failure , using a secondary target group with these "bypass machines" but i dont know if you have any other idea or better design?&lt;/P&gt;</description>
      <pubDate>Mon, 29 Nov 2021 05:48:16 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/gwlb-aws-ha-what-to-do-if-both-appliances-go-down/m-p/449846#M100983</guid>
      <dc:creator>Cgca1620</dc:creator>
      <dc:date>2021-11-29T05:48:16Z</dc:date>
    </item>
    <item>
      <title>Re: GWLB AWS - HA what to do if both appliances go down?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/gwlb-aws-ha-what-to-do-if-both-appliances-go-down/m-p/462043#M102220</link>
      <description>&lt;P&gt;The essential advantage with carrying out AWS Directory Service is that associations can now broaden AD characters and the board abilities to &lt;A href="https://sidney.instructure.com/courses/6873/pages/new-terminologies-in-aws-as-the-best-cloud-technology" target="_self"&gt;AWS&lt;/A&gt; assets. Without the AWS Directory Service, both AD and AWS would be siloed to their particular assets and would need to be overseen independently.&lt;/P&gt;</description>
      <pubDate>Mon, 31 Jan 2022 06:59:00 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/gwlb-aws-ha-what-to-do-if-both-appliances-go-down/m-p/462043#M102220</guid>
      <dc:creator>snahta</dc:creator>
      <dc:date>2022-01-31T06:59:00Z</dc:date>
    </item>
  </channel>
</rss>

