[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.
MPLS must be shut down 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 displays indicating that MPLS is still administratively up.
The no form of this command deletes this MPLS protocol instance, which removes all configuration parameters for this MPLS instance.
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.
Implicit NULL must be enabled for the use of Manual Bypass or Dynamic Bypass (FRR facility) if the 7210 SAS is used as an egress LER or is a merge point.
dynamic bypass
[no] frr-object
config>router>mpls
Supported on all 7210 SAS platforms as described in this document
This command specifies 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.
By default, the value is inherited by all LSPs.
frr-object
hold-timer seconds
no hold-timer
config>router>mpls
Supported on all 7210 SAS platforms as described in this document
This command configures the amount of time that the ingress node waits before programming its data plane and declaring to the service module that the LSP is up.
The no form of this command disables the hold timer.
1 second
Specifies the hold time, in seconds.
pce-report rsvp-te {enable | disable}
config>router>mpls
Supported on all 7210 SAS platforms as described in this document
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.
The 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 (in the config>router>mpls>lsp>pce-report context) overrides the global configuration for reporting an LSP to the PCE. The default configuration, which inherits the global MPLS-level configuration, is disabled (using the pce-report rsvp-te disable command).
The default configuration controls the introduction of a PCE into an existing network and allows the user to decide whether all RSVP-TE LSPs should be reported. If PCE reporting for an LSP is disabled, either because of the 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
Specifies PCE reporting for all RSVP-TE LSPs.
enable — Keyword to enable PCE reporting.
disable — Keyword to disable PCE reporting.
resignal-timer minutes
no resignal-timer
config>router>mpls
Supported on all 7210 SAS platforms as described in this document
This command configures 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 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 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 this command 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 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 set up and the MPLS/RSVP task keeps retrying the request to CSPF. If a path exists that meets the other TE constraints, other than the SRLG one, the 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 task is searching for a SRLG bypass tunnel to associate with the primary path of the protected LSP, the task performs the following steps.
First, the task checks for any configured manual bypass LSP that has CSPF enabled and that satisfies the SLRG constraints.
The task then skips any non-CSPF bypass LSP in the search because there is no ERO returned with which to check the SLRG constraint.
If no path is found, the task checks for an existing dynamic bypass LSP that satisfies the SLRG and other primary path constraints.
If no bypass path is found, the task makes a request to CSPF to create one.
When 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 will not be considered by the MPLS/RSVP task at the PLR for 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 a make-before-break (MBB) operation. An MBB operation occurs as a result of a global revertive operation, a reoptimization of the LSP path (timer-based or manual), or a user change to any of the path constraints.
When the bypass or detour path is set up and is operationally up, subsequent changes to the SRLG group membership of an interface that the bypass or detour LSP path is using would not be considered by the MPLS/RSVP task at the PLR until the next opportunity that 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 the srlg-frr command takes effect only after LSP paths are resignaled, which is done by shutting down and reenabling MPLS. Another option is using the tools perform router mpls resignal command. While using the tools command may have less service impact, only originating LSPs can be resignaled using the tools command. If local transit and bypass LSPs must also be resignaled, the tools command must be executed on all ingress nodes in the network. The same may 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 when the detour or bypass LSP is in use.
An RSVP interface can belong to a maximum of 64 SRLG groups. Configure the SRLG groups using the config router mpls srlg-group command. Configure the SRLG groups that an RSVP interface belongs to 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 was 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 then 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 using the config router mpls user-srlg-db disable command.
[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 assumes 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 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 enable the user to manually enter the SRLG membership information for any link in the network, including links on this node, into the user SRLG database.
An interface can be associated with up to five SRLG groups for each execution of this command. The user can associate an interface with up to 64 SRLG groups by executing the command multiple times.
CSPF does 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 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. An in-label can be associated with either a pop or 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 command.
The no form of this command administratively enables the defined label map action.
no shutdown
swap out-label nexthop ip-address
swap implicit-null-label nexthop ip-address
no swap
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 values16 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 operational status of the static LSP is set to down and the software continuously tries to ARP for the configured next hop at fixed intervals.
[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 set up LSP where the next-hop IP address and the outgoing label (push) must be specified.
The no form of this command deletes this static LSP and associated information.
The LSP must be shut down first 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.
Specifies a name that identifies the LSP, up to 32 alphanumeric 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 1048575 are defined as follows.
Label values16 through 31 are reserved.
Label values 32 through 1023 are available for static assignment.
Label values 1024 through 2047 are reserved for future use.
Label values 2048 through 18431 are statically assigned for services.
Label values 28672 through 131071 are dynamically assigned for both MPLS and services.
Label values 131072 through 1048575 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 ARP entry does not exist, software sets the operational status of the static LSP to down and 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 value used as the fast retry timer 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 functionality 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 reverts to the default value.
no static-fast-retry-timer
Specifies the value, in seconds, used as the fast retry timer for a static LSP.