4. Deactivate and Reactivate RSVP Tracing

Purpose

When you configure and commit a tracing configuration, tracing information is immediately sent to the configured log file. The tracing activity goes on in the background and can create additional activity on the CPU. In this case, it is good practice to deactivate trace options, and then reactivate it when you need more tracing information.

NOTE: Implementing trace options consumes CPU resources and affects the packet processing performance.

Action

To deactivate and then reactivate tracing, enter the following JUNOS CLI operational mode command:

[edit protocols rsvp]

user@host# deactivate traceoptions 

user@host# activate traceoptions 

Sample Output

[edit protocols rsvp]

user@R1# deactivate traceoptions 

[edit protocols rsvp]

user@R1# show 

inactive: traceoptions {

    file rsvp-log;

    flag error detail;

    flag path detail;

    flag pathtear detail;

}

interface so-0/0/0.0;

interface so-0/0/1.0;

interface so-0/0/2.0;

interface fxp0.0 {

    disable;

}

[edit protocols rsvp]

user@R1# commit 

commit complete

[edit protocols rsvp]

user@R1# activate traceoptions 

[edit protocols rsvp]

user@R1# show 

traceoptions {

    file rsvp-log;

    flag error detail;

    flag path detail;

    flag pathtear detail;

}

interface so-0/0/0.0;

interface so-0/0/1.0;

interface so-0/0/2.0;

interface fxp0.0 {

    disable;

}

[edit protocols rsvp]

user@R1# commit 

commit complete

What It Means

The sample output shows that trace options was deactivated and then reactivated.

In a configuration, you can deactivate statements and identifiers so that they do not take effect when you issue the commit command. Any deactivated statements and identifiers are marked with the inactive: tag. They remain in the configuration, but are not activated when you issue a commit command.