[no] path path-name
config>router>mpls
This command creates the path to be used for an LSP. A path can be used by multiple LSPs. A path can specify some or all hops from ingress to egress and they can be either strict or loose. A path can also be empty (no path-name specified), in which case the LSP is set up based on the IGP (best effort) calculated shortest path to the egress router. Paths are created in a shutdown state. A path must be shut down before making any changes (adding or deleting hops) to the path. When a path is shut down, any LSP using the path becomes operationally down.
To create a strict path from the ingress to the egress router, the ingress and the egress routers must be included in the path statement.
The no form of this command deletes the path and all its associated configuration information. All the LSPs that are currently using this path will be affected. Additionally, all the services that are actively using these LSPs will be affected. A path must be shut down and unbound from all LSPs using the path before it can be deleted. The no path path-name command will not result in any action except a warning message on the console indicating that the path may be in use.
n/a
specifies the unique case-sensitive alphanumeric name label for the LSP path, up to 32 characters in length
hop hop-index ip-address{strict | loose}
hop hop-indexsid-label sid-value
no hop hop-index
config>router>mpls>path
This command specifies the IP address of the hops that the LSP should traverse on its way to the egress router. The IP address can be the interface IP address, a loopback IP address, or the system IP address. If the system IP address is specified, the LSP can choose the best available interface.
Optionally, the LSP ingress and egress IP addresses can be included as the first and last hop. A hop list can include the ingress interface IP address, the system IP address, and the egress IP address of any of the hops being specified.
When the sid-label parameter is specified, this command specifies an MPLS label value for a hop in the path of an SR-TE LSP. The label value implied by the SID is only used when the path is used by an SR-TE LSP. The loose and strict options do not apply for a hop containing a SID label; a SID hop must always be strict.
When the IP address is specified, the hop must be configured as either loose or strict. The loose option specifies that the route taken by the LSP from the previous hop to this hop can traverse other routers. The strict option specifies that the LSP must take a direct path from the previous hop router to this router. No transit routers between the previous router and this router are allowed. If the IP address specified is the interface address, that is the interface the LSP must use. If there are direct parallel links between the previous router and this router and if the system IP address is specified, then any one of the available interfaces can be used by the LSP. The user must ensure that the previous router and this router have a direct link. For both options, multiple hop entries with the same IP address are flagged as errors.
The no form of this command deletes hop list entries for the path. All the LSPs currently using this path are affected. Additionally, all services actively using these LSPs are affected. The path must be first shut down in order to delete the hop from the hop list. The no hop hop-index command does not result in any action other than generating a warning message indicating that the path is administratively up.
n/a
specifies the hop index, which is used to order the specified hops. The LSP always traverses from the lowest hop index to the highest. The hop index does not need to be sequential.
specifies the system, loopback, or network interface IP address of the transit router
specifies any valid MPLS/SR label value. The value is not restricted by any locally defined label ranges.
specifies that the LSP must take a direct path from the previous hop router to this router. No transit routers between the previous router and this router are allowed.
specifies that the route taken by the LSP from the previous hop to this hop can traverse other routers