Verifying an RSVP-Signaled LSP

Suppose that RSVP is configured to establish an LSP as shown in Figure 5.

To verify the RSVP configuration, perform these verification tasks:

• Verifying RSVP Neighbors
• Verifying RSVP Sessions
• Verifying the Presence of RSVP-Signaled LSPs

Purpose

Verify that each Services Router shows the appropriate RSVP neighbors—for example, that Router R1 lists both Router R3 and Router R2 as RSVP neighbors.

Action

From the CLI, enter the show rsvp neighbor command.

RSVP neighbor: 2 learned
Address            Idle Up/Dn LastChange HelloInt HelloTx/Rx 
10.0.6.2              0  3/2       13:01        3   366/349 
10.0.3.3              0  1/0       22:49        3   448/448 

What it Means

The output shows the IP addresses of the neighboring routers. Verify that each neighboring RSVP router loopback address is listed.

Purpose

Verify that an RSVP session has been established between all RSVP neighbors. Also, verify that the bandwidth reservation value is active.

Action

From the CLI, enter the show rsvp session detail command.

Ingress RSVP: 1 sessions

10.0.9.7
  From: 10.0.6.1, LSPstate: Up, ActiveRoute: 0
  LSPname: r1–r7, LSPpath: Primary
  Bidirectional, Upstream label in: –, Upstream label out: -
  Suggested label received: -, Suggested label sent: –
  Recovery label received: -, Recovery label sent: 100000
  Resv style: 1 FF, Label in: -, Label out: 100000
  Time left:    -,  Since: Thu Jan 26 17:57:45 2002
  Tspec: rate 10Mbps size 10Mbps peak Infbps m 20 M 1500
  Port number: sender 3 receiver 17 protocol 0
  PATH rcvfrom: localclient
  PATH sentto: 10.0.4.13 (fe-0/0/1.0) 1467 pkts
  RESV rcvfrom: 10.0.4.13  (fe-0/0/1.0) 1467 pkts
  Record route:  10.0.4.13  10.0.2.1  10.0.8.10  
 

What it Means

The output shows the detailed information, including session IDs, bandwidth reservation, and next-hop addresses, for each established RSVP session. Verify the following information:

• Each RSVP neighbor address has an entry for each neighbor, listed by loopback address.
• The state for each LSP session is Up.
• Under Tspec, the appropriate bandwidth value, 10Mbps, appears.

Purpose

Verify that the inet.3 routing table of the entry (ingress) Services Router, R1, has a configured LSP to the loopback address of Router R7.

Action

From the CLI, enter the show route table inet.3 command.

inet.3: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

10.0.9.7/32         *[RSVP/7] 00:05:29, metric 10
                    > to 10.0.4.17 via fe-0/0/0.0, label-switched-path r1–r7

What it Means

The output shows the RSVP routes that exist in the inet.3 routing table. Verify that an RSVP-signaled LSP is associated with the loopback address of the exit (egress) router, R7, in the MPLS network.