<?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 Reboot in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-reboot/m-p/1876212#M491189</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Prashant,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To Identify that you woudl need to collect syslogs, from the time of the issue and also check the memory utilization and cpu usage when the firewalls rebooted. The syslogs might point towards any specific reason for the reload on the boxes. I would suggest you open a TAC case for it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Varun&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 14 Dec 2011 12:12:37 GMT</pubDate>
    <dc:creator>varrao</dc:creator>
    <dc:date>2011-12-14T12:12:37Z</dc:date>
    <item>
      <title>ASA Reboot</title>
      <link>https://community.cisco.com/t5/network-security/asa-reboot/m-p/1876211#M491188</link>
      <description>&lt;P&gt;I have&amp;nbsp; ASA's running with following hardware and software on it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hardware :&amp;nbsp; ASA5580-20, 8192 MB RAM, CPU AMD Opteron 2600 MHz 2 CPUs, 4 cores&lt;/P&gt;&lt;P&gt;Software : Version 8.4(1)&lt;/P&gt;&lt;P&gt;Uptime : up 12 days 23 hours&lt;/P&gt;&lt;P&gt;Failover : Active/Active&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Recently we have observed both devices rebooting automatically at different time intervals. Do not observe any crash information on both the devices.&lt;/P&gt;&lt;P&gt;Wanted to know if any known reasons available before raising the TAC. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Power status to the device is fine. Other network devices connected to the same power source had no issues. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Request experts opinion......&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 22:01:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-reboot/m-p/1876211#M491188</guid>
      <dc:creator>prashant.hegde</dc:creator>
      <dc:date>2019-03-11T22:01:49Z</dc:date>
    </item>
    <item>
      <title>ASA Reboot</title>
      <link>https://community.cisco.com/t5/network-security/asa-reboot/m-p/1876212#M491189</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Prashant,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To Identify that you woudl need to collect syslogs, from the time of the issue and also check the memory utilization and cpu usage when the firewalls rebooted. The syslogs might point towards any specific reason for the reload on the boxes. I would suggest you open a TAC case for it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Varun&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Dec 2011 12:12:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-reboot/m-p/1876212#M491189</guid>
      <dc:creator>varrao</dc:creator>
      <dc:date>2011-12-14T12:12:37Z</dc:date>
    </item>
  </channel>
</rss>

