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

Checklist for Examining an RSVP Failure

Problem

The Resource Reservation Protocol (RSVP) is a signaling protocol that provides reservation setup and control. This checklist provides the links and commands for a real-world scenario in which RSVP fails because links in the network are incorrectly configured. The links lead to information about some basic approaches to monitoring and examining an RSVP failure, including how, when, and why you use specific commands. This topic also includes an examination of the RSVP log file and corrective action for the specific scenario. (See Table 23.)

Solution

Table 23: Checklist for Examining an RSVP Failure

Tasks

  
Case Study for an RSVP Failure  
  1. Verify the RSVP Session

show rsvp session ingress detail
  1. Ping the Egress Router

ping ip-address-interface

  1. Enable RSVP Tracing on Transit Routers

edit

[edit]
edit protocols rsvp

[edit protocols rsvp]
set traceoptions file filename
 set traceoptions flag flag
 show
commit

  1. View the RSVP Log File on Transit Routers

clear rsvp session (Optional)
clear log filename (Optional)

show log filename

  1. Check the RSVP Log File on the Egress Router

show log rsvp-log

  1. Determine and Correct the Problem on the Egress Router

The following sequence of commands addresses the specific problem described in this section:

show configuration protocols rsvp
edit

[edit protocols rsvp]
rename interface so-0/0/3 to interface so-0/0/0
show
commit
run show rsvp session ingress detail
  1. Remove the Tracing Configuration

edit
[edit protocols rsvp]
show
delete traceoptions
show
commit
[ Contents] [ Prev] [ Next] [ Index] [ Report an Error]