[an error occurred while processing this directive][an error occurred while processing this directive]

RSVP Error, Subcode 6: No Non-lsp Route Event

LSP Event

RSVP error, subcode 6: No non-lsp route

Sample Output

user@host> show mpls lsp extensive
Ingress LSP: 1 sessions

192.168.28.1
From: 192.168.0.1, State: Dn, ActiveRoute: 0, LSPname: sj-to-lo
ActivePath: (none)
LoadBalance: Random
Encoding type: Packet, Switching type: Packet, GPID: IPv4
Primary State: Dn
87 Sep 18 08:23:12 Deselected as active
86 Sep 18 08:23:12  RSVP error, subcode 6: No non-lsp route
85 Sep 18 08:23:12 Down
84 Sep 18 08:23:12 RSVP error, subcode 6: No non-lsp route
83 Sep 18 08:23:07 Selected as active path
82 Sep 18 08:23:07 Record Route: 10.0.1.1 10.0.24.2 10.0.29.1
81 Sep 18 08:23:07 Up
80 Sep 18 08:22:27 Deselected as active
79 Sep 18 08:22:27 RSVP error, subcode 6: No non-lsp route
78 Sep 18 08:22:27 Down
77 Sep 18 08:22:27 RSVP error, subcode 6: No non-lsp route
76 Sep 18 08:22:22 Selected as active path
75 Sep 18 08:22:22 Record Route: 10.0.1.1 10.0.24.2 10.0.29.1
74 Sep 18 08:22:22 Up
[...Output truncated...]

Meaning

This LSP event indicates that RSVP Path messages for one LSP are tunneled into another RSVP LSP along the LSP path. Non-adjacent RSVP signaling is not currently supported on Juniper Networks LSRs, resulting in a path setup failure. This error is reported only by a Juniper Networks LSR.

Cause

This LSP event is most likely to occur when an LSP configured with the no-cspf statement and loose hops is in a Multiprotocol Label Switching (MPLS) network configured with interior gateway protocol (IGP) shortcuts or LSP advertisements.

Action

Find the node with the error and confirm that the ERO route to the next hop takes an LSP next hop. Also, you can configure strict hops to avert the problem. For information about configuring strict hops, see the JUNOS MPLS Applications Configuration Guide.


Published: 2010-01-30

[an error occurred while processing this directive]