You want to keep a running log of RSVP events that occur on the router in case any problems arise and you need to debug problems with RSVP or your LSPs.
When performing ongoing monitoring of RSVP operations, set up tracing options to track RSVP events that occur on the router:
[edit protocols rsvp] aviva@R1#
set traceoptions fileaviva@R1#
set traceoptions flag packets detail
It's a good practice to trace high-level RSVP operations on an ongoing basis so that if a problem occurs, you can examine the logs as part of your troubleshooting process. Then you can enable more detailed traceoptions flags to help pinpoint the causes.
This recipe sets up tracing of RSVP packets that are sent and received by the router, saving them to the file rsvp-trace-log. The
world-readable option allows anyone logged in to the router to read the file. This file is created on the router's hard disk in the directories /var/log (on M-series and T-series routers) and /cf/var/log (on J-series routers). The
detail option provides additional information about the packets. Here's what the file contains when existing RSVP sessions are cleared and then restarted:
clear rsvp sessionsaviva@R1>
show logNov 4 16:47:41 R1 clear-log: logfile cleared Nov 4 16:47:47
RSVP send PathErr10.1.13.1->10.1.13.2 Len=188 so-0/0/2.0 Nov 4 16:47:47 Integty Len 36 flag 0x0 key ...