Cisco: Route-maps

One of the main purposes of a route-map in a Cisco router is customize traffic management beyond the boundaries of the routing table, For example create load balancing, or in a different field, applying TAG's on a routes learned by a routing protocolthe structure of the route-map is very simple, it’s a set of rules, each rule has two fields, match and set.For example a route-map used for policy based routing :

In this example I created a route-map named TEST, in case we have a match on access-list "100" change the next-hop to 1.1.1.1In case we don’t, moving to rule 20, and there in case we have a match on access-list "200" change the next-hop to 1.1.1.2In this example we can apply the route-map on the LAN interface, and set part of the network to pass through one line and another part through a different one,This can be done by anything in the ACL, source or destination IP, Protocol, or port.To make it more clear the ACL and applying the route-map:

In other words, access-list 100 will match all packets with the one of the following criteria source of 192.168.0.50, GRE protocol, or ISAKMP (UDP port 500)And I applied the route-map on the LAN interface, FastEthernet 0/0Another example of using a route-map is applying custom settings to routes learned (or advertised ) by a routing protocolfor example:

In this example I used a route-map and applied it on a BGP peer 2.2.2.2 (on the incoming routes) ,the first rule applies tag '10' to any route matched in ACL 100 and tag '20' to any other ( notice that if no match statement is configured the route-map will match everything)this should cover basic route-map configuration
Hope this post was helpful, If it was please consider a donation:
BTC Address: 1CnyMpjd1RntRDxSus2hu2aDMyzL4Kj29N

Sure, you can use the same Route-map on as many interfaces as you wish.If you want you can match traffic of both interfaces or even creating a route-map with no 'Match' statement and it will be match all.