Cisco Cisco Packet Data Interworking Function (PDIF)
ACS Charging Action Configuration Mode Commands
▀ flow limit-for-bandwidth
▄ Command Line Interface Reference, StarOS Release 16
404
flow limit-for-bandwidth
For Session Control functionality this command allows you to enable/disable bandwidth limiting and configure the
uplink and downlink bandwidth limits for subscriber.
uplink and downlink bandwidth limits for subscriber.
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-bandwidth { { direction { downlink | uplink } peak-data-rate bps peak-
burst-size bytes violate-action { discard | lower-ip-precedence } [ committed-data-rate
bps committed-burst-size bytes [ exceed-action { discard | lower-ip-precedence } ] ] } |
{ id id } }
burst-size bytes violate-action { discard | lower-ip-precedence } [ committed-data-rate
bps committed-burst-size bytes [ exceed-action { discard | lower-ip-precedence } ] ] } |
{ id id } }
{ default | no } flow limit-for-bandwidth { direction { downlink | uplink } | id }
no
If previously configured, disables bandwidth control traffic policing for the specified direction for the current
subscriber.
subscriber.
default
Configures this command with its default setting.
direction { downlink | uplink }
Specifies the direction of flow to apply bandwidth limit:
downlink
: Flow of data towards subscriber.
uplink
: Flow of data from subscriber.
peak-data-rate bps
Specifies the peak data-rate for the subscriber, in bps (bits per second).
bps
must be an integer from 1 through 4294967295.
Default: 256000
peak burst-size bytes
The peak burst size allowed, in bytes.
bytes
must be an integer from 1 through 4294967295.
Default: 3000