FRR and link protection are not the same. JUNOS supports FRR, and both link and link-node protection, as configured at the lsp ingress node. Node protection will only occur if the topology allows a next-nexthop, else you get the best available which is nexthop protection via a link bypass.
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. HTHs -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Judah Scott Sent: Thursday, July 30, 2009 1:10 PM To: [email protected] Subject: [j-nsp] RSVP Fast Reroute Node Protection Anyone have a config example of Fast Reroute Node Protection? The mpls config guide is unclear which interface (the primary path interface or the bypass path interface) you must add "link-protection" and "bypass" blocks to. My bypass is not being used. I've tried but can only get a dynamic link-protection bypass even though upstream node is requesting node protection. Are dynamic node-protection bypasses supported in JUNOS 9.5? Thanks, J Scott _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
