Cisco Cisco ASR 5700 문제 해결 가이드
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).
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:
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.
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.
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 flow limit-for-flow-
type command in the ACS Charging Action Configuration Mode set to no.
type command in the ACS Charging Action Configuration Mode set to no.
●
Example:
This command defines the maximum number of 200000 flows for the rulebase: