[no] lsp lsp-name [bypass-only | mpls-tp src-tunnel-num]
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. 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 the name that identifies the LSP. The LSP name can be up to 32 characters long and must be unique.
Keyword to define 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 if found, the 7210 SAS selects it. By default, if no manual bypass tunnel is found, the 7210 SAS dynamically signals a bypass LSP. The CLI for this feature includes a knob that provides the user with the option to disable dynamic bypass creation on a per-node basis.
Keyword to define an LSP as an MPLS-TP LSP. The following parameters can only be used with an MPLS-TP LSP: to, dest-global-id, dest-tunnel-number, working-tp-path, protect-tp-path. Other parameters defined for the above LSP types cannot be used. This is supported on 7210 SAS-T network mode, 7210 SAS-R6 and 7210 SAS-R12 devices only.
Specifies the source tunnel number. This is a mandatory time parameter for MPLS-TP LSPs, and has to be assigned by the user based on the configured range of tunnel IDs.
[no] adaptive
config>router>mpls>lsp
Supported on all 7210 SAS platforms as described in this document.
This command enables the make-before-break functionality for an LSP or LSP path. When enabled for the LSP, make-before-break is performed for the primary path and all secondary paths of the LSP.
adaptive
[no] adspec
config>router>mpls>lsp
Supported on all 7210 SAS platforms as described in this document.
When enabled, the ADSPEC object will be 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 primary paths that signal the ADSPEC object and primary paths that do not. This means that MTU of the 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 controls whether RSVP-TE LSP can be used as a transport LSP for BGP tunnel routes.
bgp-transport-tunnel exclude
Keyword to enable RSVP-TE LSP to be used as transport LSP from the ASBR to local PE router, from ingress PE to ASBR in the local AS, or between multi-hop eBGP peers with ASBR to ASBR adjacency.
Disables RSVP-TE LSP from being used as transport LSP from the ASBR to local PE router, from ingress PE to ASBR in the local AS, or between multi-hop eBGP peers with ASBR to ASBR adjacency.
[no] cspf [use-te-metric]
config>router>mpls>lsp
config>router>mpls>lsp-template
Supported on all 7210 SAS platforms as described in this document.
The config>router>mpls>lsp-template context is only supported on the 7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-T (operating in network mode), and 7210 SAS-Sx/S 1/10GE (operating in standalone and standalone-VC mode).
In the lsp-template context, this command is only supported with NG-MVPN. It is not supported with other applications.
This command enables constrained shortest path first (CSPF) computation for constrained-path LSPs. Constrained-path LSPs take configuration constraints into account. CSPF is also used to calculate the detour routes when the fast-reroute command is enabled.
Explicitly configured LSPs for which each hop from ingress to egress is specified do not use CSPF. The LSP is set up using RSVP signaling from ingress to egress.
If an LSP is configured with the fast-reroute frr-method option specified but does not enable CSPF, neither global revertive nor local revertive will be available for the LSP to recover.
The no form of this command disables CSPF computation for constrained-path LSPs.
no cspf
Keyword to use the TE metric for the CSPF computation of the LSP path.
[no] exclude group-name [group-name...(up to 5 max)]
config>router>mpls>lsp
config>router>mpls>lsp-template
Supported on all 7210 SAS platforms as described in this document.
The config>router>mpls>lsp-template context is only supported on the 7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-T (operating in network mode), and 7210 SAS-Sx/S 1/10GE (operating in standalone and standalone-VC mode).
In the lsp-template context, this command is only supported with NG-MVPN. It is not supported with other applications.
This command specifies the admin groups to be excluded when an LSP is set up in the primary or secondary contexts. A maximum of 5 groups can be specified per single operation of the exclude command. However, a maximum of 32 groups can be specified per LSP through multiple operations. The admin groups are defined in the config>router>if-attribute context.
The no form of this command removes the admin groups configured for exclusion.
no exclude
Specifies the existing group name, up to 32 characters, 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 enables 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 main 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 on 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 will signal all intermediate routers using RSVP to set up their detours. TE must be enabled for fast-reroute to work.
If an LSP is configured with the fast-reroute frr-method option specified but does not enable CSPF, neither global revertive nor local revertive will be available for the LSP to recover.
The no form of this command removes the detour LSP from each node on the primary path. This command will also remove 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.
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 the fast reroute context to set how many more routers a detour is allowed to traverse compared to the LSP itself. 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.
hop-limit 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 node and link protection on the specified LSP. Node protection ensures that traffic from an LSP traversing a neighboring router will reach its destination even if the neighboring router fails.
The no form of this command disables node and link protection on the specified LSP.
node-protect
[no] propagate-admin-group
config>router>mpls>lsp>fast-reroute
7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12
The command enables the signaling of the primary LSP path admin-group constraints in the FRR object at ingress.
When this command is executed, the admin-group constraints configured in the context of the P2P LSP primary path, or the constraints configured in the context of the LSP and inherited by the primary path, are copied into the FAST_REROUTE object. The admin-group constraints are copied into the ‟include-any” or ‟exclude-any” fields.
During LSP signaling to the downstream node, the ingress LER also propagates the admin-group constraints, which allows the node to include these constraints in the selection of the FRR backup LSP for LSP primary path protection.
The ingress LER inserts the FAST_REROUTE object, by default, in a primary LSP path message. If the user disables the object using config>router>mpls>no frr-object command, the admin-group constraints are not propagated.
The same admin-group constraints can be copied into the Session Attribute object for use by an LSR, typically an ABR, to expand the ERO of an inter-area LSP path. The constraints are also used by any LSR node in the path of a CSPF or non-CSPF LSP to check the admin-group constraints against the ERO regardless if the hop is strict or loose. These constraints are governed strictly by the config>router>mpls>lsp>propagate-admin-group command.
That is, the user can copy the primary path admin-group constraints into only the FAST_REROUTE object only, or only the Session Attribute object only, or both. However, the PLR rules for processing the admin-group constraints can make use of either of the two object admin-group constraints.
This feature is supported with the primary path of an RSVP P2P LSP in both intra-area and inter-area TE.
The no form of this command disables administrative group constraint signaling in the FRR object.
no propagate-admin-group
from ip-address
config>router>mpls>lsp
Supported on all 7210 SAS platforms as described in this document.
This optional command configures 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.
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. Software 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 returns the parameter to the default value.
hop-limit 255
Specifies the number of hops the LSP can traverse, expressed as an integer.
[no] include group-name [group-name...(up to 5max)]
config>router>mpls>lsp
config>router>mpls>lsp>primary
config>router>mpls>lsp>secondary
config>router>mpls>lsp-template
Supported on all 7210 SAS platforms as described in this document.
The config>router>mpls>lsp-template context is only supported on the 7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-T (operating in network mode), and 7210 SAS-Sx/S 1/10GE (operating in standalone and standalone-VC mode).
In the lsp-template context, this command is only supported with NG-MVPN. It is not supported with other applications.
This command configures the admin groups to be included when an LSP is set up. Up to 5 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, up to 32 characters, to be included when an LSP is set up.
[no] ldp-over-rsvp [include | exclude]
config>router>mpls>lsp
Supported on all 7210 SAS platforms as described in this document.
This command configures if this LSP will be included in LDP over RSVP.
The no form of this command reverts to default operation.
no ldp-over-rsvp
Specifies that this LSP will be included in LDP over RSVP.
Specifies that this LSP will be excluded from LDP over RSVP.
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.
In LDP-over-RSVP, LDP performs a lookup in the Routing Table Manager (RTM), which provides the next hop to the destination PE and the advertising router (ABR or destination PE). If the advertising router matches the targeted LDP peer, LDP performs a second lookup for the advertising router in the Tunnel Table Manager (TTM). This lookup returns the best RSVP LSP to use to forward packets for an LDP FEC learned through the targeted LDP session. The lookup returns the LSP with the lowest metric. If multiple LSPs have the same metric, the result of the lookup is to select the first available LSP in the TTM.
metric 1
Specifies 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.
path-profile profile-id [path-group group-id]
no path-profile profile-id
config>router>mpls>lsp
7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12
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 per 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
7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12
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 feature is used in cases where the operator wants to use the PCE-specific path computation algorithm instead of the local router CSPF algorithm.
The default configuration is no pce-computation. To enable the pce-computation command or pce-control command, you must first enable the cspf option, or 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
7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12
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 will only update the path at the next network event or reoptimization.
The default configuration is no pce-control. To enable the pce-control command or pce-computation command, you must first enable the cspf option; 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
7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12
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.
[no] propagate-admin-group
config>router>mpls>lsp
config>router>mpls>lsp-template
7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12 (for config>router>mpls>lsp context)
7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-T (network mode), and 7210 SAS-Sx/S 1/10GE (standalone and standalone-VC mode) (for config>router>mpls>lsp-template context)
In the lsp-template context, this command is only supported with NG-MVPN. It is not supported with other applications.
This command enables the propagation of session attribute objects with resource affinity (C-type 1) in a Path message. If a session attribute with resource affinity is received at an LSR, the LSR checks the compatibility of admin-groups received in the Path message with configured admin-groups on the egress interface of the LSP.
To support admin-groups for inter-area LSPs, the ingress node must configure the propagation of admin-groups within the SESSION_ATTRIBUTE object. If a Path message is received by an LSR node that has the cspf-on-loose-hop command configured and the message includes admin-groups, the ERO expansion by CSPF to calculate the path to the next loose hop will include the admin-group constraints received from the ingress node.
If the cspf-on-loose-hop command is disabled, the SESSION_ATTRIBUTE object without resource affinity (C-Type 7) is propagated in the Path message, and CSPF at the LSR node will not include admin group constraints.
Admin-group propagation is supported with P2P LSPs.
The user can change the value of the propagate-admin-group option on the fly. An RSVP P2P LSP performs a make-before-break (MBB) when changing the configuration.
The no form of this command removes the configuration.
no propagate-admin-group
retry-limit number
no retry-limit
config>router>mpls>lsp
config>router>mpls>lsp-template
Supported on all 7210 SAS platforms as described in this document.
The config>router>mpls>lsp-template context is only supported on the 7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-T (operating in network mode), and 7210 SAS-Sx/S 1/10GE (operating in standalone and standalone-VC mode).
In the lsp-template context, this command is only supported with NG-MVPN. It is not supported with other applications.
This command configures the number of attempts the software should make to re-establish the LSP after the LSP has failed. After each successful attempt, the counter is reset to zero.
When the configured retry limit is reached, no more attempts are made and the LSP path is set to the shutdown state.
Use the config>router>mpls>lsp>no shutdown command to bring up the path after the retry limit is exceeded.
The no form of this command reverts the parameter to the default value.
retry-limit 0
Specifies the number of software attempts to re-establish the LSP after it has failed. A value of 0 indicates to retry forever.
retry-timer seconds
no retry-timer
config>router>mpls>lsp
config>router>mpls>lsp-template
Supported on all 7210 SAS platforms as described in this document.
The config>router>mpls>lsp-template context is only supported on the 7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-T (operating in network mode), and 7210 SAS-Sx/S 1/10GE (operating in standalone and standalone-VC mode).
In the lsp-template context, this command is only supported with NG-MVPN. It is not supported with other applications.
This command configures the time, in seconds, between LSP re-establishment attempts after the LSP has failed.
The no form of this command reverts to the default value.
retry-timer 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.
rsvp-resv-style se
Keyword to configure fixed filter reservation style, which is a 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.
Keyword to configure shared explicit reservation style, which is a 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 path and any standby secondary paths.
To shut down only the primary path, enter the config>router>mpls>lsp>primary> shutdown command.
To shut down a specific standby secondary path, enter the config>router>mpls>lsp> secondary>shutdown command. The existing configuration of the LSP is preserved.
Use the no form of this command to restart the LSP. LSPs are created in a shutdown state. Use this command to administratively bring up the LSP.
shutdown
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.
vprn-auto-bind [include | exclude]
config>router>mpls>lsp
Supported on all 7210 SAS platforms as described in this document.
This command configures whether the associated LSP can be used as part of the auto-bind feature for VPRN services. By default, a named LSP is allowed to be used for the auto-bind feature.
When the vprn-auto-bind command is set to exclude, the associated LSP is not used by the auto-bind feature within VPRN services.
The no form of this command reverts to the default value.
vprn-auto-bind include
Keyword to allow an associated LSP to be used by auto-bind for VPRN services.
Keyword to prevent the associated LSP from being used with the auto-bind feature for VPRN services.
lsp-template template-name p2mp
no lsp-template template-name
config>router>mpls
7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-T (network mode), and 7210 SAS-Sx/S 1/10GE (standalone and standalone-VC mode)
This command creates a template that can be referenced by a client application where dynamic LSP creation is required. The LSP template type p2mp is mandatory.
The lsp-template command is only supported with NG-MVPN. This command is not supported for other applications.
The no form of this command deletes the LSP template. An LSP template cannot be deleted if a client application is using it.
Specifies the name of the LSP template, up to 32 characters. An LSP template name and LSP name must not be the same.
Mandatory keyword to configure P2MP as the LSP type that this template will signal.
default-path path-name
config>router>mpls>lsp-template
7210 SAS-Mxp, 7210 SAS-R6, 7210 SAS-R12, 7210 SAS-T (network mode), and 7210 SAS-Sx/S 1/10GE (standalone and standalone-VC mode)
A default path binding must be provided before the LSP template can be used for signaling LSP. The LSP template must be shut down to modify default-path binding.
In the lsp-template context, this command is only supported with NG-MVPN. It is not supported with other applications.
Specifies the default path binding, up to 32 characters.