11-7
Device Manager Guide, Cisco ACE 4700 Series Application Control Engine Appliance
OL-26645-02
Chapter 11 Configuring High Availability
Understanding ACE Redundancy
• When you configure redundancy, the ACE keeps all interfaces that do not have an IP address in the
Down state. The IP address and the peer IP address that you assign to a VLAN interface should be
in the same subnet, but different IP addresses. For more information about configuring VLAN
interfaces, see Configuring Virtual Context VLAN Interfaces, page 10-10.
• In a high availability pair, the two configured virtual contexts synchronize with each other as part
of their ongoing communications. However, their copies do not synchronize in ACE Appliance
Device Manager and the configuration on the standby member can become out of sync with the
configuration on the ACE appliance. After the active member of a high availability pair fails and
the standby member becomes active, ACE Appliance Device Manager on the newly active member
detects any out-of-sync virtual context configurations and reports that status in the All Virtual
Contexts table so that you can synchronize the virtual context configurations.
• When a virtual context is in either the Standby Hot or Standby Warm state (see High Availability
Polling, page 11-2), the virtual context may receive configuration changes from its ACE peer
without updating the Device Manager GUI. As a result, the ACE appliance Device Manager GUI
will be out of synchronization with the CLI configuration. If you need to check configuration on a
standby virtual context using the tracking and failure detection process (see Tracking VLAN
Interfaces for High Availability, page 11-19), we recommend that you first perform a manual
synchronization using either the CLI Sync or CLI Sync All buttons before checking the
configuration values.
Kommentare zu diesen Handbüchern