LSP Event
Link protection down
Sample Output 1
user@R1> show configuration protocols mpls
label-switched-path R1-to-R6 {
to 10.0.0.6;
link-protection;
}
interface fxp0.0 {
disable;
}
interface all;
Sample Output 2
user@R1> show mpls lsp extensive
[...Output truncated...]
10.0.0.6
From: 10.0.0.1, State: Up, ActiveRoute: 1, LSPname: R1-to-R6
ActivePath: (primary)
Link protection desired
LoadBalance: Random
Encoding type: Packet, Switching type: Packet, GPID: IPv4
*Primary State: Up
Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 2)
10.1.13.2 S 10.1.36.2 S
Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt):
10.1.13.2(flag=1 Label=101936) 10.1.36.2(Label=3)
70 Feb 10 11:01:56 Link-protection Up
69 Feb 10 11:01:56 Selected as active path
68 Feb 10 11:01:56 Link-protection Down
67 Feb 10 11:01:56 Link-protection Up
66 Feb 10 11:01:56 Record Route: 10.1.13.2(flag=1 Label=101936) 10.1.36.2(Label=3)
65 Feb 10 11:01:56 Up
64 Feb 10 11:01:56 Originate Call
63 Feb 10 11:01:56 CSPF: computation result accepted
62 Feb 10 11:01:56 Clear Call
61 Feb 10 11:01:56 Deselected as active
60 Feb 10 11:01:56 Link-protection Down
59 Feb 10 10:57:58 Record Route: 10.1.13.2(flag=1 Label=101920) 10.1.36.2(Label=3)
58 Feb 10 10:57:56 Link-protection Up
57 Feb 10 10:56:58 Selected as active path
56 Feb 10 10:56:58 Record Route: 10.1.13.2(Label=101920) 10.1.36.2(Label=3)
55 Feb 10 10:56:58 Up
54 Feb 10 10:56:58 Originate Call
53 Feb 10 10:56:58 CSPF: computation result accepted
52 Feb 10 10:56:58 Clear Call
51 Feb 10 10:56:58 Deselected as active
50 Feb 10 10:56:58 Link-protection Down
49 Feb 10 10:56:35 10.1.56.2: MPLS label allocation failure[2 times]
48 Feb 10 10:48:32 Link-protection Up
47 Feb 10 10:48:32 Selected as active path
[...Output truncated...]
Meaning
Sample Output 1 shows the MPLS link-protection configuration on R1 for the LSP R1-to-R6.
Sample Output 2 shows that link protection came up and down several times. Link protection comes up when the LSP signals. Line 60 shows the result when RSVP is disabled on all alternate paths out of R6. Lines 68 to 70 are the result when the clear mpls lsp command is issued.
Cause
This LSP event is caused by a failure or configuration change that deletes or resignals the bypass LSP. For example, you clear the LSP using the clear mpls lsp command, or you disable RSVP on all alternate paths for the LSP. The bypass LSP does not use the primary path, instead it looks for an alternate path.
Action
Include the family mpls statement for all alternate paths for the LSP at the [edit interfaces type-fpc/pic/port.unit] hierarchy level.
