<?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 PANW aws vm-series ipsec tunnel ip /30 Tunnel interface in VM-Series in the Public Cloud</title>
    <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/panw-aws-vm-series-ipsec-tunnel-ip-30-tunnel-interface/m-p/1228351#M2367</link>
    <description>&lt;P&gt;Question on aws vm series ipsec tunnel ip /30 Tunnel interface&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hello Livecommunity, how is it going? I hope it's going well&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have a doubt, thinking in vmseries on Amazon, where from the virtual stick arme several ipsec tunnels site to sire either onprem or towards on prem or not, thinking in the typical network /30 for what is the tunnel interface interfaces, there at the level of aws vpc should I create more overweight for each vpn, a AWS subnet for all Tunnel Interface VPN nets&amp;nbsp; ? For that communication to work or how is there the point because I get confused.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;On prem ipsec vpn ok /30 both ends cok correct ip and we already ping each other as usual that all good but in aws vmserie like that there the issue in the vpc I have to do subnet /30 for each tunnel I use like that, that is subnet in the vpc ?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;What about HA on different Az using secondary IP .... Has anyone had experience, comments or anything with this point ?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you in advance for your time, support and collaboration&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best regards&lt;/P&gt;</description>
    <pubDate>Wed, 07 May 2025 09:05:43 GMT</pubDate>
    <dc:creator>Metgatz</dc:creator>
    <dc:date>2025-05-07T09:05:43Z</dc:date>
    <item>
      <title>PANW aws vm-series ipsec tunnel ip /30 Tunnel interface</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/panw-aws-vm-series-ipsec-tunnel-ip-30-tunnel-interface/m-p/1228351#M2367</link>
      <description>&lt;P&gt;Question on aws vm series ipsec tunnel ip /30 Tunnel interface&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hello Livecommunity, how is it going? I hope it's going well&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have a doubt, thinking in vmseries on Amazon, where from the virtual stick arme several ipsec tunnels site to sire either onprem or towards on prem or not, thinking in the typical network /30 for what is the tunnel interface interfaces, there at the level of aws vpc should I create more overweight for each vpn, a AWS subnet for all Tunnel Interface VPN nets&amp;nbsp; ? For that communication to work or how is there the point because I get confused.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;On prem ipsec vpn ok /30 both ends cok correct ip and we already ping each other as usual that all good but in aws vmserie like that there the issue in the vpc I have to do subnet /30 for each tunnel I use like that, that is subnet in the vpc ?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;What about HA on different Az using secondary IP .... Has anyone had experience, comments or anything with this point ?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you in advance for your time, support and collaboration&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best regards&lt;/P&gt;</description>
      <pubDate>Wed, 07 May 2025 09:05:43 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/panw-aws-vm-series-ipsec-tunnel-ip-30-tunnel-interface/m-p/1228351#M2367</guid>
      <dc:creator>Metgatz</dc:creator>
      <dc:date>2025-05-07T09:05:43Z</dc:date>
    </item>
  </channel>
</rss>

