<?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: topology in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/topology/m-p/141282#M48378</link>
    <description>&lt;P&gt;you could create portchannels so the ASA's can fail over all they want without interfering with the Palo Alto Networks Firewall Cluster&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="portchannel2.png"&gt;&lt;img src="https://live.paloaltonetworks.com/skins/images/2F2A72B3BE70ACC5EBC3E1D7685F5297/responsive_peak/images/image_not_found.png" alt="portchannel2.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;with this design and the PANW in AP, one member of the aggregate will always be down and simply switch if one of the PANW were to fail, if the ASA fails, the second Aggregate will kick in (controlled by the switch and ASA) and the active PANW can remain active&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 06 Feb 2017 14:06:25 GMT</pubDate>
    <dc:creator>reaper</dc:creator>
    <dc:date>2017-02-06T14:06:25Z</dc:date>
    <item>
      <title>topology</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/topology/m-p/139849#M48186</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have the below topology .&lt;/P&gt;&lt;P&gt;Planning to put &amp;nbsp;PA in vwire mode in betweent the asa and core in active standby.&lt;/P&gt;&lt;P&gt;If r1 fails and asa1 is active and asa2 is standby &amp;nbsp;,asa2 will become active .&lt;/P&gt;&lt;P&gt;. Lets say pa1 is active and pa2 is standby .&lt;/P&gt;&lt;P&gt;When asa changes active standby order ,is it possible pa changes the same order as asa do .&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Or what is the pros and cons in this design&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="PA.png" style="width: 353px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/7466iC0905A9EBC54E1CD/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="PA.png" alt="PA.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Sat, 28 Jan 2017 07:38:18 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/topology/m-p/139849#M48186</guid>
      <dc:creator>sib2017</dc:creator>
      <dc:date>2017-01-28T07:38:18Z</dc:date>
    </item>
    <item>
      <title>Re: topology</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/topology/m-p/139877#M48189</link>
      <description>&lt;P&gt;Hi,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;You can track the ASA-1 interfaces on PA-1, so when the ASA-1 failover it should shut down its interfaces connecting to PA-1 once the interfaces are down and you are tracking the Link monitoring in the PA-1. Then PA-1 will trigger the HA and if you have enabled the preempt on the PA-1 once the ASA-1 is back active the PA's will swap their roles.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 28 Jan 2017 12:37:16 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/topology/m-p/139877#M48189</guid>
      <dc:creator>Kashif.Kamal</dc:creator>
      <dc:date>2017-01-28T12:37:16Z</dc:date>
    </item>
    <item>
      <title>Re: topology</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/topology/m-p/141143#M48351</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Is there a good design &amp;nbsp;other than this&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Sun, 05 Feb 2017 08:48:51 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/topology/m-p/141143#M48351</guid>
      <dc:creator>sib2017</dc:creator>
      <dc:date>2017-02-05T08:48:51Z</dc:date>
    </item>
    <item>
      <title>Re: topology</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/topology/m-p/141274#M48374</link>
      <description>&lt;P&gt;Apart from totally removing the ASA's, monitoring the path/link from the Palo's to ASA is about as good as it gets. Whats the business case for having the ASA's? if your just doing layer 1-4 on the ASA its pointless them being there.&lt;/P&gt;</description>
      <pubDate>Mon, 06 Feb 2017 13:52:41 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/topology/m-p/141274#M48374</guid>
      <dc:creator>RichColeman</dc:creator>
      <dc:date>2017-02-06T13:52:41Z</dc:date>
    </item>
    <item>
      <title>Re: topology</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/topology/m-p/141282#M48378</link>
      <description>&lt;P&gt;you could create portchannels so the ASA's can fail over all they want without interfering with the Palo Alto Networks Firewall Cluster&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="portchannel2.png"&gt;&lt;img src="https://live.paloaltonetworks.com/skins/images/2F2A72B3BE70ACC5EBC3E1D7685F5297/responsive_peak/images/image_not_found.png" alt="portchannel2.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;with this design and the PANW in AP, one member of the aggregate will always be down and simply switch if one of the PANW were to fail, if the ASA fails, the second Aggregate will kick in (controlled by the switch and ASA) and the active PANW can remain active&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 06 Feb 2017 14:06:25 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/topology/m-p/141282#M48378</guid>
      <dc:creator>reaper</dc:creator>
      <dc:date>2017-02-06T14:06:25Z</dc:date>
    </item>
    <item>
      <title>Re: topology</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/topology/m-p/141364#M48401</link>
      <description>&lt;P&gt;I would follow the order that&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/7608"&gt;@reaper&lt;/a&gt;&amp;nbsp;laid out; that would give you true redundancy and you don't at any one point in time have a single point of failure on your firewalls. The way that you are describing would work fine, but the thing to keep in mind is that while you technicially have a backup, you are counting on that PAN to funciton during the outage. If you lose that PAN for some reason at the same time you lost the router your network sounds like it's still going to go down.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 06 Feb 2017 19:52:47 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/topology/m-p/141364#M48401</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2017-02-06T19:52:47Z</dc:date>
    </item>
    <item>
      <title>Re: topology</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/topology/m-p/142017#M48477</link>
      <description>&lt;P&gt;Another option in this scenario is to make the PA cluster Active/Active instead of Active/Passive. &amp;nbsp;This way no matter what combination of device failures occur on either side you still have a traffic path with the PA devices. &amp;nbsp;and you don't need to track anything for failures.&lt;/P&gt;</description>
      <pubDate>Wed, 08 Feb 2017 23:45:26 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/topology/m-p/142017#M48477</guid>
      <dc:creator>pulukas</dc:creator>
      <dc:date>2017-02-08T23:45:26Z</dc:date>
    </item>
    <item>
      <title>Re: topology</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/topology/m-p/142137#M48496</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You mean the port channel between core and asa ?&lt;/P&gt;&lt;P&gt;It means &amp;nbsp;one of the link will go through PA1 and another link PA2 ( eg: red)&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Thu, 09 Feb 2017 15:30:48 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/topology/m-p/142137#M48496</guid>
      <dc:creator>sib2017</dc:creator>
      <dc:date>2017-02-09T15:30:48Z</dc:date>
    </item>
    <item>
      <title>Re: topology</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/topology/m-p/142151#M48499</link>
      <description>&lt;P&gt;yes that's right, that way if ASA1 fails, PA1 does not need to fail: the portchannel will smply switch to the second link&lt;/P&gt;
&lt;P&gt;also if PA1 fails, ASA1 does not need to fail&lt;/P&gt;</description>
      <pubDate>Thu, 09 Feb 2017 16:25:35 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/topology/m-p/142151#M48499</guid>
      <dc:creator>reaper</dc:creator>
      <dc:date>2017-02-09T16:25:35Z</dc:date>
    </item>
  </channel>
</rss>

