To implement MPLS LSP link protection or node-link protection, perform the following:
You enable the level of LSP protection you want on the ingress router. Link protection redirects LSP traffic to a bypass LSP that can traverse the same router that contains the affected link, whereas node-link protection sends LSP traffic to a bypass LSP that circumvents the affected router. To enable link protection for an LSP or point-to-multipoint LSP, include the link-protection statement at the [edit protocols mpls label-switched-path lsp-name ] hierarchy level. To enable node-link protection for an LSP, include the node-link-protection statement at the [edit protocols mpls label-switched-path lsp-name] hierarchy level.
- [edit]
- protocols {
-
- mpls {
-
- label-switched-path lsp-name {
- ( link-protection | node-link-protection );
- }
- }
- }
After link protection or node-link protection is established, the LSP marks the desired link protection bit in the RSVP Session Attribute (SA) object. To disable link protection or node-link protection for an LSP, delete the link-protection or node-link-protection statements at the [edit protocols mpls label-switched-path lsp-name] hierarchy level. For more information about point-to-multipoint LSPs, see the JUNOS MPLS Applications Configuration Guide.
To complete your link protection or node-link protection configuration, configure RSVP interface-level link protection. Include the link-protection statement at the [edit protocols rsvp interface interface-name] hierarchy level. You must configure the link-protection statement on every RSVP interface used to exit each router in the LSP or point-to-multipoint LSP path. As an option, you can configure a loose or strict path for all bypass LSPs with the path statement at the [edit protocols rsvp interface interface-name link-protection] hierarchy level.
- [edit]
- protocols {
-
- rsvp {
-
- interface interface-name {
-
- link-protection {
-
- path ip-address {
- (loose | strict);
- }
- }
- }
- }
- }
To disable link protection on an RSVP interface, include the disable statement at the [edit protocols rsvp interface interface-name link-protection] hierarchy level.
You can configure multiple bypass LSP paths for a link-protected RSVP LSP. When you enable this option, RSVP signals multiple bypasses concurrently for a link-protected LSP. To configure, start by enabling link protection or node-link protection by including the link-protection or node-link-protection statement at the [edit protocols mpls label-switched-path lsp-name] hierarchy level. To configure an RSVP interface to include multiple bypasses, specify how much bandwidth the bypasses should consume by including the bandwidth statement at the [edit protocols rsvp interface interface-name link-protection] hierarchy level. To limit the total number of bypasses that can be created, include the max-bypasses statement at the [edit protocols rsvp interface interface-name link-protection] hierarchy level.
Other bypass options include limiting the maximum number of hops a bypass LSP will traverse, selectively disallowing node-link protection, setting a timer to redistribute data periodically across the bypass LSPs, requiring strict or loose paths for the bypass LSPs, and establishing the percentage of bandwidth required for the bypass LSPs. To configure, include the hop-limit, no-node-protection, optimize-timer, path, and subscription statements, respectively, at the [edit protocols rsvp interface interface-name link-protection] hierarchy level.
Another option is to specify bypass LSPs manually. To configure, include the to and bandwidth statements at the [edit protocols rsvp interface interface-name link-protection bypass bypass-name] hierarchy level. Optionally, you can specify the hop limit and path type for the manual bypass LSP. To configure the options, include the hop-limit and path statements at the [edit protocols rsvp interface interface-name link-protection bypass bypass-name] hierarchy level.
Link protection priority enables you to provide preferred combinations of priority and class in a traffic engineering class matrix. When selecting a bypass LSP, the routing platform selects the bypass containing the lowest priority. To configure link protection priority for all bypass LSP paths, include the priority statement at the [edit protocols rsvp interface interface-name link-protection] hierarchy level. To configure link protection priority for a manually specified bypass LSP path, include the priority statement at the [edit protocols rsvp interface interface-name link-protection bypass bypass-name] hierarchy level.
- [edit protocols]
- mpls {
-
- label-switched-path lsp-name {
- (link-protection | node-link-protection);
- }
- }
- rsvp {
-
- interface interface-name {
-
- link-protection {
- bandwidth bps;
-
- bypass bypass-name {
- to ip-address;
- bandwidth bps;
- hop-limit maximum-hops; #
The default value is 255 hops.
-
- path ip-address {
- (loose | strict);
- }
- priority priority;
- }
- hop-limit maximum-hops; #
The range is 2 hops to the default (255 hops).
- max-bypasses number; # The
range for this statement is 1 to 99.
- no-node-protection;
- optimize-timer seconds; #
The default value of 0 disables this option.
-
- path ip-address {
- (loose | strict);
- }
- subscription percent; # The
range for this statement is 1 to 65535.
- }
- }
- }
For more information on multiple bypass LSPs, manually configured bypass LSPs, and link protection priority, see the JUNOS MPLS Applications Configuration Guide.
For link-protected LSPs and bypass LSPs, you can specify a class-of-service designation to provide different levels of traffic quality. To configure class of service for link-protected LSPs, include the class-of-service statement at the [edit protocols rsvp interface interface-name link-protection] hierarchy level. To configure class of service for bypass LSPs, include the class-of-service statement at the [edit protocols rsvp interface interface-name link-protection bypass ip-address] hierarchy level.
For more information about class of service for link-protected LSPs and bypass LSPs, see the JUNOS MPLS Applications Configuration Guide and the JUNOS Class of Service Configuration Guide.
In JUNOS Release 7.4 and later, you can issue enhanced operational mode commands and receive system log messages that provide more details about the operation of your link-protected or node-link-protected LSPs. The following guidelines explain the type of information available from the output of each command or message.
For more information about the enhanced link protection and node-link protection operational commands, see the JUNOS Routing Protocols and Policies Command Reference. For more information about the system log message, see the JUNOS System Log Messages Reference.
