<?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: ASA to ASA Link (Cable) in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-to-asa-link-cable/m-p/4778840#M1098033</link>
    <description>&lt;P&gt;yes I’m trying to add internal static routes, I’ve got some full tunnel vpn to setup and I’ll get the Config over … thanks for the help very much appreciated &lt;span class="lia-unicode-emoji" title=":thumbs_up:"&gt;👍&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 20 Feb 2023 22:12:04 GMT</pubDate>
    <dc:creator>machine23</dc:creator>
    <dc:date>2023-02-20T22:12:04Z</dc:date>
    <item>
      <title>ASA to ASA Link (Cable)</title>
      <link>https://community.cisco.com/t5/network-security/asa-to-asa-link-cable/m-p/4778724#M1098017</link>
      <description>&lt;P&gt;I’ve got 2 ASA’s side by side and it’s connected via IPsec - it works great&amp;nbsp;&lt;/P&gt;&lt;P&gt;Since they in the same site - I’d like to use a physical connection (faster/secure) &amp;nbsp;and link the 2 firewalls and connect the internal networks on both ASA’s&lt;/P&gt;&lt;P&gt;So what is the best way to do it ?&amp;nbsp;&lt;BR /&gt;Iam thinking of giving 1 interface on each an ip on the same subnet and static route ?&amp;nbsp;&lt;BR /&gt;Please advise&amp;nbsp;&lt;/P&gt;&lt;P&gt;thanks &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 20 Feb 2023 18:56:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-to-asa-link-cable/m-p/4778724#M1098017</guid>
      <dc:creator>machine23</dc:creator>
      <dc:date>2023-02-20T18:56:00Z</dc:date>
    </item>
    <item>
      <title>Re: ASA to ASA Link (Cable)</title>
      <link>https://community.cisco.com/t5/network-security/asa-to-asa-link-cable/m-p/4778727#M1098018</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/855445"&gt;@machine23&lt;/a&gt; you can physically connect the interfaces, configure an IP address in the same network, configure routing (static/dynamic) and configure the access control list to pertmit/deny traffic accordingly.&lt;/P&gt;
&lt;P&gt;Another option, if they are physically in the same location, you could make them an HA failover pair for resilency and just configure the 2 networks on different interfaces.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 20 Feb 2023 19:01:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-to-asa-link-cable/m-p/4778727#M1098018</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2023-02-20T19:01:29Z</dc:date>
    </item>
    <item>
      <title>Re: ASA to ASA Link (Cable)</title>
      <link>https://community.cisco.com/t5/network-security/asa-to-asa-link-cable/m-p/4778732#M1098019</link>
      <description>&lt;P&gt;Thanks Rob for the input … I will try that &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 20 Feb 2023 19:19:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-to-asa-link-cable/m-p/4778732#M1098019</guid>
      <dc:creator>machine23</dc:creator>
      <dc:date>2023-02-20T19:19:26Z</dc:date>
    </item>
    <item>
      <title>Re: ASA to ASA Link (Cable)</title>
      <link>https://community.cisco.com/t5/network-security/asa-to-asa-link-cable/m-p/4778733#M1098020</link>
      <description>&lt;P&gt;connect internal network to both ASA you need to run ASA HA&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 20 Feb 2023 19:20:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-to-asa-link-cable/m-p/4778733#M1098020</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2023-02-20T19:20:36Z</dc:date>
    </item>
    <item>
      <title>Re: ASA to ASA Link (Cable)</title>
      <link>https://community.cisco.com/t5/network-security/asa-to-asa-link-cable/m-p/4778824#M1098029</link>
      <description>&lt;P&gt;So I connected them and when adding routes it says route already exists ( from the site to site I think )&amp;nbsp;&lt;/P&gt;&lt;P&gt;HA seems the-logical option ..&lt;/P&gt;&lt;P&gt;For HA connect both internal networks &amp;nbsp;to the active and configure the other as standby &amp;nbsp;?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 20 Feb 2023 21:50:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-to-asa-link-cable/m-p/4778824#M1098029</guid>
      <dc:creator>machine23</dc:creator>
      <dc:date>2023-02-20T21:50:11Z</dc:date>
    </item>
    <item>
      <title>Re: ASA to ASA Link (Cable)</title>
      <link>https://community.cisco.com/t5/network-security/asa-to-asa-link-cable/m-p/4778829#M1098030</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/855445"&gt;@machine23&lt;/a&gt; it depends what static route you are referring to. You would not need a static route for the outside interface of the other ASA, it's directly connected. You need static routes for the internal networks. It would be helpful to provide this information so we know what you've configured.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Yes, you could configure as Active/Standby, with each network on a separate interface. Example - &lt;A href="https://integratingit.wordpress.com/2016/08/12/configuring-cisco-asa-activestandby-failover/" target="_blank"&gt;https://integratingit.wordpress.com/2016/08/12/configuring-cisco-asa-activestandby-failover/&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 20 Feb 2023 21:55:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-to-asa-link-cable/m-p/4778829#M1098030</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2023-02-20T21:55:08Z</dc:date>
    </item>
    <item>
      <title>Re: ASA to ASA Link (Cable)</title>
      <link>https://community.cisco.com/t5/network-security/asa-to-asa-link-cable/m-p/4778834#M1098032</link>
      <description>&lt;P&gt;If you share your network topology it is better&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 20 Feb 2023 22:00:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-to-asa-link-cable/m-p/4778834#M1098032</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2023-02-20T22:00:45Z</dc:date>
    </item>
    <item>
      <title>Re: ASA to ASA Link (Cable)</title>
      <link>https://community.cisco.com/t5/network-security/asa-to-asa-link-cable/m-p/4778840#M1098033</link>
      <description>&lt;P&gt;yes I’m trying to add internal static routes, I’ve got some full tunnel vpn to setup and I’ll get the Config over … thanks for the help very much appreciated &lt;span class="lia-unicode-emoji" title=":thumbs_up:"&gt;👍&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 20 Feb 2023 22:12:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-to-asa-link-cable/m-p/4778840#M1098033</guid>
      <dc:creator>machine23</dc:creator>
      <dc:date>2023-02-20T22:12:04Z</dc:date>
    </item>
  </channel>
</rss>

