<?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 Feature Request - Prisma Access secondary tunnel AWS in Prisma Access Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/prisma-access-discussions/feature-request-prisma-access-secondary-tunnel-aws/m-p/304206#M43</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can I request that the devs urgently build the capability to use secondary tunnels to AWS when using dynamic routing (BGP).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is listed as a known issue but I'm not sure if it is on the roadmap for a future release:&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.paloaltonetworks.com/prisma/prisma-access/prisma-access-panorama-release-notes/prisma-access-about/prisma-access-known-issues.html" target="_blank"&gt;https://docs.paloaltonetworks.com/prisma/prisma-access/prisma-access-panorama-release-notes/prisma-access-about/prisma-access-known-issues.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;CYR-7814&amp;nbsp; -&amp;nbsp; Secondary tunnels are not supported with Prisma Access/AWS integrations that use dynamic (BGP) routing.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
    <pubDate>Wed, 18 Dec 2019 11:17:05 GMT</pubDate>
    <dc:creator>NathanielM</dc:creator>
    <dc:date>2019-12-18T11:17:05Z</dc:date>
    <item>
      <title>Feature Request - Prisma Access secondary tunnel AWS</title>
      <link>https://live.paloaltonetworks.com/t5/prisma-access-discussions/feature-request-prisma-access-secondary-tunnel-aws/m-p/304206#M43</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can I request that the devs urgently build the capability to use secondary tunnels to AWS when using dynamic routing (BGP).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is listed as a known issue but I'm not sure if it is on the roadmap for a future release:&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.paloaltonetworks.com/prisma/prisma-access/prisma-access-panorama-release-notes/prisma-access-about/prisma-access-known-issues.html" target="_blank"&gt;https://docs.paloaltonetworks.com/prisma/prisma-access/prisma-access-panorama-release-notes/prisma-access-about/prisma-access-known-issues.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;CYR-7814&amp;nbsp; -&amp;nbsp; Secondary tunnels are not supported with Prisma Access/AWS integrations that use dynamic (BGP) routing.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Wed, 18 Dec 2019 11:17:05 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/prisma-access-discussions/feature-request-prisma-access-secondary-tunnel-aws/m-p/304206#M43</guid>
      <dc:creator>NathanielM</dc:creator>
      <dc:date>2019-12-18T11:17:05Z</dc:date>
    </item>
    <item>
      <title>Re: Feature Request - Prisma Access secondary tunnel AWS</title>
      <link>https://live.paloaltonetworks.com/t5/prisma-access-discussions/feature-request-prisma-access-secondary-tunnel-aws/m-p/304223#M44</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/83793"&gt;@NathanielM&lt;/a&gt;&amp;nbsp;Thank you for sharing your interest. The best way that can help your feature request is to approach the Sales Engineer/Account Manager of your account from Palo Alto Networks. They can file a feature request and followup with product teams.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Please mark if you are satisfied with the solution. This closes the discussion and helps others to fastly identify the solutions&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 18 Dec 2019 13:30:07 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/prisma-access-discussions/feature-request-prisma-access-secondary-tunnel-aws/m-p/304223#M44</guid>
      <dc:creator>Sai_Tumuluri</dc:creator>
      <dc:date>2019-12-18T13:30:07Z</dc:date>
    </item>
    <item>
      <title>Re: Feature Request - Prisma Access secondary tunnel AWS</title>
      <link>https://live.paloaltonetworks.com/t5/prisma-access-discussions/feature-request-prisma-access-secondary-tunnel-aws/m-p/307733#M45</link>
      <description>&lt;P&gt;This issue now should be resolved by using our ECMP for Remote Networks feature. This allows up to 4 IPSEC/BGP tunnels to RN endpoints. See the documentation below for ECMP and other 1.5 Cloud Services plugin features:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://live.paloaltonetworks.com/t5/Blogs/NEW-Prisma-Access-1-5-Updates/ba-p/298139" target="_blank"&gt;https://live.paloaltonetworks.com/t5/Blogs/NEW-Prisma-Access-1-5-Updates/ba-p/298139&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 23 Jan 2020 20:08:01 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/prisma-access-discussions/feature-request-prisma-access-secondary-tunnel-aws/m-p/307733#M45</guid>
      <dc:creator>wprice</dc:creator>
      <dc:date>2020-01-23T20:08:01Z</dc:date>
    </item>
  </channel>
</rss>

