RADIUS-Based Policing
How to Configure RADIUS-Based Policing
6
Prerequisites for Per-Service Policing Using RADIUS
You must configure all traffic classes on the ISG before referencing the classes in policy maps.
You must configure and apply QoS policy maps on the ISG before the ISG can construct and apply an
ANCP-based dynamic service policy.
Restrictions for Per-Service Policing Using RADIUS
Policing cannot be configured on the class-default class at the parent level of a hierarchical policy. You
can configure per-service policing on class-default classes at the child or grandchild level.
Transient policies are not visible in the running-configuration file. Only the original policy configuration
is visible.
Configuring Per-Service Policing Using RADIUS
To configure per-service policing, perform the following configuration tasks:
• Configuring a Hierarchical QoS Child Policy with Policing, page 6
• Configuring a Hierarchical QoS Parent Policy with Policing, page 8
• Configuring Per-Service Policing on the RADIUS Server, page 10
Configuring a Hierarchical QoS Child Policy with Policing
Use the following procedure to configure a hierarchical QoS Child policy with policing.
SUMMARY STEPS
1. enable
2. configure terminal
3. policy-map policy-map-name
4. class class-name
5. shape average mean-rate [[burst-size] [excess-burst-size]] [account {qinq | dot1q | user-defined
offset} aal5 subscriber-encap]
6. police bps [burst-normal] [burst-max] conform-action action exceed-action action [violate-action
action]
7. exit
DETAILED STEPS
Command Purpose
Step 1
enable
Example:
Router> enable
Enables privileged EXEC mode.
• Enter your password if prompted.
To Next Page
Loading...
Need help?
General