Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation

Example: Configuring RIP Demand Circuits

This example describes how to configure an interface as a RIP demand circuit.

Requirements

Before you begin, configure the device interfaces. See the Router Interfaces or the Junos OS Interfaces Configuration Guide for Security Devices.

Overview

A demand circuit is a point-to-point connection between two neighboring interfaces configured for RIP. Demand circuits increase the efficiency of RIP on the configured interfaces by eliminating the periodic transmission of RIP packets. Demand circuits preserve bandwidth by establishing a link when data needs to be transferred, and terminating the link when the data transfer is complete. In this example, two devices are connected using SONET/SDH interfaces.

Note: When you configure RIP demand circuits, any silent removal of the RIP configuration goes unnoticed by the RIP peer and leads to stale entries in the routing table. To clear the stale entries, deactivate and reactivate RIP on the neighboring devices.

In this example, you configure interface so-0/1/0 with the following settings:

  • demand-circuit—Configures the interface as a demand circuit. To complete the demand circuit, you must configure both ends of the pair as demand circuits.
  • max-retrans-time—RIP demand circuits send update messages every 5 seconds to an unresponsive peer. Use the retransmission timer to limit the number of times a demand circuit resends update messages to an unresponsive peer. If the configured retransmission threshold is reached, routes from the next-hop router are marked as unreachable, and the hold-down timer starts. The value of the retransmission timer affects only the demand circuit interfaces. To determine the number of times to resend the update message, use the following calculation:
    5 seconds x retransmissions = retransmission seconds

    For example, if you want the demand circuit to send only two update messages to an unresponsive peer, the calculation is: 5 x 2 = 10. When you configure the retransmission timer, you enter 10 seconds.

    The retransmission range is from 5 through 180 seconds, which corresponds to sending an update message a minimum of 1 time (5 seconds) and a maximum of 36 times (180 seconds).

Configuration

In the following example, you configure a neighboring interface to be a RIP demand circuit and save the 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 in the CLI at the [edit] hierarchy level.

set interfaces so-0/1/0 unit 0 family inet address 192.0.2.0/24set protocols rip group group1 neighbor so-0/1/0 demand-circuit set protocols rip group group1 neighbor so-0/1/0 max-retrans-time 10

Step-by-Step Procedure

The following example requires that you 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 a RIP demand circuit on one neighboring interface:

  1. Configure the interface.
    [edit interfaces]user@host# set so-0/1/0 unit 0 family inet address 192.0.2.0/24
  2. Configure the neighbor as a demand circuit.
    [edit protocols rip]user@host# set group group1 neighbor so-0/1/0 demand-circuit
  3. Configure the demand circuit retransmission timer.
    [edit protocols rip]user@host# set group group1 neighbor so-0/1/0 max-retrans-time 10
  4. If you are done configuring the device, commit the configuration.
    [edit]user@host# commit

    Note: Repeat this entire configuration on the other neighboring interface.

Results

Confirm your configuration by entering the show interfaces and show protocols commands. If the output does not display the intended configuration, repeat the instructions in this example to correct the configuration.

user@host# show interfaces
so-0/1/0 {unit 0 {family inet {address 192.0.2.0/24;}}}
user@host# show protocols
rip {group group1 { neighbor so-0/1/0 { demand-circuit; max-retrans-time 10; }}}

Verification

Confirm that the configuration is working properly.

Verifying a Demand Circuit Configuration

Purpose

Verify that the demand circuit configuration is working.

Action

To verify that the demand circuit configuration is in effect, use the show rip neighbor operational mode command.

user@host> show rip neighbor
                         Source          Destination     Send   Receive  In
Neighbor          State  Address         Address         Mode   Mode     Met
--------          -----  -------         -----------     ----   -------  ---
so-0/1/0.0(DC)       Up  10.10.10.2      224.0.0.9       mcast  both       1

When you configure demand circuits, the show rip neighbor command displays a DC flag next to the neighboring interface configured for demand circuits.

Note: If you configure demand circuits at the [edit protocols rip group group-name neighbor neighbor-name] hierarchy level, the output shows only the neighboring interface that you specifically configured as a demand circuit. If you configure demand circuits at the [edit protocols rip group group-name] hierarchy level, all of the interfaces in the group are configured as demand circuits. Therefore, the output shows all of the interfaces in that group as demand circuits.

Published: 2013-04-01