ACE preemption not working correctly

Unanswered Question
Nov 6th, 2008

What I want to do:

ACE B, which is in the STANDBY_HOT state should going to ACTIVE mode when ACE A, which is ACTIVE,goes down. ACE B, which is in ACTIVE mode now should stay ACTIVE even when ACE A comes backup.

I made already several tests and saw, that when the ACE's are not in a productive ennvironment it works as I like it, but when it is in a productive ennvironment, ACE A takes back the ACTIVE state altough I configured no preempt. I also tried it with diffrent priorities, but same thing happend. What am I missing?

ft group 21

peer 1

no preempt

associate-context Admin

inservice

ft group 20

peer 1

no preempt

associate-context MOCS

inservice

ACE21_Secondary/Admin# sh ft gr det

FT Group : 20

No. of Contexts : 1

Context Name : MOCS

Context Id : 1

Configured Status : in-service

Maintenance mode : MAINT_MODE_OFF

My State : FSM_FT_STATE_ACTIVE

My Config Priority : 100

My Net Priority : 100

My Preempt : Disabled

Peer State : FSM_FT_STATE_STANDBY_HOT

Peer Config Priority : 100

Peer Net Priority : 100

Peer Preempt : Disabled

Peer Id : 1

Last State Change time : Wed Nov 5 12:12:23 2008

Running cfg sync enabled : Enabled

Running cfg sync status : Running configuration sync has completed

Startup cfg sync enabled : Enabled

Startup cfg sync status : Startup configuration sync has completed

Bulk sync done for ARP: 0

Bulk sync done for LB: 0

Bulk sync done for ICM: 0

FT Group : 21

No. of Contexts : 1

Context Name : Admin

Context Id : 0

Configured Status : in-service

Maintenance mode : MAINT_MODE_OFF

My State : FSM_FT_STATE_ACTIVE

My Config Priority : 100

My Net Priority : 100

My Preempt : Disabled

Peer State : FSM_FT_STATE_STANDBY_HOT

Peer Config Priority : 100

Peer Net Priority : 100

Peer Preempt : Disabled

Peer Id : 1

Last State Change time : Wed Nov 5 12:12:23 2008

Running cfg sync enabled : Enabled

Running cfg sync status : Running configuration sync has completed

Startup cfg sync enabled : Enabled

Startup cfg sync status : Startup configuration sync has completed

Bulk sync done for ARP: 0

Bulk sync done for LB: 0

Bulk sync done for ICM: 0

ACE21_Secondary/Admin#

Cheers

Peter

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Gilles Dufour Fri, 11/07/2008 - 00:38

CSCsi63012 - ACE with time greater among both always becomes active

This should fix the problem.

This ddts was integrated in A2(1.0)

Gilles.

pwenger Fri, 11/07/2008 - 04:19

Hi Gilles,

as Pascal already told you via mail I'm running a higer version.

ACE21_Secondary/Admin# sh ver

Cisco Application Control Software (ACSW)

TAC support: http://www.cisco.com/tac

Copyright (c) 1985-2008 by Cisco Systems, Inc. All rights reserved.

The copyrights to certain works contained herein are owned by

other third parties and are used and distributed under license.

Some parts of this software are covered under the GNU Public

License. A copy of the license is available at

http://www.gnu.org/licenses/gpl.html.

Software

loader: Version 0.95

system: Version A3(2.0) [build 3.0(0)A3(2.0) adbuild_17:35:22-2008/10/01_/auto/adbu-rel4/rel_a3_2_0_dev_build/REL_3_0_0_A3_2_0]

system image file: (hd0,1)/c4710ace-mz.A3_2_0.bin

Device Manager version 1.1 (0) 20080805:0415

installed license: no feature license is installed

Hardware

cpu info:

Motherboard:

number of cpu(s): 2

Daughtercard:

number of cpu(s): 16

memory info:

total: 6226392 kB, free: 4576476 kB

shared: 0 kB, buffers: 19188 kB, cached 0 kB

cf info:

filesystem: /dev/hdb2

total: 861668 kB, used: 724252 kB, available: 93644 kB

last boot reason: reload command by admin

configuration register: 0x1

ACE21_Secondary kernel uptime is 2 days 2 hours 31 minute(s) 30 second(s)

ACE21_Secondary/Admin#

Regards

Peter

Gilles Dufour Fri, 11/07/2008 - 05:19

Peter,

we will need to do some analysis of the config and the 'show ft history ...' (all 3 commands) captured on both devices just after the failover.

Better open a case for that.

Gilles.

chris.pomeroy Sat, 11/15/2008 - 10:12

You have identical ft priorities try adding a priority to you ft group.

There is

priority (which is the module you are on)

and

peer priority (which is the standby)

ft group 3

peer 1

priority 200

associate-context ITSS

inservice

Actions

This Discussion