<?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 Backup remote peer in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/backup-remote-peer/m-p/1276203#M969797</link>
    <description>&lt;P&gt;I need to configure my ASA to get a second IP-peer to be as a backup for the VPN IPSec tunnel if the primary fails.&lt;/P&gt;&lt;P&gt;Any one can help?&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;</description>
    <pubDate>Fri, 21 Feb 2020 11:47:06 GMT</pubDate>
    <dc:creator>omar.elmohri</dc:creator>
    <dc:date>2020-02-21T11:47:06Z</dc:date>
    <item>
      <title>Backup remote peer</title>
      <link>https://community.cisco.com/t5/network-security/backup-remote-peer/m-p/1276203#M969797</link>
      <description>&lt;P&gt;I need to configure my ASA to get a second IP-peer to be as a backup for the VPN IPSec tunnel if the primary fails.&lt;/P&gt;&lt;P&gt;Any one can help?&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 11:47:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/backup-remote-peer/m-p/1276203#M969797</guid>
      <dc:creator>omar.elmohri</dc:creator>
      <dc:date>2020-02-21T11:47:06Z</dc:date>
    </item>
    <item>
      <title>Re: Backup remote peer</title>
      <link>https://community.cisco.com/t5/network-security/backup-remote-peer/m-p/1276204#M969799</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Set a second peer in the crypto map:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"Configuring multiple peers is equivalent to providing a fallback list. For each tunnel, the security appliance attempts to negotiate with the first peer in the list. If that peer does not respond, the security appliance works its way down the list until either a peer responds or there are no more peers in the list."&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/docs/security/asa/asa80/command/reference/c5.html#wp2193237" target="_blank"&gt;http://www.cisco.com/en/US/docs/security/asa/asa80/command/reference/c5.html#wp2193237&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the tunnel is already active and then the first headend fails, it will take a few minutes for the DPDs (dead peer detect) to sense the tunnel is down, but after this the failover should happen automatically; when the primary tunnel negotiations fails, it should go to the backup peer configured.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-heather&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Nov 2009 04:06:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/backup-remote-peer/m-p/1276204#M969799</guid>
      <dc:creator>hdashnau</dc:creator>
      <dc:date>2009-11-09T04:06:41Z</dc:date>
    </item>
  </channel>
</rss>

