[an error occurred while processing this directive][an error occurred while processing this directive]

bypass (Signaled LSP)


bypass bypass-name {bandwidth bps;hop-limit number;no-cspf;path address <strict | loose>;priority setup-priority reservation-priority;to address;}

Hierarchy Level

[edit logical-systems logical-system-name protocols rsvp interface interface-name link-protection],[edit protocols rsvp interface interface-name link-protection]

Release Information

Statement introduced before JUNOS Release 7.4.


Enable you to configure specific bandwidth and path constraints for a bypass LSP. It is possible to individually configure multiple bypass LSPs. If you do not configure the bypass LSPs individually, they all share the same path and bandwidth constraints.

If you specify the bandwidth, hop-limit, and path statements for the bypass LSP, these values take precedence over the values configured at the [edit protocols rsvp interface interface-name link-protection] hierarchy level. The other attributes (subscription, no-node-protection, and optimize-timer) are inherited from the general constraints.


to address—(Required) Specify the address for the interface of the immediate next-hop node (for link protection) or the next-next-hop node (for node-link protection). The address specified determines whether this is a link protection bypass or a node-link protection bypass. On multiaccess networks (for example, a LAN), this address is also used to specify which next-hop node is being protected.

The remaining statements are explained separately.

Required Privilege Level

routing—To view this statement in the configuration.

routing-control—To add this statement to the configuration.

Published: 2010-04-28

[an error occurred while processing this directive]