Fast Reroute Detour Up Event
LSP Event
Sample Output 1
user@R1>show mpls lsp extensive[...Output truncated...]10.0.0.6From: 10.0.0.1, State: Up, ActiveRoute: 0, LSPname: R1-R6-3ActivePath: (primary)FastReroute desiredLoadBalance: RandomEncoding type: Packet, Switching type: Packet, GPID: IPv4*Primary State: UpComputed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 20)10.1.15.2 S 10.1.56.2 SReceived RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt):10.1.15.2(flag=1) 10.1.56.27 Feb 15 20:50:00 Record Route: 10.1.15.2(flag=1) 10.1.56.26 Feb 15 20:50:00Fast-reroute Detour Up5 Feb 15 20:49:57 Selected as active path4 Feb 15 20:49:57 Record Route: 10.1.15.2 10.1.56.23 Feb 15 20:49:57 Up2 Feb 15 20:49:56 Originate Call1 Feb 15 20:49:56 CSPF: computation result acceptedCreated: Tue Feb 15 20:49:57 2005Total 3 displayed, Up 3, Down 0[...Output truncated...]Sample Output 2
[edit protocols mpls]user@R1#showlabel-switched-path R1-R6-3 {to 10.0.0.6;fast-reroute;}[...Output truncated...]What It Means
This LSP event only applies to detours on this route, and indicates that a fast reroute detour path is up. Sample Output 1 shows the fast reroute event. Sample Output 2 shows the configuration of fast reroute on ingress router
R1.Cause
This LSP event is caused by the correct configuration of a one-to-one (1:1) fast reroute detour, resulting in the successful signaling of a fast reroute detour.
Action