<?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 ASA SFR module health modules disabled in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-sfr-module-health-modules-disabled/m-p/5037155#M1109761</link>
    <description>&lt;P&gt;I just upgraded my FMCv from 7.2.5.1 to 7.4.1.&amp;nbsp; I have two FTDs and two SFR modules being managed.&amp;nbsp; After the FMC upgrade one of the SFR devices show *all* health modules as being disabled.&amp;nbsp; It uses the same health policy as the "good" SFR and I can't find any individual setting on FMC or the SFR that would cause this.&amp;nbsp; Also note that the SFR module shows as online and managed in the FMC.&amp;nbsp; It appears to be only a health model or service related problem.&amp;nbsp; I have included a pic of the status.&amp;nbsp; Any ideas?&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Diego&lt;/P&gt;</description>
    <pubDate>Sun, 10 Mar 2024 18:07:54 GMT</pubDate>
    <dc:creator>tato386</dc:creator>
    <dc:date>2024-03-10T18:07:54Z</dc:date>
    <item>
      <title>ASA SFR module health modules disabled</title>
      <link>https://community.cisco.com/t5/network-security/asa-sfr-module-health-modules-disabled/m-p/5037155#M1109761</link>
      <description>&lt;P&gt;I just upgraded my FMCv from 7.2.5.1 to 7.4.1.&amp;nbsp; I have two FTDs and two SFR modules being managed.&amp;nbsp; After the FMC upgrade one of the SFR devices show *all* health modules as being disabled.&amp;nbsp; It uses the same health policy as the "good" SFR and I can't find any individual setting on FMC or the SFR that would cause this.&amp;nbsp; Also note that the SFR module shows as online and managed in the FMC.&amp;nbsp; It appears to be only a health model or service related problem.&amp;nbsp; I have included a pic of the status.&amp;nbsp; Any ideas?&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Diego&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2024 18:07:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-sfr-module-health-modules-disabled/m-p/5037155#M1109761</guid>
      <dc:creator>tato386</dc:creator>
      <dc:date>2024-03-10T18:07:54Z</dc:date>
    </item>
    <item>
      <title>Re: ASA SFR module health modules disabled</title>
      <link>https://community.cisco.com/t5/network-security/asa-sfr-module-health-modules-disabled/m-p/5037191#M1109762</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; = FYI :&amp;nbsp;&lt;A href="https://community.cisco.com/t5/network-security/asa-firepower-module-down/m-p/4662139#M1092339" target="_blank"&gt;https://community.cisco.com/t5/network-security/asa-firepower-module-down/m-p/4662139#M1092339&lt;/A&gt;&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &lt;FONT color="#FF6600"&gt;&lt;EM&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; (there is no included pic)&lt;/EM&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;M.&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2024 17:56:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-sfr-module-health-modules-disabled/m-p/5037191#M1109762</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2024-03-10T17:56:34Z</dc:date>
    </item>
    <item>
      <title>Re: ASA SFR module health modules disabled</title>
      <link>https://community.cisco.com/t5/network-security/asa-sfr-module-health-modules-disabled/m-p/5037193#M1109763</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/291804"&gt;@Mark Elsen&lt;/a&gt;&amp;nbsp;that post is interesting, but this is not a failover pair, just two individual ASA/SFR devices.&amp;nbsp; I have uploaded pic.&amp;nbsp; Thanks!&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2024 18:09:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-sfr-module-health-modules-disabled/m-p/5037193#M1109763</guid>
      <dc:creator>tato386</dc:creator>
      <dc:date>2024-03-10T18:09:16Z</dc:date>
    </item>
    <item>
      <title>Re: ASA SFR module health modules disabled</title>
      <link>https://community.cisco.com/t5/network-security/asa-sfr-module-health-modules-disabled/m-p/5037226#M1109764</link>
      <description>&lt;P&gt;Have you verified that the SF tunnel is up and active?&amp;nbsp; In expert mode on the SFR module and / or the FMC issue the following commands:&lt;/P&gt;
&lt;P&gt;pmtool status | grep -i down&lt;/P&gt;
&lt;P&gt;pmtool status | grep -i sftunn&lt;/P&gt;
&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;" lang="nb-NO"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P style="margin: 0in; font-family: Calibri; font-size: 11.0pt;" lang="nb-NO"&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2024 20:48:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-sfr-module-health-modules-disabled/m-p/5037226#M1109764</guid>
      <dc:creator>Marius Gunnerud</dc:creator>
      <dc:date>2024-03-10T20:48:50Z</dc:date>
    </item>
    <item>
      <title>Re: ASA SFR module health modules disabled</title>
      <link>https://community.cisco.com/t5/network-security/asa-sfr-module-health-modules-disabled/m-p/5037228#M1109765</link>
      <description>&lt;P&gt;sftunnel appears to be normal:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;root@sfr17-2:~# pmtool status | grep -i down&lt;BR /&gt;&lt;A href="mailto:root@sfr17-2:~" target="_blank"&gt;root@sfr17-2:~#&lt;/A&gt;&lt;/P&gt;&lt;P&gt;root@sfr17-2:~# pmtool status | grep -i sftunn&lt;BR /&gt;sftunnel (system) - Running 2178&lt;BR /&gt;Command: /usr/local/sf/bin/sftunnel -d -f /etc/sf/sftunnel.conf&lt;BR /&gt;PID File: /var/sf/run/sftunnel.pid&lt;BR /&gt;Enable File: /etc/sf/sftunnel.conf&lt;BR /&gt;Command: /usr/local/sf/bin/sfmgr -d -f /etc/sf/sftunnel.conf&lt;BR /&gt;Enable File: /etc/sf/sftunnel.conf&lt;BR /&gt;Requires: sftunnel&lt;BR /&gt;Command: /usr/local/sf/bin/sfmbservice -d -f /etc/sf/sftunnel.conf&lt;BR /&gt;Enable File: /etc/sf/sftunnel.conf&lt;BR /&gt;Requires: sfmb,sftunnel&lt;BR /&gt;Requires: sftunnel&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2024 21:31:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-sfr-module-health-modules-disabled/m-p/5037228#M1109765</guid>
      <dc:creator>tato386</dc:creator>
      <dc:date>2024-03-10T21:31:36Z</dc:date>
    </item>
    <item>
      <title>Re: ASA SFR module health modules disabled</title>
      <link>https://community.cisco.com/t5/network-security/asa-sfr-module-health-modules-disabled/m-p/5037233#M1109766</link>
      <description>&lt;P&gt;Have you tried restarting the sfr module?&amp;nbsp; What about reloading the ASA?&lt;/P&gt;
&lt;P&gt;sw-module module sfr restart&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2024 21:47:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-sfr-module-health-modules-disabled/m-p/5037233#M1109766</guid>
      <dc:creator>Marius Gunnerud</dc:creator>
      <dc:date>2024-03-10T21:47:42Z</dc:date>
    </item>
    <item>
      <title>Re: ASA SFR module health modules disabled</title>
      <link>https://community.cisco.com/t5/network-security/asa-sfr-module-health-modules-disabled/m-p/5037513#M1109772</link>
      <description>&lt;P&gt;yes, I restarted both several times and I was also able to upgrade the sfr from 7.0.6 to 7.0.6.1 so there is no doubt the FMC/SFR relationship is fine.&amp;nbsp; problem seems specific to health module or processes.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2024 12:48:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-sfr-module-health-modules-disabled/m-p/5037513#M1109772</guid>
      <dc:creator>tato386</dc:creator>
      <dc:date>2024-03-11T12:48:55Z</dc:date>
    </item>
    <item>
      <title>Re: ASA SFR module health modules disabled</title>
      <link>https://community.cisco.com/t5/network-security/asa-sfr-module-health-modules-disabled/m-p/5037537#M1109773</link>
      <description>&lt;P&gt;This sounds like something is hanging either on the SFR or on the FMC, have also tried restarting the FMC?&lt;/P&gt;
&lt;P&gt;What about creating a new Health policy and applying it to the SFR module?&amp;nbsp; &lt;STRONG&gt;&lt;EM&gt;Settings &amp;gt; Health &amp;gt; Policy&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2024 13:36:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-sfr-module-health-modules-disabled/m-p/5037537#M1109773</guid>
      <dc:creator>Marius Gunnerud</dc:creator>
      <dc:date>2024-03-11T13:36:08Z</dc:date>
    </item>
    <item>
      <title>Re: ASA SFR module health modules disabled</title>
      <link>https://community.cisco.com/t5/network-security/asa-sfr-module-health-modules-disabled/m-p/5037563#M1109774</link>
      <description>&lt;P&gt;no change after restart of the FMC.&amp;nbsp; This SFR was using its own unique policy and one of the first things I did was to use the policy from the other SFR (which shows normal) and that didn't make any difference either.&amp;nbsp; this one definitely has me scratching my head...&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2024 14:31:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-sfr-module-health-modules-disabled/m-p/5037563#M1109774</guid>
      <dc:creator>tato386</dc:creator>
      <dc:date>2024-03-11T14:31:42Z</dc:date>
    </item>
    <item>
      <title>Re: ASA SFR module health modules disabled</title>
      <link>https://community.cisco.com/t5/network-security/asa-sfr-module-health-modules-disabled/m-p/5037946#M1109781</link>
      <description>&lt;P&gt;Please run the following commands in expert mode on the SFR module and on the FMC (for comparison).&lt;/P&gt;
&lt;P style="margin: 0in; font-family: -apple-system; font-size: 12.0pt; color: #272b32;"&gt;&lt;SPAN&gt;pmtool status | grep Waiting&lt;/SPAN&gt;&lt;/P&gt;
&lt;P style="margin: 0in; font-family: -apple-system; font-size: 12.0pt; color: #272b32;"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P style="margin: 0in; font-family: -apple-system; font-size: 12.0pt; color: #272b32;"&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2024 07:33:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-sfr-module-health-modules-disabled/m-p/5037946#M1109781</guid>
      <dc:creator>Marius Gunnerud</dc:creator>
      <dc:date>2024-03-12T07:33:41Z</dc:date>
    </item>
    <item>
      <title>Re: ASA SFR module health modules disabled</title>
      <link>https://community.cisco.com/t5/network-security/asa-sfr-module-health-modules-disabled/m-p/5038316#M1109797</link>
      <description>&lt;P&gt;# pmtool status | grep Waiting&lt;BR /&gt;threatcorrelator (normal) - Waiting&lt;BR /&gt;beakerd (system) - Waiting&lt;BR /&gt;stunnel (normal) - Waiting&lt;BR /&gt;httpsd (system,gui) - Waiting&lt;BR /&gt;idhttpsd (system,gui) - Waiting&lt;BR /&gt;sfipmid (normal) - Waiting&lt;BR /&gt;sfestreamer (normal) - Waiting&lt;BR /&gt;snmpd (normal) - Waiting&lt;BR /&gt;adi_proxy (normal) - Waiting&lt;BR /&gt;UIMP (normal) - Waiting&lt;BR /&gt;hmlsd (normal) - Waiting&lt;BR /&gt;CloudAgent (system) - Waiting&lt;BR /&gt;UEChanneld (normal) - Waiting&lt;BR /&gt;ui_archiver (normal) - Waiting&lt;BR /&gt;eventserver (normal) - Waiting&lt;BR /&gt;eventserver2 (normal) - Waiting&lt;BR /&gt;mojo_server (system,gui) - Waiting&lt;BR /&gt;memcached (normal) - Waiting&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2024 20:15:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-sfr-module-health-modules-disabled/m-p/5038316#M1109797</guid>
      <dc:creator>tato386</dc:creator>
      <dc:date>2024-03-12T20:15:45Z</dc:date>
    </item>
  </channel>
</rss>

