Scribd
Upload
752 views1 page

Route Policy RPL XR

The document compares route map configuration in IOS to route policy configuration in IOS-XR. It outlines equivalent configuration for access lists, prefix lists, AS path lists, community lists, and basic route maps/policies. It then provides examples of configuring route maps on IOS to match prefixes and set attributes like weight, local preference, AS path prepend, MED, and redistribution policy, along with the equivalent IOS-XR route policy configuration.

Uploaded by

Harjanto Handi Kusumo
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
752 views1 page

Route Policy RPL XR

The document compares route map configuration in IOS to route policy configuration in IOS-XR. It outlines equivalent configuration for access lists, prefix lists, AS path lists, community lists, and basic route maps/policies. It then provides examples of configuring route maps on IOS to match prefixes and set attributes like weight, local preference, AS path prepend, MED, and redistribution policy, along with the equivalent IOS-XR route policy configuration.

Uploaded by

Harjanto Handi Kusumo
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

Route-map vs Route policy language - IOS to XR configuration

Description
ip access-list strd/Ext (IOS)
ipv4 access-list [name] (XR)

ip prefix-list (IOS)
prefix-set (XR)
ip as-path access-list (IOS)
as-path-set (XR)
ip community-list (IOS)
community-set (XR)
Basic Route-map (IOS)
Basic Route-policy (XR)

IOS Config
ip access-list standard TEST
permit 1.1.1.1
!
ip access-list extended TEST2
permit ip host 1.1.1.1 host 2.2.2.2
ip prefix-list ADVERTISE permit 1.1.1.1/32

ip as-path access-list 1 permit _65000$


ip as-path access-list 1 permit _65000_

ip community-list 1 permit 100:65000

route-map TEST permit 10

IOS-XR config
ipv4 access-list TEST
10 permit ip host 9.9.9.9 any
!
ipv4 access-list TEST2
permit ipv4 host 1.1.1.1 host 2.2.2.2
prefix-set ADVERTISE
1.1.1.1/32
end-set
as-path-set TEST
originates-from '65000'
dfa-regex '_65000_'
end-set
community-set TEST
100:65000
end-set
route-policy TEST

route-map TEST permit 10


match ip address prefix-list ADVERTISE

route-policy TEST
if destination in ADVERTISE then
pass
endif
end-policy

route-map TEST deny 10


match ip address prefix-list ADVERTISE

route-policy TEST
if destination in ADVERTISE then
drop
endif
end-policy

Set Weight

route-map TEST permit 10


match ip address prefix-list ADVERTISE
set weight 1000

set local preferance

route-map TEST permit 10


match ip address prefix-list ADVERTISE
set local-preference 200

route-policy TEST
if destination in ADVERTISE then
set weight 1000
endif
end-policy
route-policy TEST
if destination in ADVERTISE then
set local-preference 200
endif
end-policy
route-policy TEST
if destination in ADVERTISE then
prepend as-path 65000 3
endif
end-policy
route-policy TEST
if destination in ADVERTISE then
set med 100
endif
end-policy

match prefix-list (set) + permit

match prefix-list (set) + deny

as-path prepend

set MED

redistribution policy

route-map TEST permit 10


match ip address prefix-list ADVERTISE
set as-path prepend 65000 65000 65000

route-map TEST permit 10


match ip address prefix-list ADVERTISE
set metric 100

route-map EIGRP_INTO_BGP permit 10


description match EIGRP networks
match ip address prefix-list EIGRP_SUBNETS

Notes
IOS XR does not have the
concept of standard vs
extended, only named acl nut
you can still use [0-9]

In IOS-XR the "3" after "65000"


means prepend three times.
Does not mean as-path will be
65000 3

route-policy EIGRP_INTO_BGP
if destination in EIGRP_SUBNETS then
pass
endif
end-policy

John Spaulding, CCIE #25143

You might also like