Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Verify RSVP Interfaces



If the RSVP protocol is not configured correctly on the routers in your network, the interfaces cannot signal LSPs.


To verify RSVP interfaces, enter the following Junos OS CLI operational mode command:

Sample Output 1

Sample Output 2

Sample Output 3


Sample Output 1 shows that all interfaces on all routers in the network are enabled with RSVP, including the management interface (fxp0). The output for all routers in the network includes similar information, so we will examine R6 in detail.

R6 has five interfaces enabled with RSVP (Up). Interface so-0/1/1.0 has a single active RSVP reservation (Active resv) that did not change the default subscription percentage of 100 percent (Subscription). Interface so-0/1/1.0 did not assign a static bandwidth (Static BW) to the logical unit and therefore inherited 100 percent of the physical interface rate as the bandwidth available (Available BW) for RSVP sessions. Interface so-0/1/1.0 has no bandwidth assigned (Reserved BW), and no RSVP bandwidth allocation at any single instant in time (Highwater mark).

Sample Output 2 shows that interface so-0/0/3.0 is missing. If you do not configure the correct interface at the [edit protocols rsvp] hierarchy level, the interface cannot signal LSPs, and does not appear in the output for the show rsvp interface command.

Sample Output 3 shows that the RSVP protocol is not configured at the [edit protocols rsvp] hierarchy level.