Cisco Cisco Packet Data Gateway (PDG) Guida Alla Risoluzione Dei Problemi
ACS Configuration Mode Commands
system-limit ▀
Cisco ASR 5000 Series Command Line Interface Reference ▄
OL-22947-02
system-limit
This command configures the system-wide Layer 4 flow limit.
Important:
This command is customer specific. For more information, please contact your local sales or service
representative.
Product
ACS
Privilege
Security Administrator, Administrator
Syntax
Configures the default setting.
Default:
Default:
Disables the limit checking configuration.
Specifies the Layer 4 flows limit, and 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 5 tuple key. If the ―Effective Flows‖ exceeds the ―System-wide Flow
Limit‖, the Resource Manager indicates it to the ACS service. Once ACS is aware of the ―System-wide Flow
Limit‖ being reached, no more data sessions are setup. The packets are discarded. While processing a
successive flow-usage update from ACS service a change in behavior is indicated to ACS service to start
accepting data sessions. As this relies on periodic reporting there is an inherent delay in the detection of
―exceeding/returning once exceeded‖ to the flow limit.
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 5 tuple key. If the ―Effective Flows‖ exceeds the ―System-wide Flow
Limit‖, the Resource Manager indicates it to the ACS service. Once ACS is aware of the ―System-wide Flow
Limit‖ being reached, no more data sessions are setup. The packets are discarded. While processing a
successive flow-usage update from ACS service a change in behavior is indicated to ACS service to start
accepting data sessions. As this relies on periodic reporting there is an inherent delay in the detection of
―exceeding/returning once exceeded‖ to the flow limit.
Example
The following command sets the system limit for L4 flows to
The following command sets the system limit for L4 flows to
: