<?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: Tunnel-groups on ASA in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/tunnel-groups-on-asa/m-p/3870511#M923335</link>
    <description>Great thanks!</description>
    <pubDate>Mon, 10 Jun 2019 20:33:22 GMT</pubDate>
    <dc:creator>CiscoBrownBelt</dc:creator>
    <dc:date>2019-06-10T20:33:22Z</dc:date>
    <item>
      <title>Tunnel-groups on ASA</title>
      <link>https://community.cisco.com/t5/network-security/tunnel-groups-on-asa/m-p/3869225#M923333</link>
      <description>&lt;P&gt;Can you use the same tunnel-group for each IPSEC tunnel you have built on the ASA? Basically, I don't see how or what command associates the tunnel-group with a particular IPSEC tunnel see configs below:&lt;/P&gt;&lt;P&gt;ASA1:&lt;BR /&gt;crypto ikev2 policy 3&lt;BR /&gt;encryption aes&lt;BR /&gt;integrity sha&lt;BR /&gt;group 3&lt;BR /&gt;lifetime seconds 86400&lt;BR /&gt;exit&lt;BR /&gt;crypto ipsec ikev2 ipsec-proposal PH-4&lt;BR /&gt;protocol esp encryption aes-256&lt;BR /&gt;protocol esp integrity sha-1&lt;BR /&gt;exit&lt;BR /&gt;tunnel-group 20.20.20.20 type ipsec-l2l&lt;BR /&gt;tunnel-group 20.20.20.20 ipsec-attributes&lt;BR /&gt;ikev2 local-authentication pre-shared-key ccdp*123&lt;BR /&gt;ikev2 remote-authentication pre-shared-key ccdp*123&lt;BR /&gt;exit&lt;/P&gt;&lt;P&gt;access-list VPN_SiteB_ACL extended permit ip object-group Internal_LAN object SiteB_Internal_Lan log info&lt;BR /&gt;crypto map ASA1-MAP_SiteB 1 match address VPN_SiteB_ACL&lt;BR /&gt;crypto map ASA1-MAP_SiteB 1 set peer 20.20.20.20&lt;BR /&gt;crypto map ASA1-MAP_SiteB 1 set ikev2 ipsec-proposal PH-4&lt;BR /&gt;crypto map ASA1-MAP_SiteB interface Outside&lt;BR /&gt;crypto ikev2 enable Outside&lt;/P&gt;&lt;P&gt;sysopt connection permit-vpn&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 17:12:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/tunnel-groups-on-asa/m-p/3869225#M923333</guid>
      <dc:creator>CiscoBrownBelt</dc:creator>
      <dc:date>2020-02-21T17:12:04Z</dc:date>
    </item>
    <item>
      <title>Re: Tunnel-groups on ASA</title>
      <link>https://community.cisco.com/t5/network-security/tunnel-groups-on-asa/m-p/3870024#M923334</link>
      <description>&lt;P&gt;The tunnel-group definition has the remote peer IP address in it. So does the crypto map section.&lt;/P&gt;
&lt;P&gt;It's that common element that associates it with a given IPsec site-site VPN.&lt;/P&gt;</description>
      <pubDate>Sun, 09 Jun 2019 14:47:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/tunnel-groups-on-asa/m-p/3870024#M923334</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2019-06-09T14:47:50Z</dc:date>
    </item>
    <item>
      <title>Re: Tunnel-groups on ASA</title>
      <link>https://community.cisco.com/t5/network-security/tunnel-groups-on-asa/m-p/3870511#M923335</link>
      <description>Great thanks!</description>
      <pubDate>Mon, 10 Jun 2019 20:33:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/tunnel-groups-on-asa/m-p/3870511#M923335</guid>
      <dc:creator>CiscoBrownBelt</dc:creator>
      <dc:date>2019-06-10T20:33:22Z</dc:date>
    </item>
  </channel>
</rss>

