<?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: Taking longer time to commit on firewall from secondary panorama in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/taking-longer-time-to-commit-on-firewall-from-secondary-panorama/m-p/392146#M90863</link>
    <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/152936"&gt;@PankajDhobe&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;How far apart was the failover and the attempt to actually push configurations out? Did you attempt to do that shortly after the failover?&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 18 Mar 2021 16:26:52 GMT</pubDate>
    <dc:creator>BPry</dc:creator>
    <dc:date>2021-03-18T16:26:52Z</dc:date>
    <item>
      <title>Taking longer time to commit on firewall from secondary panorama</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/taking-longer-time-to-commit-on-firewall-from-secondary-panorama/m-p/392066#M90851</link>
      <description>&lt;UL&gt;&lt;LI&gt;As observed, when primary panorama was active, I have created an Test address object and committed and pushed from panorama. Configuration committed and pushed within 2 to 3 minutes.&lt;/LI&gt;&lt;LI&gt;After making secondary panorama as an active, configuration was committed after longer time period around 12 to 15 minutes.&lt;/LI&gt;&lt;LI&gt;As observed on both primary and secondary panorama, there was not any configuration difference between the two.&lt;/LI&gt;&lt;LI&gt;If anybody is well known about the issue. Please, let me know.&lt;/LI&gt;&lt;/UL&gt;</description>
      <pubDate>Thu, 18 Mar 2021 14:35:00 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/taking-longer-time-to-commit-on-firewall-from-secondary-panorama/m-p/392066#M90851</guid>
      <dc:creator>PankajDhobe</dc:creator>
      <dc:date>2021-03-18T14:35:00Z</dc:date>
    </item>
    <item>
      <title>Re: Taking longer time to commit on firewall from secondary panorama</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/taking-longer-time-to-commit-on-firewall-from-secondary-panorama/m-p/392146#M90863</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/152936"&gt;@PankajDhobe&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;How far apart was the failover and the attempt to actually push configurations out? Did you attempt to do that shortly after the failover?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 18 Mar 2021 16:26:52 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/taking-longer-time-to-commit-on-firewall-from-secondary-panorama/m-p/392146#M90863</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2021-03-18T16:26:52Z</dc:date>
    </item>
    <item>
      <title>Re: Taking longer time to commit on firewall from secondary panorama</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/taking-longer-time-to-commit-on-firewall-from-secondary-panorama/m-p/392238#M90880</link>
      <description>&lt;P&gt;Configuration commited successfully when secondary was active.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But while pushing configuration to the device group, it was taking longer time. Stuck&lt;SPAN&gt;&amp;nbsp;at 50% for few device group and for some, commit was showing at 0% for 4 to 5 minutes, after that percentage started increasing. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;So total duration to push is in between 10 to 15 minutes&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But when primary was active configuration was pushed within less time about 2 to 3 minutes.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If it is known issue, please let me share your suggestion.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 19 Mar 2021 04:34:38 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/taking-longer-time-to-commit-on-firewall-from-secondary-panorama/m-p/392238#M90880</guid>
      <dc:creator>PankajDhobe</dc:creator>
      <dc:date>2021-03-19T04:34:38Z</dc:date>
    </item>
    <item>
      <title>Re: Taking longer time to commit on firewall from secondary panorama</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/taking-longer-time-to-commit-on-firewall-from-secondary-panorama/m-p/392495#M90905</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/152936"&gt;@PankajDhobe&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;That's certainly not a known issue or expected behavior. It's possible that the system was already running a lot of jobs and simply couldn't queue these as quick as you are used to, but either way if you continue to see this behavior I would log a case with TAC so they can actually review logs. The system should behave exactly the same regardless of which node is active.&lt;/P&gt;</description>
      <pubDate>Sun, 21 Mar 2021 02:47:39 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/taking-longer-time-to-commit-on-firewall-from-secondary-panorama/m-p/392495#M90905</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2021-03-21T02:47:39Z</dc:date>
    </item>
    <item>
      <title>Re: Taking longer time to commit on firewall from secondary panorama</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/taking-longer-time-to-commit-on-firewall-from-secondary-panorama/m-p/392761#M90950</link>
      <description>&lt;P&gt;Just in case check this article&amp;nbsp; &lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000Cm1CCAS" target="_blank" rel="noopener"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000Cm1CCAS&lt;/A&gt; and CPU and memory of the secondary panorama before and when you coomit :&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClUbCAK" target="_blank" rel="noopener"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClUbCAK&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 22 Mar 2021 17:28:00 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/taking-longer-time-to-commit-on-firewall-from-secondary-panorama/m-p/392761#M90950</guid>
      <dc:creator>nikoolayy1</dc:creator>
      <dc:date>2021-03-22T17:28:00Z</dc:date>
    </item>
  </channel>
</rss>

