<?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: ASA FirePOWER module down in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-firepower-module-down/m-p/4662169#M1092340</link>
    <description>&lt;P&gt;Thank you&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;I shall failover ASA first, then once the new standby (former primary/active) is in "standby-ready" i'll reload the module, and maybe ASA if needed. Then discuss with my senior why the monitoring on the module is disabled, maybe to avoid unnecessary failover.&lt;/P&gt;&lt;P&gt;Thanks again.&lt;/P&gt;</description>
    <pubDate>Tue, 02 Aug 2022 15:00:12 GMT</pubDate>
    <dc:creator>atsukane</dc:creator>
    <dc:date>2022-08-02T15:00:12Z</dc:date>
    <item>
      <title>ASA FirePOWER module down</title>
      <link>https://community.cisco.com/t5/network-security/asa-firepower-module-down/m-p/4661935#M1092331</link>
      <description>&lt;P&gt;Hi there,&lt;/P&gt;&lt;P&gt;We have an issue with one of the ASA FirePOWER modules.&lt;/P&gt;&lt;P&gt;On the active primary ASA unit the sfr module state is Up but Data Plane Status is Down. This module was showing Unresponsive 10 mionutes earlier while I was looking and came back up without any intervention, not sure why.&lt;/P&gt;&lt;P&gt;The sfr module on the standby secondary ASA unit is showing Up/Up.&lt;/P&gt;&lt;P&gt;I'm planning on reloading the module with&amp;nbsp;&amp;nbsp;&lt;STRONG&gt;&lt;SPAN class=""&gt;sw-module module sfr reload&lt;/SPAN&gt;&lt;/STRONG&gt;, but wondered whether I need to failover the ASA first before doing so, or just putting the sfr to promiscuous mode is enough before reloading the module?&lt;/P&gt;&lt;P&gt;Please advise, and also please let me know if there are anything that I should be aware of before attempting to reload etc,.&lt;/P&gt;&lt;P&gt;Mod Status Data Plane Status Compatibility&lt;BR /&gt;---- ------------------ --------------------- -------------&lt;BR /&gt;0 Up Sys Not Applicable&lt;BR /&gt;ips Unresponsive Not Applicable&lt;BR /&gt;cxsc Unresponsive Not Applicable&lt;BR /&gt;&lt;STRONG&gt;sfr Up Down&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Many thanks,&lt;/P&gt;</description>
      <pubDate>Tue, 02 Aug 2022 09:01:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-firepower-module-down/m-p/4661935#M1092331</guid>
      <dc:creator>atsukane</dc:creator>
      <dc:date>2022-08-02T09:01:27Z</dc:date>
    </item>
    <item>
      <title>Re: ASA FirePOWER module down</title>
      <link>https://community.cisco.com/t5/network-security/asa-firepower-module-down/m-p/4662139#M1092339</link>
      <description>&lt;P&gt;If the primary ASA is active despite the module being up/down then you must have disabled monitoring of the module. Normally we would monitor this and then a failover event would occur automatically in the event of a fault.&lt;/P&gt;
&lt;P&gt;So, in your case do a failover (after verifying that the secondary unit is in state Standby - Ready). Then you can reload primary unit's module (or ASA itself) at will.&lt;/P&gt;</description>
      <pubDate>Tue, 02 Aug 2022 14:32:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-firepower-module-down/m-p/4662139#M1092339</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2022-08-02T14:32:46Z</dc:date>
    </item>
    <item>
      <title>Re: ASA FirePOWER module down</title>
      <link>https://community.cisco.com/t5/network-security/asa-firepower-module-down/m-p/4662169#M1092340</link>
      <description>&lt;P&gt;Thank you&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;I shall failover ASA first, then once the new standby (former primary/active) is in "standby-ready" i'll reload the module, and maybe ASA if needed. Then discuss with my senior why the monitoring on the module is disabled, maybe to avoid unnecessary failover.&lt;/P&gt;&lt;P&gt;Thanks again.&lt;/P&gt;</description>
      <pubDate>Tue, 02 Aug 2022 15:00:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-firepower-module-down/m-p/4662169#M1092340</guid>
      <dc:creator>atsukane</dc:creator>
      <dc:date>2022-08-02T15:00:12Z</dc:date>
    </item>
    <item>
      <title>Re: ASA FirePOWER module down</title>
      <link>https://community.cisco.com/t5/network-security/asa-firepower-module-down/m-p/4662189#M1092341</link>
      <description>&lt;P&gt;Slight correction - check that it is Standby-Ready state BEFORE doing the failover. The manual failover should then cause it to switch to Active state.&lt;/P&gt;</description>
      <pubDate>Tue, 02 Aug 2022 15:23:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-firepower-module-down/m-p/4662189#M1092341</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2022-08-02T15:23:49Z</dc:date>
    </item>
    <item>
      <title>Re: ASA FirePOWER module down</title>
      <link>https://community.cisco.com/t5/network-security/asa-firepower-module-down/m-p/4662192#M1092342</link>
      <description>&lt;P&gt;that makes sense.&lt;/P&gt;</description>
      <pubDate>Tue, 02 Aug 2022 15:27:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-firepower-module-down/m-p/4662192#M1092342</guid>
      <dc:creator>atsukane</dc:creator>
      <dc:date>2022-08-02T15:27:55Z</dc:date>
    </item>
    <item>
      <title>Re: ASA FirePOWER module down</title>
      <link>https://community.cisco.com/t5/network-security/asa-firepower-module-down/m-p/4662743#M1092350</link>
      <description>&lt;P&gt;Reloaded the module but as the it was showing Unresponsive, reloaded the ASA&amp;nbsp; as well but the module is still in Unresponsive state. Getting the below when running sfr debugs,&amp;nbsp;suppose SFR isn't very well.&amp;nbsp;Opened a support case.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;DP SFR Msg: SFR flow handle was not populated, so not informing SFR about flow cleanup.&lt;/P&gt;&lt;P&gt;cp_connect: Connecting to card 1, socket 3, port 7000&lt;BR /&gt;cp_connect: Error - cp_connect() returned -1&lt;BR /&gt;cp_check_connection: handle -1, conflicts with connection 1 (-1)&lt;BR /&gt;cp_check_connection: handle -1, conflicts with connection 2 (-1)&lt;BR /&gt;cp_check_connection: handle -1, conflicts with connection 3 (-1)&lt;BR /&gt;cp_update_connection: Error updating connection_id 0&lt;/P&gt;</description>
      <pubDate>Wed, 03 Aug 2022 07:20:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-firepower-module-down/m-p/4662743#M1092350</guid>
      <dc:creator>atsukane</dc:creator>
      <dc:date>2022-08-03T07:20:17Z</dc:date>
    </item>
  </channel>
</rss>

