
The redirect extended community allows the traffic to be redirected
to a VRF routing instance that lists the specified route-target in its
import policy. If several local instances match this criteria, the choice
between them is a local matter (for example, the instance with the
lowest Route Distinguisher value can be elected). This extended
community uses the same encoding as the Route Target extended
community [RFC4360].
Command syntax based on route-target
redirect {ipv4} extcommunity rt <route_target_string>
Redirect
VRF
redirect-vrf
0x8008
The traffic marking extended community instructs a system to modify
the differentiated service code point (DSCP) bits of a transiting IP
packet to the corresponding value. This extended community is
encoded as a sequence of 5 zero bytes followed by the DSCP value
encoded in the 6 least significant bits of 6th byte.
Command syntax
set dscp <6 bit value>
set ipv4 traffic-class <8 bit value>
Set
DSCP
traffic-marking
0x8009
Announces the reachability of one or more flowspec NLRI. When a
BGP speaker receives an UPDATE message with the redirect-to- IP
extended community it is expected to create a traffic filtering rule for
every flow-spec NLRI in the message that has this path as its best
path. The filter entry matches the IP packets described in the NLRI
field and redirects them or copies them towards the IPv4 address
specified in the 'Network Address of Next- Hop' field of the associated
MP_REACH_NLRI.
The redirect-to-IP extended community is valid with any
other set of flow-spec extended communities except if that
set includes a redirect-to-VRF extended community (type
0x8008) and in that case the redirect-to-IP extended
community should be ignored.
Note
Command syntax
redirect {ipv4} next-hop <ipv4 address> {ipv4 address}
Redirect
IPv4
Nexthop
Redirect IP NH
0x0800
Configure a Class Map, on page 113
explains how you can configure specific match criteria for a class map.
BGP Flowspec Client-Server (Controller) Model and Configuration with ePBR
The BGP Flowspec model comprises of a Client and a Server (Controller). The Controller is responsible for
sending or injecting the flowspec NRLI entry. The client (acting as a BGP speaker) receives that NRLI and
programs the hardware forwarding to act on the instruction from the Controller. An illustration of this model
is provided below.
BGP Flowspec Client
Routing Configuration Guide for Cisco NCS 6000 Series Routers, IOS XR Release 6.4.x
110
Implementing BGP Flowspec
BGP Flowspec Client-Server (Controller) Model and Configuration with ePBR