Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Explicit Route: Wrong Delivery Event


LSP Event

Explicit route: wrong delivery

Sample Output 1

Sample Output 2

Sample Output 3


This LSP event indicates that a RSVP message with an ERO arrived at the wrong router, even though a strict route was specified. The receiving router determines that the address is inconsistent with the ERO, and generates the error message. Note that the IP address of the sending router precedes the error event; for example, in Sample Output 1, and in Sample Output 2.


This LSP event can be caused by several factors:

  • The loopback (lo0) interface on the ingress router is not configured at the [edit protocols isis] hierarchy level. After the loopback (lo0) interface is included in the Intermediate System-to-Intermediate System (IS-IS) configuration, and while IS-IS is forming adjacencies, an RSVP packet is forwarded to an incorrect destination,, as shown in Sample Output 1.

  • A strict path is configured to a directly connected router, then another strict path is configured to an IP address that is not directly connected. For example, Sample Output 3 shows that the path to-R6 includes three IP addresses, one of which ( is not directly connected to the other IP addresses in the path.


Take appropriate action. On the ingress router, include the loopback (lo0) interface at the [edit protocols isis] hierarchy level, change the definition of the strict path at the [edit protocols mpls path path-name] hierarchy level, or verify the validity of all IP addresses listed in the named path referenced by the LSP hop by hop.