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: Tracing RIPng Protocol Traffic

Understanding RIPng Protocol Traffic Trace Operations

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

• detail—Detailed trace information
• receive—Packets being received
• send—Packets being transmitted

  Note: Use the detail flag modifier with caution as this might cause the CPU to become very busy.

• 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 as this might cause the CPU to become very busy.

Example: Tracing RIPng Protocol Traffic

This example shows how to trace RIPng protocol operations.

• Requirements
• Overview
• Configuration
• Verification

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

Figure 1 shows the topology used in this example.

Figure 1: RIPng 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.

Step-by-Step Procedure

1. Configure the network interfaces.

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

   [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 lo0 unit 1 family inet6 address 2001:db8::1/128
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.

   [edit protocols ripng group ripng-group]user@R1# set neighbor fe-1/2/0.1
3. Configure RIPng tracing operations.
   [edit protocols ripng traceoptions]user@R1# set file ripng-trace-fileuser@R1# set flag route
4. 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
5. Apply the routing policy.

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

   [edit protocols ripng group ripng-group]user@R1# set 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.

Checking the Log File

Purpose

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

Action

1. Deactivate the extra loopback interface address on Device R3.
   [edit interfaces lo0 unit 3 family inet6]user@R3# deactivate address 2001:db8::3/128user@R3# commit
2. From operational mode, enter the show log ripng-trace-file command with the | match 2001:db8::3 option.
   user@R1> show log ripng-trace-file | match 2001:db8::3

   Mar  6 14:57:03.516867  2001:db8::3/128: metric-in: 3, change: 3 -> 3; # gw: 1, pkt_upd_src fe80::2a0:a514:0:24c, inx: 0, rte_upd_src fe80::2a0:a514:0:24c
   Mar  6 14:57:32.786286  2001:db8::3/128: metric-in: 3, change: 3 -> 3; # gw: 1, pkt_upd_src fe80::2a0:a514:0:24c, inx: 0, rte_upd_src fe80::2a0:a514:0:24c
   Mar  6 14:58:02.584669  2001:db8::3/128: metric-in: 3, change: 3 -> 3; # gw: 1, pkt_upd_src fe80::2a0:a514:0:24c, inx: 0, rte_upd_src fe80::2a0:a514:0:24c
   Mar  6 14:58:30.213894  2001:db8::3/128: metric-in: 3, change: 3 -> 3; # gw: 1, pkt_upd_src fe80::2a0:a514:0:24c, inx: 0, rte_upd_src fe80::2a0:a514:0:24c
   Mar  6 14:59:00.115110  2001:db8::3/128: metric-in: 3, change: 3 -> 3; # gw: 1, pkt_upd_src fe80::2a0:a514:0:24c, inx: 0, rte_upd_src fe80::2a0:a514:0:24c
   Mar  6 14:59:05.826644 Setting RIPng rtbit on route 2001:db8::3/128, tsi = 0xbb69880
   Mar  6 14:59:13.014652  2001:db8::3/128: metric-in: 16, change: 3 -> 16; # gw: 1, pkt_upd_src fe80::2a0:a514:0:24c, inx: 0, rte_upd_src fe80::2a0:a514:0:24c
   Mar  6 14:59:13.015132 CHANGE   2001:db8::3/128     nhid 566 gw fe80::2a0:a514:0:24c RIPng    pref 100/0 metric 3/0 fe-1/2/0.1 **Delete Int>
   Mar  6 14:59:13.015197 Best route to 2001:db8::3/128 got deleted. Doing route calculation on the stored rte-info

Meaning

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