Policy Maps
A policy map is a unique set of class
maps, policing parameters, and QoS parameters that you can apply to a certain class of
traffic.
When you configure a policy map, you
specify traffic policing parameters in one location that can be applied to multiple
ports. Follow these rules when configuring traffic policing:
- A policy map name must be unique among all maps of this type.
- A policy map name must begin with an alphabetic character (a-z or A-Z). An
underscore, a hyphen, and the numeric values 0-9 can be used in the body of the
name but not as the first character.
- You can configure a maximum of 1,024 policy maps.
- You can specify only one policy map per service policy.
- You can use ACL-based class maps and default class maps in one policy map.
- ACL-based, storm-control, and port-based rate limiting can coexist on an
interface. ACL-based rate limiting has the highest priority, followed by
storm-control rate limiting, and then port-based rate limiting.
- For an ingress or egress service policy, you can specify one default class map
per policy map.
- Broadcast, unknown unicast, and multicast (BUM) policies are counted separately.
- You cannot delete a policy map that is referenced in a service policy that is
applied on an interface.
- For each port attached to the policy map, you can specify the shaping rate for
smoothing egress traffic from an interface.
