Cisco Cisco Packet Data Interworking Function (PDIF) Guía Para Resolver Problemas
![Cisco](https://files.manualsbrain.com/attachments/7380d0050044647c30f5c24bbbf5d0c0b6d9bb84/common/fit/150/50/faa183d287233c52228cfea3dbc2a127fe780f60564fcb0955d9c3d1cd23/brand_logo.png)
Rulebase Configuration Mode Commands
▀ flow limit-across-applications
▄ Cisco ASR 5000 Series Command Line Interface Reference
OL-22948-01
flow limit-across-applications
This command limits the total number of simultaneous flows per Subscriber/APN sent to a rulebase regardless of the
flow type, or limit flows based on the protocol type under the Session Control feature.
flow type, or limit flows based on the protocol type under the Session Control feature.
Product
ECS
Privilege
Security Administrator, Administrator
Syntax
Removes previously configured flow limit related to a rulebase.
Specifies the maximum number of flows across all applications for a rulebase.
must be an integer from 1 through 4000000000.
Default: No limits
Specifies the maximum limit of non-TCP type flows.
must be an integer from 1 through 4000000000.
Default: No limits
Specifies the maximum limit of TCP flows.
must be an integer from 1 through 4000000000.
Default: No limits
Usage
Use this command to limit the total number of flows allowed for a rulebase regardless of flow type, or limit
flows based on the protocol—non-TCP (connection-less) or TCP (connection-oriented).
If a subscriber attempts to exceed these limits system discards the packets of new flow. This limit processing
of this command has following aspects for UDP, TCP, ICMP and some of the exempted flows:
UDP/ICMP: System waits for the flow timeout before updating the counter and removing it from the count of
number of flows.
TCP: After a TCP flow ends, system waits for a short period of time to accommodate the retransmission of
any missed packet from one end. TCP flows those are ended, but are still in wait period for timeout are
exempted for this limit processing.
Exempted flows: System exempts all the other flows specified with the
flows based on the protocol—non-TCP (connection-less) or TCP (connection-oriented).
If a subscriber attempts to exceed these limits system discards the packets of new flow. This limit processing
of this command has following aspects for UDP, TCP, ICMP and some of the exempted flows:
UDP/ICMP: System waits for the flow timeout before updating the counter and removing it from the count of
number of flows.
TCP: After a TCP flow ends, system waits for a short period of time to accommodate the retransmission of
any missed packet from one end. TCP flows those are ended, but are still in wait period for timeout are
exempted for this limit processing.
Exempted flows: System exempts all the other flows specified with the
command in the Charging Action Configuration Mode set to
.