<?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: L2L VPNs on ASAs and failover question in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/l2l-vpns-on-asas-and-failover-question/m-p/1191758#M875170</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I agree with Jorge, There will be no disruption and I did test it out.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 02 Apr 2009 02:09:17 GMT</pubDate>
    <dc:creator>vikram_anumukonda</dc:creator>
    <dc:date>2009-04-02T02:09:17Z</dc:date>
    <item>
      <title>L2L VPNs on ASAs and failover question</title>
      <link>https://community.cisco.com/t5/network-security/l2l-vpns-on-asas-and-failover-question/m-p/1191755#M875163</link>
      <description>&lt;P&gt;If I have a pair of ASA firewalls terminating several IPSEC vpn L2L connections, and these firewalls are configured for failover, what happens to the active tunnels if a failover occurs? Is there a disruption or is it transparent? Finally, is there any special config required to make it happen?&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 15:03:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/l2l-vpns-on-asas-and-failover-question/m-p/1191755#M875163</guid>
      <dc:creator>mjsully</dc:creator>
      <dc:date>2019-03-11T15:03:15Z</dc:date>
    </item>
    <item>
      <title>Re: L2L VPNs on ASAs and failover question</title>
      <link>https://community.cisco.com/t5/network-security/l2l-vpns-on-asas-and-failover-question/m-p/1191756#M875166</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;The theory  behing Ipsec in ASA A/S architecture is when you configure stateful failover the isakmp and IPsec SA table is passed onto standby, so in theory you should not see disruption in a failover ,  personaly I have yet to test this in a IPsec scenario. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;see stateful failover &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_configuration_example09186a00807dac5f.shtml#statef" target="_blank"&gt;http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_configuration_example09186a00807dac5f.shtml#statef&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Quote from above link -&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The state information passed to the standby unit includes these: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The NAT translation table&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The TCP connection states&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The UDP connection states&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The ARP table&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The Layer 2 bridge table (when it runs in the transparent firewall mode)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The HTTP connection states (if HTTP replication is enabled)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The ISAKMP and IPSec SA table&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The GTP PDP connection database&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Mar 2009 15:57:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/l2l-vpns-on-asas-and-failover-question/m-p/1191756#M875166</guid>
      <dc:creator>JORGE RODRIGUEZ</dc:creator>
      <dc:date>2009-03-11T15:57:33Z</dc:date>
    </item>
    <item>
      <title>Re: L2L VPNs on ASAs and failover question</title>
      <link>https://community.cisco.com/t5/network-security/l2l-vpns-on-asas-and-failover-question/m-p/1191757#M875167</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In my experience, with ASAs what will happen is the SAs will indeed move from the primary to the standby ASA.  The standby ASA becomes the active ASA.  The remote sites still think the original ASA is still up and unfortunately still hold onto their SAs.  These SAs on the remote end will not work.  I speculate this is because the hardware hashs are going to fail on the IPsec integrity checks.  The remote ends manually have to have their SAs purged with a clear crypto sa.  After that, re-initiate interesting traffic, and then your tunnels will come back up on the "new" primary ASA.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 01 Apr 2009 21:54:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/l2l-vpns-on-asas-and-failover-question/m-p/1191757#M875167</guid>
      <dc:creator>cvoisin</dc:creator>
      <dc:date>2009-04-01T21:54:13Z</dc:date>
    </item>
    <item>
      <title>Re: L2L VPNs on ASAs and failover question</title>
      <link>https://community.cisco.com/t5/network-security/l2l-vpns-on-asas-and-failover-question/m-p/1191758#M875170</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I agree with Jorge, There will be no disruption and I did test it out.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 02 Apr 2009 02:09:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/l2l-vpns-on-asas-and-failover-question/m-p/1191758#M875170</guid>
      <dc:creator>vikram_anumukonda</dc:creator>
      <dc:date>2009-04-02T02:09:17Z</dc:date>
    </item>
    <item>
      <title>Re: L2L VPNs on ASAs and failover question</title>
      <link>https://community.cisco.com/t5/network-security/l2l-vpns-on-asas-and-failover-question/m-p/1191759#M875171</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm not sure if you guys are misinformed, but stateful IPsec failover is NOT supported by the ASA.  This was confirmed by my local SE.  Your SAs will need to be purged on the remote side.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Our ASA right now is flaking out on the primary and is failing right now between active and standby states.  The remote VPNs are "staying up"  and there are SAs in both the ASA and the remote VPN site routers.  Unfortunatly as I said the traffic is not passing over the VPN.  So, once I reviewed this with my SE he said you have to go back in and actually remove the SAs from the far end routers and re-initiate interesting traffic.  Voila...it works like cake.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I don't want to disagree with anyone too strongly, but again in my experience it doesn't work.  I did notice that with a 3800 or greater you can do stateful IPsec failover between two routers that are your VPN termination devices, but all PIX and ASA documentation only shows that the SAs are maintained on the standby device.  Nothing in regard to them continuing to work is mentioned.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 02 Apr 2009 03:11:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/l2l-vpns-on-asas-and-failover-question/m-p/1191759#M875171</guid>
      <dc:creator>cvoisin</dc:creator>
      <dc:date>2009-04-02T03:11:07Z</dc:date>
    </item>
    <item>
      <title>Re: L2L VPNs on ASAs and failover question</title>
      <link>https://community.cisco.com/t5/network-security/l2l-vpns-on-asas-and-failover-question/m-p/1191760#M875173</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Please I have already set up a VPN site to site with Asa 5540 . And I want to set up a 2nd VPN but the 2nd VPN is not working. How can I add 2nd VPN with ASA ASDM ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 02 Apr 2009 09:11:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/l2l-vpns-on-asas-and-failover-question/m-p/1191760#M875173</guid>
      <dc:creator>mtoure2009</dc:creator>
      <dc:date>2009-04-02T09:11:44Z</dc:date>
    </item>
  </channel>
</rss>

