<?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: asa log after reload in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-log-after-reload/m-p/1472631#M635093</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Solid amber light suggest the device has failed diagnostics.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/docs/security/asa/hw/maintenance/guide/overview.html"&gt;http://www.cisco.com/en/US/docs/security/asa/hw/maintenance/guide/overview.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It will be strange that you can not console to the device.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It is likely you will not get any infomration from the device after power cycle, though you can try to do show crashinfo, to see if there is any crash file.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For future troubleshooting, it will help to enable logging to syslog server, and setting for timestamps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also enable loggin standby, so you get both devices sending syslog to the syslog server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;More information here :&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/docs/security/asa/asa72/command/reference/l2_72.html#wp1687684"&gt;http://www.cisco.com/en/US/docs/security/asa/asa72/command/reference/l2_72.html#wp1687684&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If this keeps on happening, I suggest logging a Service Request to TAC.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 10 Jun 2010 12:07:40 GMT</pubDate>
    <dc:creator>edadios</dc:creator>
    <dc:date>2010-06-10T12:07:40Z</dc:date>
    <item>
      <title>asa log after reload</title>
      <link>https://community.cisco.com/t5/network-security/asa-log-after-reload/m-p/1472628#M635090</link>
      <description>&lt;P&gt;Dear all,&lt;/P&gt;&lt;P&gt;I have a problem with a Cisco ASA 5510 ver. 8.0(4).&lt;/P&gt;&lt;P&gt;It is connected to another ASA in a failover configuration (active/standby). Now failover is not active and I can't connect&lt;/P&gt;&lt;P&gt;to the standby unit even with console cable.&lt;/P&gt;&lt;P&gt;I tried to connect on management ehternet port without success.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would like to reload it. Will I find anything about problems after reload? For example a crashinfo file.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 17:57:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-log-after-reload/m-p/1472628#M635090</guid>
      <dc:creator>gdspa</dc:creator>
      <dc:date>2019-03-11T17:57:03Z</dc:date>
    </item>
    <item>
      <title>Re: asa log after reload</title>
      <link>https://community.cisco.com/t5/network-security/asa-log-after-reload/m-p/1472629#M635091</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What is the state of the secondary unit in the command ''sh fail'' under the primary unit?&lt;/P&gt;&lt;P&gt;I mean, does it show the failed unit as failed?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you reboot the ASA it should come back to normal (not sure you're going to find a crashinfo file since the ASA has not crashed),&lt;/P&gt;&lt;P&gt;but it should get back to normal....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let's try to find from the primary unit what's going on with the secondary.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Federico.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Jun 2010 16:04:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-log-after-reload/m-p/1472629#M635091</guid>
      <dc:creator>Federico Coto Fajardo</dc:creator>
      <dc:date>2010-06-09T16:04:45Z</dc:date>
    </item>
    <item>
      <title>Re: asa log after reload</title>
      <link>https://community.cisco.com/t5/network-security/asa-log-after-reload/m-p/1472630#M635092</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;On the active unit, the secondary is in Not Detected state.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On the asa that does not work, the status led is orange.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you for your help !&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Jun 2010 10:18:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-log-after-reload/m-p/1472630#M635092</guid>
      <dc:creator>gdspa</dc:creator>
      <dc:date>2010-06-10T10:18:12Z</dc:date>
    </item>
    <item>
      <title>Re: asa log after reload</title>
      <link>https://community.cisco.com/t5/network-security/asa-log-after-reload/m-p/1472631#M635093</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Solid amber light suggest the device has failed diagnostics.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/docs/security/asa/hw/maintenance/guide/overview.html"&gt;http://www.cisco.com/en/US/docs/security/asa/hw/maintenance/guide/overview.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It will be strange that you can not console to the device.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It is likely you will not get any infomration from the device after power cycle, though you can try to do show crashinfo, to see if there is any crash file.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For future troubleshooting, it will help to enable logging to syslog server, and setting for timestamps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also enable loggin standby, so you get both devices sending syslog to the syslog server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;More information here :&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/docs/security/asa/asa72/command/reference/l2_72.html#wp1687684"&gt;http://www.cisco.com/en/US/docs/security/asa/asa72/command/reference/l2_72.html#wp1687684&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If this keeps on happening, I suggest logging a Service Request to TAC.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Jun 2010 12:07:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-log-after-reload/m-p/1472631#M635093</guid>
      <dc:creator>edadios</dc:creator>
      <dc:date>2010-06-10T12:07:40Z</dc:date>
    </item>
  </channel>
</rss>

