Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

English  

English

Example: Configuring the Metric Value Added to Imported RIPng Routes

Requirements

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

Overview

Normally, when multiple routes are available, RIPng selects the route with the lowest hop count. Changing the default metric enables you to control the route selection process such that a route with a higher hop count can be preferred over of a route with a lower hop count.

Figure 1 shows the topology used in this example.

Figure 1: RIPng Incoming Metrics Network Topology

Device R1 has two potential paths to reach 2001:db8::2/128. The default behavior is to send traffic out the 2001:db8:0:1::/64 interface facing Device R2. Suppose, though, that the path through Device R3 is less expensive to use or has higher bandwidth links. This example shows how to use the metric-in statement to ensure that Device R1 uses the path through Device R3 to reach 2001:db8::2/128. 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.

Step-by-Step Procedure

1. Configure the network interfaces.
   [edit interfaces]user@R1# set fe-1/2/0 unit 1 description to-R2user@R1# set fe-1/2/0 unit 1 family inet6 address 2001:db8:0:1::/64 eui-64
   user@R1# set ge-1/2/1 unit 10 description to-R3user@R1# set ge-1/2/1 unit 10 family inet6 address 2001:db8:0:5::/64 eui-64
   user@R1# set lo0 unit 1 family inet6 address 2001:db8::1/128
2. Create the RIPng groups and add the interfaces.

   To configure RIPng in Junos OS, you must configure one or more groups that contain the interfaces on which RIPng is enabled. You do not need to enable RIPng on the loopback interface.

   For the interface that is facing Device R2, the metric-in 4 setting causes this route to be less likely to be chosen as the active route.

   [edit protocols ripng]user@R1# set group primary neighbor ge-1/2/1.10user@R1# set group secondary neighbor fe-1/2/0.1 metric-in 4
3. Create the routing policy to advertise both direct and RIPng-learned routes.
   [edit policy-options policy-statement advertise-routes-through-ripng term 1]user@R1# set from protocol directuser@R1# set from protocol ripnguser@R1# set then accept
4. Apply the routing policy.

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

   [edit protocols ripng]user@R1# set group primary export advertise-routes-through-ripnguser@R1# set group secondary export advertise-routes-through-ripng

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.

• Verifying That the Expected Route Is Active
• Removing the metric-in Statement

Verifying That the Expected Route Is Active

Purpose

Make sure that Device R1 uses the path through Device R3 to reach 2001:db8:0:2:2a0:a514:0:24c/128.

Action

From operational mode, enter the show route 2001:db8:0:2:2a0:a514:0:24c command.

inet6.0: 16 destinations, 17 routes (16 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

2001:db8:0:2::/64  *[RIPng/100] 01:54:35, metric 3, tag 0
                    > to fe80::2a0:a514:0:94c via ge-1/2/1.10

Meaning

The to fe80::2a0:a514:0:94c via ge-1/2/1.10 output shows that Device R1 uses the path through Device R3 to reach 2001:db8:0:2:2a0:a514:0:24c/128. The metric for this route is 3.

Removing the metric-in Statement

Purpose

Delete or deactivate the metric-in statement to see what happens to the 2001:db8:0:2:2a0:a514:0:24c/128 route.

Action

1. From configuration mode, deactivate the metric-in statement.
   [edit protocols ripng group secondary neighbor fe-1/2/0.1]user@R1# deactivate metric-inuser@R1# commit
2. From operational mode, enter the show route 2001:db8:0:2:2a0:a514:0:24c command.
   user@R1> show route 2001:db8:0:2:2a0:a514:0:24c

   inet6.0: 16 destinations, 17 routes (16 active, 0 holddown, 0 hidden)
   + = Active Route, - = Last Active, * = Both
   
   2001:db8:0:2::/64  *[RIPng/100] 00:00:02, metric 2, tag 0
                       > to fe80::2a0:a514:0:24c via fe-1/2/0.1
   

Meaning

The to fe80::2a0:a514:0:24c via fe-1/2/0.1 output shows that Device R1 uses the path through Device R2 to reach 2001:db8:0:2:2a0:a514:0:24c/128. The metric for this route is 2.