 redistributing is to keep it simple. It's easy to get confused when routes are being sent back and forth between routing protocols. Keeping the design as simple as possible will help keep the network manageable. You can create some pretty interesting problems when redistribution isn't working properly. The sim- pler the design is, the easier it is to troubleshoot. Redistribution is about converting one protocol's routes into a form that another pro- tocol can understand. You do this by assigning new metrics to the routes as they pass into the new protocol. Because the routes must adhere to the metrics of the new pro- tocol, the key to understanding redistribution is understanding metrics. When a protocol redistributes routes from any source, they become external routes in the new protocol. Routes can be redistributed from a limited number of sources: Static routes Routes that have been entered manually into the configuration of the router doing the redistribution can be redistributed into routing protocols. Injecting static routes on one router into a dynamic routing protocol can be a useful way of prop- agating those routes throughout the network. Connected routes Routes that are in the routing table as a result of a directly connected interface on the router doing the redistribution can also be redistributed into routing protocols. When a connected route is redistributed, the network in question will be inserted into the routing protocol, but the interfaces configured within that network will not advertise or listen for route advertisements. You can use this as an alternative to the network command when such behavior is desired. Other routing protocols Routes can be learned dynamically from other routing protocols that are active on the router doing the redistribution. Routes from any routing protocol can be re- distributed into any other routing protocol. An example of redistributing between routing protocols is OSPF redistributing into EIGRP. The same routing protocol from a different autonomous system or pr