<?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 Congestion in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/firepower-congestion/m-p/5160178#M1115044</link>
    <description>&lt;P&gt;Also, we are working with our 3rd party cisco support engineer, but have not been able to resolve this yet.&lt;/P&gt;</description>
    <pubDate>Tue, 13 Aug 2024 13:41:14 GMT</pubDate>
    <dc:creator>sysad43</dc:creator>
    <dc:date>2024-08-13T13:41:14Z</dc:date>
    <item>
      <title>Firepower Congestion</title>
      <link>https://community.cisco.com/t5/network-security/firepower-congestion/m-p/5160177#M1115043</link>
      <description>&lt;P&gt;ASA 5555x with firepower - 9.14 latest interim&lt;BR /&gt;SFR modules and FPMCv at 6.4 latest interim&lt;/P&gt;&lt;P&gt;Suddenly on a Monday morning at 8am, latency through our ASA 5555x firewall spiked from its usual &amp;lt;10ms to over 3000ms and started dropping packets. Voice calls failed. We started getting alerts from systems we monitored, and internet connectivity was slow to nonexistent. This is when most of our users log in, connection rates go up to 100-200/s total connections go from about 8000 to 20000. We had not made any recent changes other than upgrading some anyconnect clients to 5.1 version.&lt;/P&gt;&lt;P&gt;Now, the problem happens every monday at 8am, and calms down by about 9am. And also happens a little less at 8am every work day. It happend on a tuesday at 8am when we were closed on monday, so its certainly correlated to increased internal traffic going out.&lt;/P&gt;&lt;P&gt;To try and resolve we made sure we were on latest fixes (firepower pending), looked for DDOS, shunned some internal IPs tripping threat detection rates, but nothing has worked except bypassing the firepower module entirely. So, we think the issue is thus with the firepower module, or the config, but since nothing changed, we cant find the reason.&lt;/P&gt;&lt;P&gt;Where should I look to try and get more information on whats going on?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 13 Aug 2024 13:40:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-congestion/m-p/5160177#M1115043</guid>
      <dc:creator>sysad43</dc:creator>
      <dc:date>2024-08-13T13:40:27Z</dc:date>
    </item>
    <item>
      <title>Re: Firepower Congestion</title>
      <link>https://community.cisco.com/t5/network-security/firepower-congestion/m-p/5160178#M1115044</link>
      <description>&lt;P&gt;Also, we are working with our 3rd party cisco support engineer, but have not been able to resolve this yet.&lt;/P&gt;</description>
      <pubDate>Tue, 13 Aug 2024 13:41:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-congestion/m-p/5160178#M1115044</guid>
      <dc:creator>sysad43</dc:creator>
      <dc:date>2024-08-13T13:41:14Z</dc:date>
    </item>
    <item>
      <title>Re: Firepower Congestion</title>
      <link>https://community.cisco.com/t5/network-security/firepower-congestion/m-p/5160306#M1115046</link>
      <description>&lt;P&gt;You mentioned that the traffic internal make asa high utilize' then you need to change the GW of host into other L3 device and make asa only inspect traffic when host want to access internet.&lt;/P&gt;
&lt;P&gt;MHM&lt;/P&gt;</description>
      <pubDate>Tue, 13 Aug 2024 15:04:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-congestion/m-p/5160306#M1115046</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2024-08-13T15:04:38Z</dc:date>
    </item>
    <item>
      <title>Re: Firepower Congestion</title>
      <link>https://community.cisco.com/t5/network-security/firepower-congestion/m-p/5160343#M1115048</link>
      <description>Did you try the troubleshooting of the ASA modules? Of course! Try these&lt;BR /&gt;steps on the module to id what is causing this.&lt;BR /&gt;&lt;BR /&gt;ASA FirePOWER Module (SFR) Troubleshoot File Generation Procedures using&lt;BR /&gt;ASDM (On-box Management) (cisco.com)&lt;BR /&gt;&amp;lt;&amp;gt;&lt;BR /&gt;&lt;BR /&gt;Firepower Data Path Troubleshooting: Overview - Cisco&lt;BR /&gt;&amp;lt;&amp;gt;&lt;BR /&gt;&lt;BR /&gt;Troubleshooting ASA FirePOWER modules | CCIE Security Blog (cciesecblog.com)&lt;BR /&gt;&amp;lt;&amp;gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 13 Aug 2024 15:58:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-congestion/m-p/5160343#M1115048</guid>
      <dc:creator>james.king14</dc:creator>
      <dc:date>2024-08-13T15:58:30Z</dc:date>
    </item>
    <item>
      <title>Re: Firepower Congestion</title>
      <link>https://community.cisco.com/t5/network-security/firepower-congestion/m-p/5160372#M1115051</link>
      <description>&lt;P&gt;Thanks, I will take a look.&lt;/P&gt;</description>
      <pubDate>Tue, 13 Aug 2024 16:49:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-congestion/m-p/5160372#M1115051</guid>
      <dc:creator>sysad43</dc:creator>
      <dc:date>2024-08-13T16:49:29Z</dc:date>
    </item>
    <item>
      <title>Re: Firepower Congestion</title>
      <link>https://community.cisco.com/t5/network-security/firepower-congestion/m-p/5161537#M1115106</link>
      <description>&lt;P&gt;No real new information from testing, so next step is we are going to update FPMC and SFR modules and then change the service policy to bypass inspection for some traffic. So far, disabling inspection entirely is only thing that resolves this.&lt;/P&gt;</description>
      <pubDate>Thu, 15 Aug 2024 20:22:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-congestion/m-p/5161537#M1115106</guid>
      <dc:creator>sysad43</dc:creator>
      <dc:date>2024-08-15T20:22:54Z</dc:date>
    </item>
    <item>
      <title>Re: Firepower Congestion</title>
      <link>https://community.cisco.com/t5/network-security/firepower-congestion/m-p/5162117#M1115134</link>
      <description>&lt;P&gt;Show conn long&amp;nbsp;&lt;/P&gt;
&lt;P&gt;See the top ten traffic rate' if the traffic is internal then as I suggest before make internal traffic bypass ftd (change GW of internal host)&lt;/P&gt;
&lt;P&gt;MHM&lt;/P&gt;</description>
      <pubDate>Sat, 17 Aug 2024 14:10:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-congestion/m-p/5162117#M1115134</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2024-08-17T14:10:02Z</dc:date>
    </item>
    <item>
      <title>Re: Firepower Congestion</title>
      <link>https://community.cisco.com/t5/network-security/firepower-congestion/m-p/5162648#M1115185</link>
      <description>&lt;P&gt;Updating FPMC and SFR and/or bypassing SFR for some traffic so far seems to have resolved it.&lt;/P&gt;</description>
      <pubDate>Mon, 19 Aug 2024 13:41:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-congestion/m-p/5162648#M1115185</guid>
      <dc:creator>sysad43</dc:creator>
      <dc:date>2024-08-19T13:41:09Z</dc:date>
    </item>
  </channel>
</rss>

