Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

RIPng Timers

Example: Configuring RIPng Update Interval

This example shows how to configure the RIPng update interval and how to monitor the impact of the change.

Requirements

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

Overview

In this example, Device R2 has an update interval of 60 seconds for its neighbor Device R1, and an update interval of 10 seconds for its neighbor Device R3.

This example is not necessarily practical, but it is shown for demonstration purposes. Generally, we recommend against changing the RIPng timers, unless the effects of a change are well understood. Normally, the default values are best left in effect for standard operations.

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 Timers Network TopologyRIPng Timers Network Topology

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

Topology

Configuration

Procedure

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 different update intervals for the two RIPng neighbors.

    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. Create the routing policy to advertise both direct and RIPng-learned routes.

  4. Apply the routing policy.

    In Junos OS, you can only apply RIPng 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 RIPng Updates Sent by Device R2

Purpose

Make sure that the RIPng update packets are sent at the expected interval.

Action

From operational mode, enter the show ripng statistics command.

Meaning

The update interval field shows that the interval is 60 seconds for its neighbor Device R1 and 10 seconds for its neighbor Device R3. The Updates Sent field shows that Device R2 is sending updates to Device R1 at roughly 1/6 of the rate that it is sending updates to Device R3.

Checking the RIPng Updates Received by Device R2

Purpose

Make sure that the RIPng update packets are sent at the expected interval.

Action

From operational mode, enter the show ripng statistics command.

Meaning

The Updates Received field shows the number of updates received from Device R2.

Checking the RIPng Updates Received by Device R3

Purpose

Make sure that the RIPng update packets are sent at the expected interval.

Action

From operational mode, enter the show ripng statistics command.

Meaning

The Updates Received field shows the number of updates received from Device R2.