<?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: Change FMC managed FTD Access Control Policy assignment via CLI in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/change-fmc-managed-ftd-access-control-policy-assignment-via-cli/m-p/4696968#M1093863</link>
    <description>&lt;P&gt;Hi, Marvin.&lt;/P&gt;&lt;P&gt;Will Cisco support FMC4500 to have multiple NICs / IPs to manage different FTDs? I am thinking to put an extra FMC NIC (eth1) to have an IP address in the same subnet as FTD's management interface, so this connection won't be lost and I can use FMC (eth1) to change ACP of the FTD when FMC eth0 is lost network connectivity. Thanks.&lt;/P&gt;&lt;P&gt;Leo&lt;/P&gt;</description>
    <pubDate>Fri, 30 Sep 2022 20:12:22 GMT</pubDate>
    <dc:creator>a12288</dc:creator>
    <dc:date>2022-09-30T20:12:22Z</dc:date>
    <item>
      <title>Change FMC managed FTD Access Control Policy assignment via CLI</title>
      <link>https://community.cisco.com/t5/network-security/change-fmc-managed-ftd-access-control-policy-assignment-via-cli/m-p/4693270#M1093647</link>
      <description>&lt;P&gt;We have a need to manually change FTD Access Control Policy assignment via CLI in the event of maintenance or outage. Our FTD is being managed by FMC however our FMC is not on out-of-bound network but rather hosted in the inside zone data plane.&lt;/P&gt;&lt;P&gt;We would need to SSH to FTD and switch FTD ACP to a permit any-any like ACP via CLI (while FMC is unreachable) in order to let&amp;nbsp; certain traffics passing though FTD, and switch back to production ACP afterwards. Is it possible? Thanks.&lt;/P&gt;&lt;P&gt;Leo&lt;/P&gt;</description>
      <pubDate>Sun, 25 Sep 2022 04:43:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/change-fmc-managed-ftd-access-control-policy-assignment-via-cli/m-p/4693270#M1093647</guid>
      <dc:creator>a12288</dc:creator>
      <dc:date>2022-09-25T04:43:27Z</dc:date>
    </item>
    <item>
      <title>Re: Change FMC managed FTD Access Control Policy assignment via CLI</title>
      <link>https://community.cisco.com/t5/network-security/change-fmc-managed-ftd-access-control-policy-assignment-via-cli/m-p/4693975#M1093672</link>
      <description>&lt;P&gt;As far as I know, what you are asking is not possible. On an FTD device that is registered to an FMC manager, only the managing FMC can change the ACP.&lt;/P&gt;</description>
      <pubDate>Mon, 26 Sep 2022 17:37:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/change-fmc-managed-ftd-access-control-policy-assignment-via-cli/m-p/4693975#M1093672</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2022-09-26T17:37:06Z</dc:date>
    </item>
    <item>
      <title>Re: Change FMC managed FTD Access Control Policy assignment via CLI</title>
      <link>https://community.cisco.com/t5/network-security/change-fmc-managed-ftd-access-control-policy-assignment-via-cli/m-p/4694845#M1093700</link>
      <description>&lt;P&gt;Since I am able to use LinaConfigTool to modify routing table so I am hoping there is something similar to modify ACP, in the event of&amp;nbsp; FTD lost access to FMC.&lt;/P&gt;</description>
      <pubDate>Tue, 27 Sep 2022 16:54:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/change-fmc-managed-ftd-access-control-policy-assignment-via-cli/m-p/4694845#M1093700</guid>
      <dc:creator>a12288</dc:creator>
      <dc:date>2022-09-27T16:54:01Z</dc:date>
    </item>
    <item>
      <title>Re: Change FMC managed FTD Access Control Policy assignment via CLI</title>
      <link>https://community.cisco.com/t5/network-security/change-fmc-managed-ftd-access-control-policy-assignment-via-cli/m-p/4695251#M1093721</link>
      <description>&lt;P&gt;There is a new feature in 7.2 that may help with your use case. It is as follows:&lt;/P&gt;
&lt;TABLE border="1" width="100%"&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD&gt;
&lt;P class="p"&gt;Auto rollback of a deployment that causes a loss of management connectivity.&lt;/P&gt;
&lt;/TD&gt;
&lt;TD&gt;
&lt;P class="p"&gt;You can now enable auto rollback of the configuration if a deployment causes the management connection between the management center and the threat defense to go down. Previously, you could only manually rollback a configuration using the &lt;SPAN class="ph synph"&gt;&lt;SPAN class="keyword kwd"&gt;configure policy rollback&lt;/SPAN&gt; &lt;/SPAN&gt; command.&lt;/P&gt;
&lt;P class="p"&gt;New/modified screens:&lt;/P&gt;
&lt;UL class="ul"&gt;
&lt;LI class="li"&gt;
&lt;P class="p"&gt;&lt;SPAN class="ph uicontrol"&gt;Devices &amp;gt; Device Management &amp;gt; Device &amp;gt; Deployment Settings&lt;/SPAN&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;LI class="li"&gt;
&lt;P class="p"&gt;&lt;SPAN class="ph uicontrol"&gt;Deploy &amp;gt; Advanced Deploy &amp;gt; Preview&lt;/SPAN&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;LI class="li"&gt;
&lt;P class="p"&gt;&lt;SPAN class="ph uicontrol"&gt;Deploy &amp;gt; Deployment History &amp;gt; Preview&lt;/SPAN&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;P class="p"&gt;For more information, see &lt;A class="xref" href="https://www.cisco.com/c/en/us/td/docs/security/secure-firewall/management-center/device-config/720/management-center-device-config-72/get-started-device-management.html" target="_blank" rel="noopener"&gt;Device Management&lt;/A&gt; in the device configuration guide.&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;</description>
      <pubDate>Wed, 28 Sep 2022 09:16:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/change-fmc-managed-ftd-access-control-policy-assignment-via-cli/m-p/4695251#M1093721</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2022-09-28T09:16:00Z</dc:date>
    </item>
    <item>
      <title>Re: Change FMC managed FTD Access Control Policy assignment via CLI</title>
      <link>https://community.cisco.com/t5/network-security/change-fmc-managed-ftd-access-control-policy-assignment-via-cli/m-p/4696968#M1093863</link>
      <description>&lt;P&gt;Hi, Marvin.&lt;/P&gt;&lt;P&gt;Will Cisco support FMC4500 to have multiple NICs / IPs to manage different FTDs? I am thinking to put an extra FMC NIC (eth1) to have an IP address in the same subnet as FTD's management interface, so this connection won't be lost and I can use FMC (eth1) to change ACP of the FTD when FMC eth0 is lost network connectivity. Thanks.&lt;/P&gt;&lt;P&gt;Leo&lt;/P&gt;</description>
      <pubDate>Fri, 30 Sep 2022 20:12:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/change-fmc-managed-ftd-access-control-policy-assignment-via-cli/m-p/4696968#M1093863</guid>
      <dc:creator>a12288</dc:creator>
      <dc:date>2022-09-30T20:12:22Z</dc:date>
    </item>
    <item>
      <title>Re: Change FMC managed FTD Access Control Policy assignment via CLI</title>
      <link>https://community.cisco.com/t5/network-security/change-fmc-managed-ftd-access-control-policy-assignment-via-cli/m-p/4697161#M1093878</link>
      <description>&lt;P&gt;You can (and always have been able to) use the second (or third etc.) NIC in an FMC to manage devices. It comes down to the routing for that NIC and managed devices. As long as that is working as desired in the underlying OS (Linux) then the FMC application will use the best route to reach the managed devices. You need to be sure to understand it from the device side as you add the manager by its IP address and that must be the same as the NIC of the FMC that will be used for that device.&lt;/P&gt;</description>
      <pubDate>Sun, 02 Oct 2022 03:08:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/change-fmc-managed-ftd-access-control-policy-assignment-via-cli/m-p/4697161#M1093878</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2022-10-02T03:08:59Z</dc:date>
    </item>
  </channel>
</rss>

