<?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: FMC 1000 to HA FMC 1600: Upgrade Strategy &amp;amp; CUFA to ISE-PIC Mi in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/fmc-1000-to-ha-fmc-1600-upgrade-strategy-amp-cufa-to-ise-pic/m-p/5267914#M1119900</link>
    <description>&lt;P&gt;Dear&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/326046"&gt;@Marvin Rhoads&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;Thanks very much , What’s the update on the CFUA migration to ISE-PIC? When is it expected to be done?&lt;/P&gt;
&lt;P&gt;CFUA is already end-of-life and no longer supported.&lt;/P&gt;</description>
    <pubDate>Wed, 05 Mar 2025 18:29:50 GMT</pubDate>
    <dc:creator>GHOZLANE Haroun</dc:creator>
    <dc:date>2025-03-05T18:29:50Z</dc:date>
    <item>
      <title>FMC 1000 to HA FMC 1600: Upgrade Strategy &amp; CUFA to ISE-PIC Migration</title>
      <link>https://community.cisco.com/t5/network-security/fmc-1000-to-ha-fmc-1600-upgrade-strategy-amp-cufa-to-ise-pic/m-p/5267836#M1119896</link>
      <description>&lt;P data-start="109" data-end="126"&gt;Hi Dears,&lt;/P&gt;
&lt;P data-start="128" data-end="308"&gt;I’m currently managing a &lt;STRONG data-start="153" data-end="171"&gt;Cisco FMC 1000&lt;/STRONG&gt; running &lt;STRONG data-start="180" data-end="197"&gt;version 6.6.4&lt;/STRONG&gt;, which oversees &lt;STRONG data-start="214" data-end="254"&gt;6 Cisco Firepower 2110 firewalls&lt;/STRONG&gt; (also on &lt;STRONG data-start="264" data-end="273"&gt;6.6.4&lt;/STRONG&gt;) in an &lt;STRONG data-start="281" data-end="305"&gt;active-standby setup&lt;/STRONG&gt;.&lt;/P&gt;
&lt;P data-start="310" data-end="328"&gt;I’m planning to:&lt;/P&gt;
&lt;OL data-start="329" data-end="591"&gt;
&lt;LI data-start="329" data-end="436"&gt;&lt;STRONG data-start="332" data-end="365"&gt;Replace the existing FMC 1000&lt;/STRONG&gt; with &lt;STRONG data-start="371" data-end="387"&gt;two FMC 1600&lt;/STRONG&gt; in a &lt;STRONG data-start="393" data-end="433"&gt;high-availability (HA) configuration&lt;/STRONG&gt;.&lt;/LI&gt;
&lt;LI data-start="437" data-end="518"&gt;&lt;STRONG data-start="440" data-end="478"&gt;Upgrade both the FMC and firewalls&lt;/STRONG&gt; to the &lt;STRONG data-start="486" data-end="515"&gt;recommended version 7.4.2&lt;/STRONG&gt;.&lt;/LI&gt;
&lt;LI data-start="519" data-end="591"&gt;&lt;STRONG data-start="522" data-end="538"&gt;Replace CFUA&lt;/STRONG&gt; with &lt;STRONG data-start="544" data-end="561"&gt;Cisco ISE-PIC&lt;/STRONG&gt; for user identity services.&lt;/LI&gt;
&lt;/OL&gt;
&lt;P data-start="593" data-end="755"&gt;I’d appreciate any &lt;STRONG data-start="612" data-end="667"&gt;best practices, recommendations, or lessons learned&lt;/STRONG&gt; from those who have performed similar migrations. Specifically, I’d like guidance on:&lt;/P&gt;
&lt;UL data-start="756" data-end="954"&gt;
&lt;LI data-start="756" data-end="836"&gt;The &lt;STRONG data-start="762" data-end="784"&gt;smoothest approach&lt;/STRONG&gt; to setting up FMC HA while minimizing disruption.&lt;/LI&gt;
&lt;LI data-start="837" data-end="890"&gt;Best &lt;STRONG data-start="844" data-end="860"&gt;upgrade path&lt;/STRONG&gt; for the firewalls to 7.4.2.&lt;/LI&gt;
&lt;LI data-start="891" data-end="954"&gt;Considerations when transitioning from &lt;STRONG data-start="932" data-end="951"&gt;CUFA to ISE-PIC&lt;/STRONG&gt;.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;Thanks in advance for your support .&lt;/P&gt;</description>
      <pubDate>Wed, 05 Mar 2025 18:21:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fmc-1000-to-ha-fmc-1600-upgrade-strategy-amp-cufa-to-ise-pic/m-p/5267836#M1119896</guid>
      <dc:creator>GHOZLANE Haroun</dc:creator>
      <dc:date>2025-03-05T18:21:41Z</dc:date>
    </item>
    <item>
      <title>Re: FMC 1000 to HA FMC 1600: Upgrade Strategy &amp; CUFA to ISE-PIC Mi</title>
      <link>https://community.cisco.com/t5/network-security/fmc-1000-to-ha-fmc-1600-upgrade-strategy-amp-cufa-to-ise-pic/m-p/5267895#M1119897</link>
      <description>&lt;P&gt;Plot out a compatibility course following the information here: &lt;A href="https://www.cisco.com/c/en/us/td/docs/security/secure-firewall/compatibility/management-center-compatibility.html#id_37880" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/security/secure-firewall/compatibility/management-center-compatibility.html#id_37880&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Depending on what it shipped with, you may need to reimage the FMC 1600 since 6.6.4 devices can only be managed with FMC 7.2.x or lower.&lt;/P&gt;
&lt;P&gt;We would follow the FMC model migration guide detailed here: &lt;A href="https://www.cisco.com/c/en/us/td/docs/security/firepower/fmc_model_migration/b_FMC_Model_Migration_Guide/m_fmc_migration_workflow.html" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/security/firepower/fmc_model_migration/b_FMC_Model_Migration_Guide/m_fmc_migration_workflow.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;As always, we first upgrade FMC (subject to the compatibility matrix) and then managed devices.&lt;/P&gt;
&lt;P&gt;Your 6.6 devices would have to go to 7.2 first and then to 7.4.1. Finally, you can patch to 7.4.2.2 (current latest release for the 2110s).&lt;/P&gt;
&lt;P&gt;I would wait until the end to make your FMC HA as that will be quickest overall.&lt;/P&gt;
&lt;P&gt;Once FMC and the firewalls are upgraded, you can install and integrate ISE-PIC. Make sure it is getting good identity information before integrating it into FMC.&lt;/P&gt;</description>
      <pubDate>Wed, 05 Mar 2025 17:49:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fmc-1000-to-ha-fmc-1600-upgrade-strategy-amp-cufa-to-ise-pic/m-p/5267895#M1119897</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2025-03-05T17:49:30Z</dc:date>
    </item>
    <item>
      <title>Re: FMC 1000 to HA FMC 1600: Upgrade Strategy &amp; CUFA to ISE-PIC Mi</title>
      <link>https://community.cisco.com/t5/network-security/fmc-1000-to-ha-fmc-1600-upgrade-strategy-amp-cufa-to-ise-pic/m-p/5267914#M1119900</link>
      <description>&lt;P&gt;Dear&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/326046"&gt;@Marvin Rhoads&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;Thanks very much , What’s the update on the CFUA migration to ISE-PIC? When is it expected to be done?&lt;/P&gt;
&lt;P&gt;CFUA is already end-of-life and no longer supported.&lt;/P&gt;</description>
      <pubDate>Wed, 05 Mar 2025 18:29:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fmc-1000-to-ha-fmc-1600-upgrade-strategy-amp-cufa-to-ise-pic/m-p/5267914#M1119900</guid>
      <dc:creator>GHOZLANE Haroun</dc:creator>
      <dc:date>2025-03-05T18:29:50Z</dc:date>
    </item>
    <item>
      <title>Re: FMC 1000 to HA FMC 1600: Upgrade Strategy &amp; CUFA to ISE-PIC Mi</title>
      <link>https://community.cisco.com/t5/network-security/fmc-1000-to-ha-fmc-1600-upgrade-strategy-amp-cufa-to-ise-pic/m-p/5268084#M1119903</link>
      <description>&lt;P&gt;CFUA is not really a migration per se. The new version of FMC will not have any feature to enable CFUA. Instead, you just create a new integration for your ISE-PIC.&lt;/P&gt;
&lt;P&gt;It has no relation to anything that was setup in CFUA except for the fact that it does the same job - provide username to IP address mapping to FMC for visibility and (optionally) use in policy enforcement when integrated with an AD or LDAP realm.&lt;/P&gt;</description>
      <pubDate>Thu, 06 Mar 2025 06:49:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fmc-1000-to-ha-fmc-1600-upgrade-strategy-amp-cufa-to-ise-pic/m-p/5268084#M1119903</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2025-03-06T06:49:57Z</dc:date>
    </item>
  </channel>
</rss>

