The no form of this command places the entity into an administratively enabled state.
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 and all SDP bindings to LSPs removed before the MPLS instance can be deleted. If MPLS is not shutdown, when the
no mpls command is executed, a warning message on the console displays indicating that MPLS is still administratively up.
Admin groups must be defined in the config>router>mpls context before they can be assigned to an MPLS interface. The IGP communicates the information throughout the area.
Up to 32 group names can be defined in the config>router>mpls context. The
admin-group names must be identical across all routers in a single domain.
The no form of this command deletes the administrative group. All configuration information associated with this LSP is lost.
The no form of this command removes the accounting policy association.
When the no collect-stats command is issued the statistics are still accumulated by the forwarding engine. However, the CPU will not obtain the results and write them to the billing file. If a subsequent
collect-stats command is issued then the counters written to the billing file include all the traffic while the
no collect-stats command was in effect.
The no form of this command disables the statistics in the egress data path and removes the accounting policy association from the RSVP LSP.
The no form of this command disables the use of administrative group constraints on a FRR backup LSP at a PLR node.
This command specifies whether fast reroute for LSPs using the facility bypass method is signalled 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.
The no form of the command reverts the hold-timer to the default value.
The no form of the command resets this parameter to its default value.
The no form of this command resets this parameter to its default value.
[no
] lsp
lsp-name sender
sender-address
The no form of this command disables statistics for this RSVP LSP in the ingress data path and removes the accounting policy association from the LSP.
[no
] logger-event-bundling
The no version of this command disables the merging and bundling of the above MPLS traps.
The no form of command deletes LSP template. LSP template cannot be deleted if a client application is using it.
The no form of this command returns the timer to the default value.
The no form of command deletes LSP template. LSP template cannot be deleted if a client application is using it.
[no
] propagate-admin-group
The no form of this command disables the signaling of administrative group constraints in the FRR object.
The no form of the command re-instates the default value of this parameter.
The no form of the command disables timer-based LSP resignalling.
The no form of the command reverts to the default.
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. However, note that while the latter might be less service impacting, only originating LSPs can be resignaled with the
tools command. If also local transit and bypass LSPs are to be resignaled, the
tools command must be executed on all ingress nodes in the network. The same might 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 command config>router>mpls>srlg-group. The user configures the SRLG groups an RSVP interface belongs to using the
srlg-group command in the
config>router>mpls>interface context.
The no form of the command reverts to the default value.
RSVP interfaces must be explicitly assigned to an SRLG group. SRLG groups must be defined in the config>router>mpls context before they can be assigned to an RSVP interface. Two different SRLG group names cannot share the same value. Once an SRLG group has been bound to an MPLS interface, its value cannot be changed until the binding is removed.
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.
The no form of this command deletes the SRLG group.
The no form of the command deletes the entire SRLG database. CSPF will assume all interfaces have no SRLG membership association if the database was not disabled with the command
config>router>mpls>user-srlg-db disable.
The no form of this command will delete all interface entries under the router ID.
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)]
The no form of the 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.
[no
] interface
ip-int-name
The no form of this command deletes all MPLS commands such as
label-map which are defined under the interface. The MPLS interface must be shutdown first in order to delete the interface definition. If the interface is not shutdown, the
no interface ip-int-name command does nothing except issue a warning message on the console indicating that the interface is administratively up.
[no]
admin-group group-name [
group-name...(up to 5 max)]
auto-lsp lsp-template template-name {policy
peer-prefix-policy [peer-prefix-policy
...(upto 5 max)] | one-hop
}
The user must perform a no shutdown of the template before it takes effect. Once a template is in use, the user must shutdown the template before effecting any changes to the parameters except for those LSP parameters for which the change can be handled with the Make-Before-Break (MBB) procedures. These parameters are
bandwidth and enabling
fast-reroute without the
hop-limit or node-protect options. For all other parameters, the user shuts down the template and once a it is added, removed or modified, the existing instances of the LSP using this template are torn down and re-signaled.
The one-to-one option under
fast-reroute, the LSP Diff-Serv
class-type and
backup-class-type parameters are not supported. If
diffserv-te is enabled under RSVP, the auto-created LSP will still be signaled but with the default LSP class type.
If the one-hop option is specified instead of a prefix list, this command enables the automatic signaling of one-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. Although the provisioning model and CLI syntax differ from that of a mesh LSP only by the absence of a prefix list, the actual behavior is quite different. When the above command is executed, the TE database will keep track of each TE link that comes up to a directly connected IGP neighbor which router-id is discovered. It then instructs MPLS to signals 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. Thus, the
auto-lsp command with the
one-hop option will result in one or more LSPs signaled to the neighboring router.
An auto-created mesh or one-hop LSP can have egress statistics collected at the ingress LER by adding the egress-statistics node configuration into the LSP template. The user can also have
ingress statistics collected at the egress LER using the same ingress-statistics node in CLI used with a provisioned LSP. The user must specify the full LSP name as signaled by the ingress LER in the RSVP session name field of the Session Attribute object in the received Path message.
The no form of this command deletes all LSP signaled using the specified template and prefix policy. When the
one-hop option is used, it deletes all one-hop LSPs signaled using the specified template to all directly connected neighbors.
[no
] srlg-group
group-name [group-name...(up to 5 max)]
The no form of this command deletes the association of the interface to the SRLG group.
The no form of the command reverts to the default value.
[no
] node-id-in-rro
<include | exclude>
The no form of this command reverts to the default value.
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 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.
The no form of this command removes the
pop action for the
in-label.
The no form of this command administratively enables the defined label map action.
swap {out-label | implicit-null-label
} nexthop
ip-address
no swap {out-label | implicit-null-label
}
The no form of this command removes the swap action associated with the
in-label.
Generic MPLS-TP parameters and MPLS-TP trabsit paths are configured under this context. If a user configures no mpls, normally the entire mpls configuration is deleted. However, in the case of mpls-tp, a check is made that there is no other mpls-tp configuration (e.g., services or LSPs using mpls-tp on the node). The mpls-tp context cannot be deleted if MPLS-TP LSPs or SDPs exist on the system.
A shutdown of mpls-tp will bring down all MPLS-TP LSPs on the system.
There are no default values for the start-id and
end-id of the tunnel id range, and they must be configured to enable MPLS-TP.
path-id {lsp-num l
sp-num | working-path | protect-path
[src-global-id
src-global-id] src-node-id
src-node-id src-tunnel-num
src-tunnel-num [dest-global-id
dest-global-id] dest-node-id
dest-node-id [dest-tunnel-num
dest-tunnel-num]}
The path-id must contain at least the following parameters: lsp-num, src-node-id, src-global-id, src-tunnel-num, dest-node-id.
The no form of the command removes the path ID from the configuration.
|
Values
|
1 — 65535, or working path, or protect-path. A working-path is equivalent to a lsp-num of 1, and a protect-path is an lsp-num of 2.
|
The no form of this command removes the forward path. The forward path cannot be removed if a reverse exists.
The no form of this command removes the reverse path. The reverse path must be removed before the forward path.
in-label in-label out-label
out-label out-link
if-name [next-hop
next-hop]
The incoming label, outgoing label and outgoing interface must be configured, using the in-label,
out-label and
out-link parameters. If the out-link refers to a numbered IP interface, the user may optionally configure the
next-hop parameter and the system will determine the interface to use to reach the configured next-hop, but will check that the user-entered value for the
out-link corresponds to the link returned by the system. If they do not correspond, then the path will not come up.
[no
] lsp
lsp-name [bypass-only | p2mp-lsp | mpls-tp
src-tunnel-num]
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 for signaled LSPs, or at least one working path for MPLS-TP LSPs. All other statements under the LSP hierarchy are optional.
The no form of this command deletes the LSP. All configuration information associated with this LSP is lost. The LSP must be administratively shutdown and unbound from all SDPs before it can be deleted.
Defines an LSP as a point-to-multipoint LSP. The following parameters can be used with a P2MP LSP: adaptive, adspec, cspf, exclude, fast-reroute, from, hop-limit, include, metric, retry-limit, retry-timer, resignal-timer. The following parameters cannot be used with a P2MP LSP: primary, secondary, to, dest-global-id, dest-tunnel-number, working-tp-path, protect-tp-path.
Defines an LSP as an MPLS-TP LSP. The src-tunnel-num is a mandatory create time parameter for mpls-tp LSPs, and has to be assigned by the user based on the configured range of tunnel IDs. The following parameters can only be used with an MPLS-TP LSP: to, dest-global-id, dest-tunnel-number, working-tp-path, protect-tp-path. Other parameters defined for the above LSP types cannot be used.
no adspec — No ADSPEC objects are included in RSVP messages.
The no form of the command disables the automatic adjustments of LSP or SDP bandwidth.
The no form of this command is equivalent to adjust-down 5.
The no form of this command is equivalent to adjust-up 5.
fc fc-name sampling-weight
sampling-weight
The no form of the command means max-bandwidth is infinite (equivalent to 100 Gbps).
The no form of the command means min-bandwidth is zero.
The no form of the command the collection and display of auto-bandwidth measurements.
The no form of this command instructs the system to take the value from the auto-bandwidth-defaults command.
The no form of this command disables overflow-triggered automatic bandwidth adjustment.
The no form of this command reverts to the default value.
[no
] cspf
[use-te-metric]
If an LSP is configured with fast-reroute frr-method specified but does not enable CSPF, then neither global revertive nor local revertive will be available for the LSP to recover.
out-label out-label out-link
if-name [next-hop
ip-address]
The no form of the command removes a MEP from an MPLS-TP path.
The no form of the command removes the OAM template from the path.
[no]
exclude group-name [
group-name...(up to 5 max)]
Use the no form of the command to remove the exclude command.
[no
] exclude-node
ip-address
When fast-reroute is enabled, each node along the path of the LSP tries to establish a detour LSP as follows:
If an LSP is configured with fast-reroute frr-method specified but does not enable CSPF, then neither global revertive nor local revertive will be available for the LSP to recover.
The no form of the
fast-reroute command removes the detour 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.
The no form of
fast-reroute hop-limit command reverts to the default value.
no fast-reroute — When fast-reroute is specified, the default fast-reroute method is one-to-one.
one-to-one — In the one-to-one technique, a label switched path is established which intersects the original LSP somewhere downstream of the point of link or node failure. For each LSP which is backed up, a separate backup LSP is
facility — This option, 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 which serves to backup up a set of LSPs. This LSP tunnel is called a bypass tunnel.
If an interface IP address is specified as the from address, and the egress interface of the nexthop 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.
The no form of this command returns the parameter to the default value.
igp-shortcut [lfa-protect
| lfa-only
] [relative-metric
[offset]]
When the rsvp-shortcut or the advertise-tunnel-link option is enabled at the IGP instance level, all RSVP LSPs originating on this node are eligible by default as long as the destination address of the LSP, as configured in
config>router>mpls>lsp>to, corresponds to a router-id of a remote node.
The lfa-protect option allows an LSP to be included in both the main SPF and the Loop-Free Alternate (LFA) SPF. 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 computation selected a tunneled primary next-hop for a prefix, the LFA SPF will not select an LFA next-hop for this prefix and the protection of this prefix will rely on the RSVP LSP FRR protection. If the main SPF computation selected a direct primary next-hop, then the LFA SPF will select an LFA next-hop for this prefix but will prefer a direct LFA next-hop over a tunneled LFA next-hop.
The lfa-only option allows an LSP to be included in the LFA SPF only such that the introduction of IGP shortcuts does not impact the main SPF decision. For a given prefix, the main SPF always selects a direct primary next-hop. The LFA SPF will select a 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 computing the cost of a prefix which is resolved to the LSP. The offset value is optional and it defaults to zero. The minimum net cost for a prefix is one (1) after applying the offset. Note that the TTM continues the show the LSP operational metric as provided by MPLS. In other words, applications such as LDP-over-RSVP (when IGP shortcut is disabled) and BGP and static route shortcuts will continue to use the LSP operational metric.
The relative-metric option is mutually exclusive with the
lfa-protect or the
lfa-only options. In other words, an LSP with the
relative-metric option enabled cannot be included in the LFA SPF and vice-versa when the
rsvp-shortcut option is enabled in the IGP.
Finally, the relative-metric option is ignored when forwarding adjacency is enabled in IS-IS or OSPF. 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 maximum link metric allowed in that IGP. Both the main SPF and the LFA SPFs will use the local IGP database to resolve the routes.
The no form of this command disables the use of a specific RSVP LSP by IS-IS and OSPF routing protocols as a shortcut or a forwarding adjacency for resolving IGP routes.
[no
] ldp-over-rsvp
[include
| exclude
]
Enter the command ldporsvp include to make the associated LSP available to be used by the LDP-over-RSVP feature.
[no
] include
group-name [group-name...(up to 5max)]
The no form of the command deletes the specified groups in the specified context.
The no form of this command sets the parameter to the default value of zero (0) which means the LSP primary path will retry forever.
The no form of this command disables the administrative LSP metric and reverts to the default setting in which the metric value will represent the LSP metric returned by MPLS. The same behavior is obtained if the user entered a metric of value zero (0).
no metric. The LSP operational metric defaults to the metric retuned by MPLS.
to [ip-address | node-id [a.b.c.d | 1...4,294,967,295]]
For a non MPLS-TP LSP, the to ip-address must be the system IP address of the egress router. If the
to address does not match the SDP address, the LSP is not included in the SDP definition.
For an MPLS-TP LSP, the to node-id may be either in 4-octet IPv4 address format, or a 32bit unsigned integer. This command is mandatory to create an MPLS-TP LSP. Note tha a value of zero is invalid. This to address is used in the MPLS-TP LSP ID, and the MPLS-TP MEP ID for the LSP.
node-id a.b.c.d. | 1...4,294,967,295
[no] propagate-admin-group
To support admin-group for inter-area LSP, the ingress node must configure propagating admin-groups within the session attribute object. If a PATH message is received by an LSR node that has the cspf-on-loose 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 ingress node.
The user can change the value of the propagate-admin-group option on the fly. A RSVP P2P LSP will perform a Make-Before-Break (MBB) on changing the configuration. A S2L path of an RSVP P2MP LSP will perform a Break-Before-Make on changing the configuration.
The no form of the command resets the flag backto the default value.
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 revert the parameter to the default value.
The no form of this command reverts to the default value.
To shutdown only the primary enter the config router mpls lsp lsp-name primary path-name shutdown command.
To shutdown a specific standby secondary enter the config router mpls lsp lsp-name secondary path-name shutdown command. The existing configuration of the LSP is preserved.
Use the no form of this command to restart the LSP. LSPs are created in a shutdown state. Use this command to administratively bring up the LSP.
The no form of command deletes LSP template. LSP template cannot be deleted if a client application is using it.
lsp-template-name — Name to identify LSP template. Any LSP template name and LSP name must not be same.
The no form of command should delete path binding.
This command specifies a preferred path for the LSP. This command is optional only if the secondary path-name is included in the LSP definition. Only one primary path can be defined for an LSP.
The no form of this command deletes the association of this
path-name from the LSP
lsp-name. All configurations specific to this primary path, such as record, bandwidth, and hop limit, are deleted. The primary path must be shutdown first in order to delete it. The
no primary command will not result in any action except a warning message on the console indicating that the primary path is administratively up.
This command specifies an alternative path that the LSP uses if the primary path is not available. This command is optional and is not required if the config router mpls lsp lsp-name primary path-name command is specified. After the switch over from the primary to the secondary, the software continuously tries to revert to the primary path. The switch back to the primary path is based on the
retry-timer interval.
The no form of this command removes the association between this
path-name and
lsp-name. All specific configurations for this association are deleted. The secondary path must be shutdown first in order to delete it. The
no secondary path-name command will not result in any action except a warning message on the console indicating that the secondary path is administratively up.
The case-sensitive alphanumeric name label for the LSP path up to 32 characters in length.
When an unmapped LSP primary path goes into retry, it uses the main CT until the number of retries reaches the value of the new main-ct-retry-limit parameter. If the path did not come up, it must start using the backup CT at that point in time. By default, this parameter is set to infinite value. The new main-ct-retry-limit parameter has no effect on an LSP primary path which retries due to a failure event.
The no form of this command disables the use of the Diff-Serv backup CT.
The no form of this command resets bandwidth parameters (no bandwidth is reserved).
no bandwidth (bandwidth setting in the global LSP configuration)
[no]
exclude group-name [
group-name...(up to 5 max)]
Use the no form of the command to remove the exclude command.
This optional command overrides the config router mpls lsp lsp-name hop-limit command. This command specifies the total number of hops that an LSP traverses, including the ingress and egress routers.
The no form of this command reverts the values defined under the LSP definition using the
config router mpls lsp lsp-name hop-limit command.
This command enables recording of all the hops that an LSP path traverses. Enabling record increases the size of the PATH and RESV refresh messages for the LSP since this information is carried end-to-end along the path of the LSP. The increase in control traffic per LSP may impact scalability.
The no form of this command disables the recording of all the hops for the given LSP. There are no restrictions as to when the
no command can be used. The
no form of this command also disables the
record-label command.
The no form of this command disables the recording of the hops that an LSP path traverses.
The no form of the command reverts to the default value.
The secondary path LSP is normally signaled once the primary path LSP fails. The standby keyword ensures that the secondary path LSP is signaled and maintained indefinitely in a hot-standby state. When the primary path is re-established then the traffic is switched back to the primary path LSP.
The no form of this command specifies that the secondary LSP is signaled when the primary path LSP fails.
[no
] path-preference
value
The no form of this command resets the path-preference to the default value.
hop hop-index ip-address {strict | loose
}
The no form of this command deletes hop list entries for the path. All the LSPs currently using this path are affected. Additionally, all services actively using these LSPs are affected. The path must be shutdown first in order to delete the hop from the hop list. The
no hop hop-index command will not result in any action except a warning message on the console indicating that the path is administratively up.
This command creates the path to be used for an LSP. A path can be used by multiple LSPs. A path can specify some or all hops from ingress to egress and they can be either strict or
loose. A path can also be empty (no
path-name specified) in which case the LSP is set up based on IGP (best effort) calculated shortest path to the egress router. Paths are created in a
shutdown state. A path must be shutdown before making any changes (adding or deleting hops) to the path. When a path is shutdown, any LSP using the path becomes operationally down.
The no form of this command deletes the path and all its associated configuration information. All the LSPs that are currently using this path will be affected. Additionally all the services that are actively using these LSPs will be affected. A path must be
shutdown and unbound from all LSPs using the path before it can be deleted. The
no path path-name command will not result in any action except a warning message on the console indicating that the path may be in use.
The no form of this command administratively enables the path. All LSPs, where this path is defined as primary or defined as standby secondary, are (re)established.
The no form of this command deletes this static LSP and associated information.
The LSP must be shutdown first in order to delete it. If the LSP is not shut down, the no static-lsp lsp-name command does nothing except generate a warning message on the console indicating that the LSP is administratively up.
[no
] static-lsp-fast-retry
The no form of the commnand reverts to the default.
push {label | implicit-null-label
} nexthop
ip-address
no push {out-label | implicit-null-label
}
The no form of this command removes the association of the label to push for the static LSP.
The no form of this command administratively enables the static LSP.
The p2mp-id is a 32-bit identifier used in the session object that remains constant over the life of the P2MP tunnel. It is unique within the scope of the ingress LER.
The no form restores the default value of this parameter.
[no
] primary-p2mp-instance
instance-name
[no
] s2l-path
path-name to
ip-address
The S2L paths can be empty paths or can specify a list of explicit hops. The path name must exist and must have been defined using the config>router>mpls>path command. The same path name can be re-used by more than one S2L of the primary P2MP instance. However, the
to keyword must have a unique argument per S2L as it corresponds to the address of the egress LER node.
The no form of this command disables the timer-based re-signaling of P2MP LSPs on this system.
The no form of this command administratively enables RSVP on the interface.
The no form of this command deletes this RSVP protocol instance and removes all configuration parameters for this RSVP instance. To suspend the execution and maintain the existing configuration, use the
shutdown command. RSVP must be shutdown before the RSVP instance can be deleted. If RSVP is not shutdown, the
no rsvp command does nothing except issue a warning message on the console indicating that RSVP is still administratively enabled.
The no form of this command reverts to the default value.
class-type-bw ct0 %-link-bandwidth ct1
%-link-bandwidth ct2
%-link-bandwidth ct3
%-link-bandwidth ct4
%-link-bandwidth ct5
%-link-bandwidth ct6
%-link-bandwidth ct7
%-link-bandwidth
The RSVP interface subscription percentage parameter is configured in the
config>router>rsvp>interface context.
The no form of this command reverts to the default value.
ct0 (ct1/ct2/
— ct7
) % link-bandwidth
fc fc-name class-type
ct-number
The no form of this command reverts to the default mapping for the forwarding class name.
te-class te-class-number class-type
ct-number priority
priority
The no form of this command deletes the TE class.
The no form of the command disables the graceful shutdown operation at the RSVP interface level or at the RSVP level. The configured TE parameters of the maintenance links are restored and the maintenance node floods the links.
The no version of this command re-instates the default value for the delay timer.
The no form of this command disables the signaling of the implicit null label.
[no
] keep-multiplier
number
The keep-multiplier number is an integer used by RSVP to declare that a reservation is down or the neighbor is down.
The no form of this command reverts to the default value.
The keep-multiplier value.
The no form of this command reverts to the default value.
The no form of this command reverts to the default value.
The refresh-time controls the interval, in seconds, between the successive Path and Resv refresh messages. RSVP declares the session down after it misses
keep-multiplier number consecutive refresh messages.
The no form of this command reverts to the default value.
This command is used to control threshold-based IGP TE updates. The te-threshold-update command must enable IGP TE update based only on bandwidth reservation thresholds per interface and must block IGP TE update on bandwidth changes for each reservation. Threshold levels can be defined using the
te-up-threshold and
te-down-threshold commands at the global RSVP or per-interface level.
The no form of this command should reset te-threshold-update to the default value and disable threshold based update.
The no form of this command should reset on-cac-failure to the default value and disable the CAC failure-triggered IGP update.
The no form of this command should reset update-timer to the default value and disable timer-based IGP update.
This command configures the specific threshold levels per node and per interface. Threshold levels are for reserved bandwidth per interface. The te-threshold-update command is used to enable or disable threshold-based IGP TE updates. Any reserved bandwidth change per interface is compared with all the threshold levels and trigger an IGP TE update if a defined threshold level is crossed in either direction (LSP setup or teardown). Threshold-based updates must be supported with both ISIS and OSPF. A minimum of one and a maximum of 16 threshold levels must be supported.
The no form of this command resets te-up-threshold to its default value.
This command configures the specific threshold levels per node and per interface. Threshold levels are for reserved bandwidth per interface. The te-threshold-update command is used to enable or disable threshold-based IGP TE updates. Any reserved bandwidth change per interface is compared with all the threshold levels and trigger an IGP TE update if a defined threshold level is crossed in either direction (LSP setup or teardown). Threshold-based updates must be supported with both ISIS and OSPF. A minimum of one and a maximum of 16 threshold levels is supported.
The no form of this command resets te-down-threshold to its default value.
[no
] interface
ip-int-name
The no form of this command deletes all RSVP commands such as
hello-interval and
subscription, which are defined for the interface. The RSVP interface must be
shutdown it can be deleted. If the interface is not shut down, the
no interface ip-int-name command does nothing except issue a warning message on the console indicating that the interface is administratively up.
The no form of this command disables authentication.
Specifies the key is entered in a more complex encrypted form. If the
hash2 parameter is not used, the less encrypted
hash form is assumed.
The user configures the BFD session parameters, such as, transmit-interval,
receive-interval, and
multiplier, under the IP interface in the
config>router> interface>bfd context.
The no form of this command removes BFD from the associated RSVP protocol adjacency.
The no form of this command reverts to the default value of the hello-interval. To disable sending hello messages, set the value to zero.
The no form of this command returns the RSVP interface to use the RSVP level configuration value.
The router supportsthe sending of separate ACK messages only but is capable of processing received message_ack objects piggy-backed to hop-by-hop RSVP messages, such as path and resv.
The router sets the ack_desired flag only in non refresh RSVP messages and in refresh messages which contain new state information.
A retransmission mechanism based on an exponential backoff timer is supported in order to handle unacknowledged message_id objects. The RSVP message with the same message_id is retransmitted every 2 * rapid-retransmit-time interval of time. The rapid-retransmit-time is referred to as the rapid retransmission interval as it must be smaller than the regular refresh interval configured in the config>router>rsvp>refresh-time context. There is also a maximum number of retransmissions of an unacknowledged RSVP message rapid-retry-limit. The node will stop retransmission of unacknowledged RSVP messages whenever the updated backoff interval exceeds the value of the regular refresh interval or the number of retransmissions reaches the value of the rapid-retry-limit parameter, whichever comes first. These two parameters are configurable globally on a system in the
config>router>rsvp context.
The no form of the command reverts to the default value.
This command enables reliable delivery of RSVP messages over the RSVP interface. When refresh-reduction is enabled on an interface and reliable-delivery is disabled, then the router will send a message_id and not set ACK desired in the RSVP messages over the interface. Thus 7750 does not expect an ACK and but will accept it if received. The node will also accept message ID and reply with an ACK when requested. In this case, if the neighbor set the “refresh-reduction-capable” bit in the flags field of the common RSVP header, the node will enter summary refresh for a specific message_id it sent regardless if it received an ACK or not to this message from the neighbor.
Finally, when ‘reliable-delivery’ option is enabled on any interface, RSVP message pacing is disabled on all RSVP interfaces of the system, for example, the user cannot enable the msg-pacing option in the config>router>rsvp context, and error message is returned in CLI. Conversely, when the msg-pacing option is enabled, the user cannot enable the reliable delivery option on any interface on this system. An error message will also generated in CLI after such an attempt.
The no form of the command reverts to the default value.
When the subscription is set to zero, no new sessions are permitted on this interface. If the
percentage is exceeded, the reservation is rejected and a log message is generated.
The no form of this command reverts the
percentage to the default value.
This command configures the specific threshold levels per node and per interface. Threshold levels are for reserved bandwidth per interface. The te-threshold-update command is used to enable or disable threshold-based IGP TE updates. Any reserved bandwidth change per interface is compared with all the threshold levels and trigger an IGP TE update if a defined threshold level is crossed in either direction (LSP setup or teardown). Threshold-based updates must be supported with both ISIS and OSPF. A minimum of one and a maximum of 16 threshold levels must be supported.
The no form of this command resets the default value.
This command configures the specific threshold levels per node and per interface. Threshold levels are for reserved bandwidth per interface. The te-threshold-update command is used to enable or disable threshold-based IGP TE updates. Any reserved bandwidth change per interface is compared with all the threshold levels and trigger an IGP TE update if a defined threshold level is crossed in either direction (LSP setup or teardown). Threshold-based updates is supported with both ISIS and OSPF. A minimum of one and a maximum of 16 threshold levels is supported.
The no form of this command resets the default value.
This command enables RSVP message pacing in which the specified number of RSVP messages, specified in the max-burst command, are sent in a configured interval, specified in the
period command. A count is kept of the messages that were dropped because the output queue for the interface used for message pacing was full.
