Cisco 4700M Administration Manual page 182

Displaying or Clearing Redundancy Information
Table 6-6 Field Descriptions for the show ft track Command Output (continued)
Field Description
My State State of the FT group member in the local ACE. Possible states are:
My State (Cont.)
•
•
•
•
•
•
•
•
My Config Priority Priority configured on the FT group in the local ACE.
My Net Priority Priority of the FT group equal to the configured priority minus the priority of the FT tracking process
failures, if any.
My Preempt Preemption value of the FT group in the local ACE. Possible values are Enabled or Disabled.
Context Name Name of the context that is associated with the FT group.
Context ID Identifier of the context that is associated with the FT group.
Track Type Type of object being tracked. Possible values are TRACK_HOST or TRACK_INTERFACE.
Cisco 4700 Series Application Control Engine Appliance Administration Guide
6-38
FSM_FT_STATE_INIT—Initial state for each member (local and peer) of an FT group. The
configuration for the FT group exists but the group is not yet in service.
FSM_FT_STATE_ELECT—State that the local group member enters when you configure the
inservice command for an FT group. Through the election process, the local context negotiates
with its peer context in the FT group to determine their states. One member enters the ACTIVE
state and the other member enters the STANDBY_CONFIG state.
FSM_FT_STATE_ACTIVE—State that indicates that the local member of the FT group is active
and processing flows.
FSM_FT_STATE_STANDBY_COLD—State that indicates if either the FT VLAN is down but
the peer device is still alive, or the configuration or application state synchronization failed.
When a context is in this state and a switchover occurs, the transition to the ACTIVE state is
stateless.
FSM_FT_STATE_STANDBY_CONFIG—State that indicates that the local standby context is
waiting to receive configuration information from its active peer context in the FT group. The
active peer context receives a notification to send a snapshot of its running-configuration file to
the local standby context.
FSM_FT_STATE_STANDBY_BULK—State that indicates that the local standby context is
waiting to receive state information from its active peer context. The active peer context receives
a notification to send a snapshot of the current state information for all applications to the
standby context.
FSM_FT_STATE_STANDBY_HOT—State that indicates that the local standby context has all
the state information it needs to statefully assume the active state if a switchover occurs.
FSM_FT_STATE_STANDBY_WARM—State used when upgrading or downgrading the ACE
software. When you upgrade or downgrade the ACE from one software version to another, there
is a point in the process when the two ACEs have different software versions and, therefore, a
CLI incompatibility.
When the software versions are different while upgrading or downgrading, the
STANDBY_WARM state allows the configuration and state synchronization process to continue
on a best-effort basis, which means that the active ACE will continue to synchronize
configuration and state information to the standby even though the standby may not recognize
or understand the CLI commands or state information. This standby state allows the standby
ACE to come up with best-effort support. In the STANDBY_WARM state, as with the
STANDBY_HOT state, the configuration mode is disabled and configuration and state
synchronization continues. A failover from the active to the standby based on priorities and
preempt can still occur while the standby is in the STANDBY_WARM state.
Chapter 6 Configuring Redundant ACEs
OL-20823-01