<?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 ACE 30 Module Active-Active configuration in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/ace-30-module-active-active-configuration/m-p/1882148#M36638</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Divya!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It should work assuming the following:&lt;/P&gt;&lt;P&gt; 1.) You have a trunk/portchannel between the ACE's will all vlans each context is using including 999 for FT)&lt;/P&gt;&lt;P&gt; 2.) You are using bridged mode on ACE or one-armed with on alias. OR you are using routed mode with an alias IP that is used as the server gateway. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; Can you login to the admin context on each ACE and issue "show ft group detail" and send it back to the alias? Also, "show run interface"/"show run rserver" from each context would be useful to see the way you have the configuration setup.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 21 Mar 2012 19:15:01 GMT</pubDate>
    <dc:creator>chrhiggi</dc:creator>
    <dc:date>2012-03-21T19:15:01Z</dc:date>
    <item>
      <title>ACE 30 Module Active-Active configuration</title>
      <link>https://community.cisco.com/t5/application-networking/ace-30-module-active-active-configuration/m-p/1882147#M36637</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have two ACE 30 module in two Cat 6k with multiple contexts. And our requirement is to have both the boxes active for some context. We have configured the ft vlan, ft peer and ft group for each context on ACE level. And on Cat 6k, L2 vlan is created for ft and mapped with ACE service module with svlvc command. The interface on switch used for ft is configured as Access port with ft vlan. But when we try to do Failover testing by shutting down the upstream link of ACE2, the active context on the ACE2 is not failing over to ACE1. Let me know whether we need to do any additional configuration to achieve this.? . The running configuration is as below,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;@ Cat 6K,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;Vlan 999&lt;/P&gt;&lt;P&gt;name ft_vlan&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;svclc multiple-vlan-interfaces&lt;/P&gt;&lt;P&gt;svclc module 2 vlan-group 100&lt;/P&gt;&lt;P&gt;svclc vlan-group 100&amp;nbsp; 201,203, 999&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;int gi 1/3&lt;/P&gt;&lt;P&gt;switchport&lt;/P&gt;&lt;P&gt;switchport mode access&lt;/P&gt;&lt;P&gt;switchport access vlan 999&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;@ ACE 30,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ft interface vlan 999&lt;BR /&gt;&amp;nbsp; ip address 2.1.1.1 255.255.255.252&lt;BR /&gt;&amp;nbsp; peer ip address 2.1.1.2 255.255.255.252&lt;BR /&gt;&amp;nbsp; no shutdown&lt;/P&gt;&lt;P&gt;ft peer 1&lt;BR /&gt;&amp;nbsp; heartbeat interval 100&lt;BR /&gt;&amp;nbsp; heartbeat count 10&lt;BR /&gt;&amp;nbsp; ft-interface vlan 999&lt;BR /&gt;ft group 1&lt;BR /&gt;&amp;nbsp; peer 1&lt;BR /&gt;&amp;nbsp; priority 105&lt;BR /&gt;&amp;nbsp; peer priority 90&lt;BR /&gt;&amp;nbsp; associate-context Admin&lt;BR /&gt;&amp;nbsp; inservice&lt;BR /&gt;&amp;nbsp; &lt;BR /&gt;ft track interface INT-VLAN-203&lt;BR /&gt;&amp;nbsp; track-interface vlan 203&lt;BR /&gt;&amp;nbsp; priority 100&lt;BR /&gt;&amp;nbsp; peer priority 50&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;ft group 2&lt;/P&gt;&lt;P&gt;&amp;nbsp; peer 1&lt;/P&gt;&lt;P&gt;&amp;nbsp; priority 105&lt;/P&gt;&lt;P&gt;&amp;nbsp; peer priority 90&lt;/P&gt;&lt;P&gt;&amp;nbsp; associate-context Context1&lt;/P&gt;&lt;P&gt;&amp;nbsp; inservice&lt;/P&gt;&lt;P&gt;ft group 3&lt;/P&gt;&lt;P&gt;&amp;nbsp; peer 1&lt;/P&gt;&lt;P&gt;&amp;nbsp; priority 90&lt;/P&gt;&lt;P&gt;&amp;nbsp; peer priority 105&lt;/P&gt;&lt;P&gt;&amp;nbsp; associate-context Context2&lt;/P&gt;&lt;P&gt;&amp;nbsp; inservice&lt;/P&gt;&lt;P&gt;ft group 4&lt;/P&gt;&lt;P&gt;&amp;nbsp; peer 1&lt;/P&gt;&lt;P&gt;&amp;nbsp; priority 105&lt;/P&gt;&lt;P&gt;&amp;nbsp; peer priority 90&lt;/P&gt;&lt;P&gt;&amp;nbsp; associate-context Context3&lt;/P&gt;&lt;P&gt;&amp;nbsp; inservice&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance,&lt;/P&gt;&lt;P&gt;Divya&lt;/P&gt;</description>
      <pubDate>Tue, 13 Mar 2012 09:56:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/ace-30-module-active-active-configuration/m-p/1882147#M36637</guid>
      <dc:creator>divyaponnathithan</dc:creator>
      <dc:date>2012-03-13T09:56:11Z</dc:date>
    </item>
    <item>
      <title>ACE 30 Module Active-Active configuration</title>
      <link>https://community.cisco.com/t5/application-networking/ace-30-module-active-active-configuration/m-p/1882148#M36638</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Divya!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It should work assuming the following:&lt;/P&gt;&lt;P&gt; 1.) You have a trunk/portchannel between the ACE's will all vlans each context is using including 999 for FT)&lt;/P&gt;&lt;P&gt; 2.) You are using bridged mode on ACE or one-armed with on alias. OR you are using routed mode with an alias IP that is used as the server gateway. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; Can you login to the admin context on each ACE and issue "show ft group detail" and send it back to the alias? Also, "show run interface"/"show run rserver" from each context would be useful to see the way you have the configuration setup.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Mar 2012 19:15:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/ace-30-module-active-active-configuration/m-p/1882148#M36638</guid>
      <dc:creator>chrhiggi</dc:creator>
      <dc:date>2012-03-21T19:15:01Z</dc:date>
    </item>
  </channel>
</rss>

