[Top] [Prev] [Next] [Bottom]

Using RIPv1, RIPv2, and Triggered RIP

The Routing Information Protocol (RIP) is an Interior Gateway Protocol (IGP). This document discusses both RIP and Triggered RIP. OpenROUTE software supports RIP Version 1 (RIPv1), RIP Version 2 (RIPv2), Triggered RIPv1, and Triggered RIPv2. The document includes the following topics:

Interior Gateway Protocols

The Routing Information Protocol (RIP)

Triggered RIP

Displaying RIP Prompts

Configuring RIP

RIP Commands

Interior Gateway Protocols

Routers that use a common routing protocol form an Autonomous System (AS). This common routing protocol is called an Interior Gateway Protocol (IGP). IGPs dynamically detect network reachability and routing information within an AS and use this information to build the IP routing table. IGPs can also import external routing information into the AS.

Most router loads contain one IGP for building the IP routing table and that is RIP. However, many of the OpenROUTE software loads contain both RIP and OSPF. The Bellman-Ford or the distance-vector algorithm is the basis for RIP. Link-state technology or the Shortest-Path First (SPF) algorithm is the basis for the Open Shortest Path First (OSPF) protocol. Routers can run OSPF and RIP simultaneously.

The Routing Information Protocol (RIP)

RIP is a distance-vector protocol that allows routers to exchange information about destinations for computing routes throughout the network. You should use this routing protocol primarily in homogeneous networks of moderate size. In such networks, it may be to your advantage to run RIP rather than OSPF. (RIPv2 and Triggered RIP provide some of the advantages of OSPF without the complexity.)

Destinations may be either networks or a special destination used to convey a default route. RIP, like OSPF, does not alter IP packets and routes them based on destination address only.

Distance-vector algorithms make each router periodically broadcast its routing tables to all its neighbors. Then a router knowing its neighbors' tables can decide which destination neighbor to use for routing a packet.

Limitations

RIP has the following limitations. These limitations apply to both RIPv1 and RIPv2.

RIPv1

 OpenROUTE software supports the RIPv1 standard defined in RFC 1058. RIPv1 has the following limitations:

RIPv2

 OpenROUTE software supports the RIPv2 standard defined in RFC 1723. RIPv2 provides the following advances over RIPv1:

The following sections discuss each of these enhancements.

Subnet Mask

With RIPv2, an interface's routing information contains a subnet mask. There is no guesswork about the subnet mask for a route.

With RIPv1, the interface's routing information does not contain a subnet mask; thus, the interface's subnet mask is not known to routers or systems outside the interface's own network. Such routers or systems assume that the subnet mask for the interface is the same as its network class mask. If the sending interface is in the same network as the interface receiving the RIP packet, however, it assumes that the subnet mask is the same as that configured for the destination interface.

With RIPv2, the RIPv1 restriction that router interfaces configured with addresses contained in the same network class have the same subnet mask no longer applies. Therefore, if you need variable subnet masks on the different router interfaces, you should configure RIPv2 to run on these interfaces.

With RIPv1, routing advertisements must be aggregated on the network class boundary when advertised outside the network. This is exactly what you need if your network class is completely contiguous, and there are no intervening networks that separate your network into non-contiguous segments.

However, if your network class is not contiguous, RIPv1 does not work since it has no subnet mask, and it must aggregate advertisements on the network class boundary. RIPv2 solves this problem and can be used to advertise the individual subnets that comprise each of the separate, non-contiguous segments of your network class.

Note: The ability to advertise subnets is something that OSPF could always do. You now have this ability by using RIPv2. OSPF is the superior routing protocol for large networks, but if you have a small or medium-sized network, RIPv2 may satisfy your needs if the ability to advertise subnets was the key criterion in your choice between RIP and OSPF.

Authentication

 RIPv2 supports security by password authentication of the routing information.

Next Hop

RIPv2 can specify the next hop address to which the router sends packets destined for an advertised destination.

When Should I Choose RIPv1 Over RIPv2?

You can configure each interface on your router to use either RIPv1 or RIPv2 or both. Follow these guidelines in choosing a routing configuration:

Setting RIP Flags

 You can customize RIP with configurable flags that control sending and receiving RIP information on each router interface. At the RIP Config> prompt, you use the enable/disable receiving and the enable/disable sending commands to configure RIP flags.

The set of routes sent out from a particular address is the union of the routes selected by setting any of the flags described in Table 1. At the RIP Config> prompt, you use the enable/disable sending commands to configure RIP send flags.

Table 1 RIP Send Flags
Flag If enabled, the interface . . .
Send All Routes Sends all routes in RIP responses.

Send Default Routes Advertises a default route in RIP responses if the router itself has a default gateway in operation. The router advertises the route to the default (authoritative) gateway as a route to destination 0.0.0.0.

Send Host Routes Sends all host routes in RIP responses. (Usually only used with RIPv2.)

Send Net Routes Sends all network-level routes in RIP responses.

Send Poisoned-Reverse Routes Sends poisoned-reverse routes in RIP responses. (You can disable this flag if necessary.)

Send Static Routes Advertises all directly connected networks and statically configured routes in RIP responses.

Send Subnet Routes Sends appropriate subnet-level routes in RIP responses.

The flags described in Table 2 control how the router incorporates information that RIP receives into its routing tables. At the RIP Config> prompt, you use the enable/disable receiving commands to configure RIP receive flags.

Table 2 RIP Receive Flags
Flag If disabled, the interface ...
Receive RIP Ignores RIP packets received on the specified interface.

Receive All Dynamic Routes Accepts RIP updates for all routes specified by the add accept-rip route command.

Receive Dynamic Host Routes Accepts RIP updates only for those hosts specified by the add accept-rip route command.

Receive Dynamic Net Routes Accepts RIP updates only for those networks specified by the add accept-rip route command.

Receive Dynamic Subnet Routes Accepts RIP updates only for those subnets specified by the add accept-rip route command.

The flags described in Table 3 also control how the router incorporates information that RIP receives into its routing tables. Certain flag settings allow RIP routes to override static routing information, but only if the RIP metric is better than the static route's metric. At the RIP Config> prompt, you use the enable/disable override commands to configure RIP override flags.

Table 3 Override Flags
Flag If enabled, RIP packets received on the interface ...
Override Default May override the router's default gateway.

Override Static Routes May override any of the router's statically configured routing information.

Triggered RIP

The objective of Triggered RIP is to reduce IP routing traffic to zero traffic over a WAN connection as long as there are no changes to the routing database. It is a modification to RIP, which depends heavily on frequently broadcasting routing information to the router's neighbors. This periodic broadcast of routing information every few seconds can have the following results:

Triggered RIP overcomes these limitations by exchanging incremental updates only on a change in routing information after the initial exchange of the entire routing information when the link first comes up.

Notes:

Features

 The following list provides descriptions of some of the important features of Triggered RIP.

Displaying RIP Prompts

 To display the RIP configuration prompt (RIP config>), do the following:

1. At the Config> prompt, enter protocol ip. 

Config>protocol ip
Internet protocol user configuration
IP config>rip
2. At the IP config> prompt, enter rip. 

Config>protocol ip
Internet protocol user configuration

IP config>rip
RIP config>
To display the RIP monitoring prompt (RIP>), do the following:

1. At the Monitor> prompt, enter protocol ip. 

Monitor>protocol ip
IP>
2. At the IP> prompt, enter rip. 

IP>rip
RIP>

Configuring RIP

 This section describes how to configure RIP initially. When configuring RIP, you can specify which set of routes the router advertises and/or accepts on each interface. You can also specify how RIP information affects static routing. Since RIP uses broadcast messages for its routing updates, you must also specify the format of the IP broadcast address.

1. Enable RIP with the following command. The default is to use RIP v2. 

RIP Config>enable rip
2. Enable or disable the various flags.

By default, RIP advertises all network and subnet routes out all interfaces of the router that have assigned IP addresses or are using unnumbered IP. Once you enable RIP, you can configure what it listens to and what it advertises by setting the various RIP flags. Configure these flags for each interface.

For information on the send, receive, and override flags, see Table 1, Table 2, and Table 3 respectively.

3. If your network is using RIP, and your connected network is using another routing protocol (such as OSPF, EGP, or BGP) to establish (originate) a single default route to that network, enter the set originate-rip-default command. 

RIP config>set originate-rip-default
Always originate default route? [No]:
Originate default if EGP/BGP routes available? [No]: y
   From AS number [0]?
   To network number [0.0.0.0]?
Originate default if OSPF routes available? [No]:
Cost [1]?
RIPv2 next hop [0.0.0.0]?

You need to originate a RIP default route for the other routing protocols to which your network may be connected. This default route directs traffic bound for a non-RIP network to a boundary router that functions as a portal. Originating a single default route means that the boundary router does not have to distribute the other network's routing information to the other nodes on its network.

Answering Yes means a default route is always originated (that is, defaults to previous behavior). Answering Yes to the EGP/BGP question originates a default whenever there are EGP or BGP routes in the routing table. Answering Yes to if OSPF routes available causes the RIP default to be advertised when OSPF routes are in the routing table. When the router originates a RIP default, it uses the original default cost number.

4. If you are using Triggered RIP, you must set the send-option for Triggered V1 or V2 and the receive-option for V1 or V2. 

RIP config>set send-option trigV1
Interface address [0.0.0.0]?11.2.84.42


RIP config>set receive-option V1
Interface address [0.0.0.0]?11.2.84.42

You can verify the information you configured with the list protocol command. 

RIP config>list protocol

RIP Commands

 This section summarizes and then explains RIP configuration and monitoring commands.

Press Space twice after you type a command to display the available options for the command. Enter help for information about using the command line interface.

[C] means the command is available at the RIP config> prompt.

[M] means the command is available at the RIP> prompt.

Table 4 lists the RIP commands.

Table 4 RIP Commands

Command Function
Add [C] Adds a RIP interface and the acceptance of a RIP route.

Clear [C] [M] At the RIP Config> prompt, clears all RIP information on all interfaces and resets all settings, including flags, to default settings. (If RIP is enabled, this command still clears RIP information, but RIP remains enabled.)

At the RIP> prompt, clears counters.

Delete [C] Deletes a RIP interface and the acceptance of a RIP route.

Disable [C] Disables RIP, a selected RIP interface, or the receiving or sending of RIP packets.

Dump [M] Dumps routing tables.

Enable [C] Enables RIP, a selected RIP interface, or the receiving or sending of RIP packets.

Interface [M] Displays an interface summary.

List [C] Lists RIP configuration information.

Neighbor [M] Displays summary information on the router's neighbors.

Ping [M] Sends requests to a designated address and waits for a response.

Route [M] Routes a particular network address.

Set [C] Sets RIP configuration parameters.

Statistics [M] Displays RIP statistics on the router.

Traceroute [M] Displays information on the routing destination path(s).

Add [C]

Adds routes that accept RIP packets and interfaces that run RIP.

Syntax: add

accept-rip-route
interface

accept-rip-route

 Allows exceptions to the discarding criteria defined by any of the disable receiving dynamic commands. Allows an interface to accept a specific RIP route, thus overriding any discarding criteria defined by any of the disable receiving dynamic command settings.

Note: This command has no effect if there are no disable receiving dynamic command settings

Example: add accept-rip-route

Network number [0.0.0.0]? 128.185.227.21

interface

 Adds a RIP interface to your router.

Example: add interface

Interface address [0.0.0.0]? 128.185.227.21

Clear [C] [M]

 You can use the clear command at both the configuration (RIP config>) and monitoring (RIP>) prompts.

Clear [C]

Deletes all configured interface records. RIP uses the default values for subsequent restarts.

Note: If you enabled RIP, it remains enabled after you use this command. All RIP parameters are set to default settings.

Syntax: clear

 Example: clear

All configured interface records will be deleted;  RIP will use
the default values for subsequent restarts.
Are you sure you want to delete them (Yes or [No]):

Clear [M]

 Clears counters.

Syntax: clear

Example: clear

Specify nothing to clear global counters, or 'Interface ip_addr' to clear interface counters, or 'Neighbor ip_addr' to clear neighbor counters.

Delete [C]

 Deletes a RIP configuration parameter that you installed previously by the add command.

Syntax: delete

accept-rip-route
interface

accept-rip-route

 Removes a route from the list of networks (interfaces) that the RIP protocol always accepts.

Example: delete accept-rip-route

Enter the address to be deleted [0.0.0.0]?128.185.227.10

interface

 Removes an interface from the RIP routing table.

Example: delete interface

Interface address [0.0.0.0]?128.185.227.16

Disable [C]

 Disables RIP or RIP parameters that you previously enabled by the add command.

Syntax: disable

interface
override default
override static routes
receiving dynamic
receiving rip
rip
sending

interface

 Prevents an interface from receiving or sending RIP packets.

Example: disable interface

Interface address [0.0.0.0]? 128.185.220.45

override default

 Prevents a RIP default route received on a particular interface from being installed as the router's default route.

Example: disable override default

Set for which interface address [0.0.0.0]?128.185.223.67

override static-routes

 Prevents RIP routes received on a particular interface from overriding any of the router's static routes.

Example: disable override static-routes

Set for which interface address [0.0.0.0]?128.185.223.67

receiving rip

 Prevents RIP from receiving any RIP updates.

Example: disable receiving rip

Set for which interface address [0.0.0.0]?128.185.223.67

receiving dynamic

 Prevents the designated interface from receiving any RIP dynamic host, network, or subnet routes.

Syntax: receiving dynamic

all
hosts
nets
subnets
Example: disable receiving dynamic all

Set for which interface address [0.0.0.0]?128.185.220.64
All

 Prevents a designated interface from receiving all dynamic RIP routes.

Hosts

 Prevents RIP from receiving dynamic host routes on the interface.

Nets

 Prevents RIP from receiving dynamic network routes on the interface.

Subnets

 Prevents RIP from receiving dynamic subnet routes on the interface.

rip

Turns off RIP.

Example: disable rip

sending

Prevents the router's selected interface from advertising all routes or selected routes.

Syntax: disable sending

all-routes
default-routes
host-routes
net-routes
poisoned-reverse-routes
subnet-routes
static-routes
Example: disable sending default-routes

Set for which interface address [0.0.0.0]?128.185.223.6
All-routes

 Prevents the interface from advertising all routes (default, network, subnet, static) in RIP updates.

Default-routes

 Prevents the interface from advertising a default route in RIP updates.

Host-routes

 Prevents the interface from advertising any host routes present in its table in RIP updates.

Net-routes

 Prevents the interface from advertising a network route in RIP updates.

Poisoned-reverse-routes

 Prevents RIP from re-advertising routes with a hop count of infinity on the interface from which the routes were learned.

Subnet-routes

 Prevents the interface from advertising a subnet route in RIP updates.

Static-routes

 Prevents the interface from advertising a static route in RIP updates.

Note: You can turn off the net-routes, subnet-routes, and static-routes flags individually. If you specify a route by any of the enabled flags, OpenROUTE software advertises the route.

Dump [M]

 Displays the RIP routing table. Lists a separate entry for each reachable RIP network or subnetwork. If there is a RIP default gateway in use, it appears at the end of the display.

This command is available at the RIP> prompt for convenience. To display more information, enter this command at the IP Config> prompt. See Using IP.

Syntax: dump

Example: dump

Type   Dest net         Mask       Cost     Age   Next hop(s)

Sbnt   50.0.0.0         FF000000   1        0     None
 Dir*  50.10.1.0        FFFFFF00   1        0     Eth/0

Routing table size: 768 nets (64512 bytes), 2 nets known
Type

 Indicates how the route was derived.

Dest net

 RIP destination network or subnetwork.

Mask

 IP address mask.

Cost

 Route cost.

Age

 For RIP routes, the time that has elapsed since the routing table entry was last refreshed.

Next hop(s)

 IP address of the next router on the path toward the destination host. Also, displays the interface that the sending router used to forward the packet.

Notes:

Enable [C]

 Enables various RIP flags that control sending and receiving RIP packets.

Syntax: enable

interface
override default
override static-routes
receiving dynamic
receiving rip
rip
sending

interface

 You can enable an interface individually for RIP. When you do so, it can both send and/or receive RIP packets.

Note: When you enable RIP, in order to be compatible with previous releases, OpenROUTE software enables RIP on all IP interfaces by default.

Example: enable interface

Interface address [0.0.0.0]?128.185.225.63

override default

 Enables default RIP routes received on a particular interface to overwrite the router's current default gateway, if the cost of the new default is cheaper.

Example: enable override default

Set for which interface address [0.0.0.0]?128.185.223.67

override static-routes

 Enables static RIP routes received on a particular interface to overwrite the router's statically configured network or subnet routes, if the cost of the RIP information is cheaper.

Example: enable override static-routes

Set for which interface address [0.0.0.0]?128.185.223.67

receiving rip

 Allows the interface to receive RIP updates.

Example: enable receiving rip

Set for which interface address [0.0.0.0]?128.185.223.67

receiving dynamic

 Allows the designated interface to receive specified routes for RIP updates. Modifies the processing of RIP updates that the router receives on a particular interface.

Syntax: enable receiving dynamic

all
hosts
nets
subnets
Example: enable receiving dynamic nets

Set for which interface address [0.0.0.0]?128.185.227.23
Enabling the options in the following list modifies the processing of RIP updates.
All

 Accepts all dynamic routes received on the interface.

Hosts

 Accepts any dynamic host routes. OpenROUTE software enables this command by default.

Nets

 Accepts any dynamic network-level routes. OpenROUTE software enables this command by default.

Subnets

 Accepts any dynamic subnet-level routes. OpenROUTE software enables this command by default.

rip

Enables RIP processing on your router.

Example: enable rip

Note: Use the enable sending or disable sending commands to configure the RIP routing update sending behavior. Use the enable receiving or disable receiving and the enable override or disable override commands to configure the RIP routing update receiving behavior.

sending

 Enables sending all routes or specified types of routes. Each separate enable sending command specifies that a certain set of routes should be advertised from a particular interface. The router includes a route in a RIP update only if you have included it by at least one of the enable sending command options.

Syntax: enable sending

all-routes
default-routes
host-routes
net-routes
poisoned-reverse-routes
subnet-routes
static-routes
Example: enable sending all-routes

Set for which interface address [0.0.0.0]?128.185.66.31
All-routes

 Allows the interface to advertise all routes in RIP updates.

Default-routes

 Allows the interface to advertise the default route (if one exists in its table) in RIP updates.

Host-routes

 Allows the interface to advertise any host routes present in its table in RIP updates.

Net-routes

 Allows the interface to advertise all network-level routes present in its table in RIP updates.

Poisoned-reverse-routes

 Allows the interface to re-advertise routes with a hop count of infinity. Enabled by default.

Subnet-routes

 Allows the interface to advertise all subnetwork-level routes present in its table in RIP updates.

Static-routes

 Allows the interface to advertise all statically configured and directly connected routes present in its table in RIP updates.

Interface [M]

Displays a summary of the running state of all configured RIP interfaces. Also, displays the configured values and the neighbors that it recognizes on its network, if you specify a particular interface in the command.

Syntax: interface

Example: interface 50.10.1.63

IP-Address       Intf   State   BadPkts  BadRtes  TrigUpdts  Nbrs (V1)

50.10.1.63       Eth/0  On      0        39663    13513      0     (0)
IP-Address

 IP address of each interface.

Intf

 Type of hardware device and the interface number.

State

 The running state of the protocol:

On— RIP is enabled on the interface, and the physical device is up.
Off— RIP is disabled on the interface.
Onpend— RIP is enabled on the interface, but the interface itself is either disabled or down.
BadPkts

 Packets received with the wrong RIP version or the wrong command.

BadRtes

 Routes that the interface ignores because of an invalid metric or address family.

TrigUpdts

 Triggered updates sent to the designated interface.

Nbrs

 Active neighbors.

(V1)

 RIP version number. (The number in the parentheses indicates the number of RIPv1 routers on the given interface.)

If you enter a specific interface address with the interface command, the software displays additional information on the designated interface.

Example: interface 50.10.1.65

IP-Address       Intf   State   BadPkts  BadRtes  TrigUpdts  Nbrs (V1)

50.10.1.6        Eth/0  On      0        39663    13513      0     (0)


Source Address:              50.10.1.65
Authentication Type:         None
Default cost:                0
Send option:                 V1&2
Receive option:              V1&2
Per-interface address flags: Send net and subnet routes
                             Receive No Dynamic host routes
Neighbors:                   None

List [C]

 Displays the RIP configuration.

Syntax: list

all
protocol
rip-routes-accept

all

 Displays the entire RIP configuration

Example: list all

RIP: enabled

Intf IP-address  Source-address   State  AuType  DefCost  Send    Recv

0    50.10.1.6   50.10.1.6        On     None    0        V1      V1

RIP default origination: disabled

Per-interface address flags:
  intf  0   50.10.1.6       Send net, subnet and host routes

Accept RIP updates always for:
  128.185.227.22    128.185.227.21
Intf

 The router's interface number.

IP-address

 The interface's IP address.

Source-address

 The router's address for sending RIP packets.

State

 State of the router: On, Off, Onpend.

AuType

 Identifies authentication: None or Simple Password.

DefCost

 Default cost

Send

Identifies RIPv1 or RIPv2 for sending RIP packets.

Recv

 Identifies RIPv1 or RIPv2 for receiving RIP packets.

Note: When you run the list all and list protocol commands, the only
Per-interface address flags displayed are the enabled send flags and the disabled receive flags.

protocol

 Displays the configured state of RIP.

Example: list protocol

RIP: enabled

Intf IP-address  Source-address   State  AuType  DefCost  Send    Recv

0    50.10.1.65  50.10.1.65       On     None    0        V1      V1

RIP default origination: disabled

Per-interface address flags:
  intf  0   50.10.1.65       Send net, subnet and host routes
See the listing under the list all command, for a description of the fields displayed in the list protocol command's output.

rip-routes-accept

Displays the set of routes that RIP always accepts.

Example: list rip-routes-accept

Accept RIP updates always for:
  128.185.227.22    128.185.227.21

Neighbor [M]

 Displays a statistical summary of your router's neighbor(s).

Syntax: neighbor

Example: neighbor

Neighbor-Addr        Phys    Vers  Age  BadPkts  BadRtes  RxSeq

128.185.223.1       PPP/0      V2  20   0        0        n/a
128.185.112.2       PPP/1      V2  10   0        0        n/a
Neighbor-Addr

 IP address of the neighbor.

Phys

 Associated router device.

Vers

 RIP version running over a physical device.

Age

 Seconds since last hearing from the neighbor.

BadPkts

 Invalid packets that the router discarded.

BadRtes

 Bad routes that the router ignored.

RxSeq

 If your router is running Triggered RIP, this is the last sequence number received from the neighbor that your router has acknowledged. If not running Triggered RIP, this entry is not applicable (n/a).

Ping [M]

Causes your router to send Internet Control Message Protocol (ICMP) Echo Requests to a given destination once per second and then watch for a response. You can use the ping command to isolate trouble in an internetwork environment.

The ping process continues incrementing the ICMP sequence number with each additional packet. OpenROUTE software reports matching ICMP Echo responses received with their sequence number and the round-trip time. The process stops when you type a character. At that time, OpenROUTE displays a summary of packet loss, round-trip time, and the number of ICMP unreachable destinations. The round trip usually takes about 20 milliseconds (depending on the router platform).

When a destination has a multicast address, the software may display multiple responses for each packet sent, one for each member of the multicast group. Each response contains the source address of the responding system.

Note: The size of the ping (number of data bytes in the ICMP message, excluding the ICMP header) is 56 bytes, and the TTL is 60 seconds.

This command is available at the RIP> prompt for convenience. To display more information, enter this command at the IP Config> prompt. See Using IP.

Syntax: ping interface-address

Example: ping 128.185.142.11

PING 128.185.142.11: 56 data bytes
64 bytes from 128.185.142.11: icmp_seq=0. time=0. ms
64 bytes from 128.185.142.11: icmp_seq=1. time=0. ms
64 bytes from 128.185.142.11: icmp_seq=2. time=0. ms
64 bytes from 128.185.142.11: icmp_seq=3. time=0. ms
64 bytes from 128.185.142.11: icmp_seq=4. time=0. ms
64 bytes from 128.185.142.11: icmp_seq=5. time=0. ms

----128.185.142.11 PING Statistics----
6 packets transmitted, 6 packets received, 0% packet loss
round-trip (ms)  min/avg/max = 0/0/0

Route [M]

 Displays the route (if one exists) to an IP destination. If a route exists, OpenROUTE software displays the IP address(es) of the next hop(s), along with detailed information concerning the matching routing table entry. (See the dump command.)

This command is available at the RIP Config> prompt for convenience. To display more information, enter this command at the IP Config> prompt. See Using IP.

Syntax: route ip_destination_address

Example: route 50.10.1.6

Destination:    50.10.1.0
Mask:           255.255.255.0
Route type:     Dir
Distance:       1
Age:            0
Next hop(s):    50.10.1.65        (Eth/0)
Tag:            0x00000000

Set [C]

 Sets certain RIP parameters and flags within your RIP configuration.

Syntax: set

authentication
default-metric
max-retry
originate-rip-default
poll-timer
receive-option
reply-timer
send-option
source-address

authentication

 You can configure RIP authentication per interface.

Note: You should configure all routers on the same IP network with the same type of authentication.

Syntax: set authentication

none
simple-password
Example: set authentication none

Interface address [0.0.0.0]?
Example: set authentication simple-password

Interface address [0.0.0.0]? 50.10.1.65
Authentication key? john
Enter Auth key again? john
None

 No password checks. This is the default.

Simple-password

 Use a cleartext password. Such a password is in alphanumeric or character mode.

default-metric

Sets the default metric to be used for the default route on this interface. The metric range is 1-15 hops, and 0 (zero) is the default value.

If you set the default metric to 0, OpenROUTE software uses the global default metric that you specified by the set-originate-rip-default command.

When you first define an interface, OpenROUTE software sets the default metric value for the interface to 0. If you specify the default metric, however, the defined metric takes precedence over the one you configured with the set originate-rip-default command. This applies for both RIPv1 and RIPv2.

Example: set default-metric

Interface address [0.0.0.0]? 50.10.1.65
Default metric (1-15), or 0 to use the global default [0]? 1

max-retry

 For Triggered RIP, sets the maximum number of times the interface transmits a request or a response before it gives up and starts polling the neighbor.

The range is 1-255. The default is 5.

Example: set max-retry

Interface address [0.0.0.0]? 50.10.1.65
Maximum number of retries (1-255) [36]? 5

originate-rip-default

 If your network is using RIP and a network that you have connected to is using another routing protocol (such as OSPF or EGP), this command allows you to set a RIP next hop address for a default route, together with the cost of the default route, in order to establish (originate) a single default route to the non-RIP network.

This default route directs traffic bound for a non-RIP network to a boundary router that functions as a portal. Originating a single default route means that the boundary router does not have to distribute the other network's routing information to the other nodes on its network.

When you enter this command, the software prompts you to originate a RIP default route for the other routing protocols to which your network may be connected.

Note: The next hop field only exists in the RIPv2 packet format, not in RIPv1 packet format.

The default cost is placed into the metric field of the RIP default route, v1 or v2, unless you have overriden it by setting a specific default cost for the interface by the set-default-metric command.

Example: set originate-rip-default

Always originate default route? [No]:
Originate default if EGP/BGP routes available? [No]:
Originate default if OSPF routes available? [No]:
Example: set originate-rip-default

Always originate default route? [No]: y
Cost [3]?
RIPv2 next hop [1.2.3.4]?
Example: set originate-rip-default

Always originate default route? [Yes]: n
Originate default if EGP/BGP routes available? [No]: y
   From AS number [0]?
   To network number [0.0.0.0]?
Originate default if OSPF routes available? [No]: y
Cost [3]?
RIPv2 next hop [1.2.3.4]?
Note: The actual displays in the examples depend on your router's current configuration and your responses to the queries.

poll-timer

 For Triggered RIP, sets the number of seconds to wait before polling the neighbor for routing updates.

The range is 1-3600 seconds. The default is 60 seconds.

Example: set poll-timer

Interface address [0.0.0.0]? 128.181.97.16
Poll Timer [30]?

receive-option

 Sets options for receiving RIP packets.

Syntax: set receive-option

none
both
v1
v2
Example: set receive-option both

All interfaces (Yes or [No]):
Interface address [0.0.0.0]? 126.181.26.2
None

 Receive no RIP packets at all.

Both

 Receive both RIPv1 and RIPv2 packets.

V1

 Receive only RIPv1 packets.

V2

 Receive only RIP v2 packets. This is the default.

reply-timer

For Triggered RIP, sets the number of seconds to wait for a routing response or acknowledgment from the neighbor on a given interface before retransmitting the routing request or response.

The range is 1-255 seconds. The default is 5 seconds.

Example: set reply-timer

Interface address [0.0.0.0]? 50.10.1.6
Reply Timer [5]?

send-option

 Sets options for sending RIP packets.

Syntax: set send-option

none
both-v1v2
v1
v2
trigv1
trigv2
Example: set send-option both

All interfaces (Yes or [No]):
Interface address [0.0.0.0]? 128.185.226.25
None

 Send no RIP packets at all.

Both-v1v2

 Send both RIPv1 and RIPv2 packets.

V1

 Send only RIPv1 packets.

V2

 Send only RIP v2 packets. This is the default.

Trigv1

 Send Triggered RIPv1 packets.

Trigv2

 Send Triggered RIP v2 packets.

Note: Triggered RIP only runs on point-to-point interfaces. OpenROUTE software interprets Triggered RIPv1 and Triggered RIPv2 as RIPv1 and RIPv2 respectively on other interface types.

source-address

 Source addresses are only relevant for unnumbered IP interfaces. OpenROUTE software uses a source address as the address for any RIP packet advertised on the designated interface.

Note: The source address must be either one of the router's interface addresses or the router's internal IP address.

If you configure this field, OpenROUTE sets the RIPv1 packet source to the specified source address.

Example: set source-address

Interface address [0.0.0.0]? 50.10.1.6
Source address [0.0.0.0]? 128.180.22.13

Statistics [M]

 Displays statistics for you router.

Syntax: statistics

Example: statistics

Originate default route:               No (0, 0.0.0.0)
RIP interfaces:                        1
Memory allocation failures:            0
I/O buffer allocation failures:        0
Responses sent to neighbors queries:   12
Changes made to the routing database:  10591
Originate default route

 Indicates whether or not you have enabled global default route origination on your router. If OpenROUTE software originates default route only when certain conditions are met (such as, the existence of EGP or BGP routes), also lists the configured route and the Autonomous System (AS) information.

RIP interfaces

 Number of interfaces configured to run RIP.

Memory failures

 Number of memory allocation failures.

Buffer failures

 Number of I/O buffer failures that prevented your router from sending RIP updates.

Response queries

 Number of responses that your router has made to queries from other systems.

Routing changes

 Number of route changes or updates made in the forwarding table by RIP. (Does not include refreshing a route's age.)

Traceroute [M]

Displays the entire path to a destination, hop by hop. For each successive hop, the traceroute command sends out three probes and displays the IP address of the responding system, together with the round-trip time associated with the response. If a particular probe receives no response, the software displays an asterisk. Each line in the display relates to the set of three probes, with the left-most number indicating the distance (in router hops) from the router sending the command.

A traceroute is complete when

When a probe receives an unexpected result, the software can display several indications:
!N

 The router received an ICMP Destination Unreachable (network unreachable).

!H

 The router received an ICMP Destination Unreachable (host unreachable).

!P

 The router received an ICMP Destination Unreachable (protocol unreachable); since the probe is a UDP packet sent to a strange port, we export a port unreachable.

!

 The destination was reached, but the reply that the destination sent was received with a TTL of 1. This usually indicates an error in the destination, prevalent in some versions of UNIX, whereby the destination inserts the probe's TTL in its replies. Unfortunately, this leads to a number of lines consisting solely of asterisks before the destination is finally reached.

This command is available at the RIP> prompt for convenience. For more information, enter this command at the IP> prompt. See Using IP.

Syntax: traceroute interface address

Example: traceroute 128.185.124.110 

TRACEROUTE 128.185.124.110: 56 data bytes
 1 128.185.142.7 16 ms 0 ms 0 ms
 2 128.185.123.22 16 ms 0 ms 16 ms
 3 * * *
 4 * * *
 5 128.185.124.110 16 ms ! 0 ms ! 0 ms !
TRACEROUTE

 Displays the destination address and the size of the packet being sent to that address.

1
2
5

 The first trace showing the destination's Network Service Access Point (NSAP) and the amount of time (in milliseconds) that it took the packet to arrive at the destination. The command traces the packet three times.

3 * * *
4 * * *

 The router expects some form of response from the destination, but the destination is not responding.

Destination
unreachable

 No route to the destination is available.


[Top] [Prev] [Next] [Bottom]

Copyright © 2000, NxNetworks. All rights reserved.