ocess Protocols that support autonomous systems, such as EIGRP, OSPF, and BGP, can redistribute among these systems. An example of a single protocol redistributing between autonomous systems is EIGRP 100 redistributing into EIGRP 200. Chapter 11: Redistribution Regardless of which protocol you redistribute into, you can still only do it from one of the sources just listed. When redistributing routes, you use the command redistribute -followed by the route source-within the protocol receiving the route. Redistribution is configured on the protocol for which the routes are destined, not the one from which they are sourced. No configuration is required on the protocol providing the routes. Redistributing into RIP We'll start with RIP because it has the simplest metric and, therefore, the simplest configuration. A common problem with configuring routing protocols is the inclusion of static routes. Because the routes are static, they are, by definition, not dynamic. But if they're stati- cally defined, why include them in a dynamic routing protocol at all? Figure 11-2 shows a simple network where redistribution of a static route is required. R1 has a directly connected interface on the 50.50.50.0/24 network, but is not running a routing protocol. R2 has a static route pointing to R1 for the 50.50.50.0/24 network. R2 and R3 are both communicating using RIPv2. In this case, R3 cannot get to the 50.50.50.0/24 network because R2 has not advertised it. 50.50.50.0/24 RIPv2 10.10.10.0/24 10.20.20.0/24 Static route: ip route 50.50.50.0 255.255.255.0 10.10.10.2 Figure 11-2. Redistributing a static route into RIPv2 For RIP to advertise the static route to R3, the route must be redistributed into RIP. Here is the full RIP configuration for R2: router rip version 2 redistribute static metric 1 network 10.0.0.0 no auto-summary Redistributing into RIP Notice the metric keyword on the redistribute command. This defines the RIP metric for all static routes injected into RIP. Another way to accomplish this is with the default-metric c