The QoS Traffic Policing functionality supported by the GGSN implements QoS for subscribers based on the configuration of the APN template used as described in Traffic Policing and Shaping in this guide. As a result, all subscriber PDP contexts using the APN receive the same QoS level. This could lead to unused or under-utilized bandwidth by some subscribers and thus reducing the amount of resources available to others.
2. As the subscriber starts using some applications, the traffic gets classified on the basis of type of data packets or traffic as mentioned in section Classification of Application Traffic and accordingly the corresponding bit in Traffic-class-bitfield get set.Caution: For Dynamic QoS Renegotiation, two RADIUS attributes are required for remote subscriber configuration. For a particular subscriber, these attributes can be overridden without considering the timeout for Dynamic QoS Renegotiation and whether Dynamic QoS Renegotiation is enabled or not.
Step 1
Step 2
Step 3 Save your configuration as described in the Verifying and Saving Your Configuration chapter.
Step 4 Monitor the operations as described in the Monitoring Dynamic QoS Renegotiation Operation section.Important: Commands used in the configuration examples in this section provide base functionality to the extent 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.
context <context_name>ip access-list <acl_name>
• <context_name> must be the name of the destination context in which you want to configure the ACL. The same context must be used for APN configuration.active-charging service <service_name>charging-action <charging_action_name> [ -noconfirm ]qos-renegotiate traffic-class { background | conversational | interactive <priority> | streaming }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 } ] ]active-charging service <service_name>rulebase <rulebase_name> [ -noconfirm ]qos-renegotiate timeout <timeout>context <context_name>apn <apn_name>ip access-group <acl_name> [ in | out ]
• <context_name> must be the name of the destination context in which you have already configured the ACL, and want to configure the APN template.
• <acl_name> must be the name of the ACL that you have already configured in the context.
• If in the ip access-group command of the APN Configuration Mode, the optional in or out keywords are not specified, the ACL will be applied to all packets, in and out.
Step 1
Step 2
Step 3
Step 4 Save your configuration as described in the Verifying and Saving Your Configuration chapter.
Step 5 Monitor the operations as described in the Monitoring Dynamic QoS Renegotiation Operation section.Important: Commands used in the configuration examples in this section provide base functionality to the extent 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.
active-charging service <service_name>packet-filter <filter_name> [ -noconfirm ]ip remote-address { = { <ip_address> | <ip_address/mask> } | { range { <ip_address> | <ip_address/mask> } to { <ip_address> | <ip_address/mask> } }priority <priority>active-charging service <service_name>charging-action <charging_action_name> [ -noconfirm ]qos-class-identifier <identifier>tft packet-filter <filter_name>flow limit-for-bandwidth direction { downlink | uplink } peak-data-rate <bps> peak-burst-size <bytes> violate-action { discard | lower-ip-precedence }
• A number of optional keywords and variable are available for the flow limit-for-bandwidth direction command. Refer to the Command Line Interface Reference for more information regarding this command.context <context_name>apn <apn_name>
• show apn name <apn_name><apn_name> must be the name of the APN configured in the Configuring APNs for Dynamic QoS Renegotiation section.The output of this command displays the APN’s configuration. Examine the output for the ip output access-group and ip input access-group fields. For more details refer to the Applying a Single ACL to Multiple Subscribers section in this guide.show ip access-list <acl_name>show apn statistics [ all | name <apn_name> ]
The RADIUS attributes listed in the following table are used to configure Dynamic QoS Renegotiation for subscribers configured on remote RADIUS servers. More information on these attributes can be found in the AAA Interface Administration and Reference.
![]() |
Cisco Systems Inc. |
Tel: 408-526-4000 |
Fax: 408-527-0883 |