<?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 FMC API health policy, platform settings and group optimization in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/fmc-api-health-policy-platform-settings-and-group-optimization/m-p/5034777#M1109671</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am deploying over 900 FTD 1120 to Cisco CDO and cdFMC, doing the configuration of the device inside the cdFMC i am applying a health policy, platform settings and add the device to a device group.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;To my understanding of the API, you need to specify the total list of all devices that should have that policy at every api call. So when i need to add one device to the policy, i need to first get all devices inside a list and then send the total list to the FMC API, which can be a long and time consuming task as i come closer to the total amount of devices.&lt;/P&gt;
&lt;P&gt;In the beginning my config part of my python script took about 100 second, but now when i have around 200 FTD inside CDO the same config time is about 180 seconds&lt;/P&gt;
&lt;P&gt;Can anyone guide me to optimize that part?&lt;/P&gt;</description>
    <pubDate>Wed, 06 Mar 2024 07:35:01 GMT</pubDate>
    <dc:creator>NiclasAndersen</dc:creator>
    <dc:date>2024-03-06T07:35:01Z</dc:date>
    <item>
      <title>FMC API health policy, platform settings and group optimization</title>
      <link>https://community.cisco.com/t5/network-security/fmc-api-health-policy-platform-settings-and-group-optimization/m-p/5034777#M1109671</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am deploying over 900 FTD 1120 to Cisco CDO and cdFMC, doing the configuration of the device inside the cdFMC i am applying a health policy, platform settings and add the device to a device group.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;To my understanding of the API, you need to specify the total list of all devices that should have that policy at every api call. So when i need to add one device to the policy, i need to first get all devices inside a list and then send the total list to the FMC API, which can be a long and time consuming task as i come closer to the total amount of devices.&lt;/P&gt;
&lt;P&gt;In the beginning my config part of my python script took about 100 second, but now when i have around 200 FTD inside CDO the same config time is about 180 seconds&lt;/P&gt;
&lt;P&gt;Can anyone guide me to optimize that part?&lt;/P&gt;</description>
      <pubDate>Wed, 06 Mar 2024 07:35:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fmc-api-health-policy-platform-settings-and-group-optimization/m-p/5034777#M1109671</guid>
      <dc:creator>NiclasAndersen</dc:creator>
      <dc:date>2024-03-06T07:35:01Z</dc:date>
    </item>
    <item>
      <title>Re: FMC API health policy, platform settings and group optimization</title>
      <link>https://community.cisco.com/t5/network-security/fmc-api-health-policy-platform-settings-and-group-optimization/m-p/5052853#M1110522</link>
      <description>&lt;P&gt;Hi Niclas, So is the retrieval of the device list where you see the slowness? Can you pinpoint times per-api call to see which call is the culprit?&lt;/P&gt;
&lt;P&gt;Side note: If you are in CDO, you could get the device list from a CDO inventory endpoint, rather than from the FMC endpoint, which is quite fast, but I'm unsure on what attributes beyond name that the subsequent API call is requiring. Let me know and I can point you to that API.&lt;/P&gt;</description>
      <pubDate>Fri, 29 Mar 2024 15:30:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fmc-api-health-policy-platform-settings-and-group-optimization/m-p/5052853#M1110522</guid>
      <dc:creator>AHack210</dc:creator>
      <dc:date>2024-03-29T15:30:16Z</dc:date>
    </item>
    <item>
      <title>Re: FMC API health policy, platform settings and group optimization</title>
      <link>https://community.cisco.com/t5/network-security/fmc-api-health-policy-platform-settings-and-group-optimization/m-p/5054807#M1110567</link>
      <description>&lt;P&gt;It is both when i retrive the devices, and when i need to generate the total list that need to be sent to the api endpoint. I don't think the CDO api endpoint will give me the correct data, since i need the cdFMC device id in the list of devices in the api endpoint for healt policy, platform settings and device group.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;And as a side note, every time i configure 1 device with the health policy, all the other FTDs then need a new deployment for the updated list of devices in those policies&lt;/P&gt;</description>
      <pubDate>Tue, 02 Apr 2024 08:46:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fmc-api-health-policy-platform-settings-and-group-optimization/m-p/5054807#M1110567</guid>
      <dc:creator>NiclasAndersen</dc:creator>
      <dc:date>2024-04-02T08:46:25Z</dc:date>
    </item>
    <item>
      <title>Re: FMC API health policy, platform settings and group optimization</title>
      <link>https://community.cisco.com/t5/network-security/fmc-api-health-policy-platform-settings-and-group-optimization/m-p/5056503#M1110625</link>
      <description>&lt;P&gt;Hi Niclas,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks for the details. So the cdFMC ID will be static for the lifetime of the cdFMC, and that ID can be extracted from the CDO inventory I believe.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 04 Apr 2024 14:32:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fmc-api-health-policy-platform-settings-and-group-optimization/m-p/5056503#M1110625</guid>
      <dc:creator>AHack210</dc:creator>
      <dc:date>2024-04-04T14:32:13Z</dc:date>
    </item>
  </channel>
</rss>

