<?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: Testing failover? in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/testing-failover/m-p/1473484#M717754</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ahhh John,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The GNS3 lab - failover will not work for you in a virtual LAB - it must be an actual physical test lab, sorry I missed the "GNS" reference in the original post &lt;SPAN __jive_emoticon_name="sad" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/images/emoticons/sad.gif"&gt;&lt;/SPAN&gt; .&amp;nbsp; The issue is - the PIX/ASA are virtual machines - and as such "auto" provide ethernet keepalivesand assume a good interface....so shuting the other device down, will not being down the PIX/ASA interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just to double check - fire up a PIX/ASA with no network connections to it in GNS3 and config 1 interface, then open it.&amp;nbsp; I'm pretty sure it will say up/up all the time!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I also think your real life failover test will pass 100%.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&amp;gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 14 May 2010 17:03:03 GMT</pubDate>
    <dc:creator>andrew.prince</dc:creator>
    <dc:date>2010-05-14T17:03:03Z</dc:date>
    <item>
      <title>Testing failover?</title>
      <link>https://community.cisco.com/t5/network-security/testing-failover/m-p/1473480#M717733</link>
      <description>&lt;P&gt;All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've configured failover in GNS between two ASAs. I'm doing this for real this weekend, but I've run into a snag. If I shut the outside interface on the primary, traffic stops and the standby doesn't take over. The standby works though because I can manually fail it over and it passes traffic just fine. Is shutting the interface not a good way to test this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;John&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 17:45:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/testing-failover/m-p/1473480#M717733</guid>
      <dc:creator>John Blakley</dc:creator>
      <dc:date>2019-03-11T17:45:44Z</dc:date>
    </item>
    <item>
      <title>Re: Testing failover?</title>
      <link>https://community.cisco.com/t5/network-security/testing-failover/m-p/1473481#M717737</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;John,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If failover does not occur when the interface is close/shut - you have a config issue, you need to make sure the "outside" or any of the interfaces are monitored, you also should define either by the number of interfaces or % of failures the failover will kick in.&amp;nbsp; Including the polling times, hold times etc - you should apply this in your lab an real environment.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&amp;gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 May 2010 16:17:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/testing-failover/m-p/1473481#M717737</guid>
      <dc:creator>andrew.prince</dc:creator>
      <dc:date>2010-05-14T16:17:18Z</dc:date>
    </item>
    <item>
      <title>Re: Testing failover?</title>
      <link>https://community.cisco.com/t5/network-security/testing-failover/m-p/1473482#M717743</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;And just to be clear and clarify the "the interface is close/shut" this cannot be an interface on the PIX/ASA, it has to be the device directly connected to it i.e Switch/Router interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you admin close the "outside" or "inside" or any interface used for monitoring - this is a config change and will be "replicated" to the failover mate, this will not initiate a failover situation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&amp;gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 May 2010 16:35:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/testing-failover/m-p/1473482#M717743</guid>
      <dc:creator>andrew.prince</dc:creator>
      <dc:date>2010-05-14T16:35:49Z</dc:date>
    </item>
    <item>
      <title>Re: Testing failover?</title>
      <link>https://community.cisco.com/t5/network-security/testing-failover/m-p/1473483#M717748</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Andrew. Shutting the interface on the opposite side makes sense. All of the interfaces are monitored by default. I'm pretty confident that in a real environment, the ASA will fail over when I pull the link from the outside interface. I'm trying to reproduce the scenario if the interface itself went out.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm going to recreate my environment in GNS and try to shut the opposite end and see what happens.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;John&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 May 2010 16:43:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/testing-failover/m-p/1473483#M717748</guid>
      <dc:creator>John Blakley</dc:creator>
      <dc:date>2010-05-14T16:43:51Z</dc:date>
    </item>
    <item>
      <title>Re: Testing failover?</title>
      <link>https://community.cisco.com/t5/network-security/testing-failover/m-p/1473484#M717754</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ahhh John,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The GNS3 lab - failover will not work for you in a virtual LAB - it must be an actual physical test lab, sorry I missed the "GNS" reference in the original post &lt;SPAN __jive_emoticon_name="sad" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/images/emoticons/sad.gif"&gt;&lt;/SPAN&gt; .&amp;nbsp; The issue is - the PIX/ASA are virtual machines - and as such "auto" provide ethernet keepalivesand assume a good interface....so shuting the other device down, will not being down the PIX/ASA interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just to double check - fire up a PIX/ASA with no network connections to it in GNS3 and config 1 interface, then open it.&amp;nbsp; I'm pretty sure it will say up/up all the time!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I also think your real life failover test will pass 100%.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&amp;gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 May 2010 17:03:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/testing-failover/m-p/1473484#M717754</guid>
      <dc:creator>andrew.prince</dc:creator>
      <dc:date>2010-05-14T17:03:03Z</dc:date>
    </item>
    <item>
      <title>Re: Testing failover?</title>
      <link>https://community.cisco.com/t5/network-security/testing-failover/m-p/1473485#M717758</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I think you're right &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt; GNS is good for some things, but sometimes real world tests are the only way to prove something really works. I'm installing the standby this Sunday, so I think I'll be fine. In GNS I can manually failover and it works fine....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks Andrew!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;John&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 May 2010 17:08:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/testing-failover/m-p/1473485#M717758</guid>
      <dc:creator>John Blakley</dc:creator>
      <dc:date>2010-05-14T17:08:41Z</dc:date>
    </item>
    <item>
      <title>Re: Testing failover?</title>
      <link>https://community.cisco.com/t5/network-security/testing-failover/m-p/1473486#M717766</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;np - glad to help.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 May 2010 17:47:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/testing-failover/m-p/1473486#M717766</guid>
      <dc:creator>andrew.prince</dc:creator>
      <dc:date>2010-05-14T17:47:01Z</dc:date>
    </item>
  </channel>
</rss>

