[no] lsp lsp-name [bypass-only]
config>router>mpls
Supported on all 7210 SAS platforms as described in this document
This command creates an LSP that is signaled dynamically by the 7210 SAS.
When the LSP is created, the egress router must be specified using the to command and at least one primary or secondary path must be specified. All other statements under the LSP hierarchy are optional. Notre that the maximum number of static configurable LSPs is 4.
LSPs are created in the administratively down (shutdown) state.
The no form of this command deletes the LSP. All configuration information associated with this LSP is lost. The LSP must be administratively shutdown before it can be deleted.
Specifies a name that identifies the LSP. The LSP name can be up to 32 characters and must be unique.
Keyword to specify an LSP as a manual bypass LSP exclusively. When a path message for a new LSP requests bypass protection, the PLR first checks if a manual bypass tunnel satisfying the path constraints exists. If one is found, the 7210 SAS selects it. If no manual bypass tunnel is found, the 7210 SAS dynamically signals a bypass LSP in the default behavior. The CLI for this feature includes a command that provides the option to disable dynamic bypass creation on a per-node basis.
[no] adaptive
config>router>mpls>lsp
Supported on all 7210 SAS platforms as described in this document
This command configures the make-before-break (MBB) functionality for an LSP or LSP path. When enabled for the LSP, MBB is performed for the primary path and all the secondary paths of the LSP.
adaptive
[no] adspec
config>router>mpls>lsp
Supported on all 7210 SAS platforms as described in this document
This command specifies that the advertised data (ADSPEC) object is included in RSVP messages for this LSP. The ADSPEC object is used by the ingress LER to discover the minimum value of the MTU for links in the path of the LSP. By default, the ingress LER derives the LSP MTU from that of the outgoing interface of the LSP path.
A bypass LSP always signals the ADSPEC object because it protects both primary paths that signal the ADSPEC object and primary paths that do not. The MTU of LSP at ingress LER may change to a different value from that derived from the outgoing interface, even if the primary path has ADSPEC disabled.
no adspec
bgp-transport-tunnel {include | exclude}
config>router>mpls>lsp
Supported on all 7210 SAS platforms as described in this document
This command enables or disables RSVP-TE LSP to be used as a transport LSP for BGP tunnel routes.
bgp-transport-tunnel exclude
Keyword that enables RSVP-TE LSP to be used as transport LSP from ingress PE to ASBR in the local AS.
Keyword that disables RSVP-TE LSP to be used as transport LSP from ingress PE to ASBR in the local AS.
[no] cspf [use-te-metric]
config>router>mpls>lsp
Supported on all 7210 SAS platforms as described in this document
This command configures Constrained Shortest Path First (CSPF) computation for constrained-path LSPs. Constrained-path LSPs are the ones that take configuration constraints into account. CSPF is also used to calculate the detour routes when the fast-reroute command is enabled.
Explicitly configured LSPs where each hop from ingress to egress is specified do not use CSPF. The LSP will be set up using RSVP signaling from ingress to egress.
If an LSP is configured with fast-reroute frr-method specified but does not enable CSPF, neither global revertive nor local revertive is available for the LSP to recover.
no cspf
Keyword to specify the use of the TE metric for the purpose of the LSP path computation by CSPF.
[no] exclude group-name [group-name...(up to 5 max)]
config>router>mpls>lsp
Supported on all 7210 SAS platforms as described in this document
This command configures the admin groups to be excluded when an LSP is set up in the primary or secondary contexts.
Each single operation of the exclude command allows a maximum of five groups to be specified at a time. However, a maximum of 32 groups can be specified per LSP by using multiple operations. The admin groups are defined in the config>router>mpls>admin-group context.
The no form of this command removes the exclude command.
no exclude
Specifies the existing group-name to be excluded when an LSP is set up.
fast-reroute frr-method
no fast-reroute
config>router>mpls>lsp
Supported on all 7210 SAS platforms as described in this document
This command configures a precomputed detour LSP from each node in the path of the LSP. In case of failure of a link or LSP between two nodes, traffic is immediately rerouted on the precomputed detour LSP, which avoids packet loss.
When the fast-reroute command is enabled, each node along the path of the LSP tries to establish a detour LSP, as follows.
Each upstream node sets up a detour LSP that avoids only the immediate downstream node and merges back on to the actual path of the LSP as soon as possible.
If it is not possible to set up a detour LSP that avoids the immediate downstream node, a detour can be set up to the downstream node on a different interface.
The detour LSP may take one or more hops (see hop-limit) before merging back to the main LSP path.
When the upstream node detects a downstream link or node failure, the ingress router switches traffic to a standby path, if one was set up for the LSP.
Fast reroute is available only for the primary path. No configuration is required on the transit hops of the LSP. The ingress router signals all intermediate routers using RSVP to set up their detours. TE must be enabled for fast-reroute to work.
CSPF must be enabled for fast rerouter to work. If an LSP is configured with fast-reroute frr-method specified but without CSPF enabled, neither global revertive nor local revertive is available for the LSP to recover.
The no form of this fast-reroute command removes the detour LSP from each node on the primary path. This command also removes configuration information about the hop-limit and the bandwidth for the detour routes.
The no form of fast-reroute hop-limit command reverts to the default value.
no fast-reroute
Specifies the fast reroute method to use.
bandwidth rate-in-mbps
no bandwidth
config>router>mpls>lsp>fast-reroute
Supported on all 7210 SAS platforms as described in this document
This command configures reserved bandwidth on the detour path. When configuring an LSP, specify the traffic rate associated with the LSP.
When configuring the fast-reroute command, allocate bandwidth for the rerouted path. The bandwidth rate does not need to be the same as the bandwidth allocated for the LSP.
no bandwidth
Specifies the amount of bandwidth, in Mb/s, to be reserved for the LSP path.
hop-limit limit
no hop-limit
config>router>mpls>lsp>fast-reroute
Supported on all 7210 SAS platforms as described in this document
This command configures how many more routers a detour can traverse compared to the LSP itself on a fast reroute. For example, if an LSP traverses four routers, any detour for the LSP can be no more than ten router hops, including the ingress and egress routers.
The no form of this command reverts to the default value.
16
Specifies the maximum number of hops.
[no] node-protect
config>router>mpls>lsp>fast-reroute
Supported on all 7210 SAS platforms as described in this document
This command enables or disables node and link protection on the specified LSP. Node protection ensures that traffic from an LSP traversing a neighboring router reaches its destination even if the neighboring router fails.
node-protect
from ip-address
config>router>mpls>lsp
Supported on all 7210 SAS platforms as described in this document
This optional command specifies the IP address of the ingress router for the LSP. When this command is not specified, the system IP address is used. IP addresses that are not defined in the system are allowed. If an invalid IP address is entered, LSP bring-up fails and an error is logged.
If an interface IP address is specified as the from address, and the egress interface of the next-hop IP address is a different interface, the LSP is not signaled. As the egress interface changes because of changes in the routing topology, an LSP recovers if the from IP address is the system IP address and not a specific interface IP address.
Only one from address can be configured.
system IP address
Specifies the IP address of the ingress router. This can be either the interface or the system IP address. If the IP address is local, the LSP must egress through that local interface, which ensures local strictness.
hop-limit number
no hop-limit
config>router>mpls>lsp
config>router>mpls>lsp>fast-reroute
Supported on all 7210 SAS platforms as described in this document
This command configures the maximum number of hops that an LSP can traverse, including the ingress and egress routers. An LSP is not set up if the hop limit is exceeded. This value can be changed dynamically for an LSP that is already set up with the following implications.
If the new value is less than the current number of hops of the established LSP, the LSP is brought down. The 7210 SAS then tries to re-establish the LSP within the new hop-limit number.
If the new value is equal to or greater than the current number hops of the established LSP, the LSP is not affected.
The no form of this command reverts to the default value.
255
Specifies the number of hops the LSP can traverse, expressed as an integer.
[no] include group-name [group-name...(up to 5 max)]
config>router>mpls>lsp
config>router>mpls>lsp>primary
config>router>mpls>lsp>secondary
Supported on all 7210 SAS platforms as described in this document
This command configures the admin groups to be included when an LSP is set up. Up to five groups per operation can be specified, up to 32 maximum.
The no form of this command deletes the specified groups in the specified context.
no include
Specifies admin groups to be included when an LSP is set up.
metric metric
config>router>mpls>lsp
Supported on all 7210 SAS platforms as described in this document
This command configures the metric for this LSP, which is used to select an LSP among a set of LSPs that are destined for the same egress router. The LSP with the lowest metric is selected.
1
Specifies the metric for this LSP.
path-profile profile-id [path-group group-id]
no path-profile profile-id
config>router>mpls>lsp
Supported on all 7210 SAS platforms as described in this document
This command configures the PCE path profile and path group ID.
The PCE supports the computation of disjoint paths for two LSPs originating or terminating on the same or different PE routers. To indicate this constraint to the PCE, the user configures the PCE path profile ID and path group ID to which the PCE-computed or PCE-controlled LSP belongs. Because the PCC passes these parameters transparently to the PCE, the parameters are opaque data to the router.
The association of the optional path group ID allows the PCE to determine the profile ID to use with this path group ID. Although one path group ID is allowed for each profile ID, you can execute the path-profile command multiple times and enter the same path group ID with multiple profile IDs. A maximum of five path-profile profile-id [path-group group-id] entries can be associated with the same LSP.
Specifies the profile ID.
Specifies the path group ID.
[no] pce-computation
config>router>mpls>lsp
Supported on all 7210 SAS platforms as described in this document
This command enables the PCE-computed LSP mode of operation for an RSVP-TE LSP.
The user can grant only path computation requests (PCE-computed) or both path computation requests and path updates (PCE-controlled) to a PCE for a specific LSP.
The pce-computation command sends the path computation request to the PCE instead of the local CSPF. Enabling this option allows the PCE to perform path computations for the LSP at the request of the PCC router only. This is used in cases where the user wants to use the PCE-specific path computation algorithm instead of the local router CSPF algorithm.
The enabling of the pce-computation requires that the cspf option first be enabled; otherwise, this configuration is rejected. Conversely, an attempt to disable the cspf option on an RSVP-TE LSP that has the pce-computation command or pce-control command enabled is rejected.
no pce-computation
[no] pce-control
config>router>mpls>lsp
Supported on all 7210 SAS platforms as described in this document
This command enables the PCE-controlled LSP mode of operation for an RSVP-TE LSP.
Using the pce-control command, the PCC router delegates full control of the LSP to the PCE (PCE-controlled). As a result, PCE acts in an active stateful mode for this LSP. The PCE can reroute the path following a failure or reoptimize the path and update the router without an update request from the PCC router.
The user can delegate CSPF and non-CSPF LSPs, or LSPs that have the pce-computation option enabled or disabled. The LSP maintains the latest active path computed by the PCE or the PCC router at the time it is delegated. The PCE only updates the path at the next network event or reoptimization.
The enabling of the pce-control command requires that the cspf option first be enabled; otherwise, this configuration is rejected. Conversely, an attempt to disable the cspf option on an RSVP-TE LSP that has the pce-control command or pce-computation command enabled is rejected.
If PCE reporting is disabled for the LSP, either because of inheritance from the MPLS-level configuration or because of LSP-level configuration, enabling the pce-control option for the LSP has no effect.
no pce-control
pce-report {enable | disable | inherit}
config>router>mpls>lsp
Supported on all 7210 SAS platforms as described in this document
This command configures the reporting mode to a PCE for an RSVP-TE LSP.
The PCC LSP database is synchronized with the PCE LSP database using the PCEP PCRpt (PCE Report) message for PCC-controlled, PCE-computed, and PCE-controlled LSPs.
Use the global MPLS-level pce-report command (config>router>mpls>pce-report) to enable or disable PCE reporting for all RSVP-TE LSPs during PCE LSP database synchronization.
The LSP-level pce-report command overrides the global configuration for reporting an LSP to the PCE. The default configuration is to inherit the global MPLS-level configuration. The inherit option reconfigures the LSP to inherit the global configuration.
pce-report inherit
Keyword to enable PCE reporting.
Keyword to disable PCE reporting.
Keyword to inherit the global configuration for PCE reporting.
to ip-address
config>router>mpls>lsp
Supported on all 7210 SAS platforms as described in this document
This command configures the system IP address of the egress router for the LSP. This command is mandatory to create an LSP.
An IP address for which a route does not exist is allowed in the configuration. If the LSP signaling fails because the destination is not reachable, an error is logged and the LSP operational status is set to down.
Specifies the system IP address of the egress router.
retry-limit number
no retry-limit
config>router>mpls>lsp
Supported on all 7210 SAS platforms as described in this document
This optional command specifies the number of attempts software should make to re-establish the LSP after it has failed LSP. After each successful attempt, the counter is reset to zero.
When the specified number is reached, no more attempts are made, and the LSP path is put into the shutdown state.
Use the config router mpls lsp lsp-name no shutdown command to bring up the path after the retry limit is exceeded.
The no form of this command reverts to the default value.
0
Specifies the number of times the 7210 SAS attempts to re-establish the LSP after it has failed. Allowed values are integers; 0 indicates to retry forever.
retry-timer seconds
no retry-timer
config>router>mpls>lsp
Supported on all 7210 SAS platforms as described in this document
This command configures the time, in seconds, for LSP re-establishment attempts after the LSP has failed.
The no form of this command reverts to the default value.
30
Specifies the amount of time, in seconds, between attempts to re-establish the LSP after it has failed.
rsvp-resv-style [se | ff]
config>router>mpls>lsp
Supported on all 7210 SAS platforms as described in this document
This command configures the RSVP reservation style, shared explicit (se) or fixed filter (ff). A reservation style is a set of control options that specify a number of supported parameters. The style information is part of the LSP configuration.
se
Fixed filter is single reservation with an explicit scope. This reservation style specifies an explicit list of senders and a distinct reservation for each of them. A specific reservation request is created for data packets from a particular sender. The reservation scope is determined by an explicit list of senders.
Shared explicit is shared reservation with a limited scope. This reservation style specifies a shared reservation environment with an explicit reservation scope. This reservation style creates a single reservation over a link that is shared by an explicit list of senders. Because each sender is explicitly listed in the RESV message, different labels can be assigned to different sender-receiver pairs, thereby creating separate LSPs.
[no] shutdown
config>router>mpls>lsp
Supported on all 7210 SAS platforms as described in this document
This command disables the existing LSP including the primary and any standby secondary paths.
To shut down only the primary path, enter the config router mpls lsp lsp-name primary path-name shutdown command.
To shut down a specific standby secondary path, enter the config router mpls lsp lsp-name secondary path-name shutdown command. The existing configuration of the LSP is preserved.
The no form of this command restarts the LSP. LSPs are created in a shutdown state. Use this command to administratively bring up the LSP.
shutdown