127.0.0.0/8 reject static 0 0
127.0.0.1/32 lo0 connected 1 0
You can solve this problem by adding a second sequence to the route map to deal with the routes from the OSPF
domain. The expanded route map becomes:
route-map "PermitOdds" permit seq 10
match ip address prefix-list "Odds"
exit
route-map "PermitOdds" permit seq 20
match source-protocol ospf
exit
Now all the desired routes show up in the Southeast router's route table:
Southeast(config)# show ip route
IP Route Entries
Destination Gateway VLAN Type Sub-Type Metric Dist.
--------------- --------------- ---- --------- ---------- ---------- -----
10.1.11.0/24 10.2.21.1 21 rip 2 120
10.1.13.0/24 10.2.21.1 21 rip 2 120
10.1.15.0/24 10.2.21.1 21 rip 2 120
10.1.16.0/24 10.2.21.1 21 rip 2 120
10.2.21.0/24 VLAN21 21 connected 1 0
10.2.22.0/24 VLAN22 22 connected 1 0
10.2.23.0/24 VLAN23 23 connected 1 0
10.2.29.0/24 10.2.21.1 21 rip 2 120
10.3.31.0/24 10.2.21.1 21 rip 2 120
10.3.32.0/24 10.2.21.1 21 rip 2 120
10.3.33.0/24 10.2.21.1 21 rip 2 120
10.3.34.0/24 10.2.21.1 21 rip 2 120
10.3.37.0/24 10.2.21.1 21 rip 2 120
127.0.0.0/8 reject static 0 0
127.0.0.1/32 lo0 connected 1 0
In addition to using route maps to filter routes, you can also use them to apply properties to the routes. For
example, to apply a route metric when redistributing routes from the northern RIP domain to the OSPF domain,
you could apply the metric with a
set metric
command in a route map in the North router:
route-map "Metric25" permit seq 10
match source-protocol rip
set metric 25
exit
Then you could redistribute from the
router ospf
context:
router ospf
area backbone
redistribute connected
redistribute rip route-map "Metric25"
exit
The results are displayed in the Metric column of the East router's route map:
East(config)# show ip route
Chapter 12 Route Policy
285
