<?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: F5 failover connected behind PA in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/f5-failover-connected-behind-pa/m-p/264632#M74422</link>
    <description>&lt;P&gt;We have the same setup (using default arp cache timeouts) and we do not see this issue. everything fails over smoothly&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;p.s. to see your current arp cache timeout use: show arp all&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;it appears there is a bug with show system setting arp-cache-timeout (valid command seen here:&amp;nbsp;&lt;A href="https://docs.paloaltonetworks.com/pan-os/8-1/pan-os-new-features/networking-features/arp-cache-timeout" target="_blank"&gt;https://docs.paloaltonetworks.com/pan-os/8-1/pan-os-new-features/networking-features/arp-cache-timeout&lt;/A&gt;) because when I try that one I get an error but show arp all gives me the info&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 31 May 2019 20:32:57 GMT</pubDate>
    <dc:creator>hshawn</dc:creator>
    <dc:date>2019-05-31T20:32:57Z</dc:date>
    <item>
      <title>F5 failover connected behind PA</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/f5-failover-connected-behind-pa/m-p/264428#M74416</link>
      <description>&lt;P&gt;We have two F5 devices configured as active standby behind PA. The issue is on failover F5 failover ARP table on the PA is not updated quickly enough for smooth transition. Is there a way to mitigate this problem and increase ARP update time for that interface only.&lt;/P&gt;</description>
      <pubDate>Fri, 31 May 2019 16:59:00 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/f5-failover-connected-behind-pa/m-p/264428#M74416</guid>
      <dc:creator>raji_toor</dc:creator>
      <dc:date>2019-05-31T16:59:00Z</dc:date>
    </item>
    <item>
      <title>Re: F5 failover connected behind PA</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/f5-failover-connected-behind-pa/m-p/264618#M74420</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/56221"&gt;@raji_toor&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;From the CLI you can set the ARP cache timeout by issueing the command&amp;nbsp;&lt;EM&gt;set system setting arp-cache-timeout &amp;lt;value&amp;gt;&lt;/EM&gt; with the minimum being 60 seconds and the maximum being 65535 seconds. This of course is system wide and can't be adjusted for just one interface.&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you could script something to trigger when your F5 device logs a failover event, in a Slunk for example, you could utilize the API to clear the arp on the interface by issuing the&amp;nbsp;&lt;EM&gt;clear arp &amp;lt;interface&amp;gt;&amp;nbsp;&lt;/EM&gt;command via the API. &lt;EM&gt;/api/?type=op&amp;amp;cmd=&amp;lt;clear&amp;gt;&amp;lt;arp&amp;gt;interface&amp;lt;/arp&amp;lt;/clear&amp;gt;&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 31 May 2019 20:13:40 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/f5-failover-connected-behind-pa/m-p/264618#M74420</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2019-05-31T20:13:40Z</dc:date>
    </item>
    <item>
      <title>Re: F5 failover connected behind PA</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/f5-failover-connected-behind-pa/m-p/264632#M74422</link>
      <description>&lt;P&gt;We have the same setup (using default arp cache timeouts) and we do not see this issue. everything fails over smoothly&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;p.s. to see your current arp cache timeout use: show arp all&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;it appears there is a bug with show system setting arp-cache-timeout (valid command seen here:&amp;nbsp;&lt;A href="https://docs.paloaltonetworks.com/pan-os/8-1/pan-os-new-features/networking-features/arp-cache-timeout" target="_blank"&gt;https://docs.paloaltonetworks.com/pan-os/8-1/pan-os-new-features/networking-features/arp-cache-timeout&lt;/A&gt;) because when I try that one I get an error but show arp all gives me the info&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 31 May 2019 20:32:57 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/f5-failover-connected-behind-pa/m-p/264632#M74422</guid>
      <dc:creator>hshawn</dc:creator>
      <dc:date>2019-05-31T20:32:57Z</dc:date>
    </item>
    <item>
      <title>Re: F5 failover connected behind PA</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/f5-failover-connected-behind-pa/m-p/264695#M74424</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/42784"&gt;@hshawn&lt;/a&gt;&amp;nbsp;Do you use mac masquerading on F5&lt;/P&gt;</description>
      <pubDate>Fri, 31 May 2019 21:58:51 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/f5-failover-connected-behind-pa/m-p/264695#M74424</guid>
      <dc:creator>raji_toor</dc:creator>
      <dc:date>2019-05-31T21:58:51Z</dc:date>
    </item>
  </channel>
</rss>

