<?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 Pix loxks up changing Crypto map statement in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-loxks-up-changing-crypto-map-statement/m-p/355870#M556375</link>
    <description>&lt;P&gt;We have a site to site VPN and we are migrating to a new DSL connection on one side and when I went to remove the crypto map so I could put in the new peer address the pix locks up. I've had this happen before and know that there is a procedure to prevent this but don't know what it is. All I'm trying to do is change the address from the: "crypto map AMLVPN 10 set peer xx.xx.xx.xxx" to the new IP address of the new DSL connection. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 21 Feb 2020 07:40:46 GMT</pubDate>
    <dc:creator>tony.hanson</dc:creator>
    <dc:date>2020-02-21T07:40:46Z</dc:date>
    <item>
      <title>Pix loxks up changing Crypto map statement</title>
      <link>https://community.cisco.com/t5/network-security/pix-loxks-up-changing-crypto-map-statement/m-p/355870#M556375</link>
      <description>&lt;P&gt;We have a site to site VPN and we are migrating to a new DSL connection on one side and when I went to remove the crypto map so I could put in the new peer address the pix locks up. I've had this happen before and know that there is a procedure to prevent this but don't know what it is. All I'm trying to do is change the address from the: "crypto map AMLVPN 10 set peer xx.xx.xx.xxx" to the new IP address of the new DSL connection. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 07:40:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-loxks-up-changing-crypto-map-statement/m-p/355870#M556375</guid>
      <dc:creator>tony.hanson</dc:creator>
      <dc:date>2020-02-21T07:40:46Z</dc:date>
    </item>
    <item>
      <title>Re: Pix loxks up changing Crypto map statement</title>
      <link>https://community.cisco.com/t5/network-security/pix-loxks-up-changing-crypto-map-statement/m-p/355871#M556377</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You have to remove the crypto map from the interface before adding or changing a tunnel.  Otherwise, it will lock up tighter than a drum every time.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;no crypto map AMLVPN interface outside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just be aware it will take down the other tunnels when you do this if they use the same set.  When you have your new statements in, assign it to the outside interface once again.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;crypto map AMLVPN interface outside&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 Oct 2004 12:09:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-loxks-up-changing-crypto-map-statement/m-p/355871#M556377</guid>
      <dc:creator>sbantz</dc:creator>
      <dc:date>2004-10-13T12:09:04Z</dc:date>
    </item>
  </channel>
</rss>

