Cisco ASR 9000 Series Routing Configuration Manual page 250

Verify BGP Flowspec
Command or Action
Step 2
show flowspec summary
Example:
# show flowspec summary
FlowSpec Manager Summary:
Tables:
Flows:
RP/0/3/CPU0:RA01_R4#
Step 3 show flowspec vrf vrf_name | all { afli-all | ipv4 }
Example:
# show flowspec vrf default ipv4 summary
Flowspec VRF+AFI table summary:
VRF: default
AFI: IPv4
Total Flows:
Total Service Policies:
RP/0/3/CPU0:RA01_R4#
---------------------------------------------------
# show flowspec vrf all afi-all summary
Flowspec VRF+AFI table summary:
VRF: default
AFI: IPv4
Total Flows:
Total Service Policies:
--------------------------------------------------
# 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
Statistics
Matched
Transmitted
Dropped
Step 4 show bgp ipv4 flowspec
Example:
# show bgp ipv4 flowspec Dest:110.1.1.0/24,Source:10.1.1.0/24,
DPort:>=120&<=130,SPort:>=25&<=30,DSCP:=30/208
BGP routing table entry for Dest:110.1.1.0/24,
Source:10.1.1.0/24,Proto:=47,DPort:>=120&<=130,SPort:>=25&<=30,DSCP:=30/208
<snip>
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
Cisco ASR 9000 Series Aggregation Services Router Routing Configuration Guide, Release 5.3.x
220
2
1
1
1
1
1
(bgp.1)
(packets/bytes)
: 0/0
: 0/0
: 0/0
Implementing BGP Flowspec
Purpose
Provides a summary of the
flowspec rules present on the
entire node. In this example, IPv4
has been enabled, and a single
flow has been defined across the
entire table.
In order to obtain more granular
information on the flowspec, you
can filter the show commands
based on a particular
address-family or by a specific
VRF name. In this example, 'vrf
default' indicates that the flowspec
has 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 the table and
afli-all displays information for all
address families.
The detail option displays the
'Matched', 'Transmitted, ' and
'Dropped' fields. These can be used
to see if the flowspec rule you
have defined is in action or not. If
there is any traffic that takes this
match condition, it indicates if any
action has been taken (that is, how
many packets were matched and
whether these packets have been
transmitted or dropped.
Use this command to verify if a
flowspec rule configured on the
controller router is available on the
BGP side. In this example,
'redistributed' indicates that the
flowspec rule is not internally
originated, but one that has been
redistributed from the flowspec
process to BGP. The extended
community (BGP attribute used to
send the match and action criteria
to the peer routers) you have
configured is also displayed here.