<?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 5505 Crashing in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-5505-crashing/m-p/1760673#M493759</link>
    <description>&lt;P&gt;I have a problem with a ASA 5505. He is crashing multiple times during the day. I've setup a syslog server en I'd noticed that the last two log notification were:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2011-11-08 12:28:19&amp;nbsp;&amp;nbsp;&amp;nbsp; Local4.Debug&amp;nbsp;&amp;nbsp;&amp;nbsp; 10.0.0.254&amp;nbsp;&amp;nbsp;&amp;nbsp; %ASA-7-711002: Task ran for 27016 msec, Process = Dispatch Unit, PC = 84745ce, Traceback = &lt;/P&gt;&lt;P&gt;2011-11-08 12:28:19&amp;nbsp;&amp;nbsp;&amp;nbsp; Local4.Debug&amp;nbsp;&amp;nbsp;&amp;nbsp; 10.0.0.254&amp;nbsp;&amp;nbsp;&amp;nbsp; %ASA-7-711002: Task ran for 27016 msec, Process = Dispatch Unit, PC = 84745ce, Traceback =&amp;nbsp;&amp;nbsp; 0x084745CE&amp;nbsp; 0x08474942&amp;nbsp; 0x08475511&amp;nbsp; 0x08475DB7&amp;nbsp; 0x08475EDA&amp;nbsp; 0x08508D9B&amp;nbsp; 0x0850908A&amp;nbsp; 0x083AB5B8&amp;nbsp; 0x083A1D55&amp;nbsp; 0x080655C1&amp;nbsp; 0x08895A19&amp;nbsp; 0x08895AD0&amp;nbsp; 0x08952194&amp;nbsp; 0x08978450&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It's a 5505 with a 10 user inside host license, wich incidentally is more. Can somebody tell me what the issue is?&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 21:48:18 GMT</pubDate>
    <dc:creator>supportbsu</dc:creator>
    <dc:date>2019-03-11T21:48:18Z</dc:date>
    <item>
      <title>ASA 5505 Crashing</title>
      <link>https://community.cisco.com/t5/network-security/asa-5505-crashing/m-p/1760673#M493759</link>
      <description>&lt;P&gt;I have a problem with a ASA 5505. He is crashing multiple times during the day. I've setup a syslog server en I'd noticed that the last two log notification were:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2011-11-08 12:28:19&amp;nbsp;&amp;nbsp;&amp;nbsp; Local4.Debug&amp;nbsp;&amp;nbsp;&amp;nbsp; 10.0.0.254&amp;nbsp;&amp;nbsp;&amp;nbsp; %ASA-7-711002: Task ran for 27016 msec, Process = Dispatch Unit, PC = 84745ce, Traceback = &lt;/P&gt;&lt;P&gt;2011-11-08 12:28:19&amp;nbsp;&amp;nbsp;&amp;nbsp; Local4.Debug&amp;nbsp;&amp;nbsp;&amp;nbsp; 10.0.0.254&amp;nbsp;&amp;nbsp;&amp;nbsp; %ASA-7-711002: Task ran for 27016 msec, Process = Dispatch Unit, PC = 84745ce, Traceback =&amp;nbsp;&amp;nbsp; 0x084745CE&amp;nbsp; 0x08474942&amp;nbsp; 0x08475511&amp;nbsp; 0x08475DB7&amp;nbsp; 0x08475EDA&amp;nbsp; 0x08508D9B&amp;nbsp; 0x0850908A&amp;nbsp; 0x083AB5B8&amp;nbsp; 0x083A1D55&amp;nbsp; 0x080655C1&amp;nbsp; 0x08895A19&amp;nbsp; 0x08895AD0&amp;nbsp; 0x08952194&amp;nbsp; 0x08978450&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It's a 5505 with a 10 user inside host license, wich incidentally is more. Can somebody tell me what the issue is?&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 21:48:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5505-crashing/m-p/1760673#M493759</guid>
      <dc:creator>supportbsu</dc:creator>
      <dc:date>2019-03-11T21:48:18Z</dc:date>
    </item>
    <item>
      <title>ASA 5505 Crashing</title>
      <link>https://community.cisco.com/t5/network-security/asa-5505-crashing/m-p/1760674#M493762</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You could try an upgrade to the latest release in your particular train. Otherwise, I would suggest opening a TAC case and providing the output of 'show crash', 'show tech', and the syslogs to the engineer so the bug can be identified.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Mike&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 11 Nov 2011 14:25:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5505-crashing/m-p/1760674#M493762</guid>
      <dc:creator>mirober2</dc:creator>
      <dc:date>2011-11-11T14:25:40Z</dc:date>
    </item>
    <item>
      <title>ASA 5505 Crashing</title>
      <link>https://community.cisco.com/t5/network-security/asa-5505-crashing/m-p/1760675#M493764</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The original poster does not indicate what version of code is running on the 5505 and it might be nice to know that. And it might also help to know whether this ASA is a new install or whether it has been in use for a while (in which case has the version recently changed).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A traceback is an indication of some software problem. So I agree with MIke that there are 2 options:&lt;/P&gt;&lt;P&gt;- change the version of code running on the 5505. I agree that newer is usually better, but I believe that in this case falling back to an older version of code might also get around the problem.&lt;/P&gt;&lt;P&gt;- open a case with Cisco TAC.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rick&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 Nov 2011 03:05:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5505-crashing/m-p/1760675#M493764</guid>
      <dc:creator>Richard Burts</dc:creator>
      <dc:date>2011-11-14T03:05:12Z</dc:date>
    </item>
  </channel>
</rss>

