engine overlimit

Function

The engine overlimit command configures a performance bypass triggering condition for the IAE.

The undo engine overlimit command restores the default performance bypass triggering conditions of the IAE.

Format

engine overlimit { cpu-threshold cpu-threshold | protocol { http-detection-length http-detection-length | other-detection-length other-detection-length } | detected-app { p2p | fix | lpd | icq_im | postgre_sql | voip | software-update } }

undo engine overlimit { cpu-threshold | protocol { all | http-detection-length | other-detection-length } | detected-app { all | p2p | fix | lpd | icq_im | postgre_sql | voip | software-update } }

Parameters

Parameter	Description	Value
cpu-threshold cpu-threshold	Specifies the usage threshold of the CPU core occupied by the IAE.	The value is an integer ranging from 1 to 100, in percentages. The default value is as follows: Versions earlier than V600R007C20SPC601: 80. V600R007C20SPC601 and later versions: 70.
protocol http-detection-length http-detection-length	Specifies the detection length of HTTP.	The value is an integer ranging from 1 to 1024, in KB. The default value is 64.
protocol other-detection-length other-detection-length	Specifies the detection length of other protocols except HTTP.	The value is an integer ranging from 1 to 1024, in KB. The default value is 8.
detected-app	Indicates application detection.	-
p2p	Indicates the P2P application.	-
fix	Indicates the FIX application.	-
lpd	Indicates the LPD application.	-
icq_im	Indicates the ICQ IM application.	-
postgre_sql	Indicates the PostgreSQL application.	-
voip	Indicates the VoIP application.	-
software-update	Indicates the Software-Update application.	-
all	Indicates all protocols or applications.	-

Views

System view

Default Level

2: Configuration level

Usage Guidelines

The default performance bypass triggering conditions for the IAE are as follows:

For HTTP, when the usage of the CPU core occupied by the IAE reaches 80% and the detected HTTP packet length reaches 64 KB, the IAE performance bypass is triggered. For protocols other than HTTP, when the usage of the CPU core occupied by the IAE reaches 80% and the detected protocol packet length reaches 8 KB, the IAE engine performance bypass is triggered.
- You can run the engine overlimit cpu-threshold cpu-threshold command to configure the usage threshold of the CPU core occupied by the IAE.
- You can run the engine overlimit protocol http-detection-length http-detection-length command to configure the detection length of HTTP that triggers IAE performance bypass.
- You can run the engine overlimit protocol other-detection-length other-detection-length command to configure the detection length of other protocols (except HTTP) that triggers IAE performance bypass.
By default, the IAE enables performance bypass for P2P, FIX, LPD, ICQ IM, PostgreSQL, VoIP, and Software-Update applications and does not detect the traffic of these applications.
You can run the engine overlimit detected-app { p2p | fix | lpd | icq_im | postgre_sql | voip | software-update } command to disable performance bypass for a specified application.

Example

# For HTTP, configure the following IAE performance bypass triggering conditions: The usage of the CPU core occupied by the IAE reaches 50% and the detected HTTP packet length reaches 10 KB.

<sysname> system-view
[sysname] engine overlimit cpu-threshold 50
[sysname] engine overlimit protocol http-detection-length 10

# Disable performance bypass for the P2P application.

<sysname> system-view
[sysname] engine overlimit detected-app p2p