Supported Platforms
Related Documentation
- ACX, M, MX, PTX, T Series
- Configuring Link Protection on Interfaces Used by LSPs
path (Protocols RSVP)
Syntax
Hierarchy Level
Release Information
Statement introduced before Junos OS Release 7.4.
Description
Configure an explicit path (a sequence of strict or loose routes) to control where and how a bypass LSP is established. If multiple bypasses are configured, they all will use the same explicit path.
Default
No path is configured. CSPF automatically calculates the path the bypass LSP takes.
Options
address—IP address of each transit router in the LSP. You must specify the address or hostname of each transit router, although you do not need to list each transit router if its type is loose. As an option, you can include the ingress and egress routers in the path. Specify the addresses in order, starting with the ingress router (optional) or the first transit router, and continuing sequentially along the path until reaching the egress router (optional) or the router immediately before the egress router.
Default: If you do not specify any routers explicitly, no routing limitations are imposed on the bypass LSP.
loose—(Optional) The next address in the path statement is loose. The LSP can traverse other routers before reaching this router.
Default: strict
strict—(Optional) The LSP must go to the next address specified in the path statement without traversing other nodes. This is the default.
Required Privilege Level
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Related Documentation
- ACX, M, MX, PTX, T Series
- Configuring Link Protection on Interfaces Used by LSPs
Published: 2012-07-02
Supported Platforms
Related Documentation
- ACX, M, MX, PTX, T Series
- Configuring Link Protection on Interfaces Used by LSPs
