Step 3: Enable RSVP Tracing on Transit Routers

Purpose

RSVP tracing on transit routers (R3 and R6) can provide useful information about the problem.

Action

To enable RSVP tracing on transit routers, follow these steps:

1. In configuration mode, go to the following hierarchy level:

user@host> edit

user@host# edit protocols rsvp

2. Configure a log file:

[edit protocols rsvp]

user@host# set traceoptions file filename

3. Depending on your situation, specify all or one of the following RSVP-specific tracing flags:

[edit protocols rsvp]

user@host# set traceoptions flag error detail

user@host# set traceoptions flag path detail

user@host# set traceoptions flag pathtear detail

4. Verify and commit the configuration:

user@host# show

user@host# commit

5. Complete the above steps on any other transit routers that might provide useful information towards resolution of the problem.

Sample Output

user@R3> edit 

Entering configuration mode

[edit]

user@R3# edit protocols rsvp 

[edit protocols rsvp]

user@R3# set traceoptions file rsvp-log 

[edit protocols rsvp]

user@R3# set traceoptions flag error detail 

[edit protocols rsvp]

user@R3# set traceoptions flag path detail 

[edit protocols rsvp]

user@R3# set traceoptions flag pathtear detail 

[edit protocols rsvp]

user@R1# show 

traceoptions {

    file rsvp-log;

    flag error detail;

    flag path detail;

    flag pathtear detail;

}

interface fxp0.0 {

    disable;

}

interface all;

[edit protocols rsvp]

user@R3# commit 

commit complete

What It Means

The sample output shows a configuration of RSVP tracing on transit router R3. The same tracing configuration is placed on R6 (not shown). Various flags are included at the [edit protocols rsvp traceoptions] hierarchy level to provide slightly different information about RSVP traffic. For more information about RSVP tracing flags, see RSVP Tracing Flags. With all configured flags, the detail option is included to show granular details about errors and paths.

NOTE: Use the trace options detail flag with caution because it may cause the CPU to become very busy. For information on removing a tracing configuration, see Remove the Tracing Configuration.

After you have configured tracing and issued the commit command, the routing protocol process (rpd) immediately starts monitoring RSVP. Any RSVP activity that relates to the configured flags is placed in the log file.