100, valid, external, atomic-aggregate Community: 7018:5000 7018 8 701 7065, (received & used) 12.123.33.249 from 12.123.33.249 (12.123.33.249) Origin IGP, localpref 100, valid, external, atomic-aggregate Community: 7018:5000 7018 701 7065, (received & used) 12.123.29.249 from 12.123.29.249 (12.123.29.249) Origin IGP, localpref 100, valid, external, atomic-aggregate Community: 7018:5000 7018 701 7065, (received & used) 12.123.41.250 from 12.123.41.250 (12.123.41.250) Origin IGP, localpref 100, valid, external, atomic-aggregate Community: 7018:5000 7018 701 7065, (received & used) 12.123.1.236 from 12.123.1.236 (12.123.1.236) Origin IGP, localpref 100, valid, external, atomic-aggregate, best Community: 7018:5000 Specific Routing Protocols CHAPTER 11 Redistribution Redistribution is the process of injecting routes into a routing protocol from outside the realm of the protocol. For example, if you had a router that was running EIGRP and OSPF, and you needed the routes learned by EIGRP to be advertised in OSPF, you would redistribute the EIGRP routes into OSPF. Another common example is the redistribution of static or connected routes. Because static routes are entered manually, and not learned, they must be redistributed into a routing protocol if you wish them to be advertised. As Figure 11-1 shows, routes learned through EIGRP are not automatically adver- tised out of the OSPF interfaces. To accomplish this translation of sorts, you must configure redistribution within the protocol where you wish the routes to appear. EIGRP 100 OSPF 100 10.10.10.0/24 10.20.20.0/24 NOT advertised via OSPF 50.50.50.0/24 Learned via EIGRP Figure 11-1. Most routing protocols do not redistribute by default One of the main reasons that protocols do not redistribute routes automatically is that different protocols have vastly different metrics. OSPF, for example, calculates the best route based on the bandwidth of the links. EIGRP, on the other hand, uses bandwidth and delay (by default) to form a very different metric. While the router 