<?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 interface failover on PA500 in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/interface-failover-on-pa500/m-p/7455#M5536</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Since link aggregation (LACP or etherchannel) is only supported on PA4000++ I want to build a simple interface-failover / interface-group setup (like any other enterprise firewall allows even on low-end devices).&lt;/P&gt;&lt;P&gt;group&lt;/P&gt;&lt;P&gt;To do this I would do the following:&lt;/P&gt;&lt;P&gt;1. change interface mode to Layer2 on both interfaces making up the interface-group&lt;/P&gt;&lt;P&gt;2. create a layer2 subinterface each (with same id and vlan tag)&lt;/P&gt;&lt;P&gt;3. associate both to the same vlan&lt;/P&gt;&lt;P&gt;4. enable L3 forwarding on the vlan&lt;/P&gt;&lt;P&gt;5. create an vlan interface and assign it the IP the firewall (on its interface-group) should have&lt;/P&gt;&lt;P&gt;6. connect each port to a different switch&lt;/P&gt;&lt;P&gt;7. enable STP (on switch)&lt;/P&gt;&lt;P&gt;8. cross fingers&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(with 2. only required when this is a trunk with multiple vlans)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It seems to work but is something like this supported?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 13 Jul 2012 20:16:19 GMT</pubDate>
    <dc:creator>ctr_ts</dc:creator>
    <dc:date>2012-07-13T20:16:19Z</dc:date>
    <item>
      <title>interface failover on PA500</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/interface-failover-on-pa500/m-p/7455#M5536</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Since link aggregation (LACP or etherchannel) is only supported on PA4000++ I want to build a simple interface-failover / interface-group setup (like any other enterprise firewall allows even on low-end devices).&lt;/P&gt;&lt;P&gt;group&lt;/P&gt;&lt;P&gt;To do this I would do the following:&lt;/P&gt;&lt;P&gt;1. change interface mode to Layer2 on both interfaces making up the interface-group&lt;/P&gt;&lt;P&gt;2. create a layer2 subinterface each (with same id and vlan tag)&lt;/P&gt;&lt;P&gt;3. associate both to the same vlan&lt;/P&gt;&lt;P&gt;4. enable L3 forwarding on the vlan&lt;/P&gt;&lt;P&gt;5. create an vlan interface and assign it the IP the firewall (on its interface-group) should have&lt;/P&gt;&lt;P&gt;6. connect each port to a different switch&lt;/P&gt;&lt;P&gt;7. enable STP (on switch)&lt;/P&gt;&lt;P&gt;8. cross fingers&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(with 2. only required when this is a trunk with multiple vlans)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It seems to work but is something like this supported?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 13 Jul 2012 20:16:19 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/interface-failover-on-pa500/m-p/7455#M5536</guid>
      <dc:creator>ctr_ts</dc:creator>
      <dc:date>2012-07-13T20:16:19Z</dc:date>
    </item>
    <item>
      <title>Re: interface failover on PA500</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/interface-failover-on-pa500/m-p/7456#M5537</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Had a quick chance to try this out in the lab.&amp;nbsp; Here's what I did:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.) Created new VLAN&lt;/P&gt;&lt;P&gt;2.) Created new VLAN interface (with L3-forwarding enabled)&lt;/P&gt;&lt;P&gt;3.) Placed new VLAN interface into appropriate security zone (L3-Trust in my configuration)&lt;/P&gt;&lt;P&gt;4.) Assigned new VLAN interface an IP Address (192.168.1.1/24 in my config)&lt;/P&gt;&lt;P&gt;5.) Configured 2 firewall ports as "Layer 2" and placed them into the newly created VLAN from step #1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Commit&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On the switch side, I created a vlan in a Brocade switch with 3 access ports.&amp;nbsp; I also enabled spanning-tree in this VLAN.&amp;nbsp; Of the 3 ports, 2 go to the firewall and one to a test laptop.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In this configuration, everything works fine!&amp;nbsp; It takes 30-45 seconds to fail over, and about 15s to fail back - which is expected for standard spanning-tree behavior. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I don't see why this wouldn't work using sub-interfaces and vlan tags as well.&amp;nbsp; Same concept.&amp;nbsp; Don't see why it wouldn't be supported either.&amp;nbsp; As long as you have some sort of loop prevention technology running, it's a perfectly valid network design.&amp;nbsp; It's not optimal, and you could probably get better failover and worry less about spanning-tree if you had a pair of firewalls using Active/Passive High Availability.&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 23 Jul 2012 22:40:32 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/interface-failover-on-pa500/m-p/7456#M5537</guid>
      <dc:creator>jvalentine</dc:creator>
      <dc:date>2012-07-23T22:40:32Z</dc:date>
    </item>
  </channel>
</rss>

