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

Path Name Undefined or Disabled Event

LSP Event

Path name undefined or disabled

Sample Output 1

user@host> show mpls lsp extensive
[...Output truncated...]
10.0.0.6
  From: 0.0.0.0, 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
        No computed ERO.
    1 Jan 26 16:40:49  Path name undefined or disabled [4 times]
[...Output truncated...]

Sample Output 2

user@host> show configuration protocols mpls
[...Output truncated...]
label-switched-path R1-to-R6 {
    to 10.0.0.6;
     primary to-R6;  <<< the path to-R6 is not defined
}
[...Output truncated...]

Sample Output 3

user@R1> show configuration protocols mpls
label-switched-path R1-to-R6 {
    to 10.0.0.6;
    primary to-R6;
}
path to-R6;     <<< the path is now defined
[...Output truncated...]

Meaning

This LSP event indicates that the ingress router referenced a named path, but did not define it. The configuration was committed, but with a warning message.

Cause

This LSP event is caused when you configure a primary LSP, primary/secondary LSP, or static LSP, and do not define the named path. For example, the LSP path primary to-R6 (shown in Sample Output 2), is not defined at the [edit protocols mpls] hierarchy level. RSVP does not signal this message.

Action

Define the named path at the [edit protocols mpls] hierarchy level, as shown in Sample Output 3. For each path, specify some or all transit routers in the path, or leave the path empty, as shown in Sample Output 3. For more information on the configuration of named paths, see the JUNOS MPLS Applications Configuration Guide.


Published: 2010-01-30

[an error occurred while processing this directive]