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

RSVP Error Event

LSP Event

RSVP error

Sample Output 1

user@R1> show mpls lsp extensive
[...Output truncated...]
   50 Jan  4 18:10:44 CSPF: link down/deleted 10.1.13.1(R1.00/10.0.0.1)->10.1.13.2(R3.00/10.0.0.3)
   49 Jan  4 18:10:44 RSVP Disabled
   48 Jan  4 18:10:44  RSVP error
 , subcode 4: protocol shutdown
   47 Jan  4 18:10:44 Down
   46 Jan  4 18:06:15 Up
   45 Jan  4 18:06:15 Down
[...Output truncated...]

Sample Output 2

user@R1> show mpls lsp extensive
[...Output truncated...]
9 Jan 14 14:21:01 Deselected as active  
8 Jan 14 14:21:01  10.0.22.2: RSVP error, subcode 4: protocol shutdown
7 Jan 14 14:21:01 ResvTear received 
6 Jan 14 14:21:01 Down 
5 Jan 14 12:35:16 Selected as active path
4 Jan 14 12:35:16 Record Route: 10.0.21.2 10.0.22.2 10.0.29.2 
3 Jan 14 12:35:16 Up
2 Jan 14 12:35:16 Originate Call
1 Jan 14 12:35:16 CSPF: computation result accepted
[...Output truncated...]

Meaning

This LSP event indicates that an RSVP error object was received and RSVP was disabled. For a list of error codes, see RSVP Error Codes. For more information on RSVP error codes, see RFC 2205, Resource ReSerVation Protocol (RSVP), Version 1, Functional Specification, or RFC 3209, RSVP-TE: Extensions to RSVP for LSP Tunnels.

Cause

Sample Output 1 shows that the protocol was disabled on the ingress router. Sample Output 2 shows that the router with the IP address 10.0.22.2 notified the ingress router that RSVP was disabled.

Action

To bring the LSP back up, enable RSVP at the [edit protocols] hierarchy level.


Published: 2010-01-30

[an error occurred while processing this directive]