pf 100 redistribute eigrp 100 metric 10 subnets route-map No-EIGRP-Tag3 Here's how I've designed the route map: route-map No-EIGRP-Tag3 deny 10 match tag 3 route-map No-EIGRP-Tag3 permit 20 set tag 2 This one's a little more complicated than the last route map, but it's still pretty simple. The first line is a deny entry. It's followed by an instruction that says, "Match anything with a tag of 3." The match coming after the deny can be confusing, but the more you play with route maps, the more this will make sense. The next entry doesn't match anything; it permits everything and then sets a tag of 2 for the routes. Taken together, the route map essentially says, "Match anything with a tag of 3 and deny it," then "Match everything else and set the tag to 2." Now when we look at the OSPF database on router R2, we'll see that the route for 50.50.50.0/24 is gone. The route to 20.20.20.0/24 that was learned from R1 is still there, however, because it was not tagged with a 3: R2#sho ip ospf database OSPF Router with ID (10.10.10.2) (Process ID 100) Router Link States (Area 0) Link ID ADV Router Checksum Link count 10.10.10.2 10.10.10.2 0x80000002 0x00F5BA 1 20.20.20.1 20.20.20.1 0x80000002 0x009DD9 1 Net Link States (Area 0) Link ID ADV Router Checksum 10.10.10.1 20.20.20.1 0x80000001 0x00B5CA Type-5 AS External Link States Link ID ADV Router Checksum Tag 20.20.20.0 10.10.10.2 0x80000001 0x00D774 2 20.20.20.0 20.20.20.1 0x80000001 0x002DF9 0 The route still exists in the EIGRP topology table on R2; it just wasn't redistributed into OSPF because of our cool route map. In the routing table on R1, we'll now see that 50.50.50.0/24 is pointing to R3 the way we want it to: R1#sho ip route [text removed] Chapter 11: Redistribution Gateway of last resort is not set 50.0.0.0/24 is subnetted, 1 subnets 50.50.50.0 [170/156160] via 20.20.20.3, 00:00:16, FastEtherneto/1 20.0.0.0/24 is subnetted, 1 subnets 20.20.20.0 is directly connected, FastEtherneto/1 10.0.0.0/24 is subnetted, 1 subnets 10.10.10.0 is directly connected, FastEthe