<?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 Ah, so what you are saying is in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-multiple-context-pre-routing/m-p/2437406#M267792</link>
    <description>&lt;P&gt;Ah, so what you are saying is that I should just buy a single ASA that is large enough for the next three years and then just replace don't scale.&lt;/P&gt;</description>
    <pubDate>Mon, 07 Apr 2014 23:22:42 GMT</pubDate>
    <dc:creator>dan.letkeman</dc:creator>
    <dc:date>2014-04-07T23:22:42Z</dc:date>
    <item>
      <title>ASA multiple context pre routing</title>
      <link>https://community.cisco.com/t5/network-security/asa-multiple-context-pre-routing/m-p/2437402#M267787</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am trying to understand all of my options for routing to two different ASA's in active/active mode, which requires multiple context mode.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have an existing 4500E switch behind a single ASA 5520 right now, and the default gateway that the 4500E advertises to my internal networks is the ip address of the 5520. &amp;nbsp;I would like to replace the existing 5520 with two 5525-x ASA's and have them setup in active/active mode.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Currently I have 12 locations terminated with fiber to the 4500E and from there its default gateway is the existing single ASA that I have. &amp;nbsp;From what I understand, with the new design I have to make the ASA's into multiple context mode in order to do active/active failover , and load balance between the two ASA's.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What I don't want to have to do is put a policy route on each incoming fiber port and policy route traffic based on source IP. &amp;nbsp;I think this would be a huge waste of resources and complicate the setup on the 4500E. &amp;nbsp;Is there any other way to accomplish this besides policy routing or a separate switch between the ASA's and the 4500E?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;BR /&gt;Dan.&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 04:02:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-multiple-context-pre-routing/m-p/2437402#M267787</guid>
      <dc:creator>dan.letkeman</dc:creator>
      <dc:date>2019-03-12T04:02:24Z</dc:date>
    </item>
    <item>
      <title>While you CAN do what you're</title>
      <link>https://community.cisco.com/t5/network-security/asa-multiple-context-pre-routing/m-p/2437403#M267788</link>
      <description>&lt;P&gt;While you CAN do what you're describing with an Active-Active multiple context pair, that's not really what those features are designed for.&lt;/P&gt;&lt;P&gt;You would have to, as you surmised, handle the routing downstream using something like PBR (or possibly VRFs). I'd stay away from that solution as it would introduce a fair amount of complexity in your core with little to no added value (in my opinion).&lt;/P&gt;&lt;P&gt;A 5525-X already will have 1.5-2x the performance of your old 5520. The second unit will give you high availability in an HA pair.&lt;/P&gt;&lt;P&gt;If you're feeling adventurous, you can now (as of 9.1(4)) run a 2-member cluster with the 5500-X series below the 5585. That will give you the increased performance (~50% boost in connection/sec, 70% boost in total throughput vs. a single unit) while sticking with a single context. It does have the downside though in the event of a single member failure of throttling you back to the throughput of a single unit.&lt;/P&gt;</description>
      <pubDate>Mon, 07 Apr 2014 18:20:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-multiple-context-pre-routing/m-p/2437403#M267788</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2014-04-07T18:20:44Z</dc:date>
    </item>
    <item>
      <title>What else would you use</title>
      <link>https://community.cisco.com/t5/network-security/asa-multiple-context-pre-routing/m-p/2437404#M267789</link>
      <description>&lt;P&gt;What else would you use active/active for? &amp;nbsp;I'm looking at it from a stand point of being able to scale one ASA 5525 into two ASA 5525 for double the throughput instead of having to buy a 5545.&lt;/P&gt;&lt;P&gt;Hmmm, so I would have to setup a switch cluster between the 4500E and the ASA's.....that would add too much cost...&lt;/P&gt;&lt;P&gt;Clustering is of no use, as AVC / WSE / VPN is not available on the secondary ASA then. &amp;nbsp;So there would be no point. &amp;nbsp;Active/active mode at lease allows for use of all of the features.&lt;/P&gt;</description>
      <pubDate>Mon, 07 Apr 2014 19:06:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-multiple-context-pre-routing/m-p/2437404#M267789</guid>
      <dc:creator>dan.letkeman</dc:creator>
      <dc:date>2014-04-07T19:06:49Z</dc:date>
    </item>
    <item>
      <title>I see multiple context most</title>
      <link>https://community.cisco.com/t5/network-security/asa-multiple-context-pre-routing/m-p/2437405#M267790</link>
      <description>&lt;P&gt;I see multiple context most often used where I have distinct security policies, often in multi-tenant (or distinct business unit) use of a given firewall. In such a case, Active-Active allows us to spread the load across the units while having redundancy.&lt;/P&gt;&lt;P&gt;Most installations I have seen (actually all - and I've worked with hundreds of ASAs in dozens of enterprises) use bigger firewalls to get more throughput. A few use VPN clustering or round robin DNS for remote access VPN gateways on the ASA platform. The few Active-Active setups I've come across have all had one of the use cases I mentioned just now.&lt;/P&gt;&lt;P&gt;You're right that clustering does have a number of features that don't work in distributed mode.&lt;/P&gt;</description>
      <pubDate>Mon, 07 Apr 2014 23:09:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-multiple-context-pre-routing/m-p/2437405#M267790</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2014-04-07T23:09:30Z</dc:date>
    </item>
    <item>
      <title>Ah, so what you are saying is</title>
      <link>https://community.cisco.com/t5/network-security/asa-multiple-context-pre-routing/m-p/2437406#M267792</link>
      <description>&lt;P&gt;Ah, so what you are saying is that I should just buy a single ASA that is large enough for the next three years and then just replace don't scale.&lt;/P&gt;</description>
      <pubDate>Mon, 07 Apr 2014 23:22:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-multiple-context-pre-routing/m-p/2437406#M267792</guid>
      <dc:creator>dan.letkeman</dc:creator>
      <dc:date>2014-04-07T23:22:42Z</dc:date>
    </item>
    <item>
      <title>Well I'm on the post-sales</title>
      <link>https://community.cisco.com/t5/network-security/asa-multiple-context-pre-routing/m-p/2437407#M267796</link>
      <description>&lt;P&gt;Well I'm on the post-sales side but the pre-sales guys would most likely advise you that way - that is consistent with the Cisco reference approaches. It is how I've almost always seen it in the production settings I've worked on.&lt;/P&gt;&lt;P&gt;Your decision should take what anyone says as one input in a decision making process that is informed by your requirements and projections in the context of your business environment.&lt;/P&gt;</description>
      <pubDate>Tue, 08 Apr 2014 01:05:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-multiple-context-pre-routing/m-p/2437407#M267796</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2014-04-08T01:05:57Z</dc:date>
    </item>
  </channel>
</rss>

