<?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: Cisco ASA Firewall Issue 5508 in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/cisco-asa-firewall-issue-5508/m-p/5144617#M1114260</link>
    <description>&lt;P&gt;Hello Sir,&lt;/P&gt;&lt;P&gt;Can you please help me find the recent logs before doing force reboot?&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
    <pubDate>Sun, 14 Jul 2024 06:46:41 GMT</pubDate>
    <dc:creator>Hamidsattarrana</dc:creator>
    <dc:date>2024-07-14T06:46:41Z</dc:date>
    <item>
      <title>Cisco ASA Firewall Issue 5508</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa-firewall-issue-5508/m-p/5141522#M1114102</link>
      <description>&lt;P&gt;Hello Everyone,&lt;/P&gt;&lt;P&gt;We have a strange issue after 2 or 4 months, we are not able to reach the firewall and all the servers/systems connected with the firewall are not reachable.&lt;/P&gt;&lt;P&gt;Then we have to hard reboot the firewall and after reboot it start working fine.&lt;/P&gt;&lt;P&gt;Firewall Model and Version: ASA 5508&lt;/P&gt;&lt;P&gt;ASA Version: 9.9(2)&lt;/P&gt;&lt;P&gt;Can anyone please tell me what could be the issue?&lt;/P&gt;&lt;P&gt;Thanks in advance&lt;/P&gt;</description>
      <pubDate>Mon, 08 Jul 2024 16:09:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa-firewall-issue-5508/m-p/5141522#M1114102</guid>
      <dc:creator>Hamidsattarrana</dc:creator>
      <dc:date>2024-07-08T16:09:53Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ASA Firewall Issue 5508</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa-firewall-issue-5508/m-p/5141563#M1114112</link>
      <description>&lt;P&gt;You reboot so the asa dont keep info about issue byt if ypu have syslog message we can briefly know what issue was.&lt;/P&gt;
&lt;P&gt;You and use can not know now anything of previous issue&lt;/P&gt;
&lt;P&gt;MHM&lt;/P&gt;</description>
      <pubDate>Mon, 08 Jul 2024 17:16:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa-firewall-issue-5508/m-p/5141563#M1114112</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2024-07-08T17:16:47Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ASA Firewall Issue 5508</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa-firewall-issue-5508/m-p/5141570#M1114115</link>
      <description>&lt;P&gt;You're running a very old image (~4 years) that is not even offered for download any more. It could be affected by many different bugs. I would start by upgrading to a more recent image. Something like 9.16.4-62 would be much better.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://software.cisco.com/download/home/286285773/type/280775065/release/9.16.4%20Interim" target="_blank" rel="noopener"&gt;https://software.cisco.com/download/home/286285773/type/280775065/release/9.16.4%20Interim&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 08 Jul 2024 17:28:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa-firewall-issue-5508/m-p/5141570#M1114115</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2024-07-08T17:28:15Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ASA Firewall Issue 5508</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa-firewall-issue-5508/m-p/5144616#M1114259</link>
      <description>&lt;P&gt;Hello Marvin,&lt;/P&gt;&lt;P&gt;Thanks for your suggestion, I will check.&lt;/P&gt;</description>
      <pubDate>Sun, 14 Jul 2024 06:45:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa-firewall-issue-5508/m-p/5144616#M1114259</guid>
      <dc:creator>Hamidsattarrana</dc:creator>
      <dc:date>2024-07-14T06:45:31Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ASA Firewall Issue 5508</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa-firewall-issue-5508/m-p/5144617#M1114260</link>
      <description>&lt;P&gt;Hello Sir,&lt;/P&gt;&lt;P&gt;Can you please help me find the recent logs before doing force reboot?&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Sun, 14 Jul 2024 06:46:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa-firewall-issue-5508/m-p/5144617#M1114260</guid>
      <dc:creator>Hamidsattarrana</dc:creator>
      <dc:date>2024-07-14T06:46:41Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ASA Firewall Issue 5508</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa-firewall-issue-5508/m-p/5144832#M1114269</link>
      <description>&lt;P&gt;Are you able to console into the firewall?&lt;/P&gt;
&lt;P&gt;Syslog messages should be sent to your syslog server.&amp;nbsp; If you do not have a syslog server then "show logging" from the CLI but this is limited to how large buffer you have configured. &lt;/P&gt;
&lt;P&gt;As &lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/326046"&gt;@Marvin Rhoads&lt;/a&gt; has mentioned, the first thing you should be doing is upgrading the ASA to a newer version as you might be hitting a bug.&lt;/P&gt;
&lt;P&gt;If you are still having problems after upgrading, create a "show tech" file while the issue is happening (also create one when the issue is not present).&amp;nbsp; I would then suggest opening a TAC case and provide the two show tech files.&amp;nbsp; If opening a TAC case is not an option for you, remove any public IPs, usernames and passwords from the show tech files and then post them here and we can try to help you out.&lt;/P&gt;</description>
      <pubDate>Mon, 15 Jul 2024 08:36:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa-firewall-issue-5508/m-p/5144832#M1114269</guid>
      <dc:creator>Marius Gunnerud</dc:creator>
      <dc:date>2024-07-15T08:36:58Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ASA Firewall Issue 5508</title>
      <link>https://community.cisco.com/t5/network-security/cisco-asa-firewall-issue-5508/m-p/5144835#M1114270</link>
      <description>&lt;P&gt;Things you could try when the issue is happening are the following. Try each in turn and see if the issue is resolved after each command, that way we will know what is causing the issue.&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;clear conn&lt;/LI&gt;
&lt;LI&gt;clear xlate&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;Other things to check is if a failover has occured, and if the switch is seeing the correct MAC address for the Firewall.&amp;nbsp; Also check ARP tables on your L3 devices and make sure that IP to MAC mappings are correct.&lt;/P&gt;</description>
      <pubDate>Mon, 15 Jul 2024 08:42:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cisco-asa-firewall-issue-5508/m-p/5144835#M1114270</guid>
      <dc:creator>Marius Gunnerud</dc:creator>
      <dc:date>2024-07-15T08:42:32Z</dc:date>
    </item>
  </channel>
</rss>

