Configure local subscriber profiles on the system to support Traffic Policing by applying the following example configurations:

1. To apply the specified limits and actions to the downlink (data to the subscriber):

   configure 
        context <context_name> 
             subscriber name <user_name> 
                  qos traffic-police direction downlink 
                  end 

2. To apply the specified limits and actions to the uplink (data from the subscriber):

   configure 
        context <context_name> 
             subscriber name <user_name> 
                  qos traffic-police direction uplink 
                  end 

   Notes:

   • There are numerous keyword options associated with the qos traffic-police direction { downlink | uplink } command.
   • Repeat for each additional subscriber to be configured.

   Note

   If the exceed/violate action is set to "lower-ip-precedence", the TOS value for the outer packet becomes "best effort" for packets that exceed/violate the traffic limits regardless of what the ip user-datagram-tos-copy command in the Subscriber Configuration mode is configured to. In addition, the "lower-ip-precedence" option may also override the configuration of the ip qos-dscp command (also in the Subscriber Configuration mode). Therefore, it is recommended that command not be used when specifying this option.

Verify the subscriber profile configuration by applying the following example configuration:

context <context_name> 
     show subscriber configuration username <user_name> 

Save your configuration to flash memory, an external memory device, and/or a network location using the Exec mode command save configuration . For additional information on how to verify and save configuration files, refer to the System Administration Guide and the Command Line Interface Reference.

Set parameters by applying the following example configurations:

1. To apply the specified limits and actions to the downlink (the Gn direction):

   configure 
        context <context_name> 
             apn <apn_name> 
                  qos rate-limit downlink 
                  end 

2. To apply the specified limits and actions to the uplink (the Gi direction):

   configure 
        context <context_name> 
             apn <apn_name> 
                  qos rate-limit uplink 
                  end 

   Notes:

   • There are numerous keyword options associated with qos rate-limit { downlink | uplink } command.
   • Optionally, configure the maximum number of PDP contexts that can be facilitated by the APN to limit the APN's bandwidth consumption by entering the following command in the configuration:

     max-contents primary <number> total <total_number> 

   • Repeat as needed to configure additional Qos Traffic Policing profiles.

   Important

   If a "subscribed" traffic class is received, the system changes the class to background and sets the following: The uplink and downlink guaranteed data rates are set to 0. If the received uplink or downlink data rates are 0 and traffic policing is disabled, the default of 64 kbps is used. When enabled, the APN configured values are used. If the configured value for downlink max data rate is larger than can fit in an R4 QoS profile, the default of 64 kbps is used. If either the received uplink or downlink max data rates is non-zero, traffic policing is employed if enabled for the background class. The received values are used for responses when traffic policing is disabled.

Verify that your APNs were configured properly by entering the following command:

show apn { all | name <apn_name> } 

Save your configuration to flash memory, an external memory device, and/or a network location using the Exec mode command save configuration . For additional information on how to verify and save configuration files, refer to the System Administration Guide and the Command Line Interface Reference.

Set parameters by applying the following example configurations:

1. To apply the specified limits and actions to the downlink (data to the subscriber):

   configure 
        context <context_name> 
             subscriber name <user_name> 
                  qos traffic-shape direction downlink 
                  end 

2. To apply the specified limits and actions to the uplink (data to the subscriber):

   configure 
        context <context_name> 
             subscriber name <user_name> 
                  qos traffic-shape direction uplink 
                  end 

Verify the subscriber profile configuration by applying the following example configuration:

context <context_name> 
     show subscriber configuration username <user_name> 

Save your configuration to flash memory, an external memory device, and/or a network location using the Exec mode command save configuration . For additional information on how to verify and save configuration files, refer to the System Administration Guide and the Command Line Interface Reference.

Set parameters by applying the following example configurations.

1. To apply the specified limits and actions to the downlink (data to the subscriber):

   configure 
        context <context_name> 
             subscriber name <user_name> 
                  qos rate-limit downlink 
                  end 

2. To apply the specified limits and actions to the uplink (data to the subscriber):

   configure 
        context <context_name> 
             apn <apn_name> 
                  qos rate-limit uplink 
                  end 

Verify that your APNs were configured properly by entering the following command:

show apn { all | name <apn_name> } 

Save your configuration to flash memory, an external memory device, and/or a network location using the Exec mode command save configuration . For additional information on how to verify and save configuration files, refer to the System Administration Guide and the Command Line Interface Reference.