Enabling RSVP Tracing

Purpose

When the output of the show mpls lsp extensive command indicates that there is a problem with the LSP, you can enable RSVP tracing on the routers included in the LSP, especially the ingress and egress routers, and examine the RSVP log file to obtain more detailed information and solve the problem faster.

Figure 10 illustrates the example network topology used throughout the RSVP section. The example MPLS network uses Intermediate System-to-Intermediate System (IS-IS) Level 2 and a policy to create traffic. However, IS-IS Level 1 or an Open Shortest Path First (OSPF) area can be used and the policy omitted if the network has existing Border Gateway Protocol (BGP) traffic.

Figure 10: MPLS Network Topology

The MPLS network shown in Figure 10 is a router-only network with SONET interfaces that consist of the following components:

• A full-mesh interior BGP (IBGP) topology, using AS 65432.
• MPLS and RSVP enabled on all routers.
• A send-statics policy on router R1 that allows a new route to be advertised into the network.
• Two unidirectional LSPs between R1 and R5, allowing bidirectional traffic.

See the JUNOS MPLS Network Operations Guide for information on configuring an MPLS network.

Steps To Take

To enable RSVP tracing, follow these steps:

1. Configure RSVP Tracing
2. Display the RSVP Log File