how could I define fault-redundancy (ft) for a context?

[blankguy7]

Hi,

I'm opening a new one message and close the other..

So, how could I define redundancy on a context?

I've two ACE with 1 Admin context and 1 PROD context, ft config follows.

I could not configure track-interface or query-interface for vlan in a other context :

ACE3/Admin(config-ft-track-intf)# track-interface vlan 20

Error: vlan '20' does not exist!

the ft for the admin context is running well (1 out and 1 in) but not for the PROD context (both in) see at the end :

ACE3 config

ft interface vlan 1000

  ip address 10.1.1.1 255.255.255.0

  peer ip address 10.1.1.2 255.255.255.0

  no shutdown

ft peer 1

  heartbeat interval 300

  heartbeat count 10

  ft-interface vlan 1000

  query-interface vlan 10

ft group 1

  peer 1

  priority 150

  associate-context Admin

ip route 0.0.0.0 0.0.0.0 192.168.10.1

context PROD

  allocate-interface vlan 20

  allocate-interface vlan 30

ft group 2

  peer 1

  priority 150

  associate-context PROD

  inservice

ACE4 config

ft interface vlan 1000

  ip address 10.1.1.2 255.255.255.0

  peer ip address 10.1.1.1 255.255.255.0

  no shutdown

ft peer 1

  heartbeat interval 300

  heartbeat count 10

  ft-interface vlan 1000

  query-interface vlan 10

ft group 1

  peer 1

  peer priority 150

  associate-context Admin

  inservice

ip route 0.0.0.0 0.0.0.0 192.168.10.1

context PROD

  allocate-interface vlan 20

  allocate-interface vlan 30

ft group 2

  peer 1

  peer priority 150

  associate-context PROD

  inservice

ACE3/Admin# sh ft group det

FT Group                     : 1

No. of Contexts              : 1

Context Name                 : Admin

Context Id                   : 0

Configured Status            : out-of-service

Maintenance mode             : MAINT_MODE_OFF

My State                     : FSM_FT_STATE_INIT

My Config Priority           : 150

My Net Priority              : 150

My Preempt                   : Enabled

Peer State                   : FSM_FT_STATE_ACTIVE

Peer Config Priority         : 100

Peer Net Priority            : 100

Peer Preempt                 : Enabled

Peer Id                      : 1

Last State Change time       : Thu May 31 16:01:54 2012

Running cfg sync enabled     : Enabled

Running cfg sync status      :

Startup cfg sync enabled     : Enabled

Startup cfg sync status      :

Connection sync enabled      : Enabled

Bulk sync done for ARP       : 0

Bulk sync done for  LB       : 0

Bulk sync done for ICM       : 0

Bulk sync done for  ND       : 0

FT Group                     : 2

No. of Contexts              : 1

Context Name                 : PROD

Context Id                   : 1

Configured Status            : in-service

Maintenance mode             : MAINT_MODE_OFF

My State                     : FSM_FT_STATE_ACTIVE

My Config Priority           : 150

My Net Priority              : 150

My Preempt                   : Enabled

Peer State                   : FSM_FT_STATE_STANDBY_HOT

Peer Config Priority         : 100

Peer Net Priority            : 100

Peer Preempt                 : Enabled

Peer Id                      : 1

Last State Change time       : Thu May 31 16:01:54 2012

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

Connection sync enabled      : Enabled

Bulk sync done for ARP       : 0

Bulk sync done for  LB       : 0

Bulk sync done for ICM       : 0

Bulk sync done for  ND       : 0

ACE4/Admin# sh 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_ACTIVE

My Config Priority           : 100

My Net Priority              : 100

My Preempt                   : Enabled

Peer State                   : FSM_FT_STATE_UNKNOWN

Peer Config Priority         : Unknown

Peer Net Priority            : Unknown

Peer Preempt                 : Unknown

Peer Id                      : 1

Last State Change time       : Thu May 31 15:41:39 2012

Running cfg sync enabled     : Enabled

Running cfg sync status      :

Startup cfg sync enabled     : Enabled

Startup cfg sync status      :

Connection sync enabled      : Enabled

Bulk sync done for ARP       : 0

Bulk sync done for  LB       : 0

Bulk sync done for ICM       : 0

Bulk sync done for  ND       : 0

FT Group                     : 2

No. of Contexts              : 1

Context Name                 : PROD

Context Id                   : 1

Configured Status            : in-service

Maintenance mode             : MAINT_MODE_OFF

My State                     : FSM_FT_STATE_STANDBY_HOT

My Config Priority           : 100

My Net Priority              : 100

My Preempt                   : Enabled

Peer State                   : FSM_FT_STATE_ACTIVE

Peer Config Priority         : 150

Peer Net Priority            : 150

Peer Preempt                 : Enabled

Peer Id                      : 1

Last State Change time       : Fri Jun  1 14:02:55 2012

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

Connection sync enabled      : Enabled

Bulk sync done for ARP       : 0

Bulk sync done for  LB       : 0

Bulk sync done for ICM       : 0

Bulk sync done for  ND       : 0

ACE4/Admin#

Thanks in advance,

Best regards,

jm

[sivaksiv]

Hi,

Both context should be inservice on both boxes for ft to work.

for ft tracking do you have th vlan 20 configured in that context?

-

Siva

[Cesar Roque]

Hi JM,

I think that the problem is because you are trying to configure FT tracking using a VLAN that does not exists on the Admin Context:

ACE3/Admin(config-ft-track-intf)# track-interface vlan 20

Error: vlan '20' does not exist!

FT Tracking needs to be configured on each Context, this is the only FT configuration that you have to do in the  Context itself

The rest of the FT configuration is done in the Admin Context.

So if you want to track Vlan20 for the PROD Context, just changeto the Context and apply the configuration.

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

Cesar R

[blankguy7]

Hi Cesar,

Thanks for your answers!

I knew that it is not possible to define FT tracking VLAN that belongs to a another Context.

But I had not thoughts to configure this FT tracking VLAN in my context.

Now, I've configured the FT tracking on context and It's running well. Thanks a lot

Last question: with the command show ft track detail I saw always Status : in-service.

How to know with FT aktiv ist?

Best regards,

jm

[Cesar Roque]

Hi JM,

I did not understand your question, could you please elaborate a bit more.

[blankguy7]

Hi Cesar,

I'd like to known how to see if my "fault-redundancy" is running?

Which command to use it to check-up that?

How to see which ACE is activ and which is STANDBY?

So, that was my question! Because the command show me that all ft are in-service but not ACTIVE or STANDBY.

Thanks and best regards,

Jerome

[Cesar Roque]

Hi,

You can use the show ft group detail on each Context and that output will give you all the information. Including Active and Standby state.

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

Cesar R

[fb_webuser]

its easy to say but difficult to do on the field..........

---

Posted by WebUser Sajadur Sajed from Cisco Support Community App

[blankguy7]

All thing could be explain... I don't understood what's you mean?

[ajayku2 · Accepted solution]

Run the command and check 

ACE_5/Admin# show ft group detail           
 
FT Group                     : 1
No. of Contexts              : 1
Configured Status            : in-service
Maintenance mode             : MAINT_MODE_OFF
My State                     : FSM_FT_STATE_ACTIVE  << The context on this device is active >>
My Config Priority           : 110
My Net Priority              : 110
My Preempt                   : Enabled
Peer State                   : FSM_FT_STATE_STANDBY << Peer device is standby >>
Peer Config Priority         : 100
Peer Net Priority            : 100
Peer Preempt                 : Enabled
Peer Id                      : 1
Last State Change time       : Thu Apr  2 00:00:00 2009
Running cfg sync enabled     : Enabled
Running cfg sync status      : Running configuration sync has completed
Startup cfg sync enabled     : Enabled
Startup cfg sync status      : Running configuration sync has completed
Bulk sync done for ARP: 0
Bulk sync done for LB: 0
Bulk sync done for ICM: 0

Use this command to check if hearbit is passing or not:

ACE_5/Admin# show ft stats
HA Heartbeat Statistics
------------------------

Number of Heartbeats Sent                 : 20
Number of Heartbeats Received             : 20
Number of Heartbeats Missed               : 0
Number of Unidirectional HB's Received    : 0
Number of HB Timeout Mismatches           : 0
Num of Peer Up Events Sent                : 0
Num of Peer Down Events Sent              : 0
Successive HB's miss Intervals counter    : 0
Successive Uni HB's recv counter          : 0

[blankguy7]

Thanks for your help and answers!

It was really helpfull,

Best regards,

jm