Explicit Route: Bad Loose Route Event

LSP Event

Explicit Route: bad loose route

Sample Output 1

user@R1# run show mpls lsp extensive

Ingress LSP: 1 sessions

10.0.0.6

From: 10.0.0.1, State: Up, ActiveRoute: 0, LSPname: R1-R6-3

ActivePath: R6-3-1 (secondary)

LoadBalance: Random

Encoding type: Packet, Switching type: Packet, GPID: IPv4

Primary R6-3 State: Dn

10 Feb 15 21:21:58 Explicit Route: bad loose route[2 times]

9 Feb 15 21:21:52 Deselected as active

8 Feb 15 21:21:51 Explicit Route: bad loose route

7 Feb 15 21:21:51 10.1.15.1: MPLS label allocation failure

6 Feb 15 21:21:51 MPLS label allocation failure

5 Feb 15 21:21:51 Down

4 Feb 15 21:20:55 Selected as active path

3 Feb 15 21:20:55 Record Route: 10.1.15.2 10.1.56.2

2 Feb 15 21:20:55 Up

1 Feb 15 21:20:55 Originate Call

*Secondary R6-3-1 State: Up

Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt):

10.1.12.2 10.1.26.2

4 Feb 15 21:21:52 Selected as active path

3 Feb 15 21:21:52 Record Route: 10.1.12.2 10.1.26.2

2 Feb 15 21:21:52 Up

1 Feb 15 21:21:52 Originate Call

Created: Tue Feb 15 21:20:55 2005

Total 3 displayed, Up 2, Down 1

Sample Output 2

user@R1# run show protocols mpls

label-switched-path R1-to-R6 {

to 10.0.0.6;

bandwidth 155;

no-cspf;

link-protection;

primary to-R6;

}

label-switched-path R1-to-R6-2 {

to 10.0.0.6;

link-protection;

auto-bandwidth {

adjust-interval 300;

minimum-bandwidth 1;

maximum-bandwidth 1k;

}

}

label-switched-path R1-R6-3 {

to 10.0.0.6;

no-cspf; <--Allows a loose ERO

primary R6-3;

secondary R6-3-1;

}

path to-R6 {

10.1.15.2 strict;

10.1.56.2 strict;

}

path R6-3 {

10.1.15.2 loose; <--Loose ERO

}

path R6-3-1 {

10.1.12.2;

}

interface fxp0.0 {

disable;

}

interface all;

What It Means

This LSP error event indicates that there is an error in the loose hop specified in the Explicit Route Object (ERO) of a Path message received by a label-switched router (LSR) along the LSP path, indicating an LSP setup failure.

Cause

This LSP error event is caused by control plane unreachability or data plane incompatibility.

Action

Check the LSP configuration at the [edit protocols mpls] hierarchy level.