[an error occurred while processing this directive][an error occurred while processing this directive]

Enabling RSVP Traceoptions

Purpose

Global routing protocol tracing operations track all general routing operations and record them in a log file. Any global tracing operations that you configure are inherited by the individual routing protocols. To modify the global tracing operations for an individual protocol, enable tracing when configuring that protocol.

The error descriptions logged by the remote operations daemon can often provide more detailed information to help you solve the problem faster.

Action

To enable traceoptions for RSVP packets in your network, follow these steps:

  1. In configuration mode, go to the following hierarchy level:
    [edit]user@host# edit protocols rsvp traceoptions
  2. Configure the RSVP log file:
    [edit protocols rsvp traceoptions]user@host# set file filename.log
  3. Configure the tracing operations:
    [edit protocols rsvp traceoptions]user@host# set flag packets
  4. Verify and commit the configuration:
    user@host# show
    user@host# commit
  5. View the contents of the log file:
    user@host# run show log rsvp.log
  6. Stop monitoring the rsvp log file:
    [edit protocols rsvp]user@host# deactivate traceoptions
  7. Verify and commit the new configuration:
    user@host# show
    user@host# commit

Sample Output

user@R1> edit 
Entering configuration mode

[edit]
user@R1# edit protocols rsvp traceoptions 

[edit protocols rsvp traceoptions]
user@R1# set file rsvp.log  

[edit protocols rsvp traceoptions]
user@R1# set flag packets  

[edit protocols rsvp traceoptions]
user@R1# show 
file rsvp.log;
flag packets;

[edit protocols rsvp traceoptions]
user@R1# commit 
commit complete

[edit protocols rsvp traceoptions]
user@R1# run show log rsvp.log 
Aug 26 10:05:54 trace_on: Tracing to "/var/log/rsvp.log" started
Aug 26 10:05:54 RSVP send Hello New 10.1.13.1->10.1.13.2 Len=32 so-0/0/2.0
Aug 26 10:05:55 RSVP recv Resv 10.1.13.2->10.1.13.1 Len=128 so-0/0/2.0
Aug 26 10:05:55 RSVP send Hello New 10.1.12.1->10.1.12.2 Len=32 so-0/0/0.0
Aug 26 10:05:55 RSVP send Hello New 10.1.15.1->10.1.15.2 Len=32 so-0/0/1.0
Aug 26 10:05:55 RSVP recv Hello New 10.1.12.2->10.1.12.1 Len=32 so-0/0/0.0
Aug 26 10:05:55 RSVP recv Hello New 10.1.15.2->10.1.15.1 Len=32 so-0/0/1.0
Aug 26 10:05:57 RSVP recv Path 10.0.0.6->10.0.0.1 Len=208 so-0/0/1.0
Aug 26 10:05:57 RSVP send Resv 10.1.15.1->10.1.15.2 Len=120 so-0/0/1.0
---(more)---[abort]

[edit protocols rsvp traceoptions]
user@R1# up  

[edit protocols rsvp]
user@R1# deactivate traceoptions 

[edit protocols rsvp]
user@R1# show 
inactive: traceoptions {
    file rsvp.log;
    flag packets;
}
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

Meaning

The sample output shows the configuration of RSVP traceoptions, the output for the log file, and the deactivation of the traceoptions configuration.

To specify more than one tracing operation, include multiple flag statements in the configuration, at the following hierarchy level:

[edit protocols rsvp traceoptions]user@R1# set flag flag

Table 1: RSVP Tracing Flags

Flag

Description

all

All tracing operations

error

All detected error conditions

event

RSVP-related events

lmp

RSVP-LMP interactions

packets

All RSVP packets

path

All path messages

pathtear

PathTear messages

resv

Resv messages

resvtear

ResvTear messages

route

Routing information

state

Session state transitions

For more information on configuring traceoptions, see the JUNOS MPLS Applications Configuration Guide and the JUNOS Routing Protocols Configuration Guide.


Published: 2010-01-25

[an error occurred while processing this directive]