Hierarchical ingress policing allows users to specify the amount of traffic admitted into the system per SAP. It also allows users to share the available bandwidth per SAP among the different FCs of the SAP. For example, users can allow packets classified as Internet data to use the entire SAP bandwidth when other FCs do not have traffic.
Hierarchical ingress policing provides an option to configure a SAP aggregate policer per SAP on SAP ingress. Users should configure the PIR and, optionally, the burst size of the aggregate policer.
The aggregate policer monitors the traffic on different FCs and determines whether the packet is forwarded to an identified profile or dropped. The final behavior of the packet is based on the operating rate of the following items:
per FC policer
per SAP aggregate policer
See the command description of aggregate-meter-rate command in the 7210 SAS-Mxp, S, Sx, T Services Guide for information about the final color assigned of the packet.
The meter mode ‟trtcm2” (RFC 4115) is used only on SAP ingress. When the SAP aggregate policer is configured, the per FC policer can be only configured in ‟trtcm2” mode. The meter modes ‟srtCM” and ‟trtcm1” (formerly ‟trtcm”, as per RFC 2698) are used in the absence of an aggregate meter.
Before using a per-SAP aggregate meter/policer, meter resources must be allocated using the config system resource-profile ingress-internal-tcam sap-aggregate-meter command.When the amount of resources allocated for a SAP aggregate meter is changed, the node must be rebooted. The amount of resources allocated for this feature determines the number of SAPs that can use the aggregate meter/policer. See the ‟System Resource Allocation” section of the 7210 SAS-Mxp, R6, R12, S, Sx, T Basic System Configuration Guide for more information.