Non-RSVP Capable Router Detected Event
LSP Event
Non-RSVP capable router detected
Sample Output
user@host>show mpls lsp extensive[...Output truncated...]10.0.0.6From: 10.0.0.1, State: Dn, ActiveRoute: 0, LSPname: R1-to-R6ActivePath: (none)LoadBalance: RandomEncoding type: Packet, Switching type: Packet, GPID: IPv4Primary State: Dn, No-decrement-ttl19 Jan 21 15:05:37 10.1.24.2:Non-RSVP capable router detected18 Jan 21 15:04:52 10.1.26.2:Non-RSVP capable router detected[4 times]17 Jan 21 15:04:34 Originate Call16 Jan 21 15:04:34 Clear Call[...Output truncated...]What It Means
This LSP event indicates that a router, forwarding packets to the egress router, was not configured for RSVP.
Cause
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.
Action