<?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: Policy commit failures due to profiles exceeding platform capacity using version 10.1.8-h2 in Next-Generation Firewall Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/policy-commit-failures-due-to-profiles-exceeding-platform/m-p/575206#M2549</link>
    <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/41084"&gt;@RandyQueen&lt;/a&gt;&amp;nbsp;- I would recommend you raise a TAC case for this issue; they may be able to advise why the change in behaviour post upgrade.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 01 Feb 2024 00:40:27 GMT</pubDate>
    <dc:creator>iarobertson</dc:creator>
    <dc:date>2024-02-01T00:40:27Z</dc:date>
    <item>
      <title>Policy commit failures due to profiles exceeding platform capacity using version 10.1.8-h2</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/policy-commit-failures-due-to-profiles-exceeding-platform/m-p/574759#M2532</link>
      <description>&lt;P&gt;We have not updated the number of profiles and have been successfully committing policy for probably a year with this same number of policies, but all of a sudden we are not able to commit policy pushes either from gui or cli.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We have gone through and deleted alot of shared profiles and are still getting the following error:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Error: Total number of profiles (792) exceeds platform capacity (750) (Module: device) client useridd phase 1 failure Commit failed.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We used shared objects and we have over 20 vsys on this firewall and have been told that these objects are shared across those vsys and that is why the max limit has been reached.&amp;nbsp; However, we don't know why this just started happening when it has been working with the same number of profiles for a long time.&lt;/P&gt;</description>
      <pubDate>Mon, 29 Jan 2024 16:26:27 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/policy-commit-failures-due-to-profiles-exceeding-platform/m-p/574759#M2532</guid>
      <dc:creator>RandyQueen</dc:creator>
      <dc:date>2024-01-29T16:26:27Z</dc:date>
    </item>
    <item>
      <title>Re: Policy commit failures due to profiles exceeding platform capacity using version 10.1.8-h2</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/policy-commit-failures-due-to-profiles-exceeding-platform/m-p/575206#M2549</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/41084"&gt;@RandyQueen&lt;/a&gt;&amp;nbsp;- I would recommend you raise a TAC case for this issue; they may be able to advise why the change in behaviour post upgrade.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 01 Feb 2024 00:40:27 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/policy-commit-failures-due-to-profiles-exceeding-platform/m-p/575206#M2549</guid>
      <dc:creator>iarobertson</dc:creator>
      <dc:date>2024-02-01T00:40:27Z</dc:date>
    </item>
  </channel>
</rss>

