
Purpose
Command or Action
In order to obtain more granular information on the
flowspec, you can filter the show commands based on a
show flowspec vrf vrf_name
|
all
{
afli-all
|
ipv4
}
Step 3
particular address-family or by a specific VRF name. In
Example:
this example, 'vrf default' indicates that the flowspec has
# show flowspec vrf default ipv4 summary
been defined on the default table. The 'IPv4 summary' shows
the IPv4 flowspec rules present on that default table. 'VRF
all' displays information across all the VRFs configured on
Flowspec VRF+AFI table summary:
the table and afli-all displays information for all address
families.
VRF: default
AFI: IPv4
Total Flows:
1
Total Service Policies:
1
The
detail
option displays the 'Matched', 'Transmitted, ' and
'Dropped' fields. These can be used to see if the flowspec
RP/0/3/CPU0:RA01_R4#
---------------------------------------------------
rule you have defined is in action or not. If there is any
traffic that takes this match condition, it indicates if any
# show flowspec vrf all afi-all summary
action has been taken (that is, how many packets were
Flowspec VRF+AFI table summary:
matched and whether these packets have been transmitted
or dropped.
VRF: default
AFI: IPv4
Total Flows:
1
Total Service Policies:
1
--------------------------------------------------
# show flowspec vrf default ipv4 Dest:110.1.1.0/24,
Source:10.1.1.0/24,DPort:>=120&<=130,
SPort:>=25&<=30,DSCP:=30 detail
AFI: IPv4
Flow
:Dest:110.1.1.0/24,Source:10.1.1.0/24,
DPort:>=120&<=130,SPort:>=25&<=30,DSCP:=30
Actions
:Traffic-rate: 0 bps
(bgp.1)
Statistics
(packets/bytes)
Matched
:
0/0
Transmitted
:
0/0
Dropped
:
0/0
Use this command to verify if a flowspec rule configured
on the controller router is available on the BGP side. In this
show bgp ipv4 flowspec
Example:
Step 4
example, 'redistributed' indicates that the flowspec rule is
# show bgp ipv4 flowspec
Dest:110.1.1.0/24,Source:10.1.1.0/24,
not internally originated, but one that has been redistributed
from the flowspec process to BGP. The extended
DPort:>=120&<=130,SPort:>=25&<=30,DSCP:=30/208
community (BGP attribute used to send the match and action
BGP routing table entry for Dest:110.1.1.0/24,
criteria to the peer routers) you have configured is also
Source:10.1.1.0/24,Proto:=47,DPort:>=120&<=130,SPort:>=25&<=30,DSCP:=30/208
<snip>
displayed here. In this example, the action defined is to rate
limit the traffic.
Paths: (1 available, best #1)
Advertised to update-groups (with more than one
peer):
0.3
Path #1: Received by speaker 0
Advertised to update-groups (with more than one
peer):
0.3
Local
0.0.0.0 from 0.0.0.0 (3.3.3.3)
Origin IGP, localpref 100, valid,
redistributed, best, group-best
Received Path ID 0, Local Path ID 1, version
Routing Configuration Guide for Cisco NCS 6000 Series Routers, IOS XR Release 6.4.x
119
Implementing BGP Flowspec
Verify BGP Flowspec