<?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: BGP Across Two Data Centers in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/bgp-across-two-data-centers/m-p/51696#M38023</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I think for this application you are going to need to be active/active.&amp;nbsp; In an active/passive setup the passive device interfaces are held in a down state until failover.&amp;nbsp; You cannot have that active BGP session going in this scenario.&amp;nbsp; The alternative is you peer to both ISP from the active device.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just to clarify your connectivity,&amp;nbsp; you will need layer 2 on HA 1 &amp;amp; HA2 for Active/passive and you would need to add a third vlan for HA3 if you have active/active.&amp;nbsp; Also note that these need to have jumbo frames and low latency.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 06 Jun 2015 12:47:17 GMT</pubDate>
    <dc:creator>pulukas</dc:creator>
    <dc:date>2015-06-06T12:47:17Z</dc:date>
    <item>
      <title>BGP Across Two Data Centers</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/bgp-across-two-data-centers/m-p/51695#M38022</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hey all, we have a customer who currently has two PA-2050 nodes setup with HA at one location.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;they would like to split the pair and have one PA-2050 at Site1 and the other at Site2 ... setup as Active/Standby.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There would be two private L2 networks between them - one for the HA/keepalive and the other to tie in the inside interfaces.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;each pa-2050 would have a "single" BGP connection to its own ISP, advertising the same block.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;site1 would only have bgp to isp1 and site2 would only have bgp to isp2&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;site1 would be preferred for both ingress/egress traffic, and site2 would be backup in case site1 fails.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;is this possible? so far, have read docs where both pa's have to be at the same location where they connect to both isp's.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks in advance!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 06 Jun 2015 01:04:45 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/bgp-across-two-data-centers/m-p/51695#M38022</guid>
      <dc:creator>RHO</dc:creator>
      <dc:date>2015-06-06T01:04:45Z</dc:date>
    </item>
    <item>
      <title>Re: BGP Across Two Data Centers</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/bgp-across-two-data-centers/m-p/51696#M38023</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I think for this application you are going to need to be active/active.&amp;nbsp; In an active/passive setup the passive device interfaces are held in a down state until failover.&amp;nbsp; You cannot have that active BGP session going in this scenario.&amp;nbsp; The alternative is you peer to both ISP from the active device.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just to clarify your connectivity,&amp;nbsp; you will need layer 2 on HA 1 &amp;amp; HA2 for Active/passive and you would need to add a third vlan for HA3 if you have active/active.&amp;nbsp; Also note that these need to have jumbo frames and low latency.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 06 Jun 2015 12:47:17 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/bgp-across-two-data-centers/m-p/51696#M38023</guid>
      <dc:creator>pulukas</dc:creator>
      <dc:date>2015-06-06T12:47:17Z</dc:date>
    </item>
  </channel>
</rss>

