path (Protocols MPLS)
Syntax
path path-name {
abstract-hop-name (abstract | loose | loose-link | strict);
(address | hostname) <strict | loose>;
}
Hierarchy Level
[edit logical-systems logical-system-name protocols mpls], [edit protocols mpls]
Description
Create a named path and optionally specify the sequence of explicit routers that form the path.
You must include this statement when configuring explicit LSPs.
Options
abstract-hop-name—Name of the
predefined abstract hop. The abstract hop can be used in combination
with real IP next hops. An abstract hop is traversed by traversing
the member nodes. This traversal can be done by either links that
satisfy the logical combination of defined constituent attributes,
or by any kind of link. This choice is controlled by the use of abstract
hop qualifiers – abstract, loose, loose-link, and strict.
abstract—Indicate that the next hop configured
in the path statement is an abstract hop..
loose-link—Indicate that the next hop in the path statement is a loose-link abstract hop. This means that
the LSP cannot traverse other routers before reaching this router.
In other words, the abstract hop of type loose-link is processed only
if any of the viable routers is reached in constraint through a link
of associated abstract hop membership.
loose—Indicate that the next hop in the path statement is a loose abstract hop. The path can traverse
any real nodes that do not have abstract hop membership, before reaching
a node with abstract hop membership, which is a feasible starting
point for processing the next abstract hop.
strict—Indicate that the next hop in the path statement is a strict abstract hop. After the last processed
hop in the constraint list, the path can traverse any real nodes that
do not have abstract hop membership, before reaching a node with abstract
hop membership, which is a feasible starting point for processing
the next abstract hop.
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 LSP.
hostname—See address.
Default: If you do not specify any routers explicitly, no routing limitations are imposed on the LSP.
loose—(Optional) Indicate that the next address
in the path statement is a loose link. This means that
the LSP can traverse through other routers before reaching this router.
Default:
strict
path-name—Name that identifies
the sequence of nodes that form an LSP. The name can contain up to
32 characters and can include letters, digits, periods, and hyphens.
To include other characters or use a longer name, enclose the name
in quotation marks. The name must be unique within the ingress router.
strict—(Optional) Indicate that 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.
Release Information
Statement introduced before Junos OS Release 7.4.
abstract-hop-name option introduced in Junos OS Release
17.1 for all platforms.