Example #3: Ingress Bandwidth Policer Per Custom - ADTRAN Total Access 5000 Deployment Manual

The following policers would apply to the respective EVC.
Policer #1:
• CIR/EIR Coupling = Disabled
• CIR = 1000 kbps
• EIR = 2000 kbps
• CBS = 3125 bytes
• EBS = 12500 bytes
• Mode = Per EVC
• EVC = #1
Policer #2:
• CIR/EIR Coupling = Disabled
• CIR = 2000 kbps
• EIR = 3000 kbps
• CBS = 3125 bytes
• EBS = 12500 bytes
• Mode = Per EVC
• EVC = #2
Policer #1 is applied to ingress traffic of EVC‐map #1, because all egress traffic into the MEN
from EVC #1 is in the EVC‐map #1 criteria.
Policer #2 is applied to ingress traffic of EVC‐map #2, because all egress traffic into the MEN
from EVC #2 is in the EVC‐map #2 criteria.

Example #3: Ingress Bandwidth Policer per Custom

A single bandwidth policer can be applied to ingress frames of a particular EVC map or set of
EVC maps. Use this application of the bandwidth policer to limit traffic on ingress frames
without having to specify the UNI or EVC. The custom policer makes it possible to limit traffic
on EVC maps that have CE‐VLANs as the criteria. It also allows implementing different
policers on EVC maps that have a common connected to an EVC but are not duplicate EVC
maps.
Consider the conditions of "Example #2: Two CE‐VLANs Mapped to One EVC" on page F‐11
where two CE‐VLANs are received at the same UNI port and mapped to the same EVC. In
order to enforce a different bandwidth policer for each CE‐VLAN, apply separate custom
policers to each EVC map.
The following policers can apply to the respective EVC maps.
Policer #1
• CIR/EIR Coupling = Disabled
• CIR = 1000 kbps
• EIR = 2000 kbps
• CBS = 3125 bytes
• EBS = 12500 bytes
• Mode = Custom
65K510DEP08-1A
Appendix F, NetVanta Examples - Bandwidth Policer
F-17