Traffic Filtering Actions - Cisco ASR 9000 Series Routing Configuration Manual

Implementing BGP Flowspec
Type 10
Type 11
Type 12
In a given flowspec rule, multiple action combinations can be specified without restrictions.
Redirect IP Nexthop is only supported in default VRF cases.
Note
Traffic Filtering Actions, on page 209
How to Configure BGP Flowspec, on page 212
required tuple definitions and action sequences.

Traffic Filtering Actions

The default action for a traffic filtering flow specification is to accept IP traffic that matches that particular
rule. The following extended community values can be used to specify particular actions:
Type
IPv4 Packet length Match on the total IP packet length (excluding
Layer 2, but including IP header). Values are
encoded using 1- or 2-byte quantities.
Encoding: <type (1 octet), [op, value]+>
Syntax:
matchpacket length {packet-length-value
|min-value -max-value}
IPv4 DSCP Defines a list of {operation, value} pairs used
to match the 6-bit DSCP field. Values are
encoded using a single byte, where the two
most significant bits are zero and the six least
significant bits contain the DSCP value.
Encoding: <type (1 octet), [op, value]+>
Syntax:
match dscp {dscp-value |min-value
-max-value}
IPv4 Fragmentation Identifies a fragment-type as the match
bits criterion for a class map.
Encoding: <type (1 octet), [op, bitmask]+>
Syntax:
match fragment type [is-fragment]
provides information on the actions that can be associated with a flow.
Extended PBR Description
Community Action
Cisco ASR 9000 Series Aggregation Services Router Routing Configuration Guide, Release 5.3.x
Information About Implementing BGP Flowspec
explains the procedure to configure BGP flowpsec with the
Multi value range
Multi value range
Bit mask
209