[Contents] [Prev] [Next] [Index] [Report an Error]


Step 1: Configure RSVP Tracing

Action

To configure a log file and specify RSVP tracing flags, follow these steps:

  1. In configuration mode, go to the following hierarchy level:
  2. [edit]
    
    user@host# edit protocols rsvp
    
    
    
  3. Configure a log file:
  4. [edit protocols rsvp]
    
    user@host# set traceoptions file filename
    
    
    
  5. Depending on your situation, specify the appropriate RSVP-specific tracing flag from Table 17. For example:
  6. [edit protocols mpls]
    
    user@host# set traceoptions flag path detail
    
    
    
  7. Verify and commit the configuration:
  8. user@host# show
    
    user@host# commit
    

Sample Output

user@R1> edit 
Entering configuration mode

[edit]
user@R1# edit protocols rsvp 

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

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

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

[edit protocols rsvp]
user@R1# 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 so-0/0/2.0;
interface fxp0.0 {
    disable;
}

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

What It Means

The sample output shows the configuration of RSVP tracing on ingress router R1. The log file rsvp-log contains all the information gathered for the configured flags. In the sample output, three flags are configured: error, path, and pathtear. All flags are configured with the detail option. Each flag that you configure provides slightly different information about RSVP traffic. The error flag traces all detected error conditions, the path flag traces all Path messages, and the pathtear flag traces PathTear messages. The detail option shows granular details about the flag included in the configuration. .

NOTE: Use the tracing flags detail and all with caution. These flags may cause the central processing unit (CPU) to become very busy.


Table 17 shows the tracing flags you can configure at the [edit protocols rsvp traceoptions] hierarchy level.


Table 17: 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 information about examining an RSVP log file, see Examining RSVP Log Messages and Examining RSVP Error Messages.


[Contents] [Prev] [Next] [Index] [Report an Error]