<?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: Pre-established BGP connection to HA? in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/pre-established-bgp-connection-to-ha/m-p/589721#M117524</link>
    <description>&lt;P&gt;Hi &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/208826"&gt;@jbraswell32&lt;/a&gt; ,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;With regard to A/P HA, BGP Graceful Restart (GR) is recommended for faster failover.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000CltgCAC" target="_blank"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000CltgCAC&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The GR feature is designed to keep the BGP neighbor from dropping and routes continuing to forward during the failover process.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Tom&lt;/P&gt;</description>
    <pubDate>Mon, 17 Jun 2024 18:23:11 GMT</pubDate>
    <dc:creator>TomYoung</dc:creator>
    <dc:date>2024-06-17T18:23:11Z</dc:date>
    <item>
      <title>Pre-established BGP connection to HA?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/pre-established-bgp-connection-to-ha/m-p/589710#M117523</link>
      <description>&lt;P&gt;All,&lt;BR /&gt;I'm looking to set up established BGP connections from the upstream routers (Cisco Nexus) to the HA unit in our A/P setup for faster failover times, and to not make it look weird when trying to determine if adjacencies are up to the primary unit from the router side. I know there's some things that can be established, LACP and the like, but don't see an option for BGP anywhere. Is there a way to do this, or is this not a good idea? What other optimizations should be run in A/P BGP setup to ensure a fast failover to the HA unit? I've seen mention of BFD but haven't tried this yet, I'm curious to see if that helps me out. To be clear, I haven't tested failover yet, so I don't know if this is an issue that I'm trying to solve before it's a problem. Thanks for the help, looking forward to some good answers!&lt;/P&gt;</description>
      <pubDate>Mon, 17 Jun 2024 15:11:46 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/pre-established-bgp-connection-to-ha/m-p/589710#M117523</guid>
      <dc:creator>jbraswell32</dc:creator>
      <dc:date>2024-06-17T15:11:46Z</dc:date>
    </item>
    <item>
      <title>Re: Pre-established BGP connection to HA?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/pre-established-bgp-connection-to-ha/m-p/589721#M117524</link>
      <description>&lt;P&gt;Hi &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/208826"&gt;@jbraswell32&lt;/a&gt; ,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;With regard to A/P HA, BGP Graceful Restart (GR) is recommended for faster failover.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000CltgCAC" target="_blank"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000CltgCAC&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The GR feature is designed to keep the BGP neighbor from dropping and routes continuing to forward during the failover process.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Tom&lt;/P&gt;</description>
      <pubDate>Mon, 17 Jun 2024 18:23:11 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/pre-established-bgp-connection-to-ha/m-p/589721#M117524</guid>
      <dc:creator>TomYoung</dc:creator>
      <dc:date>2024-06-17T18:23:11Z</dc:date>
    </item>
  </channel>
</rss>

