Important: Intelligent Traffic Control is only available if you have purchased and installed a feature license Intelligent Traffic Controlon your system. If you have not previously purchased this enhanced feature, contact your sales representative for more information.
•Important: ITC includes the class-map, policy-map and policy-group commands. Currently ITC does not include an external policy server interface.
Important: The EV-DO Rev A features are only available if you have purchased and installed the session use EV-DO Rev A PDSN License on your system. If you have not previously purchased this enhanced feature, contact your sales representative for more information.
For more information on EV-DO Rev A, refer to the Policy-Based Management and EV-DO Rev A chapter. For setting the DSCP parameters to control ITC functionality, refer to the Traffic Policy-Map Configuration Mode Commands chapter in the Command Line Reference.
• condition: Specifies the flow-parameters like source-address, destination-address, source-port, destination-port, protocol, etc. for ingress and/or egress packet.
• action: Specifies a set of treatments for flow/packet when condition matches. Broadly these actions are based on:Refer to the Traffic Policing and Shaping chapter for more information on Token Bucket Algorithm.For information on how to configure subscriber profiles on a remote RADIUS server, refer to the StarentVSA and StarentVSA1 dictionary descriptions in the AAA Interface Administration and Reference.Important: This section provides the minimum instruction set for configuring flow-based traffic policing on an AGW service. Commands that configure additional properties are provided in the Command Line Interface Reference.
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6 Save your configuration as described in the Verifying and Saving Your Configuration chapter.Important: In this mode classification match rules added sequentially with match command to form a Class-Map. To change and/or delete or re-add a particular rule user must delete specific Class-Map and re-define it.
context <vpn_context_name> [ -noconfirm ]class-map name <class_name> [ match-all | match-any ]match ip-tos <service_value>match ipsec-spi <index_value>
• <vpn_context_name> is the name of the destination context in which you want to configure the flow-based traffic policing.
• <class_name> is the name of the traffic class to map with the flow for the flow-based traffic policing. A maximum of 32 class-maps can be configured in one context.
• For description and variable values of these commands and keywords, refer to the Class-Map Configuration Mode Commands chapter of the Command Line Interface Reference.context <vpn_context_name>policy-map name <policy_name>class <class_name>qos traffic-police committed <bps> peak <bps> burst-size <byte> exceed-action { drop | lower-ip-precedence | allow } violate-action { drop | lower-ip-precedence | allow }
• <vpn_context_name> is the name of the destination context in which is configured during Class-Map configuration for flow-based traffic policing.
• <policy_name> is the name of the traffic policy map you want to configure for the flow-based traffic policing. A maximum of 32 policy maps can be configured in one context.
• <class_name> is the name of the traffic class to map that you configured in Configuring Class Maps section for the flow-based traffic policing.
• For description and variable values of these commands and keywords, refer to the Traffic Policy-Map Configuration Mode Commands chapter of the Command Line Interface Reference.context <vpn_context_name>policy-group name <policy_group>
• <vpn_context_name> is the name of the destination context which is configured during Class-Map configuration for flow-based traffic policing.
• <policy_group> is name of the traffic policy group of policy maps you want to configure for the flow-based traffic policing. A maximum of 32 policy groups can be configured in one context.
• <policy_map_name> is name of the traffic policy you configured in Configuring Policy Maps section for the flow-based traffic policing. A maximum of 16 Policy Maps can be assigned in a Policy Group.
• For description and variable values of these commands and keywords, refer to the Traffic Policy-Map Configuration Mode Commands chapter of the Command Line Interface Reference.context <vpn_context_name>subscriber name <user_name>policy-group <policy_group> direction [ in | out ]
• <vpn_context_name> is the name of the destination context configured during Class-Map configuration for flow-based traffic policing.
• <user_name> is the name of the subscriber profile you want to configure for the flow-based traffic policing.
• <policy_group> is name of the traffic policy group you configured in Configuring Policy Groups section for the flow-based traffic policing. A maximum of 16 Policy groups can be assigned to a subscriber profile.
• For description and variable values of these commands and keywords, refer to the Traffic Policy-Group Configuration Mode Commands chapter of the Command Line Interface Reference.
Step 1 Verify that your flow-based traffic policing is configured properly by entering the following command in Exec Mode: show subscribers access-flows full
![]() |
Cisco Systems Inc. |
Tel: 408-526-4000 |
Fax: 408-527-0883 |