Step 3: Verify the LSP Route on the Ingress Router

Purpose

Check whether the LSP route is included in the active entries in the inet.3 routing table for the specified address.

Action

To verify the LSP route, enter the following command from the ingress router:

user@host> show route destination

Sample Output 1

user@R1> show route 10.0.0.6 

inet.0: 27 destinations, 27 routes (27 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both

10.0.0.6/32        *[IS-IS/18] 6d 01:41:37, metric 20

                      to 10.1.12.2 via so-0/0/0.0

                    > to 10.1.15.2 via so-0/0/1.0

                      to 10.1.13.2 via so-0/0/2.0

user@R6> show route 10.0.0.1 

inet.0: 28 destinations, 28 routes (28 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both

10.0.0.1/32        *[IS-IS/18] 5d 01:01:38, metric 20

                      to 10.1.56.1 via so-0/0/0.0

                    > to 10.1.26.1 via so-0/0/2.0

                      to 10.1.36.1 via so-0/0/3.0

Sample Output 2

user@R1> show route 10.0.0.6 

inet.0: 28 destinations, 28 routes (27 active, 0 holddown, 1 hidden)

+ = Active Route, - = Last Active, * = Both

10.0.0.6/32        *[IS-IS/18] 6d 02:13:42, metric 20

                      to 10.1.12.2 via so-0/0/0.0

                    > to 10.1.15.2 via so-0/0/1.0

                      to 10.1.13.2 via so-0/0/2.0

inet.3: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both

10.0.0.6/32        *[RSVP/7] 00:08:07, metric 20

                    > via so-0/0/2.0, label-switched-path R1-to-R6

user@R6> show route 10.0.0.1 

inet.0: 29 destinations, 29 routes (28 active, 0 holddown, 1 hidden)

+ = Active Route, - = Last Active, * = Both

10.0.0.1/32        *[IS-IS/18] 5d 01:34:03, metric 20

                      to 10.1.56.1 via so-0/0/0.0

                    > to 10.1.26.1 via so-0/0/2.0

                      to 10.1.36.1 via so-0/0/3.0

inet.3: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both

10.0.0.1/32        *[RSVP/7] 00:10:39, metric 20

                    > via so-0/0/3.0, label-switched-path R6-to-R1

What It Means

Sample Output 1 shows entries in the inet.0 routing table only. The inet.3 routing table is missing from the output because the LSP is not working. The inet.0 routing table is used by interior gateway protocols (IGPs) and Border Gateway Protocol (BGP) to store routing information. In this case, the IGP is Intermediate System-to-Intermediate System (IS-IS). For more information on the inet.0 routing table, see the JUNOS MPLS Applications Configuration Guide.

If the LSP was working, we would expect to see entries that include the LSP in the inet.3 routing table. The inet.3 routing table is used on ingress routers to route BGP packets to the destination egress router. BGP uses the inet.3 routing table on the ingress router to help resolve next-hop addresses. BGP is configured in the example network shown in Figure 22.

Sample Output 2 shows output you should receive when the LSP is up. The output shows both the inet.0 and inet.3 routing tables, indicating that LSPs R1-to-R6 and R6-to-R1 are available.