Route Optimization in a Nutshell Passive Interface The passive-interface command works differently with the different IP routing protocols

s that support it. RIP/IGRP: o Can receive updates but doesnt send. OSPF: o Routing information is neither sent nor received via a passive interface. o The network address of the passive interface appears as a stub network in the OSPF domain. o Better to use proper wildcard mask in network command. EIGRP: o The router stops sending hello packets on passive interfaces. o When this happens, the EIGRP router cant form neighbor adjacencies on the interface or send and receive routing updates. RTA(config-router)#passive-interface bri0 Route Filter Policy Routing

Static routes: You can use the ip route command to dictate which path a router will select to a given destination, based on the destination address. However, through policy routing, you can manually program a router to choose a route based not only on destination, but on source as well. Human factors such as monetary expense, organizational jurisdiction, or security issues can lead administrators to establish policies, or rules that routed traffic should follow. Left to their default behavior, routing protocols may arrive at path decisions that conflict with these policies. Policy routes are nothing more than sophisticated static routes. The route-map command is used to configure policy routing, which is often a complicated task. Policy routing is a technique that allows the administrator to instruct the router to forward packets according to a configured policy rather than according to the contents of the routing table and the packets destination address. Alex Zinin

The distribute-list references an access-list, which creates a route filter Route filter a set of rules that precisely controls what routes a router sends or receives in a routing update.

We want to implement a policy on Linus such that: Traffic from 172.16.6.0/24 subnet is forwarded to Lucy Traffic from 172.16.7.0/24 subnet is forwarded to Pigpen All other traffic is routed normally Linus: inter S0 ip policy route-map Sally access-list 1 permit 172.16.6.0 0.0.0.255 access-list 2 permit 172.16.7.0 0.0.0.255 route-map Sally permit 10 match ip address 1 set ip next-hop 172.16.4.2 route-map Sally permit 15 match ip address 2 set ip next-hop 172.16.4.3

RTA(config)#router rip RTA(config-router)#network 10.0.0.0 RTA(config-router)#distribute-list 24 out s2 RTA(config)#access-list 24 deny 10.1.1.0 0.0.0.255 RTA(config)#access-list 24 permit any For each interface and routing process, Cisco IOS permits: one incoming global distribute-list one outgoing global distribute-list one incoming interface distribute-list one outgoing interface distribute-list

Administrative Distance Router(config-router)#distance weight [source-ip-address source-mask (accesslist-number | name)]

The following example illustrates how RTB could be configured to redistribute static routes:

You can also apply the distance command with optional arguments to make changes to selected routes based on where they originate. Remember that the administrative distance defaults exist for a reason and will serve a network well in most circumstances. Use the distance command only when certain that it is necessary to guarantee optimal routing. Using the optional arguments, we can configure a router to apply an administrative distance of 105 to all RIP routes received from 10.4.0.2. These values are local to the router, all other routers will apply the administrative distance of 120.

RTB(config-router)#router eigrp 24 RTB(config-router)#redistribute static metric 10000 100 255 1 1500 Examples router igrp 1 redistribute ospf 1 metric 10000 100 255 1 1500 passive-interface ethernet 1 network 172.20.0.0 router ospf 1 redistribute igrp 1 metric 30 metrictype 1 subnets network 172.20.112.2 0.0.0.0 area 0

RTZ(config)#router rip RTZ(config-router)#distance 105 10.4.0.2 255.255.255.0 Redistribution

The redistribution command is available for all IP routing protocols, so the command is considered to be independent of any one protocol. Note: However, the redistribution command can be used differently depending on the IP routing protocols involved.

Router(config-router)# redistribute protocol [process-id] {level-1 | level1-2 | level-2} [metric metric-value] [metric-type type-value] [match {internal | external 1 | external 2}] [tag tag-value] [route-map map-tag] [weight weight] [subnets]

Directly connected routes can be redistributed into a routing protocol by using the redistribute connected command

RTB(config-router)#router eigrp 24 RTB(config-router)#redistribute connected metric 10000 100 255 1 1500