<?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: Palo Alto OSPF neighbor confusion in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/palo-alto-ospf-neighbor-confusion/m-p/333532#M84220</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/107877"&gt;@stevenjwilliams83&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Did the metrics stuff that&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/27580"&gt;@OtakarKlier&lt;/a&gt;&amp;nbsp;advised work for you? My issue is slightly different but more like yours. Even after increasing the ospf priority of the ae interface on the Palo Alto (PA) firewall facing 2 L3 switches, the PA firewall still didn't win the DR election, and its priority is higher than that of the interfaces on connecting switches facing it.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 15 Jun 2020 20:56:39 GMT</pubDate>
    <dc:creator>David_Ibrahim</dc:creator>
    <dc:date>2020-06-15T20:56:39Z</dc:date>
    <item>
      <title>Palo Alto OSPF neighbor confusion</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/palo-alto-ospf-neighbor-confusion/m-p/252216#M71711</link>
      <description>&lt;P&gt;I have two down stream layer 3 switches both active running HSRP connecting to the active palo alto. Switch 1s interface connecting to the palo alto is set to ospf priority 10, switch 2s interface facing the palo alto is set to ospf priority 5. For some reason the palo alto is choosing switch 2 for the next hop.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Does Palo Alto not understand priority or something? I mean switch 2 would win based on router ID being higher, but priority of that interface on switch 2 facing the PA is lower.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 04 Mar 2019 20:57:39 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/palo-alto-ospf-neighbor-confusion/m-p/252216#M71711</guid>
      <dc:creator>stevenjwilliams83</dc:creator>
      <dc:date>2019-03-04T20:57:39Z</dc:date>
    </item>
    <item>
      <title>Re: Palo Alto OSPF neighbor confusion</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/palo-alto-ospf-neighbor-confusion/m-p/252250#M71716</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;The priority is just to determine who is Dr and BDR.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;TABLE border="0" cellspacing="0" cellpadding="0"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;&lt;DIV class="List_1_inner"&gt;&lt;SPAN class="uicontrol"&gt;Priority&lt;/SPAN&gt;—Enter the OSPF priority for this interface (0-255). It is the priority for the router to be elected as a designated router (DR) or as a backup DR (BDR) according to the OSPF protocol. When the value is zero, the router will not be elected as a DR or BDR.&lt;/DIV&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For this I would say use Metrics instead. They are the values that add weight to a particulat path. For instance I have P2P links with VPN backup. I wnat them to use P2P links first so I have their metrics set lower. For VPN set the metric to say 20000 and the P2P leave it alone.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope that makes sense.&lt;/P&gt;</description>
      <pubDate>Mon, 04 Mar 2019 22:00:43 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/palo-alto-ospf-neighbor-confusion/m-p/252250#M71716</guid>
      <dc:creator>OtakarKlier</dc:creator>
      <dc:date>2019-03-04T22:00:43Z</dc:date>
    </item>
    <item>
      <title>Re: Palo Alto OSPF neighbor confusion</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/palo-alto-ospf-neighbor-confusion/m-p/333532#M84220</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/107877"&gt;@stevenjwilliams83&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Did the metrics stuff that&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/27580"&gt;@OtakarKlier&lt;/a&gt;&amp;nbsp;advised work for you? My issue is slightly different but more like yours. Even after increasing the ospf priority of the ae interface on the Palo Alto (PA) firewall facing 2 L3 switches, the PA firewall still didn't win the DR election, and its priority is higher than that of the interfaces on connecting switches facing it.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 15 Jun 2020 20:56:39 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/palo-alto-ospf-neighbor-confusion/m-p/333532#M84220</guid>
      <dc:creator>David_Ibrahim</dc:creator>
      <dc:date>2020-06-15T20:56:39Z</dc:date>
    </item>
  </channel>
</rss>

