Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Tracing RIPng Traffic

Understanding RIPng Protocol Traffic Trace Operations

You can trace various RIPng protocol traffic to help debug RIP protocol issues.

To trace RIP protocol traffic, include the traceoptions statement at the [edit protocols ripng] hierarchy level:

You can specify the following RIPng protocol-specific trace options using the flag statement:

  • error—RIPng error packets

  • expiration—RIPng route expiration processing

  • holddown—RIPng hold-down processing

  • nsr-synchronization—Nonstop routing synchronization events

  • packets—All RIPng packets

  • request—RIPng information packets

  • trigger—RIPng triggered updates

  • update—RIPng 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 might 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 RIPng protocol using the traceoptions flag statement included at the [edit protocols ripng] 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


Use the trace flag all with caution as this might cause the CPU to become very busy.

Example: Tracing RIPng Protocol Traffic

This example shows how to trace RIPng 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 RIPng.

Figure 1 shows the topology used in this example.

Figure 1: RIPng Trace Operations Network TopologyRIPng Trace Operations Network Topology

CLI Quick Configuration shows the configuration for all of the devices in Figure 1. The section ../example/ripng-trace.html#configuration311__ripng-trace-step-by-step describes the steps on Device R1.




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 RIPng update interval:

  1. Configure the network interfaces.

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

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

    To configure RIPng in Junos OS, you must configure a group that contains the interfaces on which RIPng is enabled. You do not need to enable RIPng on the loopback interface.

  3. Configure RIPng tracing operations.

  4. Create the routing policy to advertise both direct and RIPng-learned routes.

  5. Apply the routing policy.

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


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 RIPng route updates are logged in the configured log file.

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

  2. From operational mode, enter the show log ripng-trace-file command with the | match 2001:db8::3 option.


The output shows that the route to 2001:db8::3/128 was deleted.