<?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: How does an ASA log a failover event? in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/how-does-an-asa-log-a-failover-event/m-p/5327657#M1122610</link>
    <description>&lt;P&gt;Well at least I'm not crazy, and it's set up correctly.&amp;nbsp; But it isn't generating logs when it fails over, so something else must be wrong...&lt;/P&gt;</description>
    <pubDate>Fri, 05 Sep 2025 20:57:58 GMT</pubDate>
    <dc:creator>Cartesian</dc:creator>
    <dc:date>2025-09-05T20:57:58Z</dc:date>
    <item>
      <title>How does an ASA log a failover event?</title>
      <link>https://community.cisco.com/t5/network-security/how-does-an-asa-log-a-failover-event/m-p/5327620#M1122595</link>
      <description>&lt;P&gt;I have an ASA pair configured for active/standby failover.&amp;nbsp; However they don't seem to be generating syslog events related to failover status.&amp;nbsp; Do I need some specific configuration for this?&amp;nbsp; Are some contexts simply unable to log these events?&lt;/P&gt;&lt;P&gt;Contexts:&lt;BR /&gt;-Chassis Manager&lt;BR /&gt;-System Context&lt;BR /&gt;-Admin Context&lt;BR /&gt;-Normal Contexts&lt;/P&gt;&lt;P&gt;Events that need logging:&lt;BR /&gt;-Failover to other chassis&lt;BR /&gt;-Standby chassis becomes Failed&lt;BR /&gt;-Interface on Active chassis becomes Failed/No Link&lt;BR /&gt;-Interface on Standby chassis becomes Failed/No Link&lt;/P&gt;&lt;P&gt;Right now we have Informational logging on all the Normal Contexts and the Admin context, but don't seem to be getting any syslogs for these events.&amp;nbsp; Do I need logging on the System Context?&amp;nbsp; Or the Chassis Manager?&amp;nbsp; I'm really surprised that a cable can be physically unplugged and the Normal Contexts don't generate any syslogs.&amp;nbsp; Is there some logging setting I can configure to make them do so?&lt;/P&gt;</description>
      <pubDate>Fri, 05 Sep 2025 19:52:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-does-an-asa-log-a-failover-event/m-p/5327620#M1122595</guid>
      <dc:creator>Cartesian</dc:creator>
      <dc:date>2025-09-05T19:52:08Z</dc:date>
    </item>
    <item>
      <title>Re: How does an ASA log a failover event?</title>
      <link>https://community.cisco.com/t5/network-security/how-does-an-asa-log-a-failover-event/m-p/5327623#M1122597</link>
      <description>&lt;P&gt;changeto context &amp;lt;context_name&amp;gt;&lt;BR /&gt;logging enable&lt;BR /&gt;logging buffered informational&lt;BR /&gt;logging trap notifications&lt;BR /&gt;logging host &amp;lt;interface&amp;gt; &amp;lt;syslog_IP&amp;gt;&lt;/P&gt;
&lt;P&gt;This how yoh need to config log per context&lt;/P&gt;
&lt;P&gt;MHM&lt;/P&gt;</description>
      <pubDate>Fri, 05 Sep 2025 20:02:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-does-an-asa-log-a-failover-event/m-p/5327623#M1122597</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2025-09-05T20:02:00Z</dc:date>
    </item>
    <item>
      <title>Re: How does an ASA log a failover event?</title>
      <link>https://community.cisco.com/t5/network-security/how-does-an-asa-log-a-failover-event/m-p/5327631#M1122603</link>
      <description>&lt;P&gt;Hey again&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1065752"&gt;@MHM Cisco World&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;Sorry about that, MHM. I had multiple Cisco Community queries open at the same time, and I must have dropped my reply in the wrong spot by mistake.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 05 Sep 2025 20:35:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-does-an-asa-log-a-failover-event/m-p/5327631#M1122603</guid>
      <dc:creator>sidshas03</dc:creator>
      <dc:date>2025-09-05T20:35:53Z</dc:date>
    </item>
    <item>
      <title>Re: How does an ASA log a failover event?</title>
      <link>https://community.cisco.com/t5/network-security/how-does-an-asa-log-a-failover-event/m-p/5327632#M1122604</link>
      <description>&lt;P&gt;Friend you reply in wrong post&amp;nbsp;&lt;/P&gt;
&lt;P&gt;MHM&lt;/P&gt;</description>
      <pubDate>Fri, 05 Sep 2025 20:32:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-does-an-asa-log-a-failover-event/m-p/5327632#M1122604</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2025-09-05T20:32:09Z</dc:date>
    </item>
    <item>
      <title>Re: How does an ASA log a failover event?</title>
      <link>https://community.cisco.com/t5/network-security/how-does-an-asa-log-a-failover-event/m-p/5327657#M1122610</link>
      <description>&lt;P&gt;Well at least I'm not crazy, and it's set up correctly.&amp;nbsp; But it isn't generating logs when it fails over, so something else must be wrong...&lt;/P&gt;</description>
      <pubDate>Fri, 05 Sep 2025 20:57:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-does-an-asa-log-a-failover-event/m-p/5327657#M1122610</guid>
      <dc:creator>Cartesian</dc:creator>
      <dc:date>2025-09-05T20:57:58Z</dc:date>
    </item>
    <item>
      <title>Re: How does an ASA log a failover event?</title>
      <link>https://community.cisco.com/t5/network-security/how-does-an-asa-log-a-failover-event/m-p/5327663#M1122613</link>
      <description>&lt;P&gt;Can you share this&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;changeto context &amp;lt;context_name&amp;gt;&lt;/STRONG&gt;&lt;BR /&gt;show logging&lt;/P&gt;
&lt;P&gt;MHM&lt;/P&gt;</description>
      <pubDate>Fri, 05 Sep 2025 21:12:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-does-an-asa-log-a-failover-event/m-p/5327663#M1122613</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2025-09-05T21:12:26Z</dc:date>
    </item>
  </channel>
</rss>

