No Route Toward Destination Event

LSP Event

No route toward destination

Sample Output 1

user@R1> show mpls lsp extensive

[...Output truncated...]

   35 Oct 26 22:48:36 Down

   34 Oct 26 22:48:29 CSPF failed: no route toward 10.0.0.1[4 times]

   33 Oct 26 22:47:25 CSPF: link down/deleted 
10.1.13.2(R3.00/10.0.0.3)->10.1.13.1(R1.00/10.0.0.1)

   32 Oct 26 22:47:25 CSPF failed: no route toward 10.0.0.1

   31 Oct 26 22:47:25 10.1.36.1: No Route toward dest

   30 Oct 26 22:33:54 Selected as active path

   29 Oct 26 22:33:53 Record Route:  10.1.36.1 10.1.13.1

[...Output truncated...]

Sample Output 2

user@R1> show mpls lsp extensive

[...Output truncated...]

10.0.0.6

  From: 10.0.0.1, State: Dn, ActiveRoute: 0, LSPname: R1-to-R6

  ActivePath: (none)

  LoadBalance: Random

  Encoding type: Packet, Switching type: Packet, GPID: IPv4

  Primary                    State: Dn

    Will be enqueued for recomputation in 7 second(s).

   13 Oct 25 16:29:28 Deselected as active

   12 Oct 25 16:29:27 CSPF failed: no route toward 10.0.0.6

   11 Oct 25 16:29:27 CSPF: link down/deleted 
10.1.13.1(R1.00/10.0.0.1)->10.1.13.2(R3.00/10.0.0.3)

   10 Oct 25 16:29:27 CSPF failed: no route toward 10.0.0.6

    9 Oct 25 16:29:27 Clear Call

    8 Oct 25 16:29:27 Explicit Route: bad strict route

    7 Oct 25 16:29:27 No Route toward dest

    6 Oct 25 16:29:27 Down

[...Output truncated...]

What It Means

This LSP event indicates that the router at address 10.1.36.1 in Sample Output 1 does not have a route to the specified destination. Sample Output 2 shows that the local router, ingress router 10.0.0.1, does not have a route to the specified destination.

Cause

This LSP event is caused by different factors. The egress interface of a transit router might not have RSVP enabled, or IP reachability to the destination (either the egress router or the next address in the ERO) does not exist.

Action

Enable RSVP on the transit router's egress interface, or examine the IP configuration of the relevant router.