<?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 4710 FT failover failure in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/ace-4710-ft-failover-failure/m-p/1883343#M36656</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Jim,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks, I wasn't aware that preempt needed to be enabled for FT Tracking to work.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I believe I should be okay on the decrement, I have the FT primary at 210 and the peer at 120, is that what you are referring to?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Dave&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 23 Mar 2012 19:15:35 GMT</pubDate>
    <dc:creator>dpastor</dc:creator>
    <dc:date>2012-03-23T19:15:35Z</dc:date>
    <item>
      <title>ACE 4710 FT failover failure</title>
      <link>https://community.cisco.com/t5/application-networking/ace-4710-ft-failover-failure/m-p/1883341#M36654</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am running redundant ACE 4710 appliances running A3(2.7).&amp;nbsp; I have five FT groups configured along with FT Tracking and when the vlans fail due to physical links being down, the contexts to do not failover.&amp;nbsp; If one of the ACE boxes fail completely, failover works fine.&amp;nbsp; I have included the FT config from one of the contexts below.&amp;nbsp; I have a case open with TAC and the Engineer is suggesting the use of a query interface in additon to FT Tracking.&amp;nbsp; We have had two incidents on separate contexts where we lost a physical interface on the primary ACE, one for the maintenance of the core switch, the other was a cable disconnect and we are unable to understand why the indivdual context didn't failover.&amp;nbsp; Any ideas would be much appreciated.&amp;nbsp; Let me know if more info/configs are needed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Dave&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ft interface vlan 900&lt;BR /&gt;&amp;nbsp; ip address 10.10.10.1 255.255.255.0&lt;BR /&gt;&amp;nbsp; peer ip address 10.10.10.2 255.255.255.0&lt;BR /&gt;&amp;nbsp; no shutdown&lt;/P&gt;&lt;P&gt;ft peer 1&lt;BR /&gt;&amp;nbsp; heartbeat interval 300&lt;BR /&gt;&amp;nbsp; heartbeat count 20&lt;BR /&gt;&amp;nbsp; ft-interface vlan 900&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; no preempt&lt;/P&gt;&lt;P&gt;&amp;nbsp; priority 210&lt;/P&gt;&lt;P&gt;&amp;nbsp; peer priority 120&lt;/P&gt;&lt;P&gt;&amp;nbsp; associate-context XYZ&lt;/P&gt;&lt;P&gt;&amp;nbsp; inservice&lt;SPAN id="mce_marker"&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="margin-bottom: 0pt;"&gt;FT Group&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : 3&lt;/P&gt;&lt;P style="margin-bottom: 0pt;"&gt;No. of Contexts&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : 1&lt;/P&gt;&lt;P style="margin-bottom: 0pt;"&gt;Context Name&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : XYZ&lt;/P&gt;&lt;P style="margin-bottom: 0pt;"&gt;Context Id&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : 2&lt;/P&gt;&lt;P style="margin-bottom: 0pt;"&gt;Configured Status&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : in-service&lt;/P&gt;&lt;P style="margin-bottom: 0pt;"&gt;Maintenance mode&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : MAINT_MODE_OFF&lt;/P&gt;&lt;P style="margin-bottom: 0pt;"&gt;My State&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : FSM_FT_STATE_ACTIVE&lt;/P&gt;&lt;P style="margin-bottom: 0pt;"&gt;&lt;STRONG&gt;My Config Priority&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : 210&lt;/STRONG&gt;&lt;/P&gt;&lt;P style="margin-bottom: 0pt;"&gt;&lt;STRONG&gt;My Net Priority&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : 210&lt;/STRONG&gt;&lt;/P&gt;&lt;P style="margin-bottom: 0pt;"&gt;&lt;STRONG&gt;My Preempt&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : Disabled&lt;/STRONG&gt;&lt;/P&gt;&lt;P style="margin-bottom: 0pt;"&gt;Peer State&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : FSM_FT_STATE_STANDBY_HOT&lt;/P&gt;&lt;P style="margin-bottom: 0pt;"&gt;&lt;STRONG&gt;Peer Config Priority&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : 120&lt;/STRONG&gt;&lt;/P&gt;&lt;P style="margin-bottom: 0pt;"&gt;&lt;STRONG&gt;Peer Net Priority&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : 120&lt;/STRONG&gt;&lt;/P&gt;&lt;P style="margin-bottom: 0pt;"&gt;&lt;STRONG&gt;Peer Preempt&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : Disabled&lt;/STRONG&gt;&lt;/P&gt;&lt;P style="margin-bottom: 0pt;"&gt;Peer Id&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : 1&lt;/P&gt;&lt;P style="margin-bottom: 0pt;"&gt;&lt;STRONG&gt;Last State Change time&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : Wed Jan 11 13:14:16 2012&lt;/STRONG&gt;&lt;/P&gt;&lt;P style="margin-bottom: 0pt;"&gt;Running cfg sync enabled&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : Enabled&lt;/P&gt;&lt;P style="margin-bottom: 0pt;"&gt;Running cfg sync status&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : Running configuration sync has completed&lt;/P&gt;&lt;P style="margin-bottom: 0pt;"&gt;Startup cfg sync enabled&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : Enabled&lt;/P&gt;&lt;P style="margin-bottom: 0pt;"&gt;Startup cfg sync status&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; : Startup configuration sync has completed&lt;/P&gt;&lt;P style="margin-bottom: 0pt;"&gt;Bulk sync done for ARP: 0&lt;/P&gt;&lt;P style="margin-bottom: 0pt;"&gt;Bulk sync done for LB: 0&lt;/P&gt;&lt;P style="margin-bottom: 0pt;"&gt;Bulk sync done for ICM: 0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="margin-bottom: 0pt;"&gt;show int &lt;/P&gt;&lt;P style="margin-bottom: 0pt;"&gt;vlan424 is up, VLAN up on the physical port&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="margin-bottom: 0pt;"&gt;Hardware type is VLAN&lt;/P&gt;&lt;P style="margin-bottom: 0pt;"&gt;MAC address is 00:1e:68:1e:ba:b7&lt;/P&gt;&lt;P style="margin-bottom: 0pt;"&gt;Virtual MAC address is 00:0b:fc:fe:1b:03&lt;/P&gt;&lt;P style="margin-bottom: 0pt;"&gt;Mode : routed&lt;/P&gt;&lt;P style="margin-bottom: 0pt;"&gt;IP address is 10.104.224.6 netmask is 255.255.255.0&lt;/P&gt;&lt;P style="margin-bottom: 0pt;"&gt;FT status is active&lt;/P&gt;&lt;P style="margin-bottom: 0pt;"&gt;Description:"New Server VIP and real"&lt;/P&gt;&lt;P style="margin-bottom: 0pt;"&gt;MTU: 1500 bytes&lt;/P&gt;&lt;P style="margin-bottom: 0pt;"&gt;Last cleared: never&lt;/P&gt;&lt;P style="margin-bottom: 0pt;"&gt;Last Changed: Sun Mar 11 01:13:12 2012&lt;/P&gt;&lt;P style="margin-bottom: 0pt;"&gt;No of transitions: 3&lt;/P&gt;&lt;P style="margin-bottom: 0pt;"&gt;Alias IP address is 10.104.224.5 netmask is 255.255.255.0&lt;/P&gt;&lt;P style="margin-bottom: 0pt;"&gt;Peer IP address is 10.104.224.7 Peer IP netmask is 255.255.255.0&lt;/P&gt;&lt;P style="margin-bottom: 0pt;"&gt;Assigned on the physical port, up on the physical port&lt;/P&gt;&lt;P style="margin-bottom: 0pt;"&gt;&lt;STRONG&gt;Previous State: Sun Mar 11 00:04:57 2012, VLAN not up on the physical port&lt;/STRONG&gt;&lt;/P&gt;&lt;P style="margin-bottom: 0pt;"&gt;Previous State: Sun Sep 18 10:21:15 2011, administratively up&lt;/P&gt;&lt;P style="margin-bottom: 0pt;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 3991888419 unicast packets input, 23734607976687 bytes&lt;/P&gt;&lt;P style="margin-bottom: 0pt;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 20246934 multicast, 174801 broadcast&lt;/P&gt;&lt;P style="margin-bottom: 0pt;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0 input errors, 0 unknown, 0 ignored, 0 unicast RPF drops&lt;/P&gt;&lt;P style="margin-bottom: 0pt;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1609345958 unicast packets output, 23690663385228 bytes&lt;/P&gt;&lt;P style="margin-bottom: 0pt;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 7 multicast, 55807 broadcast&lt;/P&gt;&lt;P style="margin-bottom: 0pt;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 0 output errors, 0 ignored&lt;/P&gt;</description>
      <pubDate>Thu, 22 Mar 2012 20:51:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/ace-4710-ft-failover-failure/m-p/1883341#M36654</guid>
      <dc:creator>dpastor</dc:creator>
      <dc:date>2012-03-22T20:51:30Z</dc:date>
    </item>
    <item>
      <title>ACE 4710 FT failover failure</title>
      <link>https://community.cisco.com/t5/application-networking/ace-4710-ft-failover-failure/m-p/1883342#M36655</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Dave,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For tracking to work you need to have preempt enabled. Can you try enabling preempt under the ft group and test your tracking again? Another potential issue you may run into is if your tracking is not lowering the priority enough when it fails. The difference between the active and standby device is 100. If you are not decrementing the priority greater than this value even if priority is enabled it will not lower it enough to force the failover. If after enabling preempt on this group the tracking still does not work as expected send you whole config for us to look at.&lt;/P&gt;&lt;P&gt;Regarding the query interface; This is not a bad idea. It will help prevent an active active situation if there is a problem with the ft link between the two modules.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Jim&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 23 Mar 2012 14:31:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/ace-4710-ft-failover-failure/m-p/1883342#M36655</guid>
      <dc:creator>jsirstin</dc:creator>
      <dc:date>2012-03-23T14:31:40Z</dc:date>
    </item>
    <item>
      <title>ACE 4710 FT failover failure</title>
      <link>https://community.cisco.com/t5/application-networking/ace-4710-ft-failover-failure/m-p/1883343#M36656</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Jim,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks, I wasn't aware that preempt needed to be enabled for FT Tracking to work.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I believe I should be okay on the decrement, I have the FT primary at 210 and the peer at 120, is that what you are referring to?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Dave&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 23 Mar 2012 19:15:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/ace-4710-ft-failover-failure/m-p/1883343#M36656</guid>
      <dc:creator>dpastor</dc:creator>
      <dc:date>2012-03-23T19:15:35Z</dc:date>
    </item>
  </channel>
</rss>

