Prefix-Specific Counting And Policing Actions; Prefix-Specific Counting And Policing Overview; Separate Counting And Policing For Each Ipv4 Address Range - Juniper EX9200 Features Manual

CHAPTER 10
Prefix-Specific Counting and Policing
Actions

Prefix-Specific Counting and Policing Overview

Separate Counting and Policing for Each IPv4 Address Range

Copyright © 2016, Juniper Networks, Inc.
Prefix-Specific Counting and Policing Overview on page 97
Filter-Specific Counter and Policer Set Overview on page 100
Example: Configuring Prefix-Specific Counting and Policing on page 100
Prefix-Specific Counting and Policing Configuration Scenarios on page 107
This topic covers the following information:
Separate Counting and Policing for Each IPv4 Address Range on page 97
Prefix-Specific Action Configuration on page 98
Counter and Policer Set Size and Indexing on page 99
Prefix-specific counting and policing enables you to configure an IPv4 firewall filter term
that matches on a source or destination address, applies a single-rate two-color policer
as the term action, but associates the matched packet with a specific counter and policer
instance based on the source or destination in the packet header. You can implicitly
create a separate counter or policer instance for a single address or for a group of
addresses.
Prefix-specific counting and policing uses a prefix-specific action configuration that
specifies the name of the policer you want to apply, whether prefix-specific counting is
to be enabled, and a source or destination address prefix range.
The prefix range specifies between 1 and 16 sequential set bits of an IPv4 address mask.
The length of the prefix range determines the size of the counter and policer set, which
consists of as few as 2 or as many as 65,536 counter and policer instances. The position
of the bits of the prefix range determines the indexing of filter-matched packets into the
set of instances.
97