<?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 The FirePOWER modules have no in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-5585-x-firepower-module-code-upgrade-process/m-p/2922009#M154384</link>
    <description>&lt;P&gt;The FirePOWER modules have no awareness of the clustering among the ASAs. When you upgrade a FirePOWER module it will by default nark that cluster member as not eligible to receive traffic until the module is back online.&lt;/P&gt;
&lt;P&gt;You can override that as of 9.5 by telling the ASAs not to monitor service modules. If you did so and had the sfr module set to "fail open" then your module upgrade impact would be minimized from a module perspective.&lt;/P&gt;
&lt;P&gt;However you would then not be availing yourself of the protection built into an ASA cluster. Some would argue that it's better to let a member unit "fail" during the module upgrade so that the cluster can operate as intended and let another member take up the load.&lt;/P&gt;</description>
    <pubDate>Tue, 03 May 2016 02:57:08 GMT</pubDate>
    <dc:creator>Marvin Rhoads</dc:creator>
    <dc:date>2016-05-03T02:57:08Z</dc:date>
    <item>
      <title>ASA 5585-x +Firepower Module code upgrade process</title>
      <link>https://community.cisco.com/t5/network-security/asa-5585-x-firepower-module-code-upgrade-process/m-p/2922007#M154382</link>
      <description>&lt;P&gt;Guys,&lt;/P&gt;
&lt;P&gt;anyone has Firewall 5585 running in cluster code upgrade process, i want same for the Cisco Firepower Module as well?&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;will this process at all&amp;nbsp;interrupt to the data traffic ?&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Prashant&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 07:40:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5585-x-firepower-module-code-upgrade-process/m-p/2922007#M154382</guid>
      <dc:creator>prashant dwivedi</dc:creator>
      <dc:date>2019-03-12T07:40:47Z</dc:date>
    </item>
    <item>
      <title>Hello Prashant-</title>
      <link>https://community.cisco.com/t5/network-security/asa-5585-x-firepower-module-code-upgrade-process/m-p/2922008#M154383</link>
      <description>&lt;P&gt;Hello Prashant-&lt;/P&gt;
&lt;P&gt;Please take a look at the following link that will walk you through the steps on how to perform "hitless' upgrade.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="http://www.cisco.com/c/en/us/td/docs/security/asa/asa93/upgrade/upgrade93.html#73685"&gt;http://www.cisco.com/c/en/us/td/docs/security/asa/asa93/upgrade/upgrade93.html#73685&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;I hope this helps!&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;Thank you for rating helpful posts!&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 02 May 2016 07:08:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5585-x-firepower-module-code-upgrade-process/m-p/2922008#M154383</guid>
      <dc:creator>nspasov</dc:creator>
      <dc:date>2016-05-02T07:08:01Z</dc:date>
    </item>
    <item>
      <title>The FirePOWER modules have no</title>
      <link>https://community.cisco.com/t5/network-security/asa-5585-x-firepower-module-code-upgrade-process/m-p/2922009#M154384</link>
      <description>&lt;P&gt;The FirePOWER modules have no awareness of the clustering among the ASAs. When you upgrade a FirePOWER module it will by default nark that cluster member as not eligible to receive traffic until the module is back online.&lt;/P&gt;
&lt;P&gt;You can override that as of 9.5 by telling the ASAs not to monitor service modules. If you did so and had the sfr module set to "fail open" then your module upgrade impact would be minimized from a module perspective.&lt;/P&gt;
&lt;P&gt;However you would then not be availing yourself of the protection built into an ASA cluster. Some would argue that it's better to let a member unit "fail" during the module upgrade so that the cluster can operate as intended and let another member take up the load.&lt;/P&gt;</description>
      <pubDate>Tue, 03 May 2016 02:57:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5585-x-firepower-module-code-upgrade-process/m-p/2922009#M154384</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2016-05-03T02:57:08Z</dc:date>
    </item>
  </channel>
</rss>

