Cisco Cisco ACE Application Control Engine Module White Paper
© 2011 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.
Page 22 of 40
Feature
Description
Benefit
Cookie value
specification
specification
The Cisco ACE30 module can enter a cookie string value of the real
server for HTTP cookie insertion when establishing a sticky
connection. With this feature enabled, the Cisco ACE inserts the
cookie in the Set-Cookie header of the response from the server to
the client.
server for HTTP cookie insertion when establishing a sticky
connection. With this feature enabled, the Cisco ACE inserts the
cookie in the Set-Cookie header of the response from the server to
the client.
Enables intelligent web serving with stickiness of
the same client to the same real server using
server-side information.
the same client to the same real server using
server-side information.
KAL-AP
enhancements
enhancements
The Cisco ACE30 module uses this enhancement in global server
load balancing, through which the Cisco Global Site Selector (GSS)
reports the correct state of a failed Cisco ACE30 module in the
Domain Name System (DNS) response to the client if a redundant
Cisco ACE is present in a secondary data center.
load balancing, through which the Cisco Global Site Selector (GSS)
reports the correct state of a failed Cisco ACE30 module in the
Domain Name System (DNS) response to the client if a redundant
Cisco ACE is present in a secondary data center.
Reduces application downtime for end users for
a globally load-balanced application due to
failure of the primary Cisco ACE in a distributed
cluster of Cisco ACE load balancers (one or
more in each global site).
a globally load-balanced application due to
failure of the primary Cisco ACE in a distributed
cluster of Cisco ACE load balancers (one or
more in each global site).
Probe port
Inheritance
Inheritance
The Cisco ACE30 module can dynamically inherit the port number for
a probe from the real server specified in a server farm or from the
virtual IP address specified in a Layer 3 or 4 class map.
a probe from the real server specified in a server farm or from the
virtual IP address specified in a Layer 3 or 4 class map.
Provides ease of configuration for probing real
servers; only a single probe configuration is
sufficient to probe a real server on multiple ports
or on all virtual IP ports.
servers; only a single probe configuration is
sufficient to probe a real server on multiple ports
or on all virtual IP ports.
Syslog reporting for
SIP load balancing
SIP load balancing
The Cisco ACE30 module can report the Layer 7 processing status
for SIP packets as well as the reason for dropping any SIP packet
during Layer 7 processing.
for SIP packets as well as the reason for dropping any SIP packet
during Layer 7 processing.
Enables the service provider or enterprise IT
operator to troubleshoot SIP-based
communication.
operator to troubleshoot SIP-based
communication.
Detailed CLI Changes Between the Cisco ACE Software Release A2.3.x and A5.1.x
The vast majority of features and commands on the Cisco ACE modules are the same, however in the
development of the Cisco ACE30 module some commands were modified to extend their functionality. Table 4, is a
comprehensive list of all Cisco ACE10 or ACE20 commands that have been modified in Cisco ACE30. This table
lists the command, an example of how it is used, and a brief description of the new command. Please take a
moment to familiarize yourself with the minor changes listed.
Table 4.
Modified ACE 2.x Commands
Command Syntax and Example
Description
syn-cookie <value>
This cli under interface configuration is modified for values < 4 to
autoupgrade the values to 4.
autoupgrade the values to 4.
syn-cookie configuration.
show ft group status
itasca2/Admin# show ft group status
FT Group : 1
Configured Status : in-service
Maintenance mode : MAINT_MODE_OFF
My State : FSM_FT_STATE_ACTIVE
Peer State : FSM_FT_STATE_STANDBY_BULK
Peer Id : 1
No. of Contexts : 1
Running cfg sync status : Config sync disabled when peer is not fully CLI
compatible
Startup cfg sync status : Config sync disabled when peer is not fully CLI
compatible
FT Group : 1
Configured Status : in-service
Maintenance mode : MAINT_MODE_OFF
My State : FSM_FT_STATE_ACTIVE
Peer State : FSM_FT_STATE_STANDBY_BULK
Peer Id : 1
No. of Contexts : 1
Running cfg sync status : Config sync disabled when peer is not fully CLI
compatible
Startup cfg sync status : Config sync disabled when peer is not fully CLI
compatible
Adding two
“running/startup config
sync status
” entries in the end.
show ft group brief
itasca2/Admin# show ft group br
FT Group ID: 1
My State:FSM_FT_STATE_ACTIVE
Peer State:FSM_FT_STATE_STANDBY_BULK
Context Name: Admin
Context Id: 0
Cfg Sync Status:Successful
FT Group ID: 1
My State:FSM_FT_STATE_ACTIVE
Peer State:FSM_FT_STATE_STANDBY_BULK
Context Name: Admin
Context Id: 0
Cfg Sync Status:Successful
Adding
“cfg sync status” entry in the
end.