Examining an RSVP Failure

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

Table 22: Checklist for Examining an RSVP Failure

Examining an RSVP Failure Tasks
Case Study for an RSVP Failure
Verify the RSVP Session	show rsvp session ingress detail
Ping the Egress Router	ping ip-address-interface
Enable RSVP Tracing on Transit Routers	edit [edit] edit protocols rsvp [edit protocols rsvp] set traceoptions file filename set traceoptions flag flag show commit
View the RSVP Log File on Transit Routers	clear rsvp session (Optional) clear log filename (Optional) show log filename
Check the RSVP Log File on the Egress Router	show log rsvp-log
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
Remove the Tracing Configuration	edit [edit protocols rsvp] show delete traceoptions show commit