<?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 Failover in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-failover/m-p/4556656#M1087578</link>
    <description>&lt;P&gt;show failover history &amp;lt;-&lt;BR /&gt;any of ASA, and share output here we can after that know why the ASA go to cold standby.&amp;nbsp;&lt;BR /&gt;check if the status is due to mismatch config?&lt;/P&gt;</description>
    <pubDate>Mon, 21 Feb 2022 20:08:10 GMT</pubDate>
    <dc:creator>MHM Cisco World</dc:creator>
    <dc:date>2022-02-21T20:08:10Z</dc:date>
    <item>
      <title>ASA Failover</title>
      <link>https://community.cisco.com/t5/network-security/asa-failover/m-p/4556443#M1087565</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;I have 2 frp 4140 running ASA code.&lt;/P&gt;&lt;P&gt;We run multi-context with ~80 context and active/standby failover.&lt;/P&gt;&lt;P&gt;We shut down the standby unit and moved it to another DC.&lt;/P&gt;&lt;P&gt;During startup of the moved ASA we see some strange issues.&lt;/P&gt;&lt;P&gt;My Active ASA goes directly from Active to Cold standby due to&amp;nbsp;Failover state check.&lt;/P&gt;&lt;P&gt;Does anyone know why this happens ?&lt;/P&gt;&lt;P&gt;Is there a list of&amp;nbsp;scenarios, where i can see what triggers state from active to cold standby ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards Henrik&lt;/P&gt;</description>
      <pubDate>Mon, 21 Feb 2022 12:12:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-failover/m-p/4556443#M1087565</guid>
      <dc:creator>henrikj</dc:creator>
      <dc:date>2022-02-21T12:12:37Z</dc:date>
    </item>
    <item>
      <title>Re: ASA Failover</title>
      <link>https://community.cisco.com/t5/network-security/asa-failover/m-p/4556461#M1087566</link>
      <description>&lt;P&gt;Failover checks are outlined in the following:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/security/asa/asa98/configuration/general/asa-98-general-config/ha-failover.html#ID-2107-00000174" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/security/asa/asa98/configuration/general/asa-98-general-config/ha-failover.html#ID-2107-00000174&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;With that many contexts and interfaces, a lot of things could influence failover. I would recommend opening a TAC case to have an engineer look at in directly with you.&lt;/P&gt;</description>
      <pubDate>Mon, 21 Feb 2022 12:48:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-failover/m-p/4556461#M1087566</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2022-02-21T12:48:34Z</dc:date>
    </item>
    <item>
      <title>Re: ASA Failover</title>
      <link>https://community.cisco.com/t5/network-security/asa-failover/m-p/4556469#M1087567</link>
      <description>&lt;P&gt;Hi Marvin&lt;/P&gt;&lt;P&gt;I did look at that document, but it doesn´t mention anything about "cold standby".&lt;/P&gt;&lt;P&gt;I want to know what state that can get a ASA to go from "Active" to "Cold standby".&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards Henrik&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 21 Feb 2022 13:07:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-failover/m-p/4556469#M1087567</guid>
      <dc:creator>henrikj</dc:creator>
      <dc:date>2022-02-21T13:07:53Z</dc:date>
    </item>
    <item>
      <title>Re: ASA Failover</title>
      <link>https://community.cisco.com/t5/network-security/asa-failover/m-p/4556656#M1087578</link>
      <description>&lt;P&gt;show failover history &amp;lt;-&lt;BR /&gt;any of ASA, and share output here we can after that know why the ASA go to cold standby.&amp;nbsp;&lt;BR /&gt;check if the status is due to mismatch config?&lt;/P&gt;</description>
      <pubDate>Mon, 21 Feb 2022 20:08:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-failover/m-p/4556656#M1087578</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2022-02-21T20:08:10Z</dc:date>
    </item>
    <item>
      <title>Re: ASA Failover</title>
      <link>https://community.cisco.com/t5/network-security/asa-failover/m-p/4556863#M1087585</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;hereby the "show failover history":&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;23:10:07 CET Feb 2 2022&lt;BR /&gt;Active Cold Standby Failover state check&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;23:10:09 CET Feb 2 2022&lt;BR /&gt;Cold Standby Sync Config Failover state check&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;23:37:54 CET Feb 2 2022&lt;BR /&gt;Sync Config Sync File System Failover state check&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;23:37:54 CET Feb 2 2022&lt;BR /&gt;Sync File System Bulk Sync Failover state check&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;23:38:06 CET Feb 2 2022&lt;BR /&gt;Bulk Sync Standby Ready Failover state check&lt;/P&gt;</description>
      <pubDate>Tue, 22 Feb 2022 07:36:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-failover/m-p/4556863#M1087585</guid>
      <dc:creator>henrikj</dc:creator>
      <dc:date>2022-02-22T07:36:22Z</dc:date>
    </item>
    <item>
      <title>Re: ASA Failover</title>
      <link>https://community.cisco.com/t5/network-security/asa-failover/m-p/4557550#M1087598</link>
      <description>&lt;P&gt;&lt;A href="https://quickview.cloudapps.cisco.com/quickview/bug/CSCua13405" target="_blank"&gt;https://quickview.cloudapps.cisco.com/quickview/bug/CSCua13405&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 22 Feb 2022 19:12:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-failover/m-p/4557550#M1087598</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2022-02-22T19:12:28Z</dc:date>
    </item>
  </channel>
</rss>

