<?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 Cluster : Failover in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-cluster-failover/m-p/3809631#M6745</link>
    <description>&lt;P&gt;Good day,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So we have two cisco asa 5516-X which is configured as Cluster.&lt;/P&gt;&lt;P&gt;Everything is smooth until we tested the failover.&lt;/P&gt;&lt;P&gt;We connected the Cluster Control Link between the two Firewalls [Interface Gig 1/8] on both firewalls&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When we tested to poweroff the Slave in the cluster, the interface gig1/8 also go down, as well as the cluster on both ASA and the port channels as well.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there a work around on this? Without using switch in between?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Maybe there's cluster configuration which will can make the port channels active even though cluster control link is down?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks a lot!&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 21 Feb 2020 16:51:51 GMT</pubDate>
    <dc:creator>flokisaints@gmail.com</dc:creator>
    <dc:date>2020-02-21T16:51:51Z</dc:date>
    <item>
      <title>ASA Cluster : Failover</title>
      <link>https://community.cisco.com/t5/network-security/asa-cluster-failover/m-p/3809631#M6745</link>
      <description>&lt;P&gt;Good day,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So we have two cisco asa 5516-X which is configured as Cluster.&lt;/P&gt;&lt;P&gt;Everything is smooth until we tested the failover.&lt;/P&gt;&lt;P&gt;We connected the Cluster Control Link between the two Firewalls [Interface Gig 1/8] on both firewalls&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When we tested to poweroff the Slave in the cluster, the interface gig1/8 also go down, as well as the cluster on both ASA and the port channels as well.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there a work around on this? Without using switch in between?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Maybe there's cluster configuration which will can make the port channels active even though cluster control link is down?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks a lot!&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 16:51:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-cluster-failover/m-p/3809631#M6745</guid>
      <dc:creator>flokisaints@gmail.com</dc:creator>
      <dc:date>2020-02-21T16:51:51Z</dc:date>
    </item>
    <item>
      <title>Re: ASA Cluster : Failover</title>
      <link>https://community.cisco.com/t5/network-security/asa-cluster-failover/m-p/3809686#M6748</link>
      <description>&lt;P&gt;suggest to post the confifguration and topology how they are physically connected. what you see in the logs when you trun off slave device power down as part of testing.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;also provider what is the OS code running /&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Please refer the configuration guide :&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/security/asa/asa91/configuration/general/asa_91_general_config/ha_cluster.pdf" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/security/asa/asa91/configuration/general/asa_91_general_config/ha_cluster.pdf&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 26 Feb 2019 08:48:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-cluster-failover/m-p/3809686#M6748</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2019-02-26T08:48:06Z</dc:date>
    </item>
  </channel>
</rss>

