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