Cisco Cisco Tunnel Terminating Gateway (TTG)
ACS Charging Action Configuration Mode Commands
flow limit-for-flow-type ▀
Command Line Interface Reference, StarOS Release 16 ▄
407
flow limit-for-flow-type
This command allows you to specify the maximum number of simultaneous flows (of this type) that a subscriber may
have, and the action to take if the limit is reached.
have, and the action to take if the limit is reached.
Product
All
Privilege
Security Administrator, Administrator
Mode
Exec > ACS Configuration > Charging Action Configuration
active-charging service service_name > charging-action charging_action_name
Entering the above command sequence results in the following prompt:
[local]host_name(config-charging-action)#
Syntax
flow limit-for-flow-type limit over-limit-action { discard | redirect-url url |
terminate-flow | terminate-session }
terminate-flow | terminate-session }
no flow limit-for-flow-type
no
If previously configured, deletes the flow limit-for-flow-type configuration in the current charging action.
limit
Specifies the maximum number of flows of a type exceeding which the specified over-limit-action triggers.
limit
must be an integer from 1 through 4000000000.
over-limit-action { discard | redirect-url url | terminate-flow | terminate-
session }
session }
Specifies the action to take on exceeding
limit
for a flow type:
discard
: Discards the packets
redirect-url url
: Redirects the flow to the specified URL.
url
must be an alphanumeric string
of 1 through 511 characters. For example, http://search.com.
terminate-flow
: Terminates the flow to which this packet belongs
terminate-session
: Terminates the session to which this packet belongs
Usage
Use this command to specify the number of simultaneous flows (of a type) that a subscriber may have, and
the action to take if the limit is reached.
All flows with the same content-id are considered to be the same type. This limit applies to the total of all
flows for a subscriber connection (that is, an individual PDP context or individual A10 tunnel).
If the flow is not HTTP, the
the action to take if the limit is reached.
All flows with the same content-id are considered to be the same type. This limit applies to the total of all
flows for a subscriber connection (that is, an individual PDP context or individual A10 tunnel).
If the flow is not HTTP, the
redirect-url
option is ignored, that is the packet is forwarded normally. Refer
to the
flow action
CLI command.