Table of Contents
Advertisement
Traffic Policing and Shaping
Traffic Policing Configuration
Traffic Policing is configured on a per-subscriber basis. The subscribers can either be locally configured subscribers on
the system or subscriber profiles configured on a remote RADIUS server.
In 3GPP service Traffic policing can be configured for subscribers through APN configuration as well.
Important:
Important:
that the most common or likely commands and/or keyword options are presented. In many cases, other optional
commands and/or keyword options are available. Refer to the Command Line Interface Reference for complete
information regarding all commands.
Configuring Subscribers for Traffic Policing
Important:
Please refer to the documentation supplied with your server for further information.
Step 1
Configure local subscriber profiles on the system to support Traffic Policing by applying the following example
configurations:
Step a
configure
context <context_name>
Step b
configure
context <context_name>
Notes:
In 3GPP service attributes received from the RADIUS server supersede the settings in the APN.
Commands used in the configuration samples in this section provide base functionality to the extent
Instructions for configuring RADIUS-based subscriber profiles are not provided in this document.
To apply the specified limits and actions to the downlink (data to the subscriber):
subscriber name <user_name>
qos traffic-police direction downlink
end
To apply the specified limits and actions to the uplink (data from the subscriber):
subscriber name <user_name>
qos traffic-police direction uplink
end
Cisco ASR 5x00 Packet Data Network Gateway Administration Guide ▄
Traffic Policing Configuration ▀
511
Advertisement
Table of Contents
