<?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 ASAv and Juniper vSRX in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asav-and-juniper-vsrx/m-p/4650101#M1091832</link>
    <description>&lt;P&gt;Hello all,&lt;/P&gt;&lt;P&gt;I need some assistance trying to get a tunnel to work. from the debug I see my IPSec proposals are not matching. this is a lab setup. ASA has only 2 interfaces configured with INSIDE/outside and there is only 1 tunnel. transform set options are.&lt;/P&gt;&lt;P&gt;ASA(config-tunnel-ipsec)# crypto ipsec ikev1 transform-set ASA-cSRX ?&lt;/P&gt;&lt;P&gt;configure mode commands/options:&lt;BR /&gt;esp-3des esp 3des encryption&lt;BR /&gt;esp-aes esp aes 128 encryption&lt;BR /&gt;esp-aes-192 esp aes 192 encryption&lt;BR /&gt;esp-aes-256 esp aes 256 encryption&lt;BR /&gt;esp-des esp des encryption&lt;BR /&gt;esp-md5-hmac esp md5 authentication&lt;BR /&gt;esp-none esp no authentication&lt;BR /&gt;esp-null esp null encryption&lt;BR /&gt;esp-sha-hmac esp sha authentication&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;and on the juniper&lt;BR /&gt;Possible completions: Authentication&lt;BR /&gt;hmac-md5-96 HMAC-MD5-96 authentication algorithm&lt;BR /&gt;hmac-sha-256-128 HMAC-SHA-256-128 authentication algorithm&lt;BR /&gt;hmac-sha1-96 HMAC-SHA1-96 authentication algorithm&lt;/P&gt;&lt;P&gt;Possible completions: Encryption&lt;BR /&gt;3des-cbc 3DES-CBC encryption algorithm&lt;BR /&gt;aes-128-cbc AES-CBC 128-bit encryption algorithm&lt;BR /&gt;aes-128-gcm AES-GCM 128-bit encryption algorithm&lt;BR /&gt;aes-192-cbc AES-CBC 192-bit encryption algorithm&lt;BR /&gt;aes-192-gcm AES-GCM 192-bit encryption algorithm&lt;BR /&gt;aes-256-cbc AES-CBC 256-bit encryption algorithm&lt;BR /&gt;aes-256-gcm AES-GCM 256-bit encryption algorithm&lt;BR /&gt;des-cbc DES-CBC encryption algorithm&lt;/P&gt;&lt;P&gt;ASA transformset : esp-sha-hmac esp-aes-256&amp;nbsp;&lt;/P&gt;&lt;P&gt;Juniper&lt;BR /&gt;protocol esp;&lt;BR /&gt;authentication-algorithm hmac-sha1-96;&lt;BR /&gt;encryption-algorithm aes-256-cbc;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;I am assuming :&amp;nbsp; hmac-sha1-96 is not = esp-sha-hmac and esp-aes-256 not = aes-256-cbc&lt;/P&gt;&lt;P&gt;thx a lot&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 14 Jul 2022 08:08:04 GMT</pubDate>
    <dc:creator>Lance Wendel</dc:creator>
    <dc:date>2022-07-14T08:08:04Z</dc:date>
    <item>
      <title>ASAv and Juniper vSRX</title>
      <link>https://community.cisco.com/t5/network-security/asav-and-juniper-vsrx/m-p/4650101#M1091832</link>
      <description>&lt;P&gt;Hello all,&lt;/P&gt;&lt;P&gt;I need some assistance trying to get a tunnel to work. from the debug I see my IPSec proposals are not matching. this is a lab setup. ASA has only 2 interfaces configured with INSIDE/outside and there is only 1 tunnel. transform set options are.&lt;/P&gt;&lt;P&gt;ASA(config-tunnel-ipsec)# crypto ipsec ikev1 transform-set ASA-cSRX ?&lt;/P&gt;&lt;P&gt;configure mode commands/options:&lt;BR /&gt;esp-3des esp 3des encryption&lt;BR /&gt;esp-aes esp aes 128 encryption&lt;BR /&gt;esp-aes-192 esp aes 192 encryption&lt;BR /&gt;esp-aes-256 esp aes 256 encryption&lt;BR /&gt;esp-des esp des encryption&lt;BR /&gt;esp-md5-hmac esp md5 authentication&lt;BR /&gt;esp-none esp no authentication&lt;BR /&gt;esp-null esp null encryption&lt;BR /&gt;esp-sha-hmac esp sha authentication&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;and on the juniper&lt;BR /&gt;Possible completions: Authentication&lt;BR /&gt;hmac-md5-96 HMAC-MD5-96 authentication algorithm&lt;BR /&gt;hmac-sha-256-128 HMAC-SHA-256-128 authentication algorithm&lt;BR /&gt;hmac-sha1-96 HMAC-SHA1-96 authentication algorithm&lt;/P&gt;&lt;P&gt;Possible completions: Encryption&lt;BR /&gt;3des-cbc 3DES-CBC encryption algorithm&lt;BR /&gt;aes-128-cbc AES-CBC 128-bit encryption algorithm&lt;BR /&gt;aes-128-gcm AES-GCM 128-bit encryption algorithm&lt;BR /&gt;aes-192-cbc AES-CBC 192-bit encryption algorithm&lt;BR /&gt;aes-192-gcm AES-GCM 192-bit encryption algorithm&lt;BR /&gt;aes-256-cbc AES-CBC 256-bit encryption algorithm&lt;BR /&gt;aes-256-gcm AES-GCM 256-bit encryption algorithm&lt;BR /&gt;des-cbc DES-CBC encryption algorithm&lt;/P&gt;&lt;P&gt;ASA transformset : esp-sha-hmac esp-aes-256&amp;nbsp;&lt;/P&gt;&lt;P&gt;Juniper&lt;BR /&gt;protocol esp;&lt;BR /&gt;authentication-algorithm hmac-sha1-96;&lt;BR /&gt;encryption-algorithm aes-256-cbc;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;I am assuming :&amp;nbsp; hmac-sha1-96 is not = esp-sha-hmac and esp-aes-256 not = aes-256-cbc&lt;/P&gt;&lt;P&gt;thx a lot&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 14 Jul 2022 08:08:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asav-and-juniper-vsrx/m-p/4650101#M1091832</guid>
      <dc:creator>Lance Wendel</dc:creator>
      <dc:date>2022-07-14T08:08:04Z</dc:date>
    </item>
    <item>
      <title>Re: ASAv and Juniper vSRX</title>
      <link>https://community.cisco.com/t5/network-security/asav-and-juniper-vsrx/m-p/4650229#M1091837</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;- Check this&amp;nbsp;&lt;A href="https://www.youtube.com/watch?v=OF6CuYOFQSM" target="_blank"&gt;https://www.youtube.com/watch?v=OF6CuYOFQSM&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;M.&lt;/P&gt;</description>
      <pubDate>Thu, 14 Jul 2022 12:11:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asav-and-juniper-vsrx/m-p/4650229#M1091837</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2022-07-14T12:11:49Z</dc:date>
    </item>
    <item>
      <title>Re: ASAv and Juniper vSRX</title>
      <link>https://community.cisco.com/t5/network-security/asav-and-juniper-vsrx/m-p/4650318#M1091843</link>
      <description>&lt;P&gt;Thank you for the link, will check this. I guess IKEv1 is old. there are clients who would want to have an Ikev1 solution.&lt;/P&gt;</description>
      <pubDate>Thu, 14 Jul 2022 14:11:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asav-and-juniper-vsrx/m-p/4650318#M1091843</guid>
      <dc:creator>Lance Wendel</dc:creator>
      <dc:date>2022-07-14T14:11:14Z</dc:date>
    </item>
    <item>
      <title>Re: ASAv and Juniper vSRX</title>
      <link>https://community.cisco.com/t5/network-security/asav-and-juniper-vsrx/m-p/4650364#M1091844</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/323057"&gt;@Lance Wendel&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;From the JUNOS documentation:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;UL class="ul"&gt;
&lt;LI class="li"&gt;
&lt;P class="p"&gt;The local identity and remote identity make up the proxy ID for the SA.&lt;/P&gt;
&lt;P class="p"&gt;A proxy ID mismatch is one of the most common causes for a Phase 2 failure. If no IPsec SA is listed, confirm that Phase 2 proposals, including the proxy ID settings, are correct for both peers. For route-based VPNs, the default proxy ID is local=0.0.0.0/0, remote=0.0.0.0/0, and service=any. Issues can occur with multiple route-based VPNs from the same peer IP. In this case, a unique proxy ID for each IPsec SA must be specified. &lt;STRONG&gt;&lt;EM&gt;For some third-party vendors, the proxy ID must be manually entered to match.&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;A href="https://www.juniper.net/documentation/us/en/software/junos/vpn-ipsec/topics/topic-map/security-ipsec-vpn-configuration-overview.html" target="_blank"&gt;https://www.juniper.net/documentation/us/en/software/junos/vpn-ipsec/topics/topic-map/security-ipsec-vpn-configuration-overview.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;</description>
      <pubDate>Thu, 14 Jul 2022 14:51:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asav-and-juniper-vsrx/m-p/4650364#M1091844</guid>
      <dc:creator>Harold Ritter</dc:creator>
      <dc:date>2022-07-14T14:51:20Z</dc:date>
    </item>
    <item>
      <title>Re: ASAv and Juniper vSRX</title>
      <link>https://community.cisco.com/t5/network-security/asav-and-juniper-vsrx/m-p/4650367#M1091845</link>
      <description>HI Harold,&lt;BR /&gt;Thanks for the reply, the config on both are the same including the proxy-id. Only thing that goes through my mind whether the auth and encryption keys are the same&lt;BR /&gt;ASA has for an example esp-aes-256 and on junos has esp-aes-256-cbc&lt;BR /&gt;</description>
      <pubDate>Thu, 14 Jul 2022 14:57:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asav-and-juniper-vsrx/m-p/4650367#M1091845</guid>
      <dc:creator>Lance Wendel</dc:creator>
      <dc:date>2022-07-14T14:57:44Z</dc:date>
    </item>
  </channel>
</rss>

