<?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 Setup IPSEC Tunnels from Active/Standby pair to Active/Active Pair in AWS in VM-Series in the Public Cloud</title>
    <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/setup-ipsec-tunnels-from-active-standby-pair-to-active-active/m-p/272365#M626</link>
    <description>&lt;P&gt;So, we are in the process of creating a prescence in AWS. We are planning on using a pair of VM-300 series firewalls (jn Active/Active) in a Transit VPC. Our on prem firewall pair (in Active/Standby mode) will connect to the Transit VPC via IPSEC tunnels. The first tunnel will be over a DirectConnect (DX) connection, and the second tunnel will ride over the public internet (in case the DX connection fails). So basically, each firewall will have 2 IPSEC VPN tunnels going to AWS.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;While the Transit VPC IPSEC tunnels in Active/Active mode are fine to have different IPSEC tunnels going to them, I am wondering how this will work on the on prem firewalls being as though the tunnel only works on the Active firewall. What would be the best way to make this work?&lt;/P&gt;</description>
    <pubDate>Sat, 22 Jun 2019 00:52:04 GMT</pubDate>
    <dc:creator>Fr4nk4</dc:creator>
    <dc:date>2019-06-22T00:52:04Z</dc:date>
    <item>
      <title>Setup IPSEC Tunnels from Active/Standby pair to Active/Active Pair in AWS</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/setup-ipsec-tunnels-from-active-standby-pair-to-active-active/m-p/272365#M626</link>
      <description>&lt;P&gt;So, we are in the process of creating a prescence in AWS. We are planning on using a pair of VM-300 series firewalls (jn Active/Active) in a Transit VPC. Our on prem firewall pair (in Active/Standby mode) will connect to the Transit VPC via IPSEC tunnels. The first tunnel will be over a DirectConnect (DX) connection, and the second tunnel will ride over the public internet (in case the DX connection fails). So basically, each firewall will have 2 IPSEC VPN tunnels going to AWS.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;While the Transit VPC IPSEC tunnels in Active/Active mode are fine to have different IPSEC tunnels going to them, I am wondering how this will work on the on prem firewalls being as though the tunnel only works on the Active firewall. What would be the best way to make this work?&lt;/P&gt;</description>
      <pubDate>Sat, 22 Jun 2019 00:52:04 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/setup-ipsec-tunnels-from-active-standby-pair-to-active-active/m-p/272365#M626</guid>
      <dc:creator>Fr4nk4</dc:creator>
      <dc:date>2019-06-22T00:52:04Z</dc:date>
    </item>
    <item>
      <title>Re: Setup IPSEC Tunnels from Active/Standby pair to Active/Active Pair in AWS</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/setup-ipsec-tunnels-from-active-standby-pair-to-active-active/m-p/272427#M627</link>
      <description>&lt;P&gt;VM-series in the Public Cloud only supports Active/Passive High Availability.&lt;/P&gt;
&lt;P&gt;BGP for Transit VPC is configured in an Active/Standby mode.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I just wanted to clarify that before moving forward.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Also a key note. Transit VPC the VM-Series is not in an HA configuration. BGP is set to ACtive/Standby but the VM-Series are not HA.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 22 Jun 2019 20:09:44 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/setup-ipsec-tunnels-from-active-standby-pair-to-active-active/m-p/272427#M627</guid>
      <dc:creator>jperry1</dc:creator>
      <dc:date>2019-06-22T20:09:44Z</dc:date>
    </item>
  </channel>
</rss>

