Cisco Cisco ASR 5700
ACS Configuration Mode Commands
▀ system-limit l4-flows
▄ Command Line Interface Reference, StarOS Release 17
574
system-limit l4-flows
This command allows you to configure the system-wide Layer 4 flow limit.
Important:
This command is customer specific. For more information contact your Cisco account representative.
Product
ACS
Privilege
Security Administrator, Administrator
Mode
Exec > ACS Configuration
active-charging service service_name
Entering the above command sequence results in the following prompt:
[local]host_name(config-acs)#
Syntax
system-limit l4-flows limit
{ default | no } system-limit l4-flows
default
Configures this command with its default setting.
Default: Disabled; same as
Default: Disabled; same as
no system-limit l4-flows
no
Disables the limit checking configuration.
limit
Specifies the Layer 4 flows limit.
limit
must be an integer from 1 through 2147483647.
Usage
Use this command to configure the system-wide limit for Layer 4 flows.
The System-wide L4 Flow Limiting feature provides the capability to limit the number of TCP and UDP flow
over the system. This limiting can be applied to all subscribers attaching to the system and to all APNs. This
feature is compatible with the existing per-subscriber limiting (configured using the flow limit-for-flow-type
charging action). Both limiting can be active in the same time.
System-wide flow limiting is implemented by comparing the “Effective Flows” periodically (~ every 10
seconds) against the configurable “System-wide Flow Limit”. Where “Effective Flows” is the number of
active data sessions, each identified by the 5-tuple key. If the “Effective Flows” exceeds the “System-wide
Flow Limit”, the Resource Manager indicates it to the active charging service. When ACS is aware of the
“System-wide Flow Limit” being reached, no more data sessions are setup. The packets are discarded. While
The System-wide L4 Flow Limiting feature provides the capability to limit the number of TCP and UDP flow
over the system. This limiting can be applied to all subscribers attaching to the system and to all APNs. This
feature is compatible with the existing per-subscriber limiting (configured using the flow limit-for-flow-type
charging action). Both limiting can be active in the same time.
System-wide flow limiting is implemented by comparing the “Effective Flows” periodically (~ every 10
seconds) against the configurable “System-wide Flow Limit”. Where “Effective Flows” is the number of
active data sessions, each identified by the 5-tuple key. If the “Effective Flows” exceeds the “System-wide
Flow Limit”, the Resource Manager indicates it to the active charging service. When ACS is aware of the
“System-wide Flow Limit” being reached, no more data sessions are setup. The packets are discarded. While