RIP is probably the most common IP routing protocol in use. It is widely available and presents few obstacles to interoperability with other IP internetworks, most notably the Internet.
RIP performs sufficiently well in small IP internetworks that have simple architectures and few routers. However, RIP reveals its limitations in the large, complex internetworks that have become common in government and private-sector organizations throughout the world. Its most apparent limitations are the following:
To overcome or ease some of these limitations, the internetworking community developed various enhancements to RIP. RIP II, for example, is an enhanced version of RIP that supports variable-length subnet masks. It carries a field that contains the subnet mask of the destination network. RIP II also supports the use of subnet zero, whose addresses were reserved under the original IP specification. When configuring RIP on your router, you can run RIP, RIP II, or both on a single interface.
NOTE: Not all third-party routers support RIP II.
You can also enable poison reverse on an interface. This is a mechanism that causes RIP to advertise a route back through the same path from which it learned the route, but with a hop count of 16---that is, unreachable. Although poison reverse prevents routing loops, the unreachable routes carried in each RIP packet increase the bandwidth consumed by RIP traffic. This increase becomes significant in large internetworks.
RIP enables you to assign a cost value between 1 and 15 to each network interface you configure. This enables you to establish a preferred route according to the type of network media connected to the interface. For example, you might want to increase the cost of an interface that uses a slow link so that, given the choice, RIP uses the interface to a faster, less costly link. The default cost for each interface is 1. Do not increase this value on an interface unless you want to discourage its use as an eligible routing path.
RIP can run over most WAN connections, depending on which call type you use. On-demand calls, for example, typically use static routes instead of an active routing protocol. While using RIP over on-demand calls, RIP updates will not activate the call. Permanent calls on an IP network typically use a routing protocol, such as RIP, to communicate routing information. However, they can also use static routes to conserve bandwidth. RIP can also run over a nonbroadcast multiaccess network, such as X.25. For more information about using RIP over WAN connections, refer to "Configuring IP for a WAN Connection.”
When choosing an IP routing protocol, consider the following guidelines:
To configure RIP on the router, refer to "How to Configure RIP.”
However, if the network will continue to grow and perhaps become part of a larger IP internetwork, you should consider migrating the network from RIP to OSPF. For information about RIP-to-OSPF migration, refer to Novell Internet Access Server 4.1 Routing Concepts.
To configure RIP II, refer to "How to Configure RIP.” To configure OSPF, refer to "How to Configure OSPF.”
For instructions on enabling RIP I and RIP II simultaneously on a network interface, refer to "How to Configure RIP.”
You can also run RIP and OSPF concurrently; for more information, refer to "How to Configure OSPF.”
For additional information about RIP and related topics, refer to Novell Internet Access Server 4.1 Routing Concepts.
To enable RIP routing on the router and to configure RIP on a network interface, complete the following steps:
Load NIASCFG, then select the following parameter path:
Select Configure NIAS > Protocols and Routing > Protocols > TCP/IP
Make sure RIP routing is enabled globally. Set the RIP field to Enabled.
This is the default setting.
If you want to disable RIP routing on a single interface, set the Status parameter in the RIP bind options to Disabled. This action is described in Step 3.
Press Esc twice to return to the Internetworking Configuration menu, then select the following parameter path:
Select Bindings > an existing binding > RIP Bind Options
Configure the following parameters:
RIPI---Standard version of RIP used by most IP routers and end nodes. This is the default option.
RIPI & RIPII---Both versions of RIP. Select this option if your internetwork has nodes that support both RIP I and RIP II.
RIPII---Enhanced version of RIP that supports variable-length subnet masks.
Normal---Causes the router to send and accept RIP packets, RIP I, RIP II, or both.
Receive Only---Causes the router to only receive RIP packets.
Send Only---Causes the router to broadcast, in RIP packets, only the entries in its own routing table.
Some end nodes learn routes only by listening to RIP, even if portions of the internetwork run OSPF. Select Send Only if you want the router to broadcast the OSPF routes in its RIP I packets so that every end node can learn all available routes.
The RIP Bind Options menu also includes the following parameters:
IMPORTANT: Because the default settings for these parameters are suitable for most IP networks, you should change them only for a specific purpose. Incorrectly configuring these parameters can increase routing traffic or cause loss of connectivity on your network. If you are unfamiliar with these parameters, refer to Novell Internet Access Server 4.1 Routing Concepts.
For a WAN interface, you can configure the parameters for each WAN call. Refer to Step 3 of "Configuring Individual WAN Calls.”
Press Esc until you are prompted to save your changes, then select Yes.
Press Esc to return to the Internetworking Configuration menu.
If you want these changes to take effect immediately, select Reinitialize System and select Yes to activate your changes.