Standby ACE not switching to active even when priority of active member is decreased due to vlan interface tracking.

Unanswered Question
Apr 29th, 2010

I have 2 ace in active standby setup with FT configured, FT is working fine when i shut down the active box,at that time my standby becomes active.

I have enabled vlan interface tracking recently, when i shut down the interface from switch to which ACE is connected, i can see the priority is decreased in active ace than stanby but still stanby doenot become active at that time.

FT config:

ft interface vlan 2

  ip address 10.10.10.1 255.255.255.0

  peer ip address 10.10.10.2 255.255.255.0

  no shutdown

ft peer 1

  heartbeat interval 100

  heartbeat count 10

  ft-interface vlan 2

  query-interface vlan 421

ft group 1

  peer 1

  priority 150

  peer priority 145

  associate-context Admin

  inservice

 

ft track interface AAA

  track-interface vlan 421

  peer track-interface vlan 421

priority 50

  peer priority 5

ft track interface BBB

  track-interface vlan 431

  peer track-interface vlan 431

priority 50

  peer priority 5

Any help would be appreciated.

Regards

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Marko Leopold Thu, 04/29/2010 - 23:42

Did you enable the "svclc autostate" command on your switch? It is required for vlan-tracking.

greetings.

Manjunatha Jayaram Fri, 04/30/2010 - 04:28

The fact is the priority of active is getting decreased when i shut the vlan port from switch side.

It is that still i have to enable "svclc autostate" on switch.

Regards

Satish Bhat

Manjunatha Jayaram Fri, 04/30/2010 - 04:37

As per my configuration ft track interace AAA & ft track interface BBB , peer track interface should be (ft vlan)vlan 2 or vlan 431 / 421.(interface vlan)

Can some one pls clear my doubt...?

Regards

Satish

Marko Leopold Fri, 04/30/2010 - 04:53

I guess it depends on what you want to do. But usually you track on both sides the same vlan, if you want to track this interface.

Gilles Dufour Fri, 04/30/2010 - 05:45

sorry  had not seen you already had the priority.

What is the status of 'show ft track det' on each ACE when you shut down the interface ?

Gilles.

Manjunatha Jayaram Sat, 05/01/2010 - 04:43

on primary ace:

----------------------------

LoadBalancer-1/Admin# sh ft group 1 detail

FT Group : 1

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 : 150

My Net Priority : 100

My Preempt : Disabled

Peer State : FSM_FT_STATE_STANDBY_COLD

Peer Config Priority : 145

Peer Net Priority : 145

Peer Preempt : Disabled

Peer Id : 1

Last State Change time : Thu Apr 29 03:30:14 2010

Running cfg sync enabled : Enabled

Running cfg sync status : Peer in Cold State. Error on Standby device when applying configuration file replicated from active

Startup cfg sync enabled : Disabled

Startup cfg sync status : Peer in Cold State. Startup configuration sync is disabled

Bulk sync done for ARP: 1

Bulk sync done for LB: 1

Bulk sync done for ICM: 1

LoadBalancer-1/Admin#

Stanby Ace:

-------------------------------

`show ft group detail`

FT Group : 1

No. of Contexts : 1

Context Name : Admin

Context Id : 0

Configured Status : in-service

Maintenance mode : MAINT_MODE_OFF

My State : FSM_FT_STATE_STANDBY_COLD

My Config Priority : 145

My Net Priority : 145

My Preempt : Disabled

Peer State : FSM_FT_STATE_ACTIVE

Peer Config Priority : 150

Peer Net Priority : 100

Peer Preempt : Disabled

Peer Id : 1

Last State Change time : Thu Apr 29 04:25:26 2010

Running cfg sync enabled : Enabled

Running cfg sync status : Error on Standby device when applying configuration file replicated from active

Startup cfg sync enabled : Disabled

Startup cfg sync status : Startup configuration sync is disabled

Bulk sync done for ARP: 0

Bulk sync done for LB: 0

Bulk sync done for ICM: 0

Gilles Dufour Mon, 05/03/2010 - 06:47

The problem is that you disabled "preempt"

Peer Preempt : Disabled

This is required for the standby to take over.

Actually, it is possible that preemot was automatically disabled because the 2 devices are not in-synch

Running cfg sync enabled : Enabled

Running cfg  sync status : Peer in Cold State. Error on Standby device when applying  configuration file

Do a " show ft config-error" to detect the problem.

Gilles.

Actions

This Discussion