Cisco Explorer 4700 Installationsanleitung PDF herunterladen (Seite 131)

4-81

Device Manager Guide, Cisco ACE 4700 Series Application Control Engine Appliance

OL-26645-02

Chapter 4 Configuring Virtual Contexts

Managing Virtual Contexts

• Sync Failed—The last synchronization attempt failed and you must perform a manual

synchronization using either the CLI Sync or CLI Sync All buttons. The failed state could be due to

an unrecognized CLI command on the context, or due to an internal error on the ACE Appliance

Device Manager. Once the problem is resolved, another manual synchronization will be required to

move the context into the OK synchronization state.

The status bar at the bottom of the ACE Appliance Device Manager browser (see Figure 4-1) displays

DM GUI and CLI synchronization status along with a summary count of the contexts in the various

synchronization states. For example, the message “DM out of sync with CLI (1/10), DM sync with CLI

failed (2/10)” indicates that out of the 10 configured contexts, one context is in the “Out Of Sync” state

and two are is the “Sync Failed” state, and the remaining contexts are in the “OK” state. The status bar

auto-refreshes every 10 seconds.

Note Clicking the summary count in the status bar from any context-specific page accesses the All Virtual

Contexts table. You can view the CLI synchronization status for all contexts.

If a user changes the configuration for a context by using the CLI while you are viewing the All Virtual

Contexts table, the information in the CLI Sync Status column does not automatically update to reflect

an out-of-sync state. Click Refresh or set an automatic refresh rate by clicking Auto Refresh to view

out-of-sync configurations.

For information on synchronizing out-of-sync virtual context configurations, see the following topics:

• Manually Synchronizing Individual Virtual Context Configurations, page 4-82

• Manually Synchronizing All Virtual Context Configurations, page 4-83

Related Topics

• Synchronizing Virtual Context Configurations, page 4-79

• High Availability and Virtual Context Configuration Status, page 4-81

High Availability and Virtual Context Configuration Status

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.

Note When a virtual context is in either the Standby Hot or Standby Warm state (see the “High Availability

Polling” section on 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 HA Tracking And Failure Detection (see the “Tracking VLAN Interfaces for High

Availability” section on 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.

1 2 ... 126 127 128 129 130 131 132 133 134 135 136 ... 647 648

Kommentare zu diesen Handbüchern

Keine Kommentare

Cisco Explorer 4700 Installationsanleitung Seite 131

Kommentare zu diesen Handbüchern

Verwandte Produkte und Handbücher für Digitale Videorecorder (DVR) Cisco Explorer 4700