<?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: Link types for HA in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/link-types-for-ha/m-p/126138#M46498</link>
    <description>&lt;P&gt;There are no real limitations, other than the L2 (L3) connectivity.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I do the same with my 3020s and 5060s.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have two datacenters that are geographically seprarated by OTV on Nexus 7ks. &amp;nbsp;HA1/HA2 only utilize a flat L2 VLAN across &amp;nbsp;a P2P link. &amp;nbsp;That link has around 7ms latency. &amp;nbsp;We also leverage a "heart-beat backup" so that leverages a L3 connection.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It's really just going to depend upon the configuration of your HA paramaters...Your ping response times, and Hold down timers on your HA interfaces.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If the latency across the MPLS links exceed what you've set for the HA values it's not going to work.&lt;/P&gt;</description>
    <pubDate>Mon, 14 Nov 2016 14:29:09 GMT</pubDate>
    <dc:creator>Brandon_Wertz</dc:creator>
    <dc:date>2016-11-14T14:29:09Z</dc:date>
    <item>
      <title>Link types for HA</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/link-types-for-ha/m-p/125898#M46467</link>
      <description>&lt;P&gt;I have a client who wants to split their PA3020 HA cluster between 2 datacenters. &amp;nbsp; What are the limitations for the HA1/HA2 interfaces in terms of distance, and network latency for active/passive HA to work cleanly. &amp;nbsp;On a 3020 can HA1/HA2 functionality be forced through an in-band interface? (not desireable,) The customer prefers a single router uplink and all traffic flowing into (L3) MPLS across to the other datacenter.&lt;/P&gt;</description>
      <pubDate>Fri, 11 Nov 2016 19:40:36 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/link-types-for-ha/m-p/125898#M46467</guid>
      <dc:creator>rswart</dc:creator>
      <dc:date>2016-11-11T19:40:36Z</dc:date>
    </item>
    <item>
      <title>Re: Link types for HA</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/link-types-for-ha/m-p/126138#M46498</link>
      <description>&lt;P&gt;There are no real limitations, other than the L2 (L3) connectivity.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I do the same with my 3020s and 5060s.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have two datacenters that are geographically seprarated by OTV on Nexus 7ks. &amp;nbsp;HA1/HA2 only utilize a flat L2 VLAN across &amp;nbsp;a P2P link. &amp;nbsp;That link has around 7ms latency. &amp;nbsp;We also leverage a "heart-beat backup" so that leverages a L3 connection.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It's really just going to depend upon the configuration of your HA paramaters...Your ping response times, and Hold down timers on your HA interfaces.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If the latency across the MPLS links exceed what you've set for the HA values it's not going to work.&lt;/P&gt;</description>
      <pubDate>Mon, 14 Nov 2016 14:29:09 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/link-types-for-ha/m-p/126138#M46498</guid>
      <dc:creator>Brandon_Wertz</dc:creator>
      <dc:date>2016-11-14T14:29:09Z</dc:date>
    </item>
  </channel>
</rss>

