[no] mpls
config>router
This command creates the MPLS protocol instance and enables MPLS configuration. The MPLS protocol instance is not created by default, but once it is created, a no shutdown command is not required since MPLS is enabled automatically. The shutdown command administratively disables MPLS.
The no form of this command deletes this MPLS protocol instance and all configuration parameters for this MPLS instance.
MPLS must be shut down and all SDP bindings to LSPs removed before the MPLS instance can be deleted. If MPLS is not shut down, when the no mpls command is executed, a warning message on the console indicates that MPLS is still administratively up.
[no] admin-group-frr
config>router>mpls
This command enables the use of admin-group constraints in the association of a manual or dynamic bypass LSP with the primary LSP path at a Point-of-Local Repair (PLR) node.
When this command is enabled, each PLR node reads the admin-group constraints in the FAST_REROUTE object in the PATH message of the LSP primary path. If the FAST_REROUTE object is not included in the PATH message, the PLR reads the admin-group constraints from the SESSION_ATTRIBUTE object in the PATH message.
If the PLR is also the ingress LER for the LSP primary path, it only uses the admin-group constraint from the LSP and/or path level configurations.
The PLR node then uses the admin-group constraints along with other constraints, such as hop-limit and SRLG, to select a manual or dynamic bypass LSP among those that are already in use.
If none of the manual or dynamic bypass LSPs satisfies the admin-group constraints and/or the other constraints, the PLR node will request CSPF for a path that merges the closest to the protected link or node and includes or excludes the specified admin-group IDs.
Changes to this command (enabling or disabling) will apply only to new attempts to find a valid bypass.
The no form of this command disables the use of administrative group constraints on a FRR backup LSP at a PLR node.
no admin-group-frr
auto-lsp lsp-template template-name {policy peer-prefix-policy [peer-prefix-policy...(up to 5 max)] | one-hop}
no auto-lsp lsp-template template-name
config>router>mpls
This command enables the automatic creation of an RSVP-TE point-to-point LSP within a single IGP IS-IS level or OSPF area that can subsequently be used by services and/or IGP shortcuts. It can be used to create an RSVP-TE LSP mesh to a destination node whose router ID matches a prefix in a specified previously created peer prefix policy, or to create single-hop RSVP-TE LSPs. These LSP types are referred to as auto LSP of type mesh or auto LSP of type one-hop.
Multiple templates can be associated with the same or different peer prefix policies. Each application of an LSP template with a given prefix in the prefix list results in the instantiation of a single CSPF-computed LSP primary path using the LSP template parameters, as long as the prefix corresponds to a router ID for a node in the TE database. Auto LSP does not support the automatic signaling of a secondary path for an LSP. If the signaling of multiple LSPs to the same destination node is required, a separate LSP template must be associated with a prefix list that contains the same destination node address. Each instantiated LSP will have a unique LSP ID and a unique tunnel ID. Auto LSP also does not support the signaling of a non-CSPF LSP. The selection of the no cspf option in the LSP template is blocked.
Up to five peer prefix policies can be associated with an LSP template. Every time the user executes the above command with the same or different prefix policy associations or a prefix policy associated with the LSP template, the system re-evaluates the prefix policy. The outcome of the re-evaluation indicates to MPLS whether an existing LSP must be torn down or a new LSP must be signaled to a destination address that is already in the TE database.
If a /32 prefix is added to or removed from a prefix list associated with the template, or if a prefix range is expanded or narrowed, the prefix policy re-evaluation described above is performed.
A no shutdown of the template must be performed before it takes effect. When a template is in use, it must be shut down before the user can make any changes to the parameters except for LSP parameters for which the change can be handled with the Make-Before-Break (MBB) procedures. This includes fast-reroute with or without the hop-limit or node-protect options. When the template is shut down and parameters are added, removed or modified, the existing instances of the LSP using this template are torn down and resignaled.
The trigger to signal the LSP is when the router with a router ID matching a prefix in the prefix list appears in the TE database. The signaled LSP is installed in the Tunnel Table Manager (TTM) and is available to applications such as resolution of BGP label routes, and resolution of BGP, IGP, and static routes. It can also be used for auto-binding by a VPRN service but cannot be used as a provisioned SDP for explicit binding.
Except for the MBB limitations to the configuration parameter change in the LSP template, MBB procedures for manual and timer-based resignaling of the LSP, and for TE graceful shutdown, are supported.
The one-to-one option under fast-reroute is not supported.
If the one-hop option is specified instead of a prefix policy, this command enables the automatic signaling of single-hop, point-to-point LSPs using the specified template to all directly connected neighbors. This LSP type is referred to as auto LSP of type one-hop. When the above command is executed, the TE database keeps track of each TE link to a directly connected IGP neighbor whose router ID is discovered. It then instructs MPLS to signal an LSP with a destination address matching the router ID of the neighbor and with a strict hop consisting of the address of the interface used by the TE link. This results in one or more LSPs signaled to the neighboring router.
For an LSP mesh, the no form of this command deletes all LSPs signaled using the specified template and prefix policy. When the one-hop option is used, the no form of the command deletes all single-hop LSPs signaled using the specified template to all directly connected neighbors.
n/a
specifies an LSP template name
specifies that the template type is one-hop LSP, rather than LSP mesh
specifies a peer prefix policy name. The prefix policy must already be defined.
bypass-resignal-timer minutes
no bypass-resignal-timer
config>router>mpls
This command triggers the periodic global reoptimization of all dynamic bypass LSP paths associated with RSVP point-to-point LSPs. The operation is performed at each expiry of the timer.
The no form of this command disables the periodic global re-optimization of dynamic bypass LSP paths.
no bypass-resignal-timer
the time that MPLS waits before attempting to resignal dynamic bypass LSP paths originated on the system
[no] cspf-on-loose-hop
config>router>mpls
This command enables the option to perform CSPF calculations to the next loose hop or the final destination of the LSP on the LSR. On receiving a PATH message on the LSR and processing all local hops in the received ERO, if the next hop is loose, then the LSR does a CSPF calculation to the next loose hop (this is known as ERO expansion). On successful completion of the CSPF calculation, the ERO in the PATH message is modified to include the newly calculated intermediate hops and the message is propagated forward to the next hop. This allows for the setting up of inter-area LSPs based on the ERO expansion method.
The LSP may fail to set up if this option is enabled on an LSR that is not an ABR and that receives a PATH message without a proper next loose hop in the ERO. The cspf-on-loose-hop configuration can change dynamically and is applied to the new LSP setup after changes are made.
no cspf-on-loose-hop
dynamic-bypass [enable | disable]
config>router>mpls
This command disables the creation of dynamic bypass LSPs in FRR. One or more manual bypass LSPs must be configured to protect the primary LSP path at the PLR nodes.
enable
entropy-label rsvp-te {force-disable | enable}
entropy-label sr-te {force-disable | enable}
config>router>mpls
This command enables or disables the use of entropy labels for MPLS RSVP-TE and SR-TE LSPs.
If entropy-label is enabled, the entropy label and entropy label indicator (ELI) are inserted in the label stack. In some cases, this may result in an unsupported label stack depth or large changes in the label stack depth during the lifetime of an LSP (for example, due to switching from a primary path with entropy label capability (ELC) enabled to a secondary path for which the far end has not signaled ELC).
This command provides local control at the head end of an RSVP-TE or SR-TE LSP over whether an entropy label is inserted on the LSP by overriding the ELC signaled from the far-end LER, and control over how the additional label stack depth is accounted for.
By default, the value of entropy-label is inherited from the MPLS level. This command overrides the default MPLS behavior on a per-LSP basis. For auto LSPs, it can only be configured in LSP templates of type one-hop-p2p and mesh-p2p.
When the value of entropy-label changes at either the MPLS level or the LSP level, the new operational value does not take effect until the LSP is resignaled. A shutdown/no shutdown command must be performed on the LSP to enable the new value.
The user can use the clear command or bounce MPLS using the shutdown/no shutdown command to force the new value to take effect for a large numbers of LSPs.
entropy-label disable
indicates that the entropy-label command applies to RSVP-TE LSPs
indicates that the entropy-label command applies to SR-TE LSPs
the ingress LER will not consider the entropy label or the ELI in the label stack while sending the information to the TTM and NHLFE. The system will mark the TTM and NHLFE as ELC not supported, and applications will not insert an entropy label or ELI in the label stack.
the ingress LER will take into consideration what is signaled from the egress node for ELC for marking the NHLFE, while the TTM is always marked. Although applications will only insert the entropy label if the far end signals ELC, the additional two labels of the entropy label and ELI are always accounted for.
[no] frr-object
config>router>mpls
This command specifies whether signaling the FAST_REROUTE object is on or off. The value is ignored if fast reroute is disabled for the LSP or if the LSP is using one-to-one backup.
frr-object — by default, the value is inherited by all LSPs
hold-timer seconds
no hold-timer
config>router>mpls
This command specifies the amount of time that the ingress node waits before programming its data plane and declaring to the service module that the LSP status is up.
The no form of the command disables the hold-timer.
specifies the hold time, in seconds
least-fill-min-thd percent
no least-fill-min-thd
config>router>mpls
This parameter is used in the least-fill path selection process. See the description of the least-fill command for information on the least-fill path selection process. When comparing the percentages of least available link bandwidth across the available paths, whenever two percentages differ by less than the value configured as the least-fill minimum threshold, CSPF considers them to be equal and applies a random number generator to select the path.
The no form of the command resets this parameter to its default value.
5
specifies the least fill minimum threshold value as a percentage
least-fill-reoptim-thd percent
no least-fill-reoptim-thd
config>router>mpls
This parameter is used in the least-fill path selection process. See the description of the least-fill command for information on the least-fill path selection process.
During a timer-based resignaling of an LSP path that has the least-fill option enabled, CSPF first updates the least-available bandwidth value for the current path of this LSP. It then applies the least-fill path selection method to select a new path for this LSP. If the new computed path has the same cost as the current path, CSPF compares the least-available bandwidth values of the two paths and if the difference exceeds the user-configured optimization threshold, MPLS generates a trap to indicate that a better least-fill path is available for this LSP. This trap can be used by an external SNMP-based device to trigger a manual resignaling of the LSP path, since the timer-based resignaling will not resignal the path in this case. MPLS generates a path update trap at the first MBB event that results in the resignaling of the LSP path. This clears the eligibility status of the path at the SNMP device.
The no form of the command resets this parameter to its default value.
10
specifies the least fill reoptimization threshold value as a percentage
[no] logger-event-bundling
config>router>mpls
This command merges two of the most commonly generated MPLS traps, vRtrMplsXCCreate and vRtrMplsXCDelete, which can be generated at both the LER and LSR, into the new vRtrMplsSessionsModified trap. In addition, this command bundles traps of multiple RSVP sessions, such as LSPs, into this new trap.
This trap bundling allows the user to minimize trap generation in an MPLS network. MPLS trap throttling is not applied to the vRtrMplsSessionsModified trap.
The no version of the command disables the merging and bundling of the vRtrMplsXCCreate and vRtrMplsXCDelete traps.
pce-report rsvp-te {enable|disable}
pce-report sr-te {enable|disable}
config>router>mpls
This command separately configures the reporting modes to a PCE for RSVP-TE or SR-TE LSPs.
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.
The global MPLS-level pce-report command can be used to enable or disable PCE reporting for all SR-TE LSPs or RSVP-TE LSPs during PCE LSP database synchronization. This configuration is inherited by all LSPs of a particular type (RSVP-TE LSPs or SR-TE LSPs). The PCC reports both CSPF and non-CSPF LSPs.
The LSP-level pce-report command overrides the global configuration for the reporting of an LSP to the PCE (see config>router>mpls>lsp>pce-report). The default configuration is to inherit the global MPLS-level configuration.
The default configuration is disabled. This default configuration is meant to control the introduction of a PCE into an existing network and let the operator decide whether all RSVP-TE LSPs or SR-TE LSPs need to be reported. If PCE reporting is disabled for an LSP, either due to inheritance of the global MPLS configuration or due to LSP-level configuration, enabling the pce-control option for the LSP has no effect.
pce-report rsvp-te disable
pce-report sr-te disable
specifies to enable or disable PCE reporting for all RSVP-TE LSPs
specifies to enable or disable PCE reporting for all SR-TE LSPs
resignal-timer minutes
no resignal-timer
config>router>mpls
This command specifies the value for the LSP resignal timer. The resignal timer is the time, in minutes, that the 7705 SAR software waits before attempting to resignal the LSPs.
When the resignal timer expires, if the newly computed path for an LSP has a better metric than that for the currently recorded hop list, an attempt is made to resignal that LSP using the make-before-break (MBB) mechanism. If the attempt to resignal an LSP fails, the LSP will continue to use the existing path and a resignal will be attempted the next time the timer expires.
When the resignal timer expires, a trap and syslog message are generated.
The no form of the command disables timer-based LSP resignaling.
no resignal-timer
specifies the time the software waits before attempting to resignal the LSPs, in minutes
srlg-frr [strict]
no srlg-frr
config>router>mpls
This system-wide command enables or disables the use of the shared risk link group (SRLG) constraint in the computation of an FRR bypass or detour LSP for any primary LSP path on the system. When srlg-frr is enabled, CSPF includes the SRLG constraint in the computation of an FRR bypass or detour LSP for protecting the primary LSP path.
The strict option is a system-wide option that forces the CSPF to consider any configured SRLG membership lists in its calculation of every LSP path.
CSPF prunes all links with interfaces that belong to the same SRLG as the interface being protected, where the interface being protected is the outgoing interface at the PLR used by the primary path.
If one or more paths are found, the MPLS/RSVP-TE task selects one path based on best cost and signals the setup of the FRR bypass or detour LSP. If no path is found and the user included the strict option, the FRR bypass or detour LSP is not set up and the MPLS/RSVP-TE task keeps retrying the request to CSPF. If no path is found and the strict option is disabled, if a path exists that meets all the TE constraints except the SRLG constraint, then the FRR bypass or detour LSP is set up.
An FRR bypass or detour LSP is not guaranteed to be SRLG disjoint from the primary path. This is because only the SRLG constraint of the outgoing interface at the PLR that the primary path is using is checked.
When the MPLS/RSVP-TE task is searching for an SRLG bypass tunnel to associate with the primary path of the protected LSP, the task does the following steps.
First, the task checks for any configured manual bypass LSP that has CSPF enabled and that satisfies the SRLG constraints.
The task skips any non-CSPF bypass LSP since there is no ERO returned with which to check the SRLG constraint.
If no path is found, the task checks for an existing dynamic bypass LSP that satisfies the SRLG and other primary path constraints.
If no bypass path is found, then the task makes a request to CSPF to try to create one.
Once the primary path of the LSP is set up and is operationally up, any subsequent changes to the SRLG membership of an interface that the primary path is using will not be considered by the MPLS/RSVP-TE task at the PLR for FRR bypass or detour LSP association until the next opportunity that the primary path is resignaled. The path may be resignaled due to a failure or to a make-before-break (MBB) operation. A make-before-break operation occurs as a result of a global revertive operation, a reoptimization of the LSP path (timer-based or manual), or a change by the user to any of the path constraints.
Once the FRR bypass or detour LSP is set up and is operationally up, any subsequent change to the SRLG membership of an interface that the FRR bypass or detour LSP is using will not be considered by the MPLS/RSVP-TE task at the PLR until the next opportunity that the association with the primary LSP path is rechecked. The association is rechecked if the FRR bypass or detour LSP is reoptimized. Detour routes are not reoptimized and are resignaled if the primary path is down.
The user must first shut down MPLS before enabling or disabling the srlg-frr option in CLI.
An RSVP-TE interface can belong to a maximum of 64 SRLGs. The user creates SRLGs using the config>router>mpls>srlg-group command. The user associates the SRLGs with an RSVP-TE interface using the srlg-group command in the config>router> mpls>interface context.
The no form of the command reverts to the default value.
no srlg-frr
specifies that the CSPF calculation for the FRR backup must include the SRLG constraint and the backup must be on the resulting list of eligible backup paths