| Directly connected routes can be
redistributed into a routing protocol by using the redistribute
connected command with a seed metric, as shown in this example:
RTB(config-router)#router eigrp
24
RTB(config-router)#redistribute connected metric 10000 100 255 1
1500
By using the connected
keyword, redistribution will inject all connected routes into the
routing protocol's updates, without configuring a network
statement.
Static routes can be redistributed in
the same way. This example illustrates how RTB could be configured
to redistribute static routes:
RTB(config-router)#router eigrp
24
RTB(config-router)#redistribute static metric 10000 100 255 1
1500
In the figure, RTB is configured for
two-way redistribution. Note that the seed metric is included each
time the redistribute
command is issued. The default-metric
command can be used as a shortcut in this situation.
The default-metric Command
An alternative to this redistribution configuration is to use the default-metric
command instead of including
the same seed metric with each redistribute
statement. Whenever the redistribute
command is used and the metric is not specified, the router will use
the default metric value as the seed metric. The default metric
value can be administratively configured for each routing protocol,
as shown in the second show
running-config output of the
Figure. In the second example, all EIGRP redistribute
commands will use the default metric, 10000 100 255 1 1500.
Meanwhile, all RIP redistribute
commands will use a default metric of 2.
|