06-14-2009 07:57 PM
Hi all,
I have two ACE appliances installed with HA configuration. I have 5 vlans (Vlan1, Vlan2, Vlan3, Vlan4 and Vlan5) come from 1 trunk interface. I have 1 ADMIN context and 1 PRODUCTION context. I have configured FT Interface, FT Group and FT Peer in ADMIN context only. I have allocate Vlan1 in ADMIN Context only and assign VLAN2, VLAN3, VLAN4 and VLAN5 for PRODUCTION context. The L3 Interface of VLAN2, VLAN3, VLAN4 and VLAN5 are all configured in PRODUCTION context.
My question is how can I track the interface for VLAN2, VLAN3, VLAN4 and VLAN5? Should I configure FT Track Interface in ADMIN context or configure FT Track Interface in PRODUCTION context so that any VLAN interface down will trigger the failover.
Appreciate who can help me on this question. Thanks
Solved! Go to Solution.
06-15-2009 05:04 AM
The FT group can't be configured in a non-Admin context.
switch/User2(config)# ft gr?
% invalid command
All FT groups MUST be configued in Admin and allocated in Admin to a context.
ft group 112
peer 1
peer priority 90
associate-context User2
inservice
switch/Admin#
The only FT commands inside a context are :
switch/User2(config)# ft ?
auto-sync Enable auto sync
track Configure Fault Tolerance tracking for switchover
switch/User2(config)# ft
And, yes, if tracking configured in a context will reduce priority to its associated group configured in Admin.
Gilles.
06-15-2009 03:34 AM
you have to create in Admin a new FT group.
You then assign this group to the PRODUCTION contect.
Then, inside the production context you can configure the ft track interface command.
Gilles.
06-15-2009 04:07 AM
Hi Gdufour,
Thanks for your guidance. According to your explanation, does that means that I only need to configure FT Group in ADMIN context while there is no FT Group in PRODUCTION context. Then, I configure FT Track Interface in PRODUCTION context only so that the priority in FT Track Interface will be reduced in the FT Group in ADMIN context to trigger failover? Am I correct?
06-15-2009 05:04 AM
The FT group can't be configured in a non-Admin context.
switch/User2(config)# ft gr?
% invalid command
All FT groups MUST be configued in Admin and allocated in Admin to a context.
ft group 112
peer 1
peer priority 90
associate-context User2
inservice
switch/Admin#
The only FT commands inside a context are :
switch/User2(config)# ft ?
auto-sync Enable auto sync
track Configure Fault Tolerance tracking for switchover
switch/User2(config)# ft
And, yes, if tracking configured in a context will reduce priority to its associated group configured in Admin.
Gilles.
06-15-2009 07:21 PM
Hi Gdufour,
Cool. You really did a great help. Appreciate that
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide