bute command line, OSPF will assign a metric of 20 to all redistributed routes, except those from BGP, which will be assigned a metric of 1. While all redistributed routes are external, OSPF supports two types of external routes, which are cleverly described as type-1 and type-2 external routes. Type-1 routes are designated with 0 E1 in the routing table, while type-2 routes are designated with 0 E2. E1 routes include the metric as set at the point of redistribution, plus the metric of all the links within the OSPF autonomous system. E2 routes only include the metric set at the point of redistribution. Figure 11-4 illustrates how the OSPF metrics change throughout a simple network depending on the external route type in use. 50.50.50.0/24 OSPF cost :10 OSPF cost :10 Redistribute connected If E1 route then metric=110 If E1 route then metric=120 with a metric of 100 If E2 route then metric=100 If E2 route then metric=100 Figure 11-4. OSPF external route types Redistribution into OSPF defaults to type-2 routes. Which type should you use? That depends on your needs at the time. Generally, in smaller networks (less than, say, 10 routers), E2 routes may be easier to maintain, as they have the same value anywhere in the OSPF autonomous system. But to me, E1 routes function more logically because they increment with each hop, as do most other metrics. To set the route type, add the metric-type keyword to the redistribute command: 3(config-router)#redistribute eigrp 100 metric-type ? 1 Set OSPF External Type 1 metrics 2 Set OSPF External Type 2 metrics The metric type and the metric can be added onto one command line: R3 (config-router) #redistribute eigrp 100 metric-type 2 metric 100 In practice, every time you redistribute into OSPF, you should include the keyword subnets: R3 (config-router)#redistribute eigrp 100 metric 100 subnets Without the subnets keyword, OSPF will redistribute only routes that have not been subnetted. In the world of VLSM, where practically all networks are subnets, it is rare that you will not w