<?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 All OSPF neighbors suddenly down in Next-Generation Firewall Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/all-ospf-neighbors-suddenly-down/m-p/521687#M593</link>
    <description>&lt;P&gt;Hello all,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Customer has a problem were their PaloAlto suddenly declares all neighbors adjacencies down, after that the PaloAlto will do a grateful restart and the OSPF neighbors will change to init, and then go full again, this OSPF flapping lasts 15 seconds or so so there is nearly no service impact at all, but customer would like to understand why is this happening and how to avoid it.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I think the problem is related to the PaloAlto because the OSPF adjacency is lost at the exact same time for all neighbors, even though half of the neighbors are in separate interfaces and separate virtual routers, with different OSPF configuration.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The problem has happened 3 times on the last month but the system logs only show declaring the neighbor down and the grateful restart afterwards. Is there any way to troubleshoot the issue after it happened? The routerd.log are no longer showings logs for that day...&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The FW is a PA-5050, with version 8.1.21&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you in advance,&lt;/P&gt;
&lt;P&gt;Jose&lt;/P&gt;&lt;BR /&gt;&lt;BR /&gt;Please note you are posting a public message where community members and experts can provide assistance. Sharing private information such as serial numbers or company information is not recommended.</description>
    <pubDate>Fri, 18 Nov 2022 13:18:29 GMT</pubDate>
    <dc:creator>JMBerzal</dc:creator>
    <dc:date>2022-11-18T13:18:29Z</dc:date>
    <item>
      <title>All OSPF neighbors suddenly down</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/all-ospf-neighbors-suddenly-down/m-p/521687#M593</link>
      <description>&lt;P&gt;Hello all,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Customer has a problem were their PaloAlto suddenly declares all neighbors adjacencies down, after that the PaloAlto will do a grateful restart and the OSPF neighbors will change to init, and then go full again, this OSPF flapping lasts 15 seconds or so so there is nearly no service impact at all, but customer would like to understand why is this happening and how to avoid it.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I think the problem is related to the PaloAlto because the OSPF adjacency is lost at the exact same time for all neighbors, even though half of the neighbors are in separate interfaces and separate virtual routers, with different OSPF configuration.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The problem has happened 3 times on the last month but the system logs only show declaring the neighbor down and the grateful restart afterwards. Is there any way to troubleshoot the issue after it happened? The routerd.log are no longer showings logs for that day...&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The FW is a PA-5050, with version 8.1.21&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you in advance,&lt;/P&gt;
&lt;P&gt;Jose&lt;/P&gt;&lt;BR /&gt;&lt;BR /&gt;Please note you are posting a public message where community members and experts can provide assistance. Sharing private information such as serial numbers or company information is not recommended.</description>
      <pubDate>Fri, 18 Nov 2022 13:18:29 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/all-ospf-neighbors-suddenly-down/m-p/521687#M593</guid>
      <dc:creator>JMBerzal</dc:creator>
      <dc:date>2022-11-18T13:18:29Z</dc:date>
    </item>
  </channel>
</rss>

