<?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: Panorama 4.0.5 Pushing Policy to 3.1.9 in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/panorama-4-0-5-pushing-policy-to-3-1-9/m-p/18730#M13650</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We are aware of Panorama 4.0.5 not able to commit to 3.1.x devices. As you mention, workaround is to downgrade Panorama to 4.0.4. Fix should be in upcoming Panorama version 4.0.6. Note that we do not have an issue with Panorama 4.0.5 commiting to 4.0.x PAN devices. So if all your PA devices are on 4.0.x then you should not have a commit issue with Panorama 4.0.5.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Richard&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 01 Oct 2011 16:25:21 GMT</pubDate>
    <dc:creator>Retired Member</dc:creator>
    <dc:date>2011-10-01T16:25:21Z</dc:date>
    <item>
      <title>Panorama 4.0.5 Pushing Policy to 3.1.9</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/panorama-4-0-5-pushing-policy-to-3-1-9/m-p/18729#M13649</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN&gt;Confirmed with support that if Panorama is running 4.0.5 and a managed device is 3.1.9 policy will not Push to the remote device from Panorama.&amp;nbsp; The workaround would be to downgrade Panorama to 4.0.4 which requires reboot and reindexing or upgrade remote device to 4.0.x&amp;nbsp; As per the recent discussions of the data plan resets of the latter version. (See &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="https://live.paloaltonetworks.com/message/9264#9264"&gt;https://live.paloaltonetworks.com/message/9264#9264&lt;/A&gt;&lt;SPAN&gt;) perhaps its best to wait until they fix it on 4.0.6.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 30 Sep 2011 17:56:06 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/panorama-4-0-5-pushing-policy-to-3-1-9/m-p/18729#M13649</guid>
      <dc:creator>opiedrah</dc:creator>
      <dc:date>2011-09-30T17:56:06Z</dc:date>
    </item>
    <item>
      <title>Re: Panorama 4.0.5 Pushing Policy to 3.1.9</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/panorama-4-0-5-pushing-policy-to-3-1-9/m-p/18730#M13650</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We are aware of Panorama 4.0.5 not able to commit to 3.1.x devices. As you mention, workaround is to downgrade Panorama to 4.0.4. Fix should be in upcoming Panorama version 4.0.6. Note that we do not have an issue with Panorama 4.0.5 commiting to 4.0.x PAN devices. So if all your PA devices are on 4.0.x then you should not have a commit issue with Panorama 4.0.5.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Richard&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 01 Oct 2011 16:25:21 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/panorama-4-0-5-pushing-policy-to-3-1-9/m-p/18730#M13650</guid>
      <dc:creator>Retired Member</dc:creator>
      <dc:date>2011-10-01T16:25:21Z</dc:date>
    </item>
  </channel>
</rss>

