An egress policer can be configured to forward traffic that enters the policer with an exceed-profile state or exceeds its operational PIR instead of dropping it. The traffic exceeding the PIR is assigned an exceed-profile state. This is supported for any configured (not dynamic) policer in a SAP egress QoS policy, which can be used for both SAPs and subscribers, and in an egress queue group template that can be used on egress network ports.
When enable-exceed-pir is configured under the policer, the exceed-profile state of a packet takes precedence over the hard-out/in/inplus reclassification, specifically, traffic that is reprofiled to exceed within a SAP egress policer has an exceed-profile state regardless of whether it was reclassified at egress to hard-out, hard-in, or hard-inplus.
The stat-mode offered-total-cir-exceed command provides forward and drop counters for exceed-profile traffic, as follows:
configure
qos
queue-group-templates
egress
queue-group <queue-group-name> create
policer <policer-id> create
enable-exceed-pir
stat-mode offered-total-cir-exceed
exit
exit
exit
exit
sap-egress <policy-id> create
policer <policer-id> create
enable-exceed-pir
stat-mode offered-total-cir-exceed
exit
exit
exit
exit
The dot1p, outer dot1p, DSCP, and precedence can be remarked for the exceed-profile traffic.