Step 6: Determine and Correct the Problem on the Egress Router

Purpose

Check the configuration of interface so-0/0/0.0 on egress router R5 to determine the reason it was disabled.

Action

To determine the problem on R5, enter the following JUNOS CLI commands:

user@R5> show configuration protocols rsvp

user@R5> edit

[edit protocols rsvp]

user@R5# rename interface so-0/0/3 to interface so-0/0/0 

user@R5# show

user@R5# commit

user@R5# run show rsvp session ingress detail

Sample Output 1

user@R5> show configuration protocols rsvp 

traceoptions {

    file rsvp-log;

    flag error detail;

    flag path detail;

    flag pathtear detail;

}

interface so-0/0/3.0;                        <<< so-0/0/3 incorrectly included

interface so-0/0/1.0;

interface so-0/0/2.0;

interface fxp0.0 {

    disable;

}

Sample Output 2

[edit protocols rsvp]

user@R5# rename interface so-0/0/3 to interface so-0/0/0 

[edit protocols rsvp]

user@R5# show 

traceoptions {

    file rsvp-log;

    flag packets detail;

    flag error detail;

}

interface so-0/0/0.0;

interface so-0/0/1.0;

interface so-0/0/2.0;

interface fxp0.0 {

    disable;

}

[edit protocols rsvp]

user@R5# commit 

commit complete

Sample Output 3

[edit protocols mpls]

user@R5# run show rsvp session ingress detail

Ingress RSVP: 1 sessions

To              From            State   Rt Style Labelin Labelout LSPname 

10.0.0.1        10.0.0.5        Up       1  1 FF       -   103104 R5-to-R1

Total 1 displayed, Up 1, Down 0

Egress RSVP: 1 sessions

To              From            State   Rt Style Labelin Labelout LSPname 

10.0.0.5        10.0.0.1        Up       0  1 FF       3        - R1-to-R5

Total 1 displayed, Up 1, Down 0

Transit RSVP: 0 sessions

Total 0 displayed, Up 0, Down 0

What It Means

Sample Output 1 from egress router R5 shows three interfaces configured at the [edit protocols rsvp] hierarchy level, non of which is so-0/0/0.0. On examination of the network topology, it is apparent that the so-0/0/0.0 interface was configured incorrectly as so-0/0/3.0.

Sample Output 2 shows the correct configuration of interfaces at the [edit protocols rsvp] hierarchy level, and the rename command issued to correct the configuration error.

Sample Output 3 shows that the RSVP-signaled LSP (R1-to-R5) is correctly established after the changes to the RSVP configuration are committed.