Filter
Top Products
Implementing Routing Policy on Cisco IOS XR Software
Information About Implementing Routing Policy on Cisco IOS XR Software
RC-380
Cisco IOS XR Routing Configuration Guide
OL-14356-01
endif
end-policy
!
RP/0/RP0/CPU0:router# show bgp
BGP router identifier 10.0.0.1, local AS number 2
BGP main routing table version 11
BGP scan interval 60 secs
Status codes:s suppressed, d damped, h history, * valid, > best
i - internal, S stale
Origin codes:i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
*> 10.0.0.0 10.0.1.2 10 0 3 ?
*> 10.0.0.0/9 10.0.1.2 10 0 3 ?
*> 10.0.0.0/10 10.0.1.2 10 0 3 ?
*> 10.0.0.0/11 10.0.1.2 10 0 3 ?
*> 10.1.0.0/16 10.0.1.2 10 0 3 ?
*> 10.3.30.0/24 10.0.1.2 10 0 3 ?
*> 10.3.30.128/25 10.0.1.2 10 0 3 ?
*> 10.128.0.0/9 10.0.1.2 10 0 3 ?
*> 10.255.0.0/24 10.0.101.2 1000 555 0 100 e
*> 10.255.64.0/24 10.0.101.2 1000 555 0 100 e
....
RP/0/RP0/CPU0:router# show bgp policy route-policy test2
10.0.0.0/8 is advertised to 10.0.101.2
Path info:
neighbor:10.0.1.2 neighbor router id:10.0.1.2
valid external best
Attributes after inbound policy was applied:
next hop:10.0.1.2
MET ORG AS
origin:incomplete neighbor as:3 metric:10
aspath:3
Attributes after outbound policy was applied:
next hop:10.0.1.2
MET ORG AS
origin:incomplete neighbor as:3 metric:333
aspath:2 3
...
Table Policy
The table policy attach point allows the user to configure traffic-index values on routes as they are
installed into the global routing table. This attach point supports the BGP policy accounting feature.
BGP policy accounting uses the traffic indexes that are set on the BGP routes to track various counters.
This way, router operators can select different sets of BGP route attributes using the matching operations
and then set different traffic indexes for each different class of route they are interested in tracking.
The following example shows how to set the traffic index to 10 in IPv4 unicast routes that originated
from autonomous system 10.33. Likewise, any IPv4 unicast routes that originated from autonomous
system 11.60 have their traffic index set to 11 when they are installed into the FIB. These traffic indexes
are then used to count traffic being forwarded on these routes inline cards by enabling the BGP policy
accounting counters on the interfaces of interest.
route-policy sample-table
if as-path originates-from ‘10.33’ then
set traffic-index 10
elseif as-path originates-from ‘11.60’ then
set traffic-index 11