<?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: Best practices for HA PANs and switch stack in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/best-practices-for-ha-pans-and-switch-stack/m-p/17537#M12779</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So just to confirm.. in scenario 1, if switch 1 dies and firewall 1 is active.. no traffic flows to the internet unless link monitoring is enabled, correct?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 05 Sep 2014 12:23:23 GMT</pubDate>
    <dc:creator>SDorsey</dc:creator>
    <dc:date>2014-09-05T12:23:23Z</dc:date>
    <item>
      <title>Best practices for HA PANs and switch stack</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/best-practices-for-ha-pans-and-switch-stack/m-p/17535#M12777</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;For this scenario, assume a simple setup. Two firewalls in HA and two switches in a stack. Also assume the firewalls are in active/passive. Consider the below setup, each firewall has one physical link to separate switch members of the stack.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG alt="fw-ha.jpg" class="image-0 jive-image" src="https://live.paloaltonetworks.com/legacyfs/online/15327_fw-ha.jpg" style="height: auto;" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In this configuration, if switch member 1 fails and firewall 1 is the active firewall, does it automatically failover to firewall 2 if there is no link/path monitoring configured? Or are we to assume that without link/path monitoring, switch 1 failing and firewall 1 would remain active firewall and traffic to the internet would fail? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I typically always use the below configuration. Each switch has a port aggregate (802.3ad) and 1 connection in that LAG connects to each member switch. This utilizes double the ports but I was under the assumption the first scenario would only work with link/path monitoring. I also typically do the design so I can withstand any firewall failing AND any switch failing at the same time.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG alt="fw-ha2.jpg" class="image-1 jive-image" src="https://live.paloaltonetworks.com/legacyfs/online/15328_fw-ha2.jpg" style="height: auto;" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Finally, in the bottom configuration, does anyone have recommendation as far as setting up distribution configs on the switch side? (eg. mac src / dest). Are those needed? &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Sep 2014 03:24:57 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/best-practices-for-ha-pans-and-switch-stack/m-p/17535#M12777</guid>
      <dc:creator>SDorsey</dc:creator>
      <dc:date>2014-09-05T03:24:57Z</dc:date>
    </item>
    <item>
      <title>Re: Best practices for HA PANs and switch stack</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/best-practices-for-ha-pans-and-switch-stack/m-p/17536#M12778</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Mack,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Firewall1 will not trigger any failover if switch1 dies. Please refer following document.&lt;/P&gt;&lt;P&gt;&lt;A href="https://live.paloaltonetworks.com/docs/DOC-2288"&gt;HA active peer does not fail over when ethernet cable is pulled&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You have to configure link monitoring for scenario 1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Hardik Shah&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Sep 2014 06:30:26 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/best-practices-for-ha-pans-and-switch-stack/m-p/17536#M12778</guid>
      <dc:creator>hshah</dc:creator>
      <dc:date>2014-09-05T06:30:26Z</dc:date>
    </item>
    <item>
      <title>Re: Best practices for HA PANs and switch stack</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/best-practices-for-ha-pans-and-switch-stack/m-p/17537#M12779</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So just to confirm.. in scenario 1, if switch 1 dies and firewall 1 is active.. no traffic flows to the internet unless link monitoring is enabled, correct?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Sep 2014 12:23:23 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/best-practices-for-ha-pans-and-switch-stack/m-p/17537#M12779</guid>
      <dc:creator>SDorsey</dc:creator>
      <dc:date>2014-09-05T12:23:23Z</dc:date>
    </item>
    <item>
      <title>Re: Best practices for HA PANs and switch stack</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/best-practices-for-ha-pans-and-switch-stack/m-p/17538#M12780</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Mack,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It will follow bellow sequence of event.&lt;/P&gt;&lt;P&gt;1. Switch 1 dies&lt;/P&gt;&lt;P&gt;2. Which means port connected with Firewall1 dies.&lt;/P&gt;&lt;P&gt;3. Firewall will ignore the event because its not configured for link monitoring.&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;4. No Incoming traffic on Trust interface.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;7.However Untrust interface remains active, you can ping internet from Untrust.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;8. But Firewall1 remains active and rest of the interface remains active.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would suggest to configure link monitoring, its a intelligent deciwsion.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Hardik Shah&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Sep 2014 13:45:43 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/best-practices-for-ha-pans-and-switch-stack/m-p/17538#M12780</guid>
      <dc:creator>hshah</dc:creator>
      <dc:date>2014-09-05T13:45:43Z</dc:date>
    </item>
    <item>
      <title>Re: Best practices for HA PANs and switch stack</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/best-practices-for-ha-pans-and-switch-stack/m-p/17539#M12781</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you! And to 100% confirm, internal to external traffic will not flow because the secondary firewall remains in a passive state.. correct?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Sep 2014 13:53:42 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/best-practices-for-ha-pans-and-switch-stack/m-p/17539#M12781</guid>
      <dc:creator>SDorsey</dc:creator>
      <dc:date>2014-09-05T13:53:42Z</dc:date>
    </item>
    <item>
      <title>Re: Best practices for HA PANs and switch stack</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/best-practices-for-ha-pans-and-switch-stack/m-p/17540#M12782</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Mack,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I confirm 100% Internal to External Traffic will not flow, and secondary remains in passive state. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Hardik Shah&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Sep 2014 13:55:19 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/best-practices-for-ha-pans-and-switch-stack/m-p/17540#M12782</guid>
      <dc:creator>hshah</dc:creator>
      <dc:date>2014-09-05T13:55:19Z</dc:date>
    </item>
    <item>
      <title>Re: Best practices for HA PANs and switch stack</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/best-practices-for-ha-pans-and-switch-stack/m-p/17541#M12783</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you provide insight in regards to my question for scenario 2? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"&lt;SPAN style="color: #3b3b3b; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif;"&gt;Finally, in the bottom configuration, does anyone have recommendation as far as setting up distribution configs on the switch side? (eg. mac src / dest). Are those needed?"&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Sep 2014 13:57:15 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/best-practices-for-ha-pans-and-switch-stack/m-p/17541#M12783</guid>
      <dc:creator>SDorsey</dc:creator>
      <dc:date>2014-09-05T13:57:15Z</dc:date>
    </item>
    <item>
      <title>Re: Best practices for HA PANs and switch stack</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/best-practices-for-ha-pans-and-switch-stack/m-p/17542#M12784</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Mack,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ITs wise to configure interface monitoring, only in few circumstance people dont configure it. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do you have any reason for not to configure it?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Hardik Shah&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Sep 2014 13:57:38 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/best-practices-for-ha-pans-and-switch-stack/m-p/17542#M12784</guid>
      <dc:creator>hshah</dc:creator>
      <dc:date>2014-09-05T13:57:38Z</dc:date>
    </item>
    <item>
      <title>Re: Best practices for HA PANs and switch stack</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/best-practices-for-ha-pans-and-switch-stack/m-p/17543#M12785</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Mac,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Lets say you have implemented scenario 2, then cabling is good on Switch. You dont need any cabling changes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, Ports connected with Firewall remains in Access VLAN of Trust interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let me know if that answers your query.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Hardik Shah&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Sep 2014 14:02:07 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/best-practices-for-ha-pans-and-switch-stack/m-p/17543#M12785</guid>
      <dc:creator>hshah</dc:creator>
      <dc:date>2014-09-05T14:02:07Z</dc:date>
    </item>
    <item>
      <title>Re: Best practices for HA PANs and switch stack</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/best-practices-for-ha-pans-and-switch-stack/m-p/17544#M12786</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;And Inteface on the firewall should be aggregated interface in L3 Mode with an IP address.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Sep 2014 14:31:46 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/best-practices-for-ha-pans-and-switch-stack/m-p/17544#M12786</guid>
      <dc:creator>hshah</dc:creator>
      <dc:date>2014-09-05T14:31:46Z</dc:date>
    </item>
    <item>
      <title>Re: Best practices for HA PANs and switch stack</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/best-practices-for-ha-pans-and-switch-stack/m-p/17545#M12787</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks.. though my question is in relation to distribution algorithms for the 802.3ad channel.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Sep 2014 14:38:19 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/best-practices-for-ha-pans-and-switch-stack/m-p/17545#M12787</guid>
      <dc:creator>SDorsey</dc:creator>
      <dc:date>2014-09-05T14:38:19Z</dc:date>
    </item>
    <item>
      <title>Re: Best practices for HA PANs and switch stack</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/best-practices-for-ha-pans-and-switch-stack/m-p/17546#M12788</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Mac,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On the switch there is no Etherchannel, its an individual Ethernet Ports.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Aggregate interface exist on PANW Firewall. You can leave it to default as its outgoing traffic from firewall. It doesnt matter which switch recieves it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Hardik Shah&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Sep 2014 14:41:20 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/best-practices-for-ha-pans-and-switch-stack/m-p/17546#M12788</guid>
      <dc:creator>hshah</dc:creator>
      <dc:date>2014-09-05T14:41:20Z</dc:date>
    </item>
    <item>
      <title>Re: Best practices for HA PANs and switch stack</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/best-practices-for-ha-pans-and-switch-stack/m-p/17547#M12789</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So you're suggesting to have the aggregate on the firewall but have that aggregate connect to standard interfaces on the switch with no port-channeling configured? The switch doesn't have to be configured for an 802.3ad aggregation as well?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Sep 2014 14:43:33 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/best-practices-for-ha-pans-and-switch-stack/m-p/17547#M12789</guid>
      <dc:creator>SDorsey</dc:creator>
      <dc:date>2014-09-05T14:43:33Z</dc:date>
    </item>
    <item>
      <title>Re: Best practices for HA PANs and switch stack</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/best-practices-for-ha-pans-and-switch-stack/m-p/17548#M12790</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;That is right Mackwage, Firwewall in aggregate, and it goes to stand alone port of Switch. And it will work just fine.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let me know if my answer is Helpful.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Sep 2014 14:50:20 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/best-practices-for-ha-pans-and-switch-stack/m-p/17548#M12790</guid>
      <dc:creator>hshah</dc:creator>
      <dc:date>2014-09-05T14:50:20Z</dc:date>
    </item>
    <item>
      <title>Re: Best practices for HA PANs and switch stack</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/best-practices-for-ha-pans-and-switch-stack/m-p/17549#M12791</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Check out the full sample design in the Design Guide example 4.6 on page 80 and following.&amp;nbsp; I think this is the scenario for your setup.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://live.paloaltonetworks.com/docs/DOC-2561"&gt;Designing Networks with Palo Alto Networks Firewalls&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 06 Sep 2014 17:29:08 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/best-practices-for-ha-pans-and-switch-stack/m-p/17549#M12791</guid>
      <dc:creator>pulukas</dc:creator>
      <dc:date>2014-09-06T17:29:08Z</dc:date>
    </item>
  </channel>
</rss>

