<?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: FirePOWER Module Installation in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/firepower-module-installation/m-p/3850273#M949895</link>
    <description>&lt;P&gt;Hi Magesh,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Yes that sounds at a high level a plan if you require constant inspection from Firepower during the upgrades.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sat, 04 May 2019 11:40:50 GMT</pubDate>
    <dc:creator>GRANT3779</dc:creator>
    <dc:date>2019-05-04T11:40:50Z</dc:date>
    <item>
      <title>FirePOWER Module Installation</title>
      <link>https://community.cisco.com/t5/network-security/firepower-module-installation/m-p/3848382#M949887</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have two ASA 5525-X Firewall in our Public Zone with Failover setup. Both ASAs running with SFR module version 5.4.0.2. Now we have planned to upgrade FirePOWER module version to 6.3.0. Since our FirePOWER module version is 5.4.0.2, Upgrading FirePOWER module through FirePOWER Management Center become more hectic. So we have planned to uninstall existing FirePOWER module 5.4.0.2 from ASA 5525-X and freshly Install FirePOWER module 6.3.0.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Our doubt is, when uninstalling FirePOWER module version 5.4.0.2 from ASA 5525-X, we&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;must reload ASA&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;or it is optional step?&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;In ASA, We configured SFR redirection policy to&amp;nbsp;permit traffic if SFR card fails (&lt;STRONG&gt;fail-open&lt;/STRONG&gt;), So Uninstalling existing SFR module will affect the traffic flow?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is their any cisco&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;guide&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;with an complete procedure to uninstall and reinstall SFR module in failover setup?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any other&lt;STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;constraints&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;we need to consider before doing SFR module uninstall and Install specially for failover setup?&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Also,&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Upgrading FirePOWER management center&lt;/STRONG&gt;, will affect FirePOWER Module devices?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Please help us...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 17:05:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-module-installation/m-p/3848382#M949887</guid>
      <dc:creator>Magesh Kumar</dc:creator>
      <dc:date>2020-02-21T17:05:46Z</dc:date>
    </item>
    <item>
      <title>Re: FirePOWER Module Installation</title>
      <link>https://community.cisco.com/t5/network-security/firepower-module-installation/m-p/3848593#M949888</link>
      <description>Hi Magesh,&lt;BR /&gt;&lt;BR /&gt;I completely understand in the decision to just uninstall and rebuild the module with the newer image. This is a lot easier/cleaner with the jump you are doing.&lt;BR /&gt;You do not need to reload the ASA at any point for this.&lt;BR /&gt;&lt;BR /&gt;With regards to the redirect policy for the SFR, I have took this out temporarily during this procedure.&lt;BR /&gt;&lt;BR /&gt;A gotcha that you should also look out for is the interfaces you are monitoring in your ASA Failover pair. If you are monitoring the SFR module then remember this will reboot a few times during the uninstall/install which in turn would cause your ASAs to failover. Disable monitoring of your SFR temporarily if you are doing so as part of the HA setup.&lt;BR /&gt;&lt;BR /&gt;For the FMC upgrade, be aware that it cannot manage any devices that run a higher code than itself so it may make sense to upgrade this first.&lt;BR /&gt;&lt;BR /&gt;reference for the complete upgrade/uninstall you are looking to do -&lt;BR /&gt;&lt;A href="https://www.cisco.com/c/en/us/support/docs/security/asa-firepower-services/118644-configure-firepower-00.html" target="_blank"&gt;https://www.cisco.com/c/en/us/support/docs/security/asa-firepower-services/118644-configure-firepower-00.html&lt;/A&gt;</description>
      <pubDate>Wed, 01 May 2019 16:25:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-module-installation/m-p/3848593#M949888</guid>
      <dc:creator>GRANT3779</dc:creator>
      <dc:date>2019-05-01T16:25:48Z</dc:date>
    </item>
    <item>
      <title>Re: FirePOWER Module Installation</title>
      <link>https://community.cisco.com/t5/network-security/firepower-module-installation/m-p/3848801#M949889</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/324869"&gt;@GRANT3779&lt;/a&gt;&amp;nbsp;- perfect - well said.&lt;/P&gt;</description>
      <pubDate>Thu, 02 May 2019 02:34:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-module-installation/m-p/3848801#M949889</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2019-05-02T02:34:29Z</dc:date>
    </item>
    <item>
      <title>Re: FirePOWER Module Installation</title>
      <link>https://community.cisco.com/t5/network-security/firepower-module-installation/m-p/3850226#M949890</link>
      <description>&lt;P&gt;Hi GRANT,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for your reply.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;With respect to uninstalling SFR module in fail-over setup, If we have sets ASA to block all the traffic when SFR fails (&lt;STRONG&gt;fail-close&lt;/STRONG&gt;), we should d&lt;/SPAN&gt;isable traffic redirection from the ASA to SFR module by removing SFR redirection policy?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If we need to do it, from where we can start? Whether In Active ASA or Standby ASA?&lt;/P&gt;&lt;P&gt;For example, If we removed SFR redirection policy in Active ASA, It will be replicated in Standby ASA. So overall all the traffic will by passes or avoids SFR module?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;With Regards,&lt;/P&gt;&lt;P&gt;Magesh Kumar.G&lt;/P&gt;</description>
      <pubDate>Sat, 04 May 2019 07:20:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-module-installation/m-p/3850226#M949890</guid>
      <dc:creator>Magesh Kumar</dc:creator>
      <dc:date>2019-05-04T07:20:25Z</dc:date>
    </item>
    <item>
      <title>Re: FirePOWER Module Installation</title>
      <link>https://community.cisco.com/t5/network-security/firepower-module-installation/m-p/3850240#M949891</link>
      <description>&lt;P&gt;Hi Magesh,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have always removed the class from the policy-map when doing this. E. G if you were using global policy (see below) you would go in there and remove the class below. I think in theory you could also amend the action to fail-open but i have always been more cautious and just removed the whole redirect. Another way i guess would be to just deny all traffic in your redirect acl so it doesn't go to SFR. If you do any of the above on the primary it will in turn apply to the secondary.&amp;nbsp; Just remember though that the actual SFRs are completely independent of each other and when rebuilding them, they will both need to be done.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;policy-map global_policy&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;&amp;nbsp;class inspection_default&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;&amp;nbsp; inspect dns preset_dns_map&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;&amp;nbsp; inspect ftp&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;&amp;nbsp; inspect h323 h225&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;&amp;nbsp; inspect h323 ras&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;&amp;nbsp; inspect rsh&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;&amp;nbsp; inspect rtsp&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;&amp;nbsp; inspect esmtp&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;&amp;nbsp; inspect sqlnet&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;&amp;nbsp; inspect skinny&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;&amp;nbsp; inspect sunrpc&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;&amp;nbsp; inspect xdmcp&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;&amp;nbsp; inspect sip&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;&amp;nbsp; inspect netbios&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;&amp;nbsp; inspect tftp&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;&amp;nbsp; inspect ip-options&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;&amp;nbsp; inspect icmp&lt;/EM&gt;&lt;BR /&gt;&lt;STRONG&gt;&lt;EM&gt;&amp;nbsp;class YOUR_SFR_REDIRECT&lt;/EM&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;EM&gt;&amp;nbsp;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;sfr fail-close&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 04 May 2019 08:15:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-module-installation/m-p/3850240#M949891</guid>
      <dc:creator>GRANT3779</dc:creator>
      <dc:date>2019-05-04T08:15:52Z</dc:date>
    </item>
    <item>
      <title>Re: FirePOWER Module Installation</title>
      <link>https://community.cisco.com/t5/network-security/firepower-module-installation/m-p/3850249#M949893</link>
      <description>&lt;P&gt;So you mean If we disable traffic redirection on ASA, all the traffic will bypass SFR module?&amp;nbsp; But we always need to send our traffic thorough SFR module.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Below I have briefly described my plan, please let me know if you found any lags...&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;We will plan to start our activity from secondary ASA (Standby). Will uninstall and install SFR module on secondary ASA (Standby). Since it is an Standby ASA, It will not affect the traffic flow?&lt;/LI&gt;&lt;LI&gt;After installed SFR module on secondary ASA, we will manually change state of secondary ASA from &lt;STRONG&gt;standby to active.&amp;nbsp;&lt;/STRONG&gt;Then will uninstall and install SFR on Primary ASA (stand by now).&lt;/LI&gt;&lt;LI&gt;During above activity, overall the traffic will go through SFR module without any interruption ?&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;With Regards,&lt;/P&gt;&lt;P&gt;Magesh Kumar.G&lt;/P&gt;</description>
      <pubDate>Sat, 04 May 2019 10:51:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-module-installation/m-p/3850249#M949893</guid>
      <dc:creator>Magesh Kumar</dc:creator>
      <dc:date>2019-05-04T10:51:44Z</dc:date>
    </item>
    <item>
      <title>Re: FirePOWER Module Installation</title>
      <link>https://community.cisco.com/t5/network-security/firepower-module-installation/m-p/3850273#M949895</link>
      <description>&lt;P&gt;Hi Magesh,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Yes that sounds at a high level a plan if you require constant inspection from Firepower during the upgrades.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 04 May 2019 11:40:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-module-installation/m-p/3850273#M949895</guid>
      <dc:creator>GRANT3779</dc:creator>
      <dc:date>2019-05-04T11:40:50Z</dc:date>
    </item>
  </channel>
</rss>

