primary path-name
no primary
config>router>mpls>lsp
Supported on all 7210 SAS platforms as described in this document.
This command configures a preferred path for the LSP. This command is optional only if the secondary path name is included in the LSP definition. Only one primary path can be defined for an LSP.
Some of the attributes of the LSP, such as the bandwidth and hop limit, can be optionally specified as the attributes of the primary path. The attributes specified in the primary path-name command override the LSP attributes.
The no form of this command deletes the association of this path-name from the lsp lsp-name. All configurations specific to this primary path, such as record, bandwidth, and hop limit, are deleted. The primary path must be shut down to delete it. The no primary command will not result in any action except a warning message on the console indicating that the primary path is administratively up.
Specifies the case-sensitive alphanumeric name label for the LSP path, up to 32 characters in length.
[no] secondary path-name
config>router>mpls>lsp
Supported on all 7210 SAS platforms as described in this document.
This command configures an alternative path that the LSP uses if the primary path is not available. This command is optional and is not required if the config router mpls lsp lsp-name primary path-name command is specified. After the switch over from the primary to the secondary path, the software continuously tries to revert to the primary path. The switch back to the primary path is based on the retry-timer interval.
Up to eight secondary paths can be specified. All the secondary paths are considered equal and the first available path is used. The software will not switch back among secondary paths.
Software starts the signaling of all non-standby secondary paths at the same time. Retry counters are maintained for each unsuccessful attempt. Once the retry limit is reached on a path, software will not attempt to signal the path and administratively shuts down the path. The first successfully established path is made the active path for the LSP.
The no form of this command removes the association between this path-name and lsp-name. All specific configurations for this association are deleted. The secondary path must be shut down first to delete it. The no secondary path-name command will not result in any action except a warning message on the console indicating that the secondary path is administratively up.
Specifies the case-sensitive alphanumeric name label for the LSP path, up to 32 characters in length.
[no] adaptive
config>router>mpls>lsp>primary
config>router>mpls>lsp>secondary
Supported on all 7210 SAS platforms as described in this document.
This command enables the make-before-break functionality for an LSP or a primary or secondary LSP path. When enabled for the LSP, make-before-break is performed for the primary path and all the secondary paths of the LSP.
adaptive
[no] working-tp-path
config>router>mpls>lsp
7210 SAS-T, 7210 SAS-R6, and 7210 SAS-R12
This command configures or edits the working path for an MPLS-TP LSP. At least one working path (but not more than one working path) must be created for an MPLS-TP LSP. If MPLS-TP linear protection is also configured, this is the path that is used as the default working path for the LSP, and it must be created before the protect path. The working-tp-path can only be deleted if no protect-tp-path exists for the LSP.
The following commands are applicable to the working-tp-path: lsp-num, in-label, out-label, mep, shutdown.
no working-tp-path
[no] protect-tp-path
config>router>mpls>lsp
7210 SAS-T, 7210 SAS-R6, and 7210 SAS-R12
This command configures or edits the protect path for an MPLS-TP LSP. At least one working path must exist before a protect path can be created for an MPLS-TP LSP. If MPLS-TP linear protection is also configured, this is the path that is used as the default protect path for the LSP. The protect path must be deleted before the working path. Only one protect path can be created for each MPLS-TP LSP.
The following commands are applicable to the working-tp-path: lsp-num, in-label, out-label, mep, and shutdown.
lsp-num lsp-num
no lsp-num
config>router>mpls>lsp>working-tp-path
config>router>mpls>lsp>protect-tp-path
7210 SAS-T, 7210 SAS-R6, and 7210 SAS-R12
This command configures the MPLS-TP LSP number for the working TP path or the protect TP path.
no lsp-num
Specifies the LSP number.
in-label in-label
config>router>mpls>lsp>working-tp-path
config>router>mpls>lsp>protect-tp-path
7210 SAS-T, 7210 SAS-R6, and 7210 SAS-R12
This command configures the incoming label for the reverse path, working path, or protect path of an MPLS-TP LSP. MPLS-TP LSPs are bidirectional, and so an incoming label value must be specified for each path.
no in-label
Specifies the in label.
out-label out-label out-link if-name [next-hop ip-address]
no out-label
config>router>mpls>lsp>working-tp-path
config>router>mpls>lsp>protect-tp-path
7210 SAS-T, 7210 SAS-R6, and 7210 SAS-R12
This command configures the outgoing label value to use for an MPLS-TP working or protect path. The out-link is the outgoing interface on the node that this path will use, and must be specified. If the out-link refers to a numbered IP interface, the user may optionally configure the next-hop parameter and the system will determine the interface to use to reach the configured next-hop, but will check that the user-entered value for the out-link corresponds to the link returned by the system. If they do not correspond, the path will not come up.
no out-label
Specifies the out label.
Specifies the interface name.
Specifies the IPv4 address in a.b.c.d.
[no] mep
config>router>mpls>lsp>working-tp-path
config>router>mpls>lsp>protect-tp-path
7210 SAS-T, 7210 SAS-R6, and 7210 SAS-R12
This command creates or edits an MPLS-TP maintenance entity group (MEG) endpoint (MEP) on an MPLS-TP path. MEPs represent the termination point for OAM flowing on the path, as well as linear protection for the LSP. Only one MEP can be configured at each end of the path.
The following commands are applicable to a MEP on an MPLS-TP working or protect path: oam-template, bfd-enable, and shutdown. In addition, a protection-template may be configured on a protect path.
The no form of this command removes a MEP from an MPLS-TP path.
oam-template name
no oam-template
config>router>mpls>lsp>working-tp-path
config>router>mpls>lsp>protect-tp-path
7210 SAS-T, 7210 SAS-R6, and 7210 SAS-R12
This command applies an OAM template to an MPLS-TP working or protect path. It contains configuration parameters for proactive OAM mechanisms that can be enabled on the path, for example, BFD. Configuration of an OAM template is optional.
The no form of this command removes the OAM template from the path.
no oam-template
Specifies a text string name for the template up to 32 characters in printable 7-bit ASCII, enclosed in double quotes.
[no] shutdown
config>router>mpls>lsp>working-tp-path>mep
config>router>mpls>lsp>protect-tp-path>mep config>router>mpls>lsp>working-tp-path
config>router>mpls>lsp>protect-tp-path
7210 SAS-T, 7210 SAS-R6, and 7210 SAS-R12
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 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
bfd-enable bfd-mode
no bfd-enable
config>router>mpls>lsp>working-tp-path>mep
config>router>mpls>lsp>protect-tp-path>mep
7210 SAS-T, 7210 SAS-R6, and 7210 SAS-R12
This command associates the operational state of an MPLS-TP path with a BFD session for which control packets flow on the path. The BFD packets are encapsulated in a generic associated channel (G-ACh) on the path. The timer parameters of the BFD session are taken from the OAM template of the MEP.
A value of cc means that the BFD session is only used for continuity check of the MPLS-TP path. In this case, the cc timer parameters of the OAM template apply. A value of cc_cv means that the BFD session is used for both continuity checking and connectivity verification, and the cc_cv timers of the OAM template apply.
This form of this bfd-enable command is only applicable when it is configured under a MEP used on an MPLS-TP working or protect path.
no bfd-enable
Specifies the BFD mode.
protection-template name
no protection-template
config>mpls>lsp>protect-tp-path
7210 SAS-T, 7210 SAS-R6, and 7210 SAS-R12
This command applies a protection template name to an MPLS-TP LSP under which the protect path is configured. If the template is applied, MPLS-TP 1:1 linear protection is enabled on the LSP using the parameters specified in the named template.
A named protection template can only be applied to the protect path context of an MPLS-TP LSP.
The no form of this command removes the template and disables MPLS-TP linear protection on the LSP.
no protection-template
Specifies at text string for the template, up to 32 characters in printable 7-bit ASCII, enclosed in double quotes.
bandwidth rate-in-mbps
no bandwidth
config>router>mpls>lsp>primary
config>router>mpls>lsp>secondary
Supported on all 7210 SAS platforms as described in this document.
This command specifies the amount of bandwidth to be reserved for the LSP path.
The no form of this command resets bandwidth parameters (no bandwidth is reserved). This is the bandwidth setting in the global LSP configuration.
no bandwidth
Specifies the amount of bandwidth reserved for the LSP path in Mbps.
[no] exclude group-name [group-name...(up to 5 max)]
config>router>mpls>lsp>primary
config>router>mpls>lsp>secondary
Supported on all 7210 SAS platforms as described in this document.
This command specifies the admin groups to be excluded when an LSP is set up. Up to five groups per operation can be specified, up to 32 maximum. The admin groups are defined in the config>router>if-attribute 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.
hop-limit number
no hop-limit
config>router>mpls>lsp>primary
config>router>mpls>lsp>secondary
Supported on all 7210 SAS platforms as described in this document.
This optional command overrides the config router mpls lsp lsp-name hop-limit command. This command specifies the total number of hops that an LSP traverses, including the ingress and egress routers.
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 hops of the established LSP, the LSP is brought down. MPLS then tries to re-establish the LSP within the new hop limit number. If the new value is equal to or more than the current hops of the established LSP, the LSP will be unaffected.
The no form of this command reverts to the default values defined using the config router mpls lsp lsp-name hop-limit command.
no hop-limit
Specifies the number of hops the LSP can traverse, expressed as an integer.
[no] path-preference value
config>router>mpls>lsp>secondary
Supported on all 7210 SAS platforms as described in this document.
This command enables the use of path preference among configured standby secondary paths for each LSP. If all standby secondary paths have a default path preference value, a non-standby secondary path remains an active path, while a standby secondary is available. A standby secondary path configured with highest priority (lowest path preference value) must be made the active path when the primary path is not in use. Path preference can be configured on standby secondary path.
The no form of this command resets the path preference to the default value.
path-preference 255
Specifies an alternate path for the LSP if the primary path is not available.
[no] record
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 enables recording of all hops that an LSP path traverses. Enabling record increases the size of the PATH and RESV refresh messages for the LSP because this information is carried end-to-end along the LSP path. The increase in control traffic for each LSP may impact scalability.
The no form of this command disables the recording of all hops for a specific LSP. There are no restrictions for the no command usage.
The no form of this command also disables the record-label command.
record
[no] record-label
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 enables recording of all labels at each node that an LSP path traverses. Enabling the record-label command also enables the record command if it is not already enabled.
The no form of this command disables the recording of hops that an LSP path traverses.
record-label
[no] srlg
config>router>mpls>lsp>secondary
Supported on all 7210 SAS platforms as described in this document.
This command enables the use of the SRLG constraint in the computation of a secondary path for an LSP at the head-end LER. When this feature is enabled, CSPF includes the SRLG constraint in the computation of the secondary LSP path.
CSPF requires that the primary LSP be established already and in the up state, because the head-end LER needs the most current ERO computed by CSPF for the primary path and CSPF includes the list of SRLGs in the ERO during the CSPF computation of the primary path. At a subsequent establishment of a secondary path with the SRLG constraint, the MPLS/RSVP task queries CSPF again, which provides the list of SLRG group numbers to be avoided. CSPF prunes all links with interfaces that belong to the same SRLGs as the interfaces included in the ERO of the primary path. If CSPF finds a path, the secondary is setup. If CSPF does not find a path, MPLS/RSVP keeps retrying the requests to CSPF.
If CSPF is not enabled on the LSP (using the lsp lsp-name cspf command), a secondary path of that LSP that includes the SRLG constraint is shut down and a specific failure code indicates the exact reason for the failure in the show>router>mpls>lsp path detail output.
At initial primary LSP path establishment, if primary does not come up or is not configured, the SRLG secondary is not signaled and is put in the down state. A specific failure code indicates the exact reason for the failure in the show>router>mpls>lsp path detail output. However, if a non-SRLG secondary path was configured, such as a secondary path with the SRLG option disabled, the MPLS/RSVP task signals it and the LSP uses it.
As soon as the primary path is configured and successfully established, MPLS/RSVP moves the LSP to the primary path and signals all SRLG secondary paths.
Any time the primary path is reoptimized, has undergone MBB operation, or has come back up after being down, the MPLS/RSVP task checks with CSPF to determine if the SRLG secondary path should be resignaled. If the MPLS/RSVP task finds that the current secondary path is no longer SRLG disjoint — for example, the path became ineligible — it puts the path on a delayed MBB immediately after the expiry of the retry timer. If MBB fails on the first try, the secondary path is torn down and the path is put on retry.
At the next opportunity that the primary goes down, the LSP uses an eligible SRLG secondary path if the path is in the up state. If all secondary eligible SLRG paths are in the down state, MPLS/RSVP uses a non-SRLG secondary path if the path is configured and in the up state. If, while the LSP is using a non-SRLG secondary path, an eligible SRLG secondary path comes back up, MPLS/RSVP will not switch the path of the LSP to it. As soon as the primary path is resignaled and comes up with a new SLRG list, MPLS/RSVP resignals the secondary path using the new SRLG list.
A secondary path that becomes ineligible as a result of an update to the SRLG membership list of the primary path will have the ineligibility status removed when any of the following events occur.
A successful MBB operation of the standby SRLG path occurs, making the path eligible again.
The standby path goes down, in which case MPLS/RSVP puts the standby on retry when the retry timer expires. If successful, it becomes eligible. If not successful after the retry-timer expires or the number of retries reaches the number configured under the retry-limit parameter, it is left down.
The primary path goes down, in which case the ineligible secondary path is immediately torn down and will only be resignaled when the primary path comes back up with a new SRLG list.
After the primary path of the LSP is set up and is operationally up, any subsequent changes to the SRLG group membership of an interface that the primary path is using is not considered until the next opportunity that the primary path is resignaled. The primary path may be resignaled because of a failure or to a make-before-break operation. A make-before-break operation occurs as a result of a global revertive operation, a timer-based or manual re-optimization of the LSP path, or a change by a user to any of the path constraints.
After an SRLG secondary path is setup and is operationally up, any subsequent changes to the SRLG group membership of an interface that the secondary path is using is not considered until the next opportunity that the secondary path is resignaled. The secondary path is resignaled because of a failure, to a resignaling of the primary path, or to a make-before-break operation. A make-before break operation occurs as a result of a timer-based or manual reoptimization of the secondary path, or an operator change to any of the path constraints of the secondary path, including enabling or disabling the SRLG constraint itself.
In addition, the user-configured include or exclude admin group statements for this secondary path are also checked along with the SRLG constraints by CSPF.
The no form of this command reverts to the default value.
no srlg
[no] standby
config>router>mpls>lsp>secondary
Supported on all 7210 SAS platforms as described in this document.
The secondary path LSP is normally signaled when the primary path LSP fails. The standby keyword ensures that the secondary path LSP is signaled and maintained indefinitely in a hot-standby state. When the primary path is re-established, the traffic is switched back to the primary path LSP.
The no form of this command specifies that the secondary LSP is signaled when the primary path LSP fails.