Configuring General Protocol Settings - SMC Networks TigerStack II SMC8848M Management Manual

length subnet masks, and multicast transmissions for route advertising
(RFC 1723).
• There are several serious problems with RIP that you should consider.
First of all, RIP (version 1) has no knowledge of subnets, both RIP
versions can take a long time to converge on a new route after the failure
of a link or router during which time routing loops may occur, and its
small hop count limitation of 15 restricts its use to smaller networks.
Moreover, RIP (version 1) wastes valuable network bandwidth by
propagating routing information via broadcasts; it also considers too few
network variables to make the best routing decision.

Configuring General Protocol Settings

RIP is used to specify how routers exchange routing information. When
RIP is enabled on this router, it sends RIP messages to all devices in the
network every 30 seconds (by default), and updates its own routing table
when RIP messages are received from other routers. To communicate
properly with other routers using RIP, you need to specify the RIP version
used globally by the router, as well as the RIP send and receive versions
used on specific interfaces (page 17-35).
Command Usage
• When you specify a Global RIP Version, any VLAN interface not
previously set to a specific Receive or Send Version (page 17-35) is set to
the following values:
- RIP Version 1 configures previously unset interfaces to send RIPv1
compatible protocol messages and receive either RIPv1 or RIPv2
protocol messages.
- RIP Version 2 configures previously unset interfaces to use RIPv2 for
both sending and receiving protocol messages.
• The update timer is the fundamental timer used to control all basic RIP
processes.
- Setting the update timer to a short interval can cause the router to
spend an excessive amount of time processing updates. On the other
C
ONFIGURING THE
R I
OUTING NFORMATION
P
ROTOCOL
17-31