[no] lsp lsp-name[bypass-only | sr-te]
config>router>mpls
This command creates an LSP that is signaled dynamically by the 7705 SAR.
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.
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 shut down and unbound from all SDPs before it can be deleted.
n/a
specifies the name that identifies the LSP. The LSP name can be up to 32 characters long and must be unique.
defines 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 is found, the 7705 SAR selects it. If no manual bypass tunnel is found, the 7705 SAR dynamically signals a bypass LSP as the default behavior. The CLI for this feature includes a command that provides the user with the option to disable dynamic bypass creation on a per-node basis.
defines an LSP as a segment routing LSP exclusively
lsp-template template-name
lsp-template template-name mesh-p2p
lsp-template template-name one-hop-p2p
no lsp-template template-name
config>router>mpls
This command creates an LSP template that is referenced when dynamic LSP creation is required. The LSP template type, mesh-p2p or one-hop-p2p, must be specified when the template is first created.
The no form of this command deletes the LSP template. The LSP template cannot be deleted if a client application is using it.
specifies an LSP template name up to 32 characters in length. The LSP template name and the LSP name cannot be the same.
specifies the type of LSP the template signals
[no] adaptive
config>router>mpls>lsp
config>router>mpls>lsp-template
This command enables the make-before-break (MBB) functionality for an LSP, LSP path, or LSP instance created using an LSP template. When enabled for the LSP, a make-before-break operation will be performed for the primary path and all the secondary paths of the LSP.
adaptive
[no] adspec
config>router>mpls>lsp
config>router>mpls>lsp-template
When enabled, the advertised data (ADSPEC) object will be included in RSVP-TE messages.
no adspec
bfd
config>router>mpls>lsp
config>router>mpls>lsp>primary
config>router>mpls>lsp>secondary
This command enables the context to configure seamless BFD (S-BFD) parameters on an LSP that is defined as an SR-TE LSP. The configuration in the config>router>mpls>lsp> secondary context is valid only for SR-TE LSPs.
[no] bfd-enable
config>router>mpls>lsp>bfd
config>router>mpls>lsp>primary>bfd
config>router>mpls>lsp>secondary>bfd
This command enables S-BFD for an SR-TE LSP. The BFD template must be configured in the config>router>bfd context before issuing the bfd-enable command.
The no form of this command disables S-BFD on the SR-TE LSP.
no bfd-enable
bfd-template name
no bfd-template
config>router>mpls>lsp>bfd
config>router>mpls>lsp>primary>bfd
config>router>mpls>lsp>secondary>bfd
This command specifies the BFD template to be used for an S-BFD session on an SR-TE LSP. The BFD template is configured in the config>router>bfd context and defines the parameters used during the session, such as the minimum transmit and receive intervals for control packets.
The no form of this command removes the template.
no bfd-template
the name of the existing BFD template
failure-action failover-or-down
no failure-action
config>router>mpls>lsp>bfd
This command configures the resulting action when BFD fails on an SR-TE LSP.
A failure action of failover-or-down means that a switchover from the active path is triggered if the BFD session fails on the active path (primary or standby). If there is no available path to switch to, the LSP is taken operationally down. This failure action is only applicable to SR-TE LSPs.
The system generates an SNMP trap if BFD fails on an LSP, regardless of whether a failure action is configured.
The no form of the command removes the configuration.
no failure-action
the active path of an SR-TE LSP switches to the secondary path, or the LSP goes operationally down if no other path is available
wait-for-up-timer seconds
no wait-for-up-timer
config>router>mpls>lsp>bfd
config>router>mpls>lsp>primary>bfd
config>router>mpls>lsp>secondary>bfd
This command configures the time to wait for BFD to come up on a path. This timer applies to SR-TE LSPs. The timer is started when BFD is first enabled on a path or BFD transitions from up to down. If the timer expires before BFD comes up, the path is torn down and the retry timer is started.
The wait-for-up-timer command is only available if the configured failure action is failover-or-down.
The no form of the command resets the timer to the default value.
4
the time to wait for BFD to come up
bgp-transport-tunnel {include | exclude}
config>router>mpls>lsp
config>router>mpls>lsp-template
This command allows an RSVP-TE LSP to be used as a transport LSP for BGP tunnel routes or blocks it from being used.
include
allows an RSVP-TE LSP to be used as a transport LSP from the ASBR to a local PE router, from an ingress PE to the ASBR in the local AS or between multihop EBGP peers with ASBR-to-ASBR adjacency
blocks an RSVP-TE LSP from being used as a transport LSP from the ASBR to a local PE router, from an ingress PE to the ASBR in the local AS or between multihop EBGP peers with ASBR-to-ASBR adjacency
[no] cspf [use-te-metric]
config>router>mpls>lsp
config>router>mpls>lsp-template
This command enables Constrained Shortest Path First (CSPF) computation for constrained-path LSPs. Constrained-path LSPs are the LSPs that take configuration constraints into account. CSPF is also used to calculate the FRR bypass or detour LSP routes when fast reroute is enabled.
Explicitly configured LSPs where each hop from ingress to egress is specified do not use CSPF. The LSP is set up using RSVP-TE signaling from ingress to egress.
If an LSP is configured with fast-reroute specified but does not enable CSPF, neither global revertive nor local revertive will be available for the LSP to recover.
When an LSP template is created, CSPF is automatically enabled and cannot be disabled.
no cspf
specifies to use the TE metric for the purpose of the LSP path computation by CSPF
default-path path-name
config>router>mpls>lsp-template
This command specifies the default path to be used for signaling an LSP created using the LSP template. You must reference a default path before the template is put in a no shutdown state.
specifies the default path name to be used
entropy-label {force-disable | inherit | enable}
config>router>mpls>lsp
This command configures the use of entropy labels for an LSP.
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 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 LSP over whether an entropy label is inserted on an 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.
Under the LSP context, when the value of entropy-label is set to enable, the ingress LER considers what is signaled from the egress node for ELC when marking the NHLFE as entropy-label-capable. When the value of entropy-label is set to enable at the LSP level, the system always marks the LSP as entropy label-capable regardless of the signaled value, in order to ensure that the potential additional label stack depth is accounted for. In this scenario, the TTM and NHLFE can be out of synchronization based on what is configured at the egress node. That is, the application will always account for the entropy label and ELI in the label stack without taking into consideration the signaled value of the ELC.
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 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 inherit
the ingress LER will not consider the entropy label and 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 entropy label indicator in the label stack.
the value of entropy-label is inherited from the setting in the MPLS context
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] exclude group-name[group-name...(up to 5 max)]
config>router>mpls>lsp
config>router>mpls>lsp>primary
config>router>mpls>lsp>secondary
config>router>mpls>lsp-template
This command specifies the admin groups to be excluded when an LSP is set up. Up to 5 groups per operation can be specified, up to 32 maximum. The admin groups are defined in the config>router>if-attribute context.
Use the no form of the command to remove the exclude command.
no exclude
specifies the existing group name to be excluded when an LSP is set up
fallback-path-computation-method [none]
no fallback-path-computation-method
config>router>mpls>lsp
This command specifies the fallback path computation method used if all configured PCEs are down or are signaling overload and the redelegation timer has expired. This method is used regardless of whether the LSP is PCE-controlled and PCE-computed, or just PCE-computed.
The no form of this command removes the fallback path computation method used.
fallback-path-computation-method none
[no] fast-reroute [frr-method]
config>router>mpls>lsp
config>router>mpls>lsp-template
This command creates a precomputed protection LSP from each node in the path of the LSP. If a link or LSP failure occurs between two nodes, traffic is immediately rerouted on the precomputed protection LSP. When fast-reroute is specified, the default fast-reroute method is the one-to-one method.
When fast-reroute is enabled, each node along the path of the LSP tries to establish a protection LSP as follows.
Each upstream node sets up a protection LSP that avoids only the immediate downstream node, and merges back onto the actual path of the LSP as soon as possible.
If it is not possible to set up a protection LSP that avoids the immediate downstream node, a protection LSP can be set up to the downstream node on a different interface.
The protection LSP may take one or more hops (see igp-shortcut) before merging back onto 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.
FRR 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-TE to set up their protection LSP. TE must be enabled for fast reroute to work.
CSPF must be enabled for fast reroute to work. If an LSP is configured with fast-reroute frr-method specified but does not enable CSPF, neither global revertive nor local revertive will be available for the LSP to recover.
The one-to-one fast reroute method creates a separate detour LSP for each backed-up LSP. One-to-one is not supported for LSP templates.
The facility fast reroute method, sometimes called many-to-one, takes advantage of the MPLS label stack. Instead of creating a separate LSP for every backed-up LSP, a single LSP is created that serves to back up a set of LSPs. This LSP tunnel is called a bypass tunnel. The bypass tunnel must intersect the path of the original LSPs somewhere downstream of the point of local repair (PLR). This constrains the set of LSPs being backed up via that bypass tunnel to those LSPs that pass through a common downstream node. All LSPs that pass through the PLR and through this common node that do not also use the facilities involved in the bypass tunnel are candidates for this set of LSPs.
The no form of the fast-reroute command removes the protection 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.
no fast-reroute
specifies the fast reroute method to use
hop-limit limit
no hop-limit
config>router>mpls>lsp>fast-reroute
config>router>mpls>lsp-template>fast-reroute
For fast reroute, this command defines how many more routers a protection tunnel is allowed to traverse compared with the LSP itself. For example, if an LSP traverses four routers, any protection tunnel for the LSP can be no more than 10 router hops, including the ingress and egress routers.
The no form of the command reverts to the default value.
16
specifies the maximum number of hops
[no] node-protect
config>router>mpls>lsp>fast-reroute
config>router>mpls>lsp-template>fast-reroute
This command enables or disables 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.
When node-protect is enabled, the 7705 SAR provides node protection on the specified LSP. If node protection cannot be provided, link protection is attempted. If link protection cannot be provided, there will be no protection.
The no form of this command provides link protection. If link protection cannot be provided, there will be no protection.
node-protect (for an LSP)
no node-protect (for an LSP template)
[no] propagate-admin-group
config>router>mpls>lsp>fast-reroute
config>router>mpls>lsp-template>fast-reroute
The command enables the signaling of the primary LSP path admin-group constraints in the FAST_REROUTE object at the ingress LER.
When this command is executed, the admin-group constraints configured in the context of the point-to-point 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.
The ingress LER propagates these constraints to the downstream nodes during the signaling of the LSP so that the downstream nodes can include the constraints in the selection of the FRR backup LSP for the LSP primary path.
The ingress LER inserts the FAST_REROUTE object by default in a primary LSP PATH message.
The same admin-group constraints can be copied into the SESSION_ATTRIBUTE object using the propagate-admin-group command at the config>router>mpls>lsp level. They are intended for the use of an LSR, typically an ABR, to expand the ERO of an inter-area LSP path. They 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 whether the hop is strict or loose.
The primary path admin-group constraints can be copied into the FAST_REROUTE object only, the SESSION_ATTRIBUTE object only, or both. The PLR rules for processing the admin-group constraints can make use of either of the two objects.
If the FAST_REROUTE object is disabled (no frr-object), the admin-group constraints will not be propagated.
no propagate-admin-group
from ip-address
config>router>mpls>lsp
config>router>mpls>lsp-template
This command specifies 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. This command is only allowed for an LSP template of type mesh-p2p.
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 due to 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.
system IP address
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-template
This command specifies 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. The 7705 SAR 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 of hops of the established LSP, the LSP is not affected.
The no form of this command returns the parameter to the default value.
255 (LSP and LSP mesh template)
2 (one-hop template)
specifies the number of hops the LSP can traverse, expressed as an integer
igp-shortcut [lfa-protect | lfa-only] [relative-metric [offset]]
no igp-shortcut
config>router>mpls>lsp
config>router>mpls>lsp-template
This command enables the use of an RSVP-TE LSP by OSPF or IS-IS routing protocols as a shortcut or as a forwarding adjacency for resolving IGP routes.
When the rsvp-shortcut or the advertise-tunnel-link command is enabled at the OSPF or IS-IS instance level, all RSVP-TE LSPs originating on this node are eligible by default as long as the destination address of the LSP, as configured with the config>router>mpls>lsp>to command, corresponds to a router ID of a remote node.
If the command is used with no options, and the rsvp-shortcut command is enabled, the LSP is included in the main SPF but not in the LFA SPF algorithm. If the advertise-tunnel-link command is enabled, the tunnel is advertised as a point-to-point link if it has the best LSP metric, is included in the main SPF if advertised, but is not included in the LFA SPF algorithm.
If the command is used with the lfa-protect option, and the rsvp-shortcut command is enabled, an LSP can be included in both the main SPF and the LFA SPF algorithm. If the advertise-tunnel-link command is enabled, the tunnel is advertised as a point-to-point link if it has the best LSP metric, is included in the main SPF if advertised, and is included in the LFA SPF algorithm whether it is advertised or not.
For a given prefix, the LSP can be used either as a primary next hop or as an LFA next hop, but not both. If the main SPF calculation selects a tunneled primary next hop for a prefix, the LFA SPF calculation will not select an LFA next hop for this prefix and the protection of this prefix will rely on the RSVP-TE LSP FRR protection. If the main SPF calculation selects a direct primary next hop, the LFA SPF calculation will select an LFA next hop for this prefix but will prefer a direct LFA next hop over a tunneled LFA next hop.
If the command is used with the lfa-only option, and the rsvp-shortcut command is enabled, an LSP can be included in the LFA SPF algorithm only. If the advertise-tunnel-link command is enabled, the tunnel is not advertised as a point-to-point link, is not included in the main SPF, and is only included in the LFA SPF algorithm.
When the lfa-only option is enabled, the introduction of IGP shortcuts does not affect the main SPF decision. For a given prefix, the main SPF calculation always selects a direct primary next hop. The LFA SPF calculation will select an LFA next hop for this prefix but will prefer a direct LFA next hop over a tunneled LFA next hop.
When the relative-metric option is enabled, IGP will apply the shortest IGP cost between the endpoints of the LSP plus the value of the offset (instead of the LSP operational metric) when calculating the cost of a prefix that is resolved to the LSP. The offset value is optional and defaults to zero. The minimum net cost for a prefix is one (1) after applying the offset. The Tunnel Table Manager (TTM) continues to show the LSP operational metric as provided by MPLS; therefore, applications such as BGP and static route shortcuts will continue to use the LSP operational metric.
The relative-metric option and the lfa-protect or the lfa-only options are mutually exclusive. An LSP with the relative-metric option enabled cannot be included in the LFA SPF calculation and the relative-metric option cannot be enabled if the LSP is included in the LFA SPF calculation when the rsvp-shortcut option is enabled in the IGP.
The relative-metric option is ignored when forwarding adjacency is enabled in OSPF or IS-IS. In this case, IGP advertises the LSP as a point-to-point unnumbered link along with the LSP operational metric as returned by MPLS and capped to the maximum link metric allowed in that IGP.
Both the main SPF and the LFA SPF algorithms use the local IGP database to resolve the routes.
The no form of this command disables the use of an RSVP-TE LSP by OSPF or IS-IS as a shortcut or a forwarding adjacency for resolving IGP routes.
For more information about IGP shortcuts and LFA, see the 7705 SAR Routing Protocols Guide, ‟LDP and IP Fast Reroute (FRR) for OSPF Prefixes” and ‟LDP and IP Fast Reroute (FRR) for IS-IS Prefixes”.
igp-shortcut — all RSVP-TE LSPs originating on this node are eligible by default as long as the destination address of the LSP corresponds to a router ID of a remote node
an LSP is included in both the main SPF and the LFA SPF calculation
an LSP is included in the LFA SPF calculation only
the shortest IGP cost between the endpoints of the LSP plus the configured offset, instead of the LSP operational metric returned by MPLS, is used when calculating the cost of prefix resolved to this LSP. The offset parameter is optional. If the relative-metric option is enabled without specifying the offset parameter value, a value of 0 is used.
[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
This command specifies the admin groups to be included when an LSP is set up. Up to 5 groups per operation can be specified, and up to 32 maximum.
The no form of the command deletes the specified groups in the specified context.
no include
specifies admin groups to be included when an LSP is set up
[no] least-fill
config>router>mpls>lsp
config>router>mpls>lsp-template
This command enables the use of the least-fill path selection method for the computation of the path of this LSP.
When MPLS requests the computation of a path for this LSP, CSPF finds all equal-cost shortest paths that satisfy the constraints of this path. Then, CSPF identifies the single link in each of these paths that has the least available bandwidth as a percentage of its maximum reservable bandwidth. It then selects the path that has the highest percentage available bandwidth. CSPF identifies the least-available bandwidth link in each equal-cost path after it has accounted for the bandwidth of the new requested path of this LSP.
CSPF applies the least-fill path selection method to all requests for a path, primary and secondary, of an LSP for which this option is enabled. The bandwidth of the path can be any value, including zero.
MPLS resignals and moves the LSP to the new path in the following cases:
initial LSP path signaling
retry of an LSP path after failure
MBB due to an LSP path configuration change, that is, a user change to the bandwidth parameter of the primary or secondary path, or a user enabling of the fast-reroute option for the LSP
MBB of the path due to an update to the primary path SRLG
MBB due to fast reroute global revertive procedures on the primary path
manual resignaling of an LSP path or of all LSP paths by the user
During a manual resignaling of an LSP path, MPLS always resignals the path even if the new path is the same as the current path and even if the metric of the new path is the same as the metric of the current path.
During a timer-based resignaling of an LSP path that has the least-fill option enabled, MPLS only resignals the path if the metric of the new path is different from the metric of the current path.
no least-fill - the path of an LSP is randomly chosen among a set of equal-cost paths
load-balancing-weight weight
no load-balancing-weight
config>router>mpls>lsp>load-balancing-weight
config>router>mpls>lsp-template>load-balancing-weight
This command assigns a weight to an MPLS LSP or an MPLS LSP template for use in weighted load balancing (weighted ECMP) over MPLS.
The no form of this command removes the load-balancing weight from the LSP or LSP template.
0
a 32-bit integer representing the weight of the LSP
max-sr-labels label-stack-size[additional-frr-labels labels]
no max-sr-labels
config>router>mpls>lsp
This command configures the maximum number of labels that the ingress LER can push for an SR-TE LSP.
This command is used to allow room to insert additional transport, service, and other labels when packets are forwarded in a context.
The max-sr-labels label-stack-size value should reflect the desired maximum label stack of the primary path of the SR-TE LSP.
The value in additional-frr-labels labels should reflect additional labels inserted by remote LFA for the backup next hop of the SR-TE LSP.
The sum of both label values represents the worst-case transport of SR label stack size for this SR-TE LSP. The sum is populated by MPLS in the Tunnel Table Manager (TTM) so that services and shortcut applications can check the TTM to determine whether a service can be bound or a route can be resolved to this SR-TE LSP.
The maximum label stack supported by the router is always signaled by the PCC in the PCEP Open object as part of the SR-PCE-CAPABILITY TLV. The maximum label stack is referred to as the Maximum Stack Depth (MSD).
In addition, the per-LSP value for the max-sr-labels option, if configured, is signaled by the PCC to the PCE in the Segment-ID (SID) Depth value in a METRIC object for both a PCE-computed LSP and a PCE-controlled LSP. The PCE will compute and provide the full explicit path with TE links specified. If there is no path with the number of hops lower than the MSD value or the SID Depth value (if signaled), a reply with no path will be returned to the PCC.
For a PCC-controlled LSP, if the label stack returned by the TE-DB hop-to-label translation exceeds the per-LSP maximum label stack size for the SR, the LSP is brought down.
max-sr-labels 6
additional-frr-labels 1
specifies the label stack size of the primary path of the SR-TE LSP
sets the number of additional labels inserted by remote LFA for the backup next hop of the SR-TE LSP
metric metric
config>router>mpls>lsp
config>router>mpls>lsp-template
This command specifies the metric for this LSP, which is used to select an LSP from among a set of LSPs that are destined for the same egress router. The LSP with the lowest metric will be selected.
The operational metric for an LSP that uses the TE metric in CSPF path calculations can be overridden by the configured administrative LSP metric parameter.
1
specifies the metric for this LSP
path-profile profile-id[path-group group-id]
no path-profile profile-id
config>router>mpls>lsp
This command configures the PCE path profile and path group ID.
The PCE supports the computation of disjoint paths for two different LSPs originating or terminating on the same or different PE routers. In order to indicate this constraint to the PCE, the user must configure the PCE path profile ID and path group ID that the PCE-computed or PCE-controlled LSP belongs to. These parameters are passed transparently by the PCC to the PCE and are thus opaque data to the router.
The association of the optional path group ID is to allow the PCE to determine which profile ID this path group ID must be used with. One path group ID is allowed per profile ID. The user can, however, enter the same path group ID with multiple profile IDs by executing this command multiple times. A maximum of five entries of path-profile [path-group] can be associated with the same LSP.
specifies the profile ID
specifies the path group ID
[no] pce-computation
config>router>mpls>lsp
This command enables a PCE-computed LSP mode of operation for RSVP-TE LSPs and SR-TE LSPs.
The user can grant only path computation requests (PCE-computed) or both path computation requests and path update (PCE-controlled) to a PCE for a specific LSP.
The pce-computation option allows the path computation request to be sent 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 is used in cases where the operator wants to make use of the PCE-specific path computation algorithm instead of the local router CSPF algorithm.
The default configuration is no pce-computation. The enabling of the pce-computation option or pce-control option requires that the cspf option first be enabled; otherwise, this configuration will be rejected. Conversely, an attempt to disable the cspf option on an LSP that has the pce-computation option or pce-control option enabled will be rejected.
no pce-computation
[no] pce-control
config>router>mpls>lsp
This command enables a PCE-controlled LSP mode of operation for RSVP-TE LSPs and SR-TE LSPs.
The pce-control option means that the PCC router delegates full control of the LSP to the PCE (PCE-controlled). Enabling PCE control means that the PCE is acting in active stateful mode for this LSP; the PCE will be able to reroute the path following a failure or reoptimize the path and update the router without the PCC router requesting the update.
The user can delegate CSPF and non-CSPF LSPs, or LSPs that have the pce-computation option enabled or disabled. The LSP maintains its latest active path computed by the PCE or the PCC router at the time it is delegated. The PCE will only make an update to the path at the next network event or reoptimization.
The default configuration is no pce-control. The enabling of the pce-control option or pce-computation option requires that the cspf option first be enabled; otherwise, this configuration will be rejected. Conversely, an attempt to disable the cspf option on an LSP that has the pce-control option or pce-computation option enabled will be rejected.
If PCE reporting is disabled for the LSP, either due to inheritance from the MPLS-level configuration or due to 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
config>router>mpls>lsp-template
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.
The global MPLS-level pce-report command can be used to enable or disable PCE reporting for all RSVP-TE LSPs during PCE LSP database synchronization (see config>router>mpls>pce-report).
The LSP-level pce-report command overrides the global configuration for the reporting of 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
enables PCE reporting
disables PCE reporting
inherits the global configuration for PCE reporting
[no] propagate-admin-group
config>router>mpls>lsp
config>router>mpls>lsp-template
This command enables propagation of the SESSION_ATTRIBUTE object with resource affinity (C-type 1) in the PATH message. If a SESSION_ATTRIBUTE object with resource affinity is received at an LSR, the LSR will check the compatibility of admin groups received in the PATH message against 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 option enabled and the message includes admin groups, then 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 this 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.
If the configuration of this command is changed (enabled or disabled), the LSP will perform a make-before-break (MBB).
no propagate-admin-group
retry-limit number
no retry-limit
config>router>mpls>lsp
config>router>mpls>lsp-template
This optional command specifies the number of attempts software should make to re-establish the LSP after it has failed. After each successful attempt, the counter is reset to zero.
When the specified number is reached, no more attempts are made and the LSP path is put into the shutdown state.
Use the config>router>mpls>lsp lsp-name>no shutdown command to bring up the path after the retry limit is exceeded.
The no form of this command resets the parameter to the default value.
0
specifies the number of times that the 7705 SAR software will attempt to re-establish the LSP after it has failed. Allowed values are integers in the range of 0 to 10000, where 0 indicates to retry forever.
retry-timer seconds
no retry-timer
config>router>mpls>lsp
config>router>mpls>lsp-template
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.
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
This command specifies the RSVP-TE 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.
se
fixed filter is 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.
shared explicit is 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
config>router>mpls>lsp>primary
config>router>mpls>lsp>secondary
config>router>mpls>lsp-template
This lsp form of this command disables the existing LSP, including the primary and any standby secondary paths.
The primary and secondary forms of this command administratively disable an LSP path and disable an existing LSP. Shutting down an LSP path does not change other configuration parameters for the LSP path.
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 lsp-template form of this command disables the existing LSP template.
Use the no form of this command to restart the LSP or LSP template. LSPs and LSP templates are created in a shutdown state. Use this command to administratively bring up the LSP or LSP template.
lsp — shutdown
primary — no shutdown
secondary — no shutdown
lsp-template — shutdown
to ip-address
config>router>mpls>lsp
This command specifies the 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.
If the to address does not match the SDP address, the LSP is not included in the SDP definition.
n/a
specifies the IP address of the egress router
vprn-auto-bind [include | exclude]
config>router>mpls>lsp
config>router>mpls>lsp-template
This command determines whether the associated LSP can be used as part of the auto-bind feature for VPRN services. By default, an LSP is allowed to be used by the auto-bind feature.
When VPRN auto-bind is set to exclude, the associated LSP is not used by the auto-bind feature for VPRN services.
include
allows an associated LSP to be used by auto-bind for VPRN services
prevents the associated LSP from being used with the auto-bind feature for VPRN services