<?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: OSPF annomoly in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/ospf-annomoly/m-p/167452#M53473</link>
    <description>&lt;P&gt;'Aged out' sessions would be perfectly normal as many OSPF messages are not acknowledged (e.g. multicast hellos)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;0 byte sessions might be normal if you are logging on initiation.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We need more info.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 20 Jul 2017 12:41:20 GMT</pubDate>
    <dc:creator>9t89m8fu</dc:creator>
    <dc:date>2017-07-20T12:41:20Z</dc:date>
    <item>
      <title>OSPF annomoly</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ospf-annomoly/m-p/167097#M53424</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have OSPF setup on an interface and a policy that allows OSPF from any to any .&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But I see a lot of aged-out / unknown log entries and some are with 0 bytes&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;is this normal .. OSPF seems to be stable, but it very strange ..&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 19 Jul 2017 01:09:33 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ospf-annomoly/m-p/167097#M53424</guid>
      <dc:creator>Alex_Samad</dc:creator>
      <dc:date>2017-07-19T01:09:33Z</dc:date>
    </item>
    <item>
      <title>Re: OSPF annomoly</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ospf-annomoly/m-p/167452#M53473</link>
      <description>&lt;P&gt;'Aged out' sessions would be perfectly normal as many OSPF messages are not acknowledged (e.g. multicast hellos)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;0 byte sessions might be normal if you are logging on initiation.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We need more info.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 20 Jul 2017 12:41:20 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ospf-annomoly/m-p/167452#M53473</guid>
      <dc:creator>9t89m8fu</dc:creator>
      <dc:date>2017-07-20T12:41:20Z</dc:date>
    </item>
    <item>
      <title>Re: OSPF annomoly</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ospf-annomoly/m-p/168543#M53671</link>
      <description>&lt;P&gt;Sorry just logging on end of session.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Again I would have thought a next gen firewall with all of these extra capabilities ... that can actually do OSPF would understand when a session of OSPF had aged out. I don't see the VR dropping all its learned routes because it understands OSPF, I would have thought the fw component would to.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;A&lt;/P&gt;</description>
      <pubDate>Wed, 26 Jul 2017 22:48:27 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ospf-annomoly/m-p/168543#M53671</guid>
      <dc:creator>Alex_Samad</dc:creator>
      <dc:date>2017-07-26T22:48:27Z</dc:date>
    </item>
  </channel>
</rss>

