On Thu, Jul 30, 2009 at 02:15:04PM -0700, Harry Reynolds wrote: > I think that you only need to configure the rsvp interface > <interface-name> link-protection statement on the lsp's protection > paths. That is to say, if the primary path exits a transit node on > fe-0/1/1, and you want that node to provide link or link-node > protection for that LSP, you would add the link-protection statement > to some other rsvp/mpls enabled interface that is not Fast > Ethernet-0/1/1. Adding the statement to the lsp's primary path > interfaces should have no ill effect, but obviously no gain as the > primary and link protection interfaces now share the same fate.
I think you need to configure rsvp interface <> link-protection on the links of the primary path. A very simple example, link-protecting a one-hop LSP: k...@m320-1# run show mpls lsp ingress detail Ingress LSP: 1 sessions 10.0.0.5 From: 10.0.0.4, State: Up, ActiveRoute: 0, LSPname: to-m320-2 ActivePath: (primary) Link protection desired LoadBalance: Random Encoding type: Packet, Switching type: Packet, GPID: IPv4 *Primary State: Up Priorities: 7 0 SmartOptimizeTimer: 180 Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 1) 10.0.1.2 S Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt): 10.0.1.2(Label=3) Total 1 displayed, Up 1, Down 0 k...@m320-1# run show mpls lsp bypass ingress detail Ingress LSP: 2 sessions 10.0.0.5 From: 10.0.0.4, LSPstate: Up, ActiveRoute: 0 LSPname: Bypass->10.0.1.2 Suggested label received: -, Suggested label sent: - Recovery label received: -, Recovery label sent: 299872 Resv style: 1 SE, Label in: -, Label out: 299872 Time left: -, Since: Thu Jul 30 23:54:23 2009 Tspec: rate 0bps size 0bps peak Infbps m 20 M 1500 Port number: sender 1 receiver 22134 protocol 0 Type: Bypass LSP Number of data route tunnel through: 1 Number of RSVP session tunnel through: 0 PATH rcvfrom: localclient Adspec: sent MTU 1500 Path MTU: received 1500 PATH sentto: 10.0.2.2 (ge-1/0/9.0) 18 pkts RESV rcvfrom: 10.0.2.2 (ge-1/0/9.0) 18 pkts Explct route: 10.0.2.2 10.0.3.1 Record route: <self> 10.0.2.2 10.0.3.1 Total 1 displayed, Up 1, Down 0 k...@m320-1# run show route 10.0.0.5 inet.0: 21 destinations, 21 routes (20 active, 0 holddown, 1 hidden) + = Active Route, - = Last Active, * = Both 10.0.0.5/32 *[OSPF/10] 00:07:39, metric 1 > to 10.0.1.2 via ge-1/1/0.1 ... k...@m320-1# show protocols rsvp interface ge-1/1/0.1 { link-protection; } interface ge-1/0/9.0; Kari _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp