Option: Configuring Multiple Bypass LSPs, Manual Bypass LSPs, and Link Protection Priority
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.