<?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 switch requirements for active/active failover configuration on  in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/switch-requirements-for-active-active-failover-configuration-on/m-p/2129787#M392223</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;1. yes, because both ASA are used at the same time, BUT: you have to remember that it's difficult to divide traffic by exactly 50% and assign it to context. Remember that you can manage resources assigned to contexts:&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.cisco.com/en/US/docs/security/asa/asa84/configuration/guide/mode_contexts.html#wp1195334"&gt;http://www.cisco.com/en/US/docs/security/asa/asa84/configuration/guide/mode_contexts.html#wp1195334&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. It depends on type of deployment. Usually you use separate interfaces in contexts (for example vlans). Even when you share interface between contexts you use "mac-address auto". Then the same shared interface has different MAC address in each context - and upstream/downstream switch do not have any problems switching traffic to separate mac address. So - you do not need VSS to have Active-Active working correctly.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;---&lt;/P&gt;&lt;P&gt;Michal&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 24 Jan 2013 17:34:15 GMT</pubDate>
    <dc:creator>Michal Garcarz</dc:creator>
    <dc:date>2013-01-24T17:34:15Z</dc:date>
    <item>
      <title>switch requirements for active/active failover configuration on ASA</title>
      <link>https://community.cisco.com/t5/network-security/switch-requirements-for-active-active-failover-configuration-on/m-p/2129785#M392214</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a basic setup of two 6509 chassis (non-VSS) with an etherchannel trunk between them.&amp;nbsp;&amp;nbsp; I have a pair of ASA 5585-X configured for active/standby (each appliance inside interface is connected to one 6509).&amp;nbsp; I also have a pair of 3560E switches also an etherchannel trunk between them and the outside interfaces of each ASA connect to each.&amp;nbsp;&amp;nbsp; I want to explore active/active failover and what it can do for me.&amp;nbsp; My questions:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) does this mean I get the performance of both ASAs (meaning if one appliance handles max 2 million connections, would active/active permit 2 million to each appliance or would it still be just 2 million total?).&amp;nbsp; Obviously I won't see combined throughput but am curious about the connection limit since theoretically I am now putting two appliances into use with active/active?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2) does the 6509 need to be configured for VSS in order for active/active to work properly on the ASA or can I still keep the 6509s configured as they are?&amp;nbsp; How will packets going into one ASA to the switch will know how to get back to the same ASA if active/active?&amp;nbsp; Likewise with the 3560E on the outside.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 00:51:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/switch-requirements-for-active-active-failover-configuration-on/m-p/2129785#M392214</guid>
      <dc:creator>DannyHuston</dc:creator>
      <dc:date>2019-03-12T00:51:59Z</dc:date>
    </item>
    <item>
      <title>switch requirements for active/active failover configuration on</title>
      <link>https://community.cisco.com/t5/network-security/switch-requirements-for-active-active-failover-configuration-on/m-p/2129786#M392217</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P style="background-color: #ffffff; border-collapse: collapse; font-size: 12px; list-style: none; font-family: Arial, verdana, sans-serif;"&gt;1) does this mean I get the performance of both ASAs (meaning if one appliance handles max 2 million connections, would active/active permit 2 million to each appliance or would it still be just 2 million total?).&amp;nbsp; Obviously I won't see combined throughput but am curious about the connection limit since theoretically I am now putting two appliances into use with active/active?&lt;/P&gt;&lt;P&gt; A/ Well that depends on the amount of traffic one context is using.&lt;/P&gt;&lt;P&gt;Example:&lt;/P&gt;&lt;P&gt;You have context A and B, and of course each of the ASA's is active for one. so you will split the amount of data between the 2 units so you can see the performance improvement &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/4.5.4/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="background-color: #ffffff; border-collapse: collapse; font-size: 12px; list-style: none; font-family: Arial, verdana, sans-serif;"&gt;2) does the 6509 need to be configured for VSS in order for active/active to work properly on the ASA or can I still keep the 6509s configured as they are?&amp;nbsp; How will packets going into one ASA to the switch will know how to get back to the same ASA if active/active?&amp;nbsp; Likewise with the 3560E on the outside.&lt;/P&gt;&lt;P style="background-color: #ffffff; border-collapse: collapse; font-size: 12px; list-style: none; font-family: Arial, verdana, sans-serif; min-height: 8pt; height: 8pt;"&gt; A/ I am not sure I get the whole picture of your desing but let me think.....................each interface on the failover group will have it's own virtual mac-address so that is where the switch will know where to send the packets back.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let me know if you have any other question&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Julio&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 24 Jan 2013 17:33:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/switch-requirements-for-active-active-failover-configuration-on/m-p/2129786#M392217</guid>
      <dc:creator>Julio Carvajal</dc:creator>
      <dc:date>2013-01-24T17:33:45Z</dc:date>
    </item>
    <item>
      <title>switch requirements for active/active failover configuration on</title>
      <link>https://community.cisco.com/t5/network-security/switch-requirements-for-active-active-failover-configuration-on/m-p/2129787#M392223</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;1. yes, because both ASA are used at the same time, BUT: you have to remember that it's difficult to divide traffic by exactly 50% and assign it to context. Remember that you can manage resources assigned to contexts:&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.cisco.com/en/US/docs/security/asa/asa84/configuration/guide/mode_contexts.html#wp1195334"&gt;http://www.cisco.com/en/US/docs/security/asa/asa84/configuration/guide/mode_contexts.html#wp1195334&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. It depends on type of deployment. Usually you use separate interfaces in contexts (for example vlans). Even when you share interface between contexts you use "mac-address auto". Then the same shared interface has different MAC address in each context - and upstream/downstream switch do not have any problems switching traffic to separate mac address. So - you do not need VSS to have Active-Active working correctly.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;---&lt;/P&gt;&lt;P&gt;Michal&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 24 Jan 2013 17:34:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/switch-requirements-for-active-active-failover-configuration-on/m-p/2129787#M392223</guid>
      <dc:creator>Michal Garcarz</dc:creator>
      <dc:date>2013-01-24T17:34:15Z</dc:date>
    </item>
    <item>
      <title>switch requirements for active/active failover configuration on</title>
      <link>https://community.cisco.com/t5/network-security/switch-requirements-for-active-active-failover-configuration-on/m-p/2129788#M392226</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You need to keep this in mind:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ASA can only do Active/Active on a context basis.&amp;nbsp; In other words, Active/Active in ASA similar to using HSRP with multiple HSRP group.&amp;nbsp; Therefore, if you have a single source and single destination using different services such as http, https, ssh, telnet, it will bind to a single context and Active/Active will NOT help you.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 25 Jan 2013 03:02:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/switch-requirements-for-active-active-failover-configuration-on/m-p/2129788#M392226</guid>
      <dc:creator>david.tran</dc:creator>
      <dc:date>2013-01-25T03:02:10Z</dc:date>
    </item>
  </channel>
</rss>

