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

Non-RSVP Capable Router Detected Event

LSP Event

Non-RSVP capable router detected

Sample Output

user@host> show mpls lsp extensive
[...Output truncated...]
  From:, State: Dn, ActiveRoute: 0, LSPname: R1-to-R6
  ActivePath: (none)
  LoadBalance: Random
  Encoding type: Packet, Switching type: Packet, GPID: IPv4
  Primary                    State: Dn, No-decrement-ttl
   19 Jan 21 15:05:37  Non-RSVP capable router detected
   18 Jan 21 15:04:52  Non-RSVP capable router detected [4 times]
   17 Jan 21 15:04:34 Originate Call
   16 Jan 21 15:04:34 Clear Call 
[...Output truncated...]


This LSP event indicates that a router, forwarding packets to the egress router, was not configured for RSVP.


This LSP event might be caused when a router not configured for RSVP forwards an RSVP packet toward the egress router without decrementing the Send_TTL value in the RSVP common header. The next downstream router detects that the Send_TTL value and the IP_TTL value are different, and generates this LSP event. Note that two different routers generated the same error message at different times.


Configure the router in question with RSVP.

Published: 2010-01-30

[an error occurred while processing this directive]