Juniper EX9200 Features Manual page 154

Traffic Policers Feature Guide for EX9200 Switches
Requirements
Overview
Configuration
136
Configuration on page 136
Verification on page 142
Before you begin, make sure that interface for which you are applying ingress or egress
policer overhead is hosted on one of the following:
Gigabit Ethernet IQ2 PIC
IQ2E PIC
DPCs in MX Series routers
This example shows how to configure policer overhead values for all physical interfaces
on a supported PIC or MPC so that the rate shaping value configured on a logical interface
is accounted for in any policing on that logical interface.
Topology
The router hosts a Gigabit Ethernet IQ2 PIC, installed in PIC location 3 of the Flexible PIC
Concentrator (FPC) in slot number 1. The physical interface on port 1 on that PIC is
configured to receive traffic on logical interface 0 and send it back out on logical
interface 1. Class-of-service scheduling includes 100 Mbps of traffic rate-shaping overhead
for the output traffic. A policer egress overhead of 100 bytes is configured on the entire
PIC so that, for any policers applied to the output traffic, 100 bytes are added to the final
Ethernet frame length when determining ingress and egress policer actions.
NOTE:
Traffic rate-shaping and corresponding policer overhead are configured
separately:
You configure rate shaping at the
interface-name unit unit-number]
You configure policer overhead at the
hierarchy level.
pic-number]
When a policer overhead value is changed, the PIC or DPC goes offline and then comes
back online.
The following example requires you to navigate various levels in the configuration
hierarchy. For information about navigating the CLI, see Using the CLI Editor in Configuration
Mode.
[edit class-of-service interfaces
hierarchy level.
[edit chassis fpc slot-number pic
Copyright © 2016, Juniper Networks, Inc.