<?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: DIPP A/A Enviroment Floating IP in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/dipp-a-a-enviroment-floating-ip/m-p/142016#M48476</link>
    <description>&lt;P&gt;Hi Mate,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cool article at the link below talks about this.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also mentions some limitations with what you are trying to achieve.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Mainly 'You cannot configure NAT for a floating IP address that is bound to an active-primary firewall'&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;A href="https://www.paloaltonetworks.com/documentation/71/pan-os/pan-os/high-availability/use-case-configure-active-active-ha-with-floating-ip-address-bound-to-active-primary-firewall" target="_blank"&gt;https://www.paloaltonetworks.com/documentation/71/pan-os/pan-os/high-availability/use-case-configure-active-active-ha-with-floating-ip-address-bound-to-active-primary-firewall&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Best regards,&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Robert d&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 08 Feb 2017 23:40:05 GMT</pubDate>
    <dc:creator>DonohoeRobert</dc:creator>
    <dc:date>2017-02-08T23:40:05Z</dc:date>
    <item>
      <title>DIPP A/A Enviroment Floating IP</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/dipp-a-a-enviroment-floating-ip/m-p/141997#M48470</link>
      <description>&lt;P&gt;Hi Guys,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;we´ve an Active/active Cluster enviroment. For the normal Internetconnection we will use Source/Hide NAT (DIPP).&lt;/P&gt;&lt;P&gt;At the moment we will NAT on both firewalls the traffic through the interface IP. This works fine, the failover is&lt;/P&gt;&lt;P&gt;ok only one paket lost during failover. The proble is, that in the case of an failover the Users will access the webservers with an other IP-Adress. Now, the Users are using services which recognize that and they will clothe the session.&lt;/P&gt;&lt;P&gt;So, we decide us to use a floating IP for NAT. So far so good. We´ve configure two identical NAT policies and&lt;/P&gt;&lt;P&gt;bind onde to device 0 and one to device 1. In a normal situation it works and I can see the NAT policy on the firewall&lt;BR /&gt;if I make tshoot via CLI. But in a failover condition (I´ve reboot the primary device). The connection is broken and&lt;BR /&gt;I can´t see any NAT entry on the second firewall. What we´ve done wrong. I´ve found this config example in a PAN document.&lt;BR /&gt;Any other Idea, how we can realizied our main goal (one IP toe the outside)?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Just for information. On the inside network, we also use floating IP to access the firewall.&lt;/P&gt;&lt;P&gt;So all clients have only the floating IP as a default gateway.....&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I hope that someone have an idea.....&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;BR M&lt;/P&gt;</description>
      <pubDate>Wed, 08 Feb 2017 22:53:05 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/dipp-a-a-enviroment-floating-ip/m-p/141997#M48470</guid>
      <dc:creator>mschwab</dc:creator>
      <dc:date>2017-02-08T22:53:05Z</dc:date>
    </item>
    <item>
      <title>Re: DIPP A/A Enviroment Floating IP</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/dipp-a-a-enviroment-floating-ip/m-p/142016#M48476</link>
      <description>&lt;P&gt;Hi Mate,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cool article at the link below talks about this.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also mentions some limitations with what you are trying to achieve.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Mainly 'You cannot configure NAT for a floating IP address that is bound to an active-primary firewall'&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;A href="https://www.paloaltonetworks.com/documentation/71/pan-os/pan-os/high-availability/use-case-configure-active-active-ha-with-floating-ip-address-bound-to-active-primary-firewall" target="_blank"&gt;https://www.paloaltonetworks.com/documentation/71/pan-os/pan-os/high-availability/use-case-configure-active-active-ha-with-floating-ip-address-bound-to-active-primary-firewall&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Best regards,&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Robert d&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 08 Feb 2017 23:40:05 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/dipp-a-a-enviroment-floating-ip/m-p/142016#M48476</guid>
      <dc:creator>DonohoeRobert</dc:creator>
      <dc:date>2017-02-08T23:40:05Z</dc:date>
    </item>
    <item>
      <title>Re: DIPP A/A Enviroment Floating IP</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/dipp-a-a-enviroment-floating-ip/m-p/142133#M48494</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is there a specific reason you configured your cluster as Active/Active?&lt;/P&gt;
&lt;P&gt;There's only a few scenarios where A/A would be beneficial and these are when asymmetric traffic is expected or when dynamic routing needs active peers for fast failover&lt;/P&gt;
&lt;P&gt;if neither is the case, your config can be dramatically simplified at no cost of failover times and with increase in firewall throughput (as no portion of the resources need to be dedicated to the A/A communication between both peers)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;in A/P you can simply configure NAT rules that will travel along with the Active peer and all the interface IP addresses will also follow (gratuitous ARP)&lt;/P&gt;</description>
      <pubDate>Thu, 09 Feb 2017 14:35:09 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/dipp-a-a-enviroment-floating-ip/m-p/142133#M48494</guid>
      <dc:creator>reaper</dc:creator>
      <dc:date>2017-02-09T14:35:09Z</dc:date>
    </item>
    <item>
      <title>Re: DIPP A/A Enviroment Floating IP</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/dipp-a-a-enviroment-floating-ip/m-p/142219#M48503</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;we have special VPN´s for panorama connection and don´t use the MGMT Ports for that.&lt;/P&gt;&lt;P&gt;So, we can´t monitor the secondary firewall and have some more restrictions.&lt;/P&gt;&lt;P&gt;And of course, one of them is dynamic routing (OSPF) and VPN´s.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I know the article from the admin guide, but in this example, they use two floating&lt;BR /&gt;IP´s (one on every firewall), so we´ve the problem, that we use two different IP´s&lt;/P&gt;&lt;P&gt;when we go to outside.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;One other solution, what we´ve found in an other article, use two identicle NAT entries,&lt;/P&gt;&lt;P&gt;without a floating IP. The problem with that solution is the duplicate IP error on the WAN Network.....&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 09 Feb 2017 23:24:26 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/dipp-a-a-enviroment-floating-ip/m-p/142219#M48503</guid>
      <dc:creator>mschwab</dc:creator>
      <dc:date>2017-02-09T23:24:26Z</dc:date>
    </item>
  </channel>
</rss>

