Tracing RIP Traffic
Understanding RIP Trace Operations
You can trace various types of RIP protocol traffic to help debug RIP protocol issues. Note that the functionality of tracing RIP protocol traffic described in this topic is not supported in Junos OS Releases 15.1X49, 15.1X49-D30, or 15.1X49-D40.
To trace RIP protocol traffic, include the traceoptions statement at the [edit protocols rip] hierarchy level:
You can specify the following RIP protocol-specific trace options using the flag statement:
error—RIP error packets
expiration—RIP route expiration processing
holddown—RIP hold-down processing
nsr-synchronization—Nonstop active routing synchronization events
packets—All RIP packets
request—RIP information packets
trigger—RIP triggered updates
update—RIP update packets
You can optionally specify one or more of the following flag modifiers:
detail—Detailed trace information
receive—Packets being received
send—Packets being transmitted
Use the detail flag modifier with caution as this may cause the CPU to become very busy.
Global tracing options are inherited from the configuration set by the traceoptions statement at the [edit routing-options] hierarchy level. You can override the following global trace options for the RIP protocol using the traceoptions flag statement included at the [edit protocols rip] hierarchy level:
all—All tracing operations
general—All normal operations and routing table changes (a combination of the normal and route trace operations)
task—Routing protocol task processing
timer—Routing protocol timer processing
Use the trace flag all with caution because this may cause the CPU to become very busy.
Example: Tracing RIP Protocol Traffic
This example shows how to trace RIP protocol operations.
No special configuration beyond device initialization is required before configuring this example.
In this example, Device R1 is set to trace routing information updates.
An export policy is also shown because an export policy is required as part of the minimum configuration for RIP.
Figure 1 shows the topology used in this example.
CLI Quick Configuration
To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your network configuration, and then copy and paste the commands into the CLI at the  hierarchy level.
The following example requires you to navigate various levels in the configuration hierarchy. For information about navigating the CLI, see Using the CLI Editor in Configuration Mode in the CLI User Guide.
To configure the RIP update interval:
- Configure the network interfaces.
This example shows multiple loopback interface addresses to simulate attached networks.[edit interfaces]user@R1# set fe-1/2/0 unit 1 family inet address 10.0.0.1/30user@R1# set lo0 unit 1 family inet address 172.16.0.1/32user@R1# set lo0 unit 1 family inet address 192.168.1.1/32
- Configure the RIP group, and add the interface to the
To configure RIP in Junos OS, you must configure a group that contains the interfaces on which RIP is enabled. You do not need to enable RIP on the loopback interface.[edit protocols rip group rip-group]user@R1# set neighbor fe-1/2/0.1
- Configure RIP tracing operations.[edit protocols rip traceoptions]user@R1# set file rip-trace-fileuser@R1# set flag route
- Create the routing policy to advertise both direct and
RIP-learned routes.[edit policy-options policy-statement advertise-routes-through-rip term 1]user@R1# set from protocol directuser@R1# set from protocol ripuser@R1# set then accept
- Apply the routing policy.
In Junos OS, you can only apply RIP export policies at the group level.[edit protocols rip group rip-group]user@R1# set export advertise-routes-through-rip
From configuration mode, confirm your configuration by entering the show interfaces, show protocols, and show policy-options commands. If the output does not display the intended configuration, repeat the configuration instructions in this example to correct it.
If you are done configuring the device, enter commit from configuration mode.
Confirm that the configuration is working properly.
Checking the Log File
Make sure that the RIP route updates are logged in the configured log file.
Deactivate the extra loopback interface address on Device R3.[edit interfaces lo0 unit 3 family inet]user@R3# deactivate address 172.16.3.3/32user@R3# commit
From operational mode on Device R1, enter the show log rip-trace-file command with the | match 172.16.3.3 option.
user@R1> show log rip-trace-file | match 172.16.3.3
Mar 1 11:39:53.975192 Setting RIPv2 rtbit on route 172.16.3.3/32, tsi = 0xbb69228 Mar 1 11:39:59.847118 172.16.3.3/32: metric-in: 16, change: 3 -> 16; # gw: 1, pkt_upd_src 10.0.0.2, inx: 0, rte_upd_src 10.0.0.2 Mar 1 11:39:59.847568 CHANGE 172.16.3.3/32 nhid 591 gw 10.0.0.2 RIP pref 100/0 metric 3/0 fe-1/2/0.1 <Delete Int> Mar 1 11:39:59.847629 Best route to 172.16.3.3/32 got deleted. Doing route calculation on the stored rte-info
The output shows that the route to 172.16.3.3/32 was deleted.