Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

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:

  • auth—RIP authentication

  • error—RIP error packets

  • expiration—RIP route expiration processing

  • holddown—RIP hold-down processing

  • nsr-synchronizationNonstop 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

    Note

    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)

  • normal—Normal events

  • policy—Policy processing

  • route—Routing information

  • state—State transitions

  • task—Routing protocol task processing

  • timer—Routing protocol timer processing

Note

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.

Requirements

No special configuration beyond device initialization is required before configuring this example.

Overview

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.

Figure 1: RIP Trace Operations Network Topology
RIP Trace Operations Network Topology

CLI Quick Configuration shows the configuration for all of the devices in Figure 1. The section Step-by-Step Procedure describes the steps on Device R1.

Configuration

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 [edit] hierarchy level.

Device R1

Device R2

Device R3

Step-by-Step Procedure

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:

  1. Configure the network interfaces.

    This example shows multiple loopback interface addresses to simulate attached networks.

  2. Configure the RIP group, and add the interface to the group.

    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.

  3. Configure RIP tracing operations.
  4. Create the routing policy to advertise both direct and RIP-learned routes.
  5. Apply the routing policy.

    In Junos OS, you can only apply RIP export policies at the group level.

Results

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.

Verification

Confirm that the configuration is working properly.

Checking the Log File

Purpose

Make sure that the RIP route updates are logged in the configured log file.

Action

  1. Deactivate the extra loopback interface address on Device R3.

  2. 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

Meaning

The output shows that the route to 172.16.3.3/32 was deleted.

Related Documentation

Release History Table
Release
Description
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.