Tunnel Local Repaired Event - MPLS Network Operations Guide Log Reference

10.0.0.6
  From: 10.0.0.1, State: Up, ActiveRoute: 0, LSPname: R1-R6-3
  ActivePath:  (primary)
  FastReroute desired
  LoadBalance: Random
  Encoding type: Packet, Switching type: Packet, GPID: IPv4
 *Primary                    State: Up
    Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 20)
 10.1.12.2 S 10.1.26.2 S 
    Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt):
          10.1.12.2(flag=1) 10.1.26.2
   24 Feb 15 20:56:12 Record Route:  10.1.12.2(flag=1) 10.1.26.2
   23 Feb 15 20:56:11 Fast-reroute Detour Up
   22 Feb 15 20:56:09 Record Route:  10.1.12.2 10.1.26.2
   21 Feb 15 20:56:09 Up
   20 Feb 15 20:56:09 CSPF: computation result accepted
   19 Feb 15 20:56:09 CSPF: link down/deleted 10.1.15.1(R1.00/10.0.0.1)->10.1.15.2(R5.00/10.0.0.5)
   18 Feb 15 20:56:09 Record Route:  10.1.12.2 10.1.26.2
   17 Feb 15 20:56:09 Up
   16 Feb 15 20:56:08 CSPF: computation result accepted
   15 Feb 15 20:56:08  Tunnel local repaired
   14 Feb 15 20:56:08 CSPF: computation result accepted
   13 Feb 15 20:56:08 10.1.15.1: MPLS label allocation failure
   12 Feb 15 20:56:08 MPLS label allocation failure
   11 Feb 15 20:56:08 Record Route:  10.1.13.2 10.1.36.2
   10 Feb 15 20:56:08 Down
    9 Feb 15 20:52:56 Fast-reroute Detour Up
    8 Feb 15 20:52:53 Fast-reroute Detour Down
    7 Feb 15 20:50:00 Record Route:  10.1.15.2(flag=1) 10.1.56.2
    6 Feb 15 20:50:00 Fast-reroute Detour Up
    5 Feb 15 20:49:57 Selected as active path
    4 Feb 15 20:49:57 Record Route:  10.1.15.2 10.1.56.2
    3 Feb 15 20:49:57 Up
    2 Feb 15 20:49:56 Originate Call
    1 Feb 15 20:49:56 CSPF: computation result accepted
  Created: Tue Feb 15 20:49:56 2005
Total 3 displayed, Up 2, Down 1

This LSP error event indicates to the head-end (ingress) router that a local protection path was used when a link or node failed along the protected LSP path. Also, the LSR received a PathErr message from RSVP for the label-switched path.

This LSP error event is caused by a network failure along an LSP path that is locally protected with either a bypass LSP or fast reroute detour. In this case, the failure occurred when the primary link was deactivated, resulting in the fast reroute detour repairing the tunnel.