[no] mpls
config>router
Supported on all 7210 SAS platforms as described in this document.
Commands in this context configure MPLS parameters. MPLS is not enabled by default and must be explicitly enabled (no shutdown). The shutdown command administratively disables MPLS.
The no form of this command deletes this MPLS protocol instance; this will remove all configuration parameters for this MPLS instance.
MPLS must be shutdown before the MPLS instance can be deleted. If MPLS is not shutdown, when the no mpls command is executed, a warning message is displayed on the console indicating that MPLS is still administratively up.
[no] admin-group-frr
config>router>mpls
7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12
This command enables the use of admin-group constraints when a manual or dynamic bypass LSP is associated 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 included in the Path message of the LSP primary path. If the object is not included, the PLR reads the Session Attribute object in the Path message.
If the PLR is also the ingress LER for the LSP primary path, only the admin-group constraints from the LSP or path level configurations are used.
Next, the PLR node uses the admin-group and other constraints, such as hop-limit and SRLG, to select a manual or dynamic bypass LSP among the bypass LSPs that are already in use.
If none of the manual or dynamic bypass LSPs satisfy the admin-group and other constraints, the PLR node requests the CSPF for a path that merges the closest to the protected link or node and that includes or excludes the specified admin-group IDs.
Modifying the configuration of this command does not affect existing bypass associations. The change only applies to new attempts to find a valid bypass.
The no form of this command disables the use of administrative group constraints on an FRR backup LSP at a PLR node.
no admin-group-frr
bypass-resignal-timer minutes
no bypass-resignal-timer
config>router>mpls
7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12
This command triggers the periodic global reoptimization of all dynamic bypass LSP paths associated with RSVP P2P LSP. The operation is performed at each expiry of the user-configurable bypass LSP resignal timer.
When this command is enabled, MPLS requests the CSPF for the best path for each dynamic bypass LSP originated on this node. The constraints of the first associated LSP primary path that originally triggered the signaling of the bypass LSP must be satisfied. To do this, MPLS saves the original Path State Block (PSB) of that LSP primary path, even if the latter is torn down.
If CSPF returns no path or returns a new path with a cost that is higher than the current path, MPLS does not signal the new bypass path. If CSPF returns a new path with a cost that is lower than the current path, MPLS signals it. Also, if the new bypass path is SRLG strict disjoint with the primary path of the original PSB while the current path is SLRG loose disjoint, the manual bypass path is resignaled, regardless of cost comparison.
After the new path is successfully signaled, MPLS evaluates each PSB of each PLR (that is, each unique avoid-node or avoid-link constraint) associated with the older bypass LSP path to check if the corresponding LSP primary path constraints are still satisfied by the new bypass LSP path. If so, the PSB association is moved to the new bypass LSP.
Each PSB for which constraints are not satisfied remains associated with the older bypass LSP and is checked at the next background PSB re-evaluation, or at the next timer or manual bypass reoptimization. If the older bypass LSP is SRLG disjoint with a primary path that has the non-strict SRLG constraint while the new bypass LSP is not SRLG disjoint, the PSB association is not moved.
If a specific PLR associated with a bypass LSP is active, the corresponding PSBs remain associated with the older bypass LSP until the global revertive Make-Before-Break (MBB) tears down all corresponding primary paths, which will also cause the older bypass LSP to be torn down.
This periodic bypass reoptimization feature also implements a background PSB re-evaluation task that audits in the background each RSVP session and determines if an existing manual or dynamic bypass is more optimal for that session. If so, it moves the PSB association to this existing bypass. If the PLR for this session is active, no action is taken and the PSB is re-examined at the next re-evaluation.
The periodic bypass reoptimization feature evaluates only the PSBs of the PLRs associated with that bypass LSP and only against the new bypass LSP path. The background re-evaluation task, however, audits all PSBs on the system against all existing manual and dynamic bypass LSPs.
PSBs that have not been moved by the dynamic or manual reoptimization of a bypass LSP because the PSB constraints have not been met by the new signaled bypass LSP path are re-evaluated by the background task against all existing manual and dynamic bypass LSPs.
Finally, the background re-evaluation task checks for PSBs that have requested node-protect bypass LSP but are currently associated with a link-protect bypass LSP, and PSBs that requested FRR protection but have no association. This is in addition to the attempt made at the receipt of a Resv message on the protected LSP path to accelerate the association.
This feature is not supported with inter-area dynamic bypass LSP and bypass LSP protecting S2L paths of a P2MP LSP.
The no form of this command disables the periodic global reoptimization of dynamic bypass LSP paths.
no bypass-resignal timer
Specifies the time, in minutes, that MPLS waits before attempting to resignal dynamic bypass LSP paths originated on the system.
[no] cspf-on-loose-hop
config>router>mpls
7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12
This command enables the option to perform CSPF calculations until the next loose hop or the final destination of the LSP on LSR. On receiving a PATH message on the LSR and processing all local hops in the received ERO, if the next hop is loose, the LSR node does a CSPF calculation until the next loose hop. On successful completion of the CSPF calculation, the ERO in the PATH message is modified to include 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 command is enabled on an LSR that is not an area border router and that receives a PATH message without a proper next loose hop in the ERO. The cspf-on-loose-hop command can change dynamically and is applied to the new LSP setup after changes are made.
The no form of this command reverts to the default value.
no cspf-on-loose-hop
dynamic-bypass [enable | disable]
no dynamic-bypass
config>router>mpls
Supported on all 7210 SAS platforms as described in this document.
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.
If the 7210 SAS is used as an egress LER and is a merge point, implicit null must be enabled for use of manual bypass or dynamic bypass (FRR facility).
dynamic-bypass enable
[no] frr-object
config>router>mpls
Supported on all 7210 SAS platforms as described in this document.
This command configures whether fast reroute for LSPs using the facility bypass method is signaled with or without the fast reroute object using the one-to-one keyword. The value is ignored if fast reroute is disabled for the LSP or if the LSP is using one-to-one backup.
frr-object
hold-timer seconds
no hold-timer
config>router>mpls
Supported on all 7210 SAS platforms as described in this document.
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 state is up.
The no form of this command disables the hold timer.
hold-timer 1
Specifies the hold time, in seconds.
p2mp-resignal-timer minutes
no p2mp-resignal-timer
config>router>mpls
7210 SAS-T, 7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12
This command configures the resignal timer for a P2MP LSP instance.
MPLS requests CSPF to recompute the whole set of S2L paths of a specific active P2MP instance each time the P2MP resignal timer expires. The P2MP resignal timer is configured separately from the P2P LSP parameter. MPLS performs a global MBB and moves each S2L sub-LSP in the instance into its new path using a new P2MP LSP ID if the global MBB is successful, regardless of the cost of the new S2L path.
The no form of this command disables the timer-based resignaling of P2MP LSPs on this system.
no resignal-timer
Specifies the time, in minutes, that MPLS waits before attempting to resignal the P2MP LSP instance.
pce-report rsvp-te {enable | disable}
config>router>mpls
7210 SAS-Mxp, 7210 SAS-R6, and 7210 SAS-R12
This command configures the reporting mode for RSVP-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.
This global MPLS-level pce-report command enables or disables PCE reporting for all RSVP-TE LSPs during PCE LSP database synchronization. The PCC reports both CSPF and non-CSPF LSPs.
The LSP-level pce-report command (config>router>mpls>lsp>pce-report) overrides the global configuration for reporting an LSP to the PCE. The default configuration, which inherits the global MPLS-level configuration, is disabled (pce-report rsvp-te disable).
The default configuration controls the introduction of a PCE into an existing network and allows the operator to decide whether all RSVP-TE LSPs should be reported. If PCE reporting for an LSP is disabled, either because of inheritance of the global MPLS configuration or because of LSP-level configuration, enabling the pce-control option for the LSP has no effect.
pce-report rsvp-te disable
Enables or disables PCE reporting for all RSVP-TE LSPs.
resignal-timer minutes
no resignal-timer
config>router>mpls
Supported on all 7210 SAS platforms as described in this document.
This command specifies the value for the LSP resignal timer. The resignal timer is the wait time, in minutes, before the software attempts to resignal the LSPs.
When the resignal timer expires, if the new computed path for an LSP has a better metric than the current recorded hop list, an attempt is made to resignal that LSP using the make-before-break mechanism. If the attempt to resignal an LSP fails, the LSP continues to use the existing path and a resignal is attempted the next time the timer expires.
The no form of this command disables timer-based LSP resignaling.
no resignal-timer
Specifies the time, in minutes, that the software waits before attempting to resignal the LSPs.
srlg-frr [strict]
no srlg-frr
config>router>mpls
Supported on all 7210 SAS platforms as described in this document.
This command enables 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 this system.
When this option is enabled, CSPF includes the SRLG constraint in the computation of an FRR detour or bypass for protecting the primary LSP path.
CSPF prunes all links with interfaces that belong to the same SRLG as the interface that is 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 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 setup and the MPLS/RSVP task will keep 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, the FRR bypass or detour LSP is set up.
An FRR bypass or detour LSP path 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 task is searching for a SRLG bypass tunnel to associate with the primary path of the protected LSP, the task first checks if any configured manual bypass LSP with CSPF enabled satisfies the SLRG constraints. The MPLS/RSVP skips any non-CSPF bypass LSP in the search as there is no ERO returned to check the SLRG constraint. If no path is found, the task checks if an existing dynamic bypass LSP satisfies the SLRG and other primary path constraints. If not, it will make a request to CSPF.
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 be considered by the MPLS/RSVP 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 because of a failure or to a make-before-break operation. Make-before-break occurs as a result of a global revertive operation, a timer based or manual reoptimization of the LSP path, or a user change to any of the path constraints.
After the FRR bypass or detour LSP path is setup and is operationally up, any subsequent changes to the SRLG group membership of an interface that the FRR bypass or detour LSP path is using would not be considered by the MPLS/RSVP task at the PLR until the next opportunity the association with the primary LSP path is rechecked. The association is rechecked if the bypass path is reoptimized. Detour paths are not reoptimized and are resignaled if the primary path is down.
Enabling or disabling srlg-frr only takes effect after LSP paths are resignaled. This can be achieved by shutting down and re-enabling MPLS. Another option is using the tools>perform>router>mpls>resignal command. Though the latter has less impact on service, only originating LSPs can be resignaled with the tools command. If local transit and bypass LSPs are also to be resignaled, the tools command must be executed on all ingress nodes in the network. The same can be locally achieved by disabling and enabling using the configure>router>mpls>dynamic-bypass command, but this can trigger the LSP to go down and traffic loss to occur in case detour or bypass LSP is in use.
An RSVP interface can belong to a maximum of 64 SRLG groups. The user configures the SRLG groups using the config>router>mpls>srlg-group command. The user associates the SRLG with an RSVP interface using the srlg-group command in the config>router>mpls>interface context.
The no form of this command reverts to the default value.
no srlg-frr
Specifies the name of the SRLG group within a virtual router instance.
user-srlg-db [enable | disable]
config>router>mpls
Supported on all 7210 SAS platforms as described in this document.
This command enables the use of CSPF by the user SRLG database. When the MPLS module makes a request to CSPF for the computation of an SRLG secondary path, CSPF queries the local SRLG and computes a path after pruning links that are members of the SRLG IDs of the associated primary path. When MPLS makes a request to CSPF for an FRR bypass or detour path to associate with the primary path, CSPF queries the user SRLG database and computes a path after pruning links that are members of the SRLG IDs of the PLR outgoing interface.
If an interface is not entered into the user SRLG database, it is assumed that it does not have any SRLG membership. CSPF will not query the TE database for IGP advertised interface SRLG information.
The disable keyword disables the use of the user SRLG database. CSPF resumes queries into the TE database for SRLG membership information. The user SRLG database is maintained.
user-srlg-db disable
Keyword to enable the use of the user SRLG database.
Keyword to disable the use of the user SRLG database.
[no] srlg-database
config>router>mpls
Supported on all 7210 SAS platforms as described in this document.
Commands in this context manually enter the link members of SRLG groups for the entire network at any node that needs to signal LSP paths (for example, a head-end node).
The no form of this command deletes the entire SRLG database. CSPF assumes all interfaces have no SRLG membership association if the database was not disabled with the command config>router>mpls>user-srlg-db disable.
[no] router-id ip-address
config>router>mpls>srlg-database
Supported on all 7210 SAS platforms as described in this document.
This command manually enters the link members of SRLG groups for a specific router in the network. The user must also use this command to enter the local interface SRLG membership into the user SRLG database. Use by CSPF of all interface SRLG membership information of a specific router ID may be temporarily disabled by shutting down the node. If this occurs, CSPF will assume these interfaces have no SRLG membership association.
The no form of this command deletes all interface entries under the router ID.
Specifies the router ID for this system. This value must be the router ID configured under the base router instance, the base OSPF instance, or the base IS-IS instance.
interface ip-address srlg-group group-name [group-name...(up to 5 max)]
no interface ip-address [srlg-group group-name...(up to 5 max)]
config>router>mpls>srlg-database>router-id
Supported on all 7210 SAS platforms as described in this document.
This command configures SRLG membership information for any link in the network, including links on this node, in the user SRLG database.
An interface can be associated with up to five SRLG groups for each execution of this command. The operator can associate an interface with up to 64 SRLG groups by executing the command multiple times.
CSPF will not use entered SRLG membership if an interface is not validated as part of a router ID in the routing table.
The no form of this command deletes a specific interface entry in this user SRLG database. The group name must already exist in the config>router>mpls>srlg-group context.
Specifies the name of the network IP interface. An interface name cannot be in the form of an IP address.
Specifies the SRLG group name, up to 32 characters. Up to 1024 group names can be defined in the config>router>mpls context. The SRLG group names must be identical across all routers in a single domain.
[no] label-map in-label
config>router>mpls>interface
Supported on all 7210 SAS platforms as described in this document.
This command is used on transit routers when a static LSP is defined. The static LSP on the ingress router is initiated using the config>router>mpls>static-lsp lsp-name command. The in-label is associated with either a pop or a swap action, but not both. If both actions are specified, the last action specified takes effect.
The no form of this command deletes the static LSP configuration associated with the in-label.
Specifies the incoming MPLS label on which to match.
[no] pop
config>router>mpls>if>label-map
Supported on all 7210 SAS platforms as described in this document.
This command specifies that the incoming label must be popped (removed). No label stacking is supported for a static LSP. The service header follows the top label. After the label is popped, the packet is forwarded based on the service header.
The no form of this command removes the pop action for the in-label.
[no] shutdown
config>router>mpls>if>label-map
Supported on all 7210 SAS platforms as described in this document.
This command disables the label map definition. This drops all packets that match the in-label specified in the label-map in-label command.
The no form of this command administratively enables the defined label map action.
no shutdown
swap {out-label | implicit-null-label} nexthop ip-address
no swap {out-label | implicit-null-label}
config>router>mpls>interface>label-map
Supported on all 7210 SAS platforms as described in this document.
This command swaps the incoming label and specifies the outgoing label and next hop IP address on an LSR for a static LSP.
The no form of this command removes the swap action associated with the in-label.
Keyword to specify the use of the implicit label value for the outgoing label of the swap operation.
Specifies the label value to be swapped with the in-label. Label values 16 through 1,048,575 are defined as follows.
Label values 16 through 31 are reserved.
Label values 32 through 1,023 are available for static assignment.
Label values 1,024 through 2,047 are reserved for future use.
Label values 2,048 through 18,431 are statically assigned for services.
Label values 28,672 through 131,071 are dynamically assigned for both MPLS and services.
Label values 131,072 through 1,048,575 are reserved for future use.
Specifies the IP address to forward to. If an ARP entry for the next hop exists, the static LSP is marked operational. If an ARP entry does not exist, the software sets the operational status of the static LSP to down and continues to the ARP for the configured next hop. Software will continue to the ARP for the configured next hop at a fixed interval.
[no] static-lsp lsp-name
config>router>mpls
Supported on all 7210 SAS platforms as described in this document.
This command configures a static LSP on the ingress router. The static LSP is a manually setup LSP where the next-hop IP address and the outgoing label (push) must be specified.
The LSP must first be shut down to delete it. If the LSP is not shut down, the no static-lsp lsp-name command generates a warning message on the console indicating that the LSP is administratively up.
The no form of this command deletes this static LSP and associated information.
Specifies the LSP name, up to 32 characters.
no push label
push label nexthop ip-address
config>router>mpls>static-lsp
Supported on all 7210 SAS platforms as described in this document.
This command specifies the label to be pushed on the label stack and the next hop IP address for the static LSP.
The no form of this command removes the association of the label to push for the static LSP.
Specifies the label to push on the label stack. Label values 16 through 1,048,575 are defined as follows.
Label values 16 through 31 are reserved.
Label values 32 through 1,023 are available for static assignment.
Label values 1,024 through 2,047 are reserved for future use.
Label values 2,048 through 18,431 are statically assigned for services.
Label values 28,672 through 131,071 are dynamically assigned for both MPLS and services.
Label values 131,072 through 1,048,575 are reserved for future use.
Specifies the IP address of the next hop toward the LSP egress router. If an ARP entry for the next hop exists, the static LSP is marked operational.
If an ARP entry does not exist, software sets the operational status of the static LSP to down and continues to ARP for the configured next hop. Software continuously tries to ARP for the configured next hop at a fixed interval.
[no] shutdown
config>router>mpls>static-lsp
Supported on all 7210 SAS platforms as described in this document.
This command administratively disables the static LSP.
The no form of this command administratively enables the static LSP.
shutdown
to ip-address
config>router>mpls>static-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 static LSP. This command is required while creating an LSP. For LSPs that are used as transport tunnels for services, the to IP address must be the system IP address. If the to address does not match the SDP address, the LSP is not included in the SDP definition.
Specifies the system IP address of the egress router.
static-lsp-fast-retry seconds
[no] static-lsp-fast-retry
config>router>mpls
Supported on all 7210 SAS platforms as described in this document.
This command configures the fast retry timer value for a static LSP.
When a static LSP is trying to come up, the MPLS request for the ARP entry of the LSP next hop may fail when it is made while the next hop is still down or unavailable. In that case, MPLS starts a retry timer before making the next request. This enhancement allows the user to configure the retry timer so that the LSP comes up as soon as the next hop is up.
The no form of this command removes the configuration.
no static-fast-retry-timer
Specifies the value, in seconds, used as the fast retry timer for a static LSP.