<?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 Planes in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/planes/m-p/28630#M20886</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Is there a matrix or list of items that describes each of the plane functions? I know there is a management &amp;amp; data plane on the Palo but I'm not sure where to place the 'control' functions such as routing updates or switching path information and caching.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example, if you restart the mgmt plane, will this trigger HA failover? I am guessing (because I don't know) that the failover would take place. Because if the interface receives a heartbeat, the heartbeat 'ping' would be destined for the device itself and need to be processed by the route processor which resides in the mgmt plane, right? The fact that there is a separation of mgmt and data plane implies a table that is created from the control/mgmt plane to switch packets like a graceful restart when the managment plane is restarted. Is this the case?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm aware of the single pass architecture but does the network processor on the data plane process packets destined for the device itself?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If anyone could provide a listing of such things that would be greatly appreciated!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 11 Apr 2013 20:55:43 GMT</pubDate>
    <dc:creator>das</dc:creator>
    <dc:date>2013-04-11T20:55:43Z</dc:date>
    <item>
      <title>Planes</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/planes/m-p/28630#M20886</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Is there a matrix or list of items that describes each of the plane functions? I know there is a management &amp;amp; data plane on the Palo but I'm not sure where to place the 'control' functions such as routing updates or switching path information and caching.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example, if you restart the mgmt plane, will this trigger HA failover? I am guessing (because I don't know) that the failover would take place. Because if the interface receives a heartbeat, the heartbeat 'ping' would be destined for the device itself and need to be processed by the route processor which resides in the mgmt plane, right? The fact that there is a separation of mgmt and data plane implies a table that is created from the control/mgmt plane to switch packets like a graceful restart when the managment plane is restarted. Is this the case?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm aware of the single pass architecture but does the network processor on the data plane process packets destined for the device itself?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If anyone could provide a listing of such things that would be greatly appreciated!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Apr 2013 20:55:43 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/planes/m-p/28630#M20886</guid>
      <dc:creator>das</dc:creator>
      <dc:date>2013-04-11T20:55:43Z</dc:date>
    </item>
    <item>
      <title>Re: Planes</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/planes/m-p/28631#M20887</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hopefully someone from PA will see this thread and create such document? &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Closest to your request today is:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A __default_attr="1628" __jive_macro_name="document" class="jive_macro jive_macro_document" href="https://live.paloaltonetworks.com/"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;(look at page 4)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;along with&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://media.paloaltonetworks.com/documents/techbrief-app-id.pdf" title="http://media.paloaltonetworks.com/documents/techbrief-app-id.pdf"&gt;http://media.paloaltonetworks.com/documents/techbrief-app-id.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;and&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="active_link" href="http://media.paloaltonetworks.com/documents/techbrief-content-id.pdf" title="http://media.paloaltonetworks.com/documents/techbrief-content-id.pdf"&gt;http://media.paloaltonetworks.com/documents/techbrief-content-id.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;but these docs are more into the flow of a packet and not necessary the architecture of the hardware (regarding dependencies).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There are also some slides in the PAN-EDU-301 course which somewhat shows what happens where but still not on the level as your example.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Even if PA has one mgmtplane and one dataplane (well sometimes several DP's) there are still dependencies between them. For example if you use url-categories and the url doesnt already exist in the DP cache then a request is made towards mgmtplane which will perform the lookup if im not mistaken. Same goes with userid-stuff. Which gives that during a reboot of the mgmtplane, even if dataplane is separate, then new sessions (during the time the mgmtplane is rebooting) might be blocked depending on how your rules are setup (like if they use userid and/or url-filtering and the item doesnt already exist in the DP cache).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 12 Apr 2013 03:58:50 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/planes/m-p/28631#M20887</guid>
      <dc:creator>mikand</dc:creator>
      <dc:date>2013-04-12T03:58:50Z</dc:date>
    </item>
  </channel>
</rss>

