Maximum path: 4 Routing for Networks: 10.0.0.0 Routing Information Sources: Gateway Distance Last Update Distance: (default is 120) Be careful with default metrics because they apply to all routes redistributed into the routing protocol, regardless of the source. If you now redistribute EIGRP into RIP, the metric assigned in RIP will be 3 because that is the configured default. You can override the default metric by specifying a metric on each redistribute command. Here, I have specified a default metric of 5, but I've also configured EIGRP routes to have a metric of 1 when redistributed into RIP: router rip version 2 redistribute static redistribute eigrp 100 metric 1 network 10.0.0.0 default-metri 5 no auto-summary Redistributing into RIP Here is the routing table on R3 after the final configuration on R2: R3# sho ip route [text removed] Gateway of last resort is not set 192.192.192.0/30 is subnetted, 1 subnets 192.192.192.4 is directly connected, Serialo/o 50.0.0.0/24 is subnetted, 1 subnets 50.50.50.0 [120/5] via 10.20.20.1, 00:00:07, Ethernet1/0 10.0.0.0/24 is subnetted, 2 subnets 10.10.10.0 [120/1] via 10.20.20.1, 00:00:10, Ethernet1/0 10.20.20.0 is directly connected, Ethernet1/0 The route 50.50.50.0/24 is in the routing table, and has a metric of 5. The route below it is a result of the network 10.0.0.0 statement on R2. This route is not a product of redistribution, and SO has a normal RIP metric. Another common issue is the need to advertise networks that are connected to a router, but are not included in the routing process. Figure 11-3 shows a network with three routers, all of which are participating in RIPv2. R1 has a network that is not included in the RIP process. The configuration for R1's RIP process is as follows: router rip version 2 network 10.0.0.0 no auto-summary 50.50.50.0/24 RIPv2 10.10.10.0/24 10.20.20.0/24 Figure 11-3. Redistributing connected routes into RIP There are no routers on the 50.50.50.0/24 network, SO enabling RIP on that inter- face would add useless broadcasts on that networ