
Summarize Routes
Routes in the RIPv2 routing table are summarized by default, thus reducing the size of the routing table and improving routing
efficiency in large networks.
By default, the
autosummary
command in ROUTER RIP mode is enabled and summarizes RIP routes up to the classful network
boundary.
If you must perform routing between discontiguous subnets, disable automatic summarization. With automatic route summarization
disabled, subnets are advertised.
The
autosummary
command requires no other configuration commands. To disable automatic route summarization, enter
no
autosummary
in ROUTER RIP mode.
NOTE: If you enable the
ip split-horizon
command on an interface, the system does not advertise the summarized
address.
Controlling Route Metrics
As a distance-vector protocol, RIP uses hop counts to determine the best route, but sometimes the shortest hop count is a route
over the lowest-speed link.
To manipulate RIP routes so that the routing protocol prefers a different route, manipulate the route by using the
offset
command.
Exercise caution when applying an
offset
command to routers on a broadcast network, as the router using the
offset
command
is modifying RIP advertisements before sending out those advertisements.
The
distance
command also allows you to manipulate route metrics. To assign different weights to routes so that the ones with
the lower weight or administrative distance assigned are preferred, use the
distance
command.
To set route matrixes, use the following commands.
•
Apply a weight to all routes or a specific route and ACL.
ROUTER RIP mode
distance weight [
ip-address mask
[
access-list-name
]]
Configure the following parameters:
–
weight
: the range is from 1 to 255. The default is
120
.
–
ip-address mask
: the IP address in dotted decimal format (A.B.C.D), and the mask in slash format (/x).
–
access-list-name
: the name of a configured IP ACL.
•
Apply an additional number to the incoming or outgoing route metrics.
ROUTER RIP mode
offset-list
access-list-name
{in | out}
offset
[
interface
]
Configure the following parameters:
–
prefix-list-name
: the name of an established Prefix list to determine which incoming routes are modified
–
offset
: the range is from 0 to 16.
–
interface
: the type, slot, and number of an interface.
To view the configuration changes, use the
show config
command in ROUTER RIP mode.
Debugging RIP
The
debug ip rip
command enables RIP debugging.
When you enable debugging, you can view information on RIP protocol changes or RIP routes.
To enable RIP debugging, use the following command.
716
Routing Information Protocol (RIP)
Содержание S4048-ON
Страница 1: ...Dell Configuration Guide for the S4048 ON System 9 9 0 0 ...
Страница 146: ...Figure 14 BFD Three Way Handshake State Changes 146 Bidirectional Forwarding Detection BFD ...
Страница 477: ...Figure 68 Inspecting Configuration of LAG 10 on ALPHA Link Aggregation Control Protocol LACP 477 ...
Страница 480: ...Figure 70 Inspecting a LAG Port on BRAVO Using the show interface Command 480 Link Aggregation Control Protocol LACP ...
Страница 481: ...Figure 71 Inspecting LAG 10 Using the show interfaces port channel Command Link Aggregation Control Protocol LACP 481 ...
Страница 522: ...Figure 87 Configuring Interfaces for MSDP 522 Multicast Source Discovery Protocol MSDP ...
Страница 523: ...Figure 88 Configuring OSPF and BGP for MSDP Multicast Source Discovery Protocol MSDP 523 ...
Страница 524: ...Figure 89 Configuring PIM in Multiple Routing Domains 524 Multicast Source Discovery Protocol MSDP ...
Страница 528: ...Figure 91 MSDP Default Peer Scenario 1 528 Multicast Source Discovery Protocol MSDP ...
Страница 529: ...Figure 92 MSDP Default Peer Scenario 2 Multicast Source Discovery Protocol MSDP 529 ...
Страница 530: ...Figure 93 MSDP Default Peer Scenario 3 530 Multicast Source Discovery Protocol MSDP ...
Страница 633: ...Policy based Routing PBR 633 ...
Страница 777: ...Figure 119 Single and Double Tag TPID Match Service Provider Bridging 777 ...
Страница 778: ...Figure 120 Single and Double Tag First byte TPID Match 778 Service Provider Bridging ...