SMC Networks TigerStack II SMC8848M

C ONFIGURING THE R OUTING I NFORMATION P ROTOCOL
17-39
CLI - This example sets the receive version to accept both RIPv1 or
RIPv2 messages, the send mode to RIPv1 compatible (i.e., called
v2-broadcast in the CLI), sets the method of preventing instability in the
network topology to Split Horizon, enables authentication via a simple
password (i.e., called text mode in the CLI).
Redistributing Routing Information from Other Domains
RIP can be confiugred to import external routing information from other
routing domains (that is, protocols or staic routes) into the autonomous
system.
Command Usage
• If a redistributon metric has not been configured for static routes, the
default-metric command (page 37-9) sets the metric value to be used
for all imported external routes.
• A route metric must be used to resolve the problem of redistributing
external routes with incompatible metrics.
• It is advisable to use a low metric when redistributing routes from
another protocol into RIP. Using a high metric limits the usefulness of
external routes redistributed into RIP. For example, if a metric of 10 is
defined for redistributed routes, these routes can only be advertised to
routers up to 5 hops away, at which point the metric exceeds the
maximum hop count of 15. By defining a low metric of 1, traffic can
follow a imported route the maximum number of hops allowed within a
RIP domain. However, using a low metric can increase the possibility of
routing loops For example, this can occur if there are multiple
redistribution points and the router learns about the same external
network with a better metric from a redistribution point other than that
derived from the original source.
Console(config)#interface vlan 1 24-2
Console(config-if)#ip rip receive version 1 2 37-16
Console(config-if)#ip rip send version v2-broadcast 37-17
Console(config-if)#ip split-horizon 37-19
Console(config-if)#ip rip authentication mode text 37-21
Console(config-if)#ip rip authentication key mighty 37-20
Console#