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

Explicit Route: Wrong Delivery Event

LSP Event

Explicit route: wrong delivery

Sample Output 1

user@host> show mpls lsp extensive
[...Output truncated...]
Primary use-TOKYO State: Dn, No-decrement-ttl
   3 Sep 19 00:25:45  10.222.45.2: Explicit Route: wrong delivery
   2 Sep 19 00:25:34 No Route[8 times]
   1 Sep 19 00:23:01 Originate Call
[...Output truncated...]

Sample Output 2

user@host> show mpls lsp extensive
[...Output truncated...]
10.0.0.6
  From: 10.0.0.1, State: Dn, ActiveRoute: 0, LSPname: R1-to-R6
  ActivePath: (none)
  LoadBalance: Random
  Encoding type: Packet, Switching type: Packet, GPID: IPv4
  Primary   to-R6            State: Dn
   40 Jan 26 16:35:26  10.1.36.2: Explicit Route: wrong delivery [2 times]
   39 Jan 26 16:35:23 Originate Call
   38 Jan 26 16:35:23 Clear Call
[...Output truncated...]

Sample Output 3

user@R1> show configuration protocols mpls
label-switched-path R1-to-R6 {
    to 10.0.0.6;
    no-cspf;
    primary to-R6;
}
path to-R6 {
    10.1.13.2 strict;
     10.1.56.1 strict;      <<< IP address not directly connected to 10.1.13.2
    10.1.26.1 strict;

Meaning

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, 10.222.45.2 in Sample Output 1, and 10.1.36.2 in Sample Output 2.

Cause

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, 10.222.45.2, 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 (10.1.56.1) is not directly connected to the other IP addresses in the path.

Action

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.


Published: 2010-01-30

[an error occurred while processing this directive]