Table Of Contents

Optimize Configuration Mode Commands

(config-optimize) appscope-log

(config-optimize) concurrent-connections

(config-optimize) debug-level

Optimize Configuration Mode Commands

(ACE appliance only) The optimize mode includes a set of commands that allow you to globally configure application acceleration and optimization operation on the ACE. To remove an optimize mode selection, use the no form of the command. For details about using the commands in the optimize mode, see the Cisco 4700 Series Application Control Engine Appliance Application Acceleration and Optimization Configuration Guide.

To access the optimize mode, enter the optimize command. The CLI prompt changes to (config-optimize).

optimize

no optimize

Syntax Description

This command has no keywords or arguments.

Command Modes

Configuration mode

Admin and user contexts

Command History

ACE Appliance Release	Modification
A1(7)	This command was introduced.

Usage Guidelines

The commands in this mode require the loadbalance feature in your user role. For details about role-based access control (RBAC) and user roles, see the Virtualization Guide, Cisco ACE Application Control Engine.

Examples

To access the optimize mode, enter:

host1/Admin(config)# optimize

host1/Admin(config-optimize)# 

Related Commands

show optimization-global

(config-optimize) appscope-log

(ACE appliance only) To configure the ACE to upload the application acceleration and optimization statistical log information to the optional Cisco AVS 3180A Management Station, use the appscope-log command. Use the no form of this command to disable sending statistical log information to a Management Station.

appscope-log

no appscope-log

Syntax Description

This command has no keywords or arguments.

Command Modes

Optimize mode

Admin and user contexts

Command History

ACE Appliance Release	Modification
A1(7)	This command was introduced.

Usage Guidelines

The statistical log file contains an entry for each ACE optimization request to the server and is used for statistical analysis by the optional Cisco AVS 3180A Management Station. The ACE collects statistical log data and then sends it to the Management Station for loading into the management station database. For details about the optional Cisco AVS 3180A Management Station database, management, and reporting features, including AppScope reporting, see the Cisco 4700 Series Application Control Engine Appliance Application Acceleration and Optimization Configuration Guide.

To enable the AppScope feature, use the appscope command in action list optimization configuration mode. See the (config-actlist-optm) appscope command.

For each ACE request, information about the statistical log is written to the statlog.nnn file, where nnn is a three-digit number. Each entry in the statlog file is written in an XML-like syntax, where each element is opened with an angle-bracketed tag, and closed with a similar tag, and can contain several fields with nested elements.

---

Note Statistical log information from active ACE nodes is carried by the syslog-ng daemon to the Cisco AVS 3180A Management Console and written to a file under the avs-log/syslog/ directory. The file is <optm-id>_<virtual-context-id>, which is unique across all ACE nodes.

---

To specify the host (the syslog server on the Management Station) that receives the syslog messages sent by the ACE, use the logging host configuration command. See the (config) logging host command. This command allows you to identify the IP address of the Management Station that will be used as the syslog server. You can specify that the host uses either UDP or TCP to send messages to the syslog server.

Examples

To specify that the information about statistical log is to be sent to a Management Station at 192.168.10.1 using TCP, enter:

host1/Admin(config)# optimize

host1/Admin(config-optimize)# appscope-log

host1/Admin(config-optimize)# exit

host1/Admin(config)# logging host 192.168.10.1 tcp

To disable sending information about the statistical log information to an AVS 3180A Management Station, enter:

host1/Admin(config-optimize)# no appscope-log

Related Commands

(config-actlist-optm) appscope
(config-parammap-optmz) appscope optimize-rate-percent
(config-parammap-optmz) parameter-summary parameter-value-limit
(config-parammap-optmz) request-grouping-string

(config-optimize) concurrent-connections

(ACE appliance only) To define the concurrent connection limit at which optimization will be disabled for all new connections that are received by the ACE, use the concurrent-connections command. Use the no form of this command to return to the default concurrent connection limit of 1000.

concurrent-connections connection_limit

no concurrent-connections

Syntax Description

connection_limit

Maximum concurrent connection limit. Enter an integer from 100 to 9500. The default is 1000.

Command Modes

Optimize mode

Admin and user contexts

Command History

ACE Appliance Release	Modification
A1(8)	This command was introduced.
A4(1.0)	The limit keyword was removed.
A4(2.0)	This command was deprecated. Application acceleration concurrent connections are now fixed at 100.

Usage Guidelines

When you use the ACE to perform a specific set of application acceleration and optimization functions, and the ACE reaches the maximum of 10,000 concurrent connections, the ACE stops accepting any additional concurrent connections until the count drops below 10,000. You can define the limit at which all new connections are directly sent to the real server without the ACE performing application acceleration and optimization. This user-defined limit bypasses application acceleration and optimization requests on a connection until the concurrent connection count is less than the allowed specified maximum of 9,500 concurrent connections.

The ACE will always perform application acceleration and optimization for FlashForward URLs, AppScope URLs, and base file URLs in a new connection even if you have specified a concurrent connection limit.

---

Note The show stats loadbalance command in Exec mode displays the optimized connection counter (maximum and concurrent) and the unoptimized connection counter for all application acceleration connections.

---

Examples

To specify a concurrent connection limit of 5000, enter:

host1/Admin(config)# optimize

host1/Admin(config-optimize)# concurrent-connections 5000

To return to the default concurrent connection limit of 1000, enter:

host1/Admin(config-optimize)# no concurrent-connections 

Related Commands

This command has no related commands.

(config-optimize) debug-level

(ACE appliance only) To enable HTTP optimization logging and control the maximum level for system log messages sent to the host (the syslog server on the optional Cisco AVS 3180A Management Station), use the debug-level command. Use the no form of the command to disable the debug function for HTTP optimization.

debug-level severity_level

no debug-level severity_level

Syntax Description

severity_level

Maximum level for system log messages sent to a syslog server. The severity level that you specify indicates that you want syslog messages at that level and messages lower than that level. For example, if the specified level is 3, the syslog displays level 3, 2, 1, and 0 messages. The severity level that you specify indicates that you want to log messages at that level and below. Allowable entries are as follows: •0—emergencies (system unusable messages) •1—alerts (take immediate action) •2—critical (critical condition) •3—errors (error message) •4—warnings (warning message) •5—notifications (normal but significant condition) •6—informational (information message) •7—debugging (debug messages)

Command Modes

Optimize mode

Admin and user contexts

Command History

ACE Appliance Release	Modification
A1(7)	This command was introduced.

Usage Guidelines

The debug-level command limits the HTTP optimization logging messages sent to a syslog server based on severity.

To specify the host (the syslog server on the optional Management Station) that receives the syslog messages sent by the ACE, use the logging host configuration command. See the (config) logging host command. You can specify that the host uses either UDP or TCP to send messages to the syslog server.

Examples

To enable HTTP optimization logging and send informational system message logs to the syslog server, enter:

host1/Admin(config)# debug-level 6

To disable the debug function for HTTP optimization, enter:

host1/Admin(config)# no debug-level

Related Commands

(config-parammap-optmz) appscope optimize-rate-percent
(config-parammap-optmz) parameter-summary parameter-value-limit
(config-parammap-optmz) request-grouping-string

Command Modes

Optimize mode