The administrative-group command specifies the inclusion or exclusion of links that are part of an administrative group. The administrative group IDs are global and the specification contains lists and ranges of admin groups to include or exclude.

Every chosen link for a dynamic path must be in all of the admin groups specified in the include all range or must be in one of the admin groups specified in the include any range. A chosen link must not be in the exclude range. The administrative group range is 0 to 511.

Administrative groups can be specified using a name as an alias mapped to a numerical value. The mapping can be configured under the global Traffic-Engineering (TE) mode. For more information, refer to the IS-IS Traffic-Engineering TOI.

Command Mode

Traffic Engineering RSVP Dynamic Path Configuration

Command Syntax

administrative-group [ include any <RANGE>] | [include all <RANGE>] | [exclude <RANGE>] with RANGE being: ( <0x0-0xFFFFFFFF> | <0-511> | <0-511>-<0-511> | WORD )

[no | default] administrative-group

Parameters

exclude - Excludes the specified administrative group identified by either a group name or number.

include all - Includes the specified administrative groups identified by either a group name or number.

include any - Includes any of the specified range of administrative groups identified by either a group name or number.

Example

switch(config-te-rsvp-path-dyn-MyPath)# administrative-group include all 1 include any 2-4 exclude 7,9

The alias endpoint command configures a tunnel endpoint alias for both IPv4 and IPv6 endpoints and allows the additional next-hops to resolve using the existing tunnel. A maximum of 15 alias endpoints per tunnel can be configured.

Command Mode

Traffic Engineering RSVP P2P Tunnel Configuration

Command Syntax

alias endpoint ( ipv4_address | ipv6_address)

[no|default] alias endpoint

Example

switch(config-te-rsvp-tunnel-MyTunnel)# alias endpoint 192.168.11.5

The command authentication index index_num active configures the MPLS RSVP cryptographic authentication password used globally for signing outgoing messages to neighbors that do not have per-neighbor authentication configuration. The active password must also be configured with the authentication index index_num password command to have any effect. Note that per-neighbor authentication takes precedence over global authentication.

Command Mode

MPLS RSVP Configuration

Command Syntax

[ no | default ] authentication index <INDEX_NUM> active

Example

switch(config)# mpls rsvp
switch(config-mpls-rsvp)# authentication type md5
switch(config-mpls-rsvp)# authentication index 755 password s3cr3t
switch(config-mpls-rsvp)# authentication index 755 active

The command authentication index index_num password is used to create the password with a given index. This can be done with different indices to create multiple passwords. All configured passwords are used to authenticate incoming messages from neighbors that do not have per-neighbor authentication configuration.

The no authentication sequence-number window and default authentication sequence-number window commands reset the size of the window to 5.

Command Mode

MPLS RSVP Configuration

Command Syntax

authentication sequence-number window size_num

no authentication sequence-number window

default authentication sequence-number window

Parameter

size_num - Sequence-number window size. Values range from 1-255. The default value is 5. A value of 1 disables packet reordering.

Example

switch(config)# mpls rsvp
switch(config-mpls-rsvp)# authentication sequence-number window 50

The authentication type command configures the MPLS RSVP cryptographic authentication type globally. Setting the type to md5 enables cryptographic authentication (RFC 2747) for MPLS RSVP messages sent from the switch. Setting the type to none disables authentication globally. Note that per-neighbor authentication settings take precedence over global settings.

The no authentication type and default authentication type commands disable authentication. Cryptographic authentication is disabled by default. These commands are functionally the same as authentication type none.

Command Mode

MPLS RSVP Configuration

Command Syntax

authentication type (md5 | none)

no authentication type (md5 | none)

default authentication type (md5 | none)

The bandwidth command configures the reserve bandwidth within the tunnel. The bandwidth can be set explicitly by setting a bandwidth value and the unit. When a bandwidth value of 0 is entered no bandwidth reservation is signalled. An alternative to explicit bandwidth configuration is to use the autobandwidth feature which specifies the minimum and maximum bandwidth to be used for the tunnel and otherwise adjusts bandwidth based on the observed traffic going over the tunnel.

Command Mode

Traffic Engineering RSVP P2P Tunnel Configuration

Traffic Engineering RSVP P2P Tunnel Profile Configuration

Command Syntax

bandwidth 0-1000 (bps | kbps | mbps | gbps | tbps)

bandwidth auto min 0-1000 ( bps | kbps | mbps | gbps | tbps ) max 0-1000 ( bps | kbps | mbps | gbps | tbps ) [ adjustment-period <1-4294967295> ] [ sensitivity ( <1-10> | dynamic ) ]

no bandwidth

default bandwidth

The bandwidth signaling command is used to enable bandwidth signaling (default behaviour) for the tunnel in cases where the LSP is used for UCMP weights and reserves bandwidth.

The bandwidth signaling disabled command is used to disable bandwidth signaling for the tunnel in cases where the LSP is used for UCMP weights but does not actually reserve bandwidth.

Command Mode

Traffic Engineering RSVP P2P Tunnel Configuration

Traffic Engineering RSVP P2P Tunnel Profile Configuration

Command Syntax

bandwidth signaling [ disabled ]

no bandwidth signaling

default bandwidth signaling

Parameters

disabled - Disables bandwidth signaling.

Examples

The following example enables bandwidth signaling for MyTunnel, if it was disabled:

switch(config-te-rsvp-tunnel-MyTunnel)# bandwidth signaling

The following example disables bandwidth signaling for MyTunnel:

switch(config-te-rsvp-tunnel-MyTunnel)# bandwidth signaling disabled

The clear mpls rsvp counters command clears RSVP message counters. The clear mpls rsvp counters ( ip | ipv6 ) access-list command clears the ACL counters.

Command Mode

PrivilegedEXEC

Command Syntax

clear mpls rsvp counters

clear mpls rsvp counters ( ip | ipv6 ) access-list

Example

switch# clear mpls rsvp counters 

switch# clear mpls rsvp counters ip access-list 

switch# clear mpls rsvp counters ipv6 access-list 

The clear mpls rsvp session command can be used to clear RSVP sessions. Clearing a session will remove the current state for the LSPs and send the appropriate TEAR messages. This can be useful for cleaning up stale sessions, renegotiating a session immediately after a config change, or forcing a recreation of an LSP that could be in an error state.

Command Mode

Privileged EXEC

Command Syntax

clear mpls rsvp session ( <filters> | all ) [ detail ]

Parameters

all - Clears all RSVP sessions.

<filters> -a list of one or more of: ( destination <ipv4> | id <id> ) | ( name <name> |lsp <lsp> |bypass ) | ( role <role> ) | ( state <state> )

• bypass - Filter for bypass LSPs. Only applicable on the ingress node.
• destination - Filter by destination address.
• id - Filter by Session ID.
• lsp- Filter by LSP number.
• name - Filter by session name.
• role - Filter by session role.
• state - Filter by LSP state.

detail - Can be specified after all or any filters. When the command is run with detail, the names of the sessions that are cleared are displayed, not just the count.

Examples

The color command assigns a color to a tunnel to publish the tunnel to the system-colored-tunnel-rib, to help steer traffic into the tunnel.

Command Mode

Traffic Engineering RSVP P2P Tunnel Configuration

Traffic Engineering RSVP P2P Tunnel Profile Configuration

Command Syntax

color ( <color value> | disabled )

[no | default] color

color disabled - explicitly disables the color configuration irrespective of a profile being configured

Example

switch(config-te-rsvp-tunnel-MyTunnel)# color 60

RSVP-TE uses CSPF to compute the FRR backup path. CSPF can be throttled to avoid frequent path changes when frequent network events occur. The cspf delay command configures the frequency of CSPF running after a network event by specifying the initial wait interval, back-off interval, and maximum wait interval for CSPF. The no form of the command removes the CSPF delay. The default cspf delay values are 100 for initial wait interval, 200 for back-off interval, and 1000 for maximum wait interval.

Command Mode

Traffic Engineering Configuration

Command Syntax

cspf delay [initial n back-off n] max n

no cspf delay

default cspf delay

Example

switch(config-te)#cspf delay initial 200 back-off 400 max 2000

The cspf ecmp tie-break command disables bandwidth least-fill when the random option is selected, and enables bandwidth least-fill when least-fill is selected. Bandwidth least-fill is enabled by default.

The no and default forms of the command restore bandwidth least-fill.

Command Mode

Traffic Engineering RSVP Configuration

Command Syntax

cspf ecmp tie-break (least-fill|random)

no cspf ecmp tie-break

default cspf ecmp tie-break

Example

switch(config-te-rsvp)# cspf ecmp tie-break random

Each P2P tunnel requires a destination IP to function. The destination ip command assigns a destination IP to the tunnel. For P2MP, this can be set multiple times, one for each of the multicast destinations.

Command Mode

Traffic Engineering RSVP P2P Tunnel Configuration

Traffic Engineering RSVP P2MP Tunnel Configuration

Command Syntax

destination ip IP_address

no destination ip

default destination ip

Parameters

IP_address - The destination IPv4 address for the tunnel.

Example

switch(config-te-rsvp-tunnel-MyTunnel)# destination ip 10.2.2.2

The disabled command in the MPLS RSVP P2MP mode can be used to disable P2MP functionality without clearing the configuration in the mode.

Command Mode

MPLS RSVP P2MP Configuration

Command Syntax

disabled

no disabled

default disabled

Example

The following command disables P2MP functionality for RSVP-TE but retains the configuration currently in the MPLS RSVP P2MP mode:

switch(config-mpls-rsvp-p2mp)# disabled 

The fast-reroute bypass tunnel optimization interval command configures the interval at which paths used for bypass tunnels are re-optimized. Paths are re-optimized every 30 seconds by default.

The no fast-reroute bypass tunnel optimization interval and default fast-reroute bypass tunnel optimization interval commands return the optimization interval to the default value of 30 seconds.

Command Mode

MPLS RSVP Configuration

Command Syntax

fast-reroute bypass tunnel optimization interval < number of seconds > seconds

no fast-reroute bypass tunnel optimization interval

default fast-reroute bypass tunnel optimization interval

Parameters

seconds - The time between re-optimizations of bypass tunnel paths in seconds. The values range from 1 to 65535. The default is 30 seconds.

Example

switch(config-mpls-rsvp)# fast-reroute bypass tunnel optimization interval 45 seconds 

The fast-reroute mode command configures fast-reroute (FRR) (RFC 4090). The link-protection option protects against failure of the next link, the node-protection option protects against failure of the next node, and the none option disables the feature. Fast reroute is disabled by default.

On the headend, this knob acts as the global configuration which determines the type of protection requested by any LSPs originating there. This is superseded if the tunnels have a fast-reroute mode specified in the tunnel configuration (see fast-reroute mode (RSVP tunnel)) or in an associated profile.

On transit and headend, it also determines which type of bypass tunnels will be created at that node.

If node-protection is configured and requested by the LSP, then both node and link protection bypass tunnels will be created, with the node bypass being preferred if it's available.

If link-protection is configured or requested by the LSP, then only link-protection bypasses are created and used.

If the FRR mode is set to none or not requested at all by the LSP, then no bypass tunnels are created.

The no and default versions of the command disable fast reroute.

Command Mode

MPLS RSVP Configuration

Command Syntax

fast-reroute mode (link-protection | node-protection | none)

no fast-reroute mode

default fast-reroute mode

By default, RSVP tunnels inherit fast-reroute settings from the global RSVP configuration. The fast-reroute mode can also be configured for a specific RSVP tunnel by issuing the command in Traffic Engineering RSVP Tunnel configuration mode. Note that this only modifies the type of protection requested by the tunnel. If the requested protection is not enabled by the global RSVP configuration, it may not be provided to the tunnel.

The link-protection option protects against failure of the next link, the node-protection option protects against failure of the next node, and the none option disables the feature.

The default is no fast-reroute mode whichmeans that the inherit fast-reroute settings from the global RSVP configuration.

Command Mode

Traffic Engineering RSVP P2P Tunnel Configuration

Traffic Engineering RSVP P2P Tunnel Profile Configuration

Command Syntax

fast-reroute mode (link-protection | node-protection | none)

no fast-reroute mode

default fast-reroute mode

You can change the revertive behavior of the FRR from the global revertive mode to the local revertive mode. In the global revertive mode, an LSP re-routed over a bypass tunnel because the downstream link became unavailable keeps using the bypass tunnel after the link recovers. This expects the headend router to set up a new LSP upon notification that a link became unavailable. In the local revertive mode, the LSP switches back to using the primary link after recovery.

The default for reversion is global.

Command Mode

MPLS RSVP Configuration

Command syntax

fast-reroute reversion (global | local)

default fast-reroute reversion

no fast-reroute reversion

The graceful-restart role helper command leads to the MPLS RSVP Graceful Restart Helper Configuration Mode. Under this mode we have the timer restart maximum and timer recovery maximum commands. These are used to set the maximum values accepted by helpers. If the helper receives larger values from the speaker, then it will use the configured maximum.

The maximum accepted restart time value is configurable under the graceful-restart role helper configuration mode, timer restart maximum time seconds.

The maximum accepted recovery time value is configurable under the graceful-restart role helper configuration mode, timer recovery maximum time seconds.

Command Mode

MPLS RSVP Configuration

Command Syntax

graceful-restart role helper

no graceful-restart role helper

default graceful-restart role helper

timer restart maximum time seconds - The maximum accepted restart time value.

default timer restart maximum

no timer restart maximum

timer recovery maximum time seconds - The maximum accepted recovery time value.

default timer recovery maximum

no timer recovery maximum

Example

switch(config-mpls-rsvp)#graceful-restart role helper
switch(config-mpls-rsvp-gr-helper)#

The graceful-restart role speaker command leads to the MPLS RSVP Graceful Restart Speaker Configuration Mode. Under this mode we have the timer restart and timer recover commands. These are used to set the time values sent to helpers to advertise how long the speaker will remain in the restart and recovery phases.

The restart time value is configurable under the graceful-restart role speaker configuration mode, timer restart time seconds

The recovery time value is configurable under the graceful-restart role speaker configuration mode, timer recovery time seconds.

Command Mode

MPLS RSVP Configuration Mode

Command Syntax

graceful-restart role speaker

no graceful-restart role speaker

default graceful-restart role speaker

timer restart time seconds - The restart time value.

default timer restart

no timer restart

timer recovery time seconds- The recovery time value.

default timer recovery

no timer recovery

Example

switch(config-mpls-rsvp)#graceful-restart role speaker
switch(config-mpls-rsvp-gr-speaker)#

The hardware next-hop fast-failover command enables hardware-accelerated next-hop failover on the switch. This should be enabled in every case where FRR is desired, especially for sub-50ms in the case of link protection and sub-150ms in the case of node protection.

It is disabled by default. Bypass tunnels can still be created even without this knob and FRR will still work on the software side, but on the hardware this is necessary for fast convergence.

The no and default forms of the command disable hardware-accelerated next-hop failover and fast-reroute bypass tunnels.

Command Mode

Router General Configuration

Command Syntax

hardware next-hop fast-failover

no hardware next-hop fast-failover

default hardware next-hop fast-failover

Example

switch(config)#router general
switch(config-router-general)#hardware next-hop fast-failover

The hello interval command sets the time between the hello packets. The no form of the command explicitly disables the Hello messages, while the default form of the command resets to the default setting of 10 seconds with a multiplier of 4.

Command Mode

MPLS RSVP Configuration

Command Syntax

hello interval <interval> multiplier <num>

no hello interval

default hello interval

The hitless-restart command enables RSVP hitless restart. Hitless restart allows RSVP agents to restart without interrupting data-plane traffic. When hitless restart is enabled, the switch observes a recovery period after RSVP restarts. The switch preserves existing installed RSVP states until they are refreshed by neighbors. If RSVP states have not been refreshed before the expiration of the recovery period, they are cleared. The recovery period is 90 seconds by default when hitless restart is enabled, but can be configured using the timer recovery command. Hitless restart is disabled by default.

The no hitless-restart and default hitless-restart commands disable hitless restart.

The recovery time value timer recovery time seconds is configurable under the hitless-restart mode.

Command Mode

MPLS RSVP Configuration

Command Syntax

hitless-restart

no hitless-restart

default hitless-restart

Example

switch(config-mpls-rsvp)# hitless-restart
switch (config-mpls-rsvp-hr)#

The hop command adds a hop to the path in the dynamic path configuration mode. If entered without options, it is configured as a strict include hop and appended at the end of the path. A strict include hop must be directly reachable after the previously specified hop in the path (or from the ingress if it is the first hop). The loose keyword configures the hop as a loose include hop, which does not have to be directly reachable from the previous hop. The before and after options can be used to reorder include hop constraints in relation to another include hop in an existing path.

The exclude keyword configures an exclude hop constraint which indicates that neither end of a link in the path may have the specified address. Unlike strict and loose hops, exclude hops cannot be reordered with before and after keywords.

The no and default forms of the command remove the specified hop constraint.

Command Mode

Traffic Engineering RSVP Dynamic Path Configuration

Command Syntax

hop IPv4_address [ exclude | ( [ loose ] [ ( before | after ) IPv4_address ] ) ]

default hop [IPv4_address] - The address is optional, if no address is supplied then all hops are removed.

no hop [IPv4_address] - The address is optional, if no address is supplied then all hops are removed.

The hop command adds a hop to the path in the explicit path configuration mode. If entered without options, the command places the specified hop at the end of the path. The before and after options can be used to insert the specified hop in relation to another existing hop in the existing path.

Command Mode

Traffic Engineering RSVP Explicit Path Configuration

Command Syntax

hop IPv4_address [ ( before | after ) ] IPv4_address

[no | default] hop [IPv4_address] - If no address is supplied then all hops are removed.

The igp shortcut command is used to specify whether an RSVP tunnel should participate in Interior Gateway Protocol (IGP) shortcuts.

Command Mode

Traffic Engineering RSVP P2P Tunnel Configuration

Traffic Engineering RSVP P2P Tunnel Profile Configuration

Command Syntax

igp shortcut [ disabled ]

default igp shortcut

no igp shortcut

Parameters

disabled - explicitly disables the IGP shortcut configuration irrespective of profile configuration.

Example

switch(config-te-rsvp-tunnel-MyTunnel)# igp shortcut

The ip access-group command can be used to apply IPv4 access-lists to RSVP. Access-lists can be configured with the ​​ip access-list command.

Command Mode

MPLS RSVP Configuration

Command Syntax

ip access-group ACL_NAME

no ip access-group ACL_NAME

default ip access-group ACL_NAME

Parameters

ACL_NAME - Access list name.

Example

switch#(config-mpls-rsvp)#ip access-group MyACL

The ipv6 access-group command can be used to apply IPv6 access-lists to RSVP. Access-lists can be configured with the ​ipv6 access-list command.

Command Mode

MPLS RSVP Configuration

Command Syntax

ipv6 access-group ACL_NAME

no ipv6 access-group ACL_NAME

default ipv6 access-group ACL_NAME

Parameters

ACL_NAME - Access list name.

Example

switch#(config-mpls-rsvp)#ipv6 access-group MyACL

The label local-termination commandcan be used to configure the termination mode advertised by an egress node. Using the explicit-null option will enable the egress node to advertise an IPv4 explicit-null label (Label 0) to its upstream router.

The no label local-termination or default label local-termination or label local-termination implicit-null commands can be used to return the switch to the default state of advertising implicit-null labels (Label 3).

Command Mode

MPLS RSVP Configuration

Command Syntax

label local-termination (explicit-null | implicit-null)

no label local-termination

default label local-termination

Example

switch(config-mpls-rsvp)# label local-termination explicit-null

The leaf command can be used in explicit tree specifications to configure the path to leaves in the tree. Leaves are specified by their destination IP address. Hops in the leaf’s path can be configured with the hop command and can either be interface or node hops (the latter being configured with the node keyword).

Command Mode

Traffic Engineering RSVP Explicit Tree Configuration

Command Syntax

leaf IP_ADDR

no leaf IP_ADDR

default leaf IP_ADDR

Parameters

IP_ADDR - Destination IP address of the leaf in the tree.

Example

switch(config-te-rsvp-tree-expl-myTree)#leaf 4.4.4.4
switch(config-te-rsvp-tree-expl-myTree-leaf-4.4.4.4)#

The local-interface command specifies a local interface from which to derive the source IP address for RSVP-TE tunnels.

Command Mode

Traffic Engineering RSVP Configuration

Command Syntax

local-interface

no local-interface

default local-interface

Example

switch(config-te-rsvp)# local-interface Loopback0

The lsp no-path preservation timer command in the Traffic-Engineering RSVP Configuration Mode configures a timer to control how long the switch maintains an original Label Switched Path (LSP) if a Make-Before-Break (MBB) attempt fails due to CSPF finding no replacement path for it.

The [no | default] versions of the command restores the default preservation timer of 0 seconds, meaning an LSP will be taken down immediately if no new path is found.

Command Mode

Traffic-Engineering RSVP Configuration

Command Syntax

lsp no-path preservation timer ( PRESERVATION_TIME seconds| infinite )

[ no | default ]lsp no-path preservation timer

Parameters

seconds seconds - Specify the time in seconds, 0 - 3600, to preserve an existing LSP after an MBB failure if no replacement path is found.

infinite - An existing LSP will be preserved indefinitely even if no replacement path is found.

Example

 switch(config-te-rsvp)# lsp no-path preservation timer 300 seconds

The lsp self-ping command enables LSP self-ping (RFC 7746). When enabled, all new LSPs created by RSVP-TE LER tunnels will perform self-ping. LSP self-ping verifies end-to-end establishment of the LSP by sending a self-ping message through the LSP before sending regular traffic. When LSP self-ping is enabled, an LSP created by an RSVP-TE tunnel will only be considered up and ready to carry traffic when a self-ping message successfully returns to the head end. LSP self-ping is disabled by default.

The no and default forms of the command disable LSP self-ping.

Command Mode

Traffic Engineering RSVP Configuration

Command Syntax

lsp self-ping

default lsp self-ping

no lsp self-ping

Example

switch(config-te-rsvp)# lsp self-ping

The metric command configures a per RSVP tunnel metric to allow specific tunnels to an endpoint to take precedence over other tunnels to the same endpoint when forming ECMP. The tunnel metric is published to the tunnel RIB for BGP cost calculations.

The tunnel metric can alsobe set to dynamically track the IGP SPF metric for the tunnel destination IP regardless of the changes in the Constrain-based Shortest Path First (CSPF) path to the destination. This can be done with the igp keyword.

Command Mode

Traffic Engineering RSVP P2P Tunnel Configuration

Traffic Engineering RSVP P2P Tunnel Profile Configuration

Command Syntax

metric ( igp | metric_value)

[no | default] metric

The mpls rsvp command places the switch in the MPLS RSVP configuration mode.

Command Mode

Global Configuration

Command Syntax

mpls rsvp

[no | default] mpls rsvp - Will wipe the configuration in the mode and disable RSVP.

Example

switch(config)# mpls rsvp

The mtu signaling command configures RSVP to enable MTU discovery. MTU signaling is disabled by default. The MTU is discovered with the AdSpec object in the Path message, which contains the minimum MTU seen in the path so-far, and is then reported back in the Resv message. If the config knob is not set on a transit node, then the MTU in the AdSpec is not updated on the node (essentially ignoring the node for MTU discovery). If it is not set on the ingress node, then MTU discovery is not done for any LSPs originating at that node.

The no and default forms of the command disable MTU signaling.

Command Mode

MPLS RSVP Configuration

Command Syntax

mtu signaling

no mtu signaling

default mtu signaling

Example

switch(config-mpls-rsvp)# mtu signaling

The neighbor authentication index active command configures the MPLS RSVP cryptographic authentication password used for incoming and outgoing messages to and from the specified neighbor. Per-neighbor authentication takes precedence over global authentication. The per-neighbor authentication password must also be configured globally with the authentication index password command.

The no and default versions of the command remove neighbor-specific authentication password configuration; the neighbor then inherits the global configuration.

Command Mode

MPLS RSVP Configuration

Command Syntax

neighbor neighbor_address authentication index index_num active

no neighbor neighbor_address authentication index index_num active

default neighbor neighbor_address authentication index index_num active

Example

switch(config-mpls-rsvp)# neighbor 172.16.0.0 authentication type md5
switch(config-mpls-rsvp)# neighbor 172.16.0.0 authentication index 755 active

The neighbor authentication type command configures the MPLS RSVP cryptographic authentication type for the specified neighbor. Setting the type to md5 enables cryptographic authentication (RFC 2747) for MPLS RSVP messages sent to the specified neighbor. Setting the type to none disables authentication for the neighbor. Note that per-neighbor authentication takes precedence over global authentication.

The no and default versions of the command remove neighbor-specific authentication type configuration; the neighbor then inherits the global configuration.

Command Mode

MPLS RSVP Configuration

Command Syntax

neighbor neighbor_address authentication type (md5 | none)

no neighbor neighbor_address authentication type

default neighbor neighbor_address authentication type

Periodic tunnel optimization can be configured globally or individually for a specific tunnel using the optimization interval command. This configuration is applied to all RSVP tunnels.

The optimization interval can also be configured on an individual tunnel by entering the command in the tunnel mode. The optimization interval configured in the tunnel mode overrides the optimization interval configured globally.

Optimization can also be disabled on a specific tunnel or globally, which is the default.

Command Mode

Traffic Engineering RSVP P2P Configuration

Traffic Engineering RSVP P2P Tunnel Configuration

Command Syntax

optimization interval numerical value seconds

default optimization

no optimization

Parameters

numerical value - enter the optimization interval in seconds.

disabled - explicitly disables periodic optimization irrespective of global or profile configuration. Not available for the global optimization interval.

From the config-mpls-rsvp configuration mode, the p2mp command places the switch in config-mpls-rsvp-p2mp configuration mode.

Command Mode

MPLS RSVP Configuration

Command Syntax

p2mp - Enters the mode and enables RSVP P2MP.

default p2mp - Will wipe the configuration in the mode and disable RSVP P2MP.

no p2mp- Will wipe the configuration in the mode and disable RSVP P2MP.

Examples

• RSVP P2MP signaling functionality is enabled using the p2mp command , which also enters the config-mpls-rsvp-p2mp mode.

  switch(config-mpls-rsvp)# p2mp
  switch(config-mpls-rsvp-p2mp)#

• P2MP functionality is disabled by issuing the disabled command in the p2mp mode. This allows disabling RSVP P2MP without wiping any active configuration in the p2mp mode.

  switch(config-mpls-rsvp-p2mp)# disabled

• The no p2mp will remove all configuration in the mode and also disable RSVP P2MP.

  switch(config-mpls-rsvp)# no p2mp

• The exit command will leave the mode but will retain the configuration in it.

  switch(config-mpls-rsvp-p2mp)# exit
  switch(config-mpls-rsvp)#

The path command in Traffic Engineering RSVP configuration mode creates path specifications and enters the configuration mode for the path. These path specifications define the constraints for paths used by RSVP tunnels. If the path does not already exist, the path command creates it. Path configuration modes are group-change modes: changes take effect only when exiting the mode. To exit the mode without saving changes, use the abort command.

The no path and default path commands delete the specified path.

Command Mode

Traffic Engineering RSVP Configuration

Command Syntax

path path_name (dynamic | explicit)

no path path_name

default path path_name

Example

switch(config-te-rsvp)#path spec1 explicit
switch(config-te-rsvp-path-expl-spec1)# 

switch(config-te-rsvp)#path spec2 dynamic  
switch(config-te-rsvp-path-dyn-spec2)#

The path command in the Traffic Engineering RSVP P2P Tunnel configuration mode specifies a primary or secondary path along which the LSPs are established for the tunnel.

The no and default forms of the command remove the specified path from the tunnel configuration.

Command Mode

Traffic Engineering RSVP P2P Tunnel Configuration

Command Syntax

path path_name (secondary pre-signaled)

no path path_name (secondary)

default path path_name(secondary)

Parameters

• pathspec_name - Specification name for the path to use for this tunnel.

• secondary - Use the path specification to create a secondary path.

• pre-signaled - Indicates the secondary path should be pre-signaled. The default behaviour without this is to only signal a secondary path when the primary path is down or encounters an error.

The ping mpls rsvp session command allows the user to check if the remote endpoint of an RSVP session is reachable through the LSP. Running ping on an RSVP LSP creates an LSP Ping Request packet with the label programmed by RSVP and that packet will follow the MPLS path until it reaches the end of the tunnel. If the node that receives this Request is the intended destination, it replies with an RSVP Ping Reply through normal IP routing. When the source receives the Reply it indicates that there are no apparent data plane failures and that the endpoint of that LSP is reachable.

Command Mode

Privileged EXEC

Command Syntax

ping mpls rsvp session ( ( id SESSION_ID [ lsp LSP ] ) | ( name SESSION_NAME ) ) [ ( { ( source SRC_IP ) | ( standard STANDARD ) | ( traffic-class TRAFFIC_CLASS ) | ( tos ( TOS_VAL | ( dscp ( DSCP | DSCP_ACL ) ) ) ) | pad-reply | ( size SIZE ) | ( repeat REPEAT ) | ( interval INTERVAL ) } ) ]

Parameters

The preemption method command can be used to set the desired preemption method on a node. Soft preemption enables deferred failure of RSVP-TE LSPs on link oversubscription. When an LSP loses its bandwidth reservation, the LSP is torn down only after a delay in order to give a chance for the headend to replace it. The delay is configurable with the timer parameter. Hard preemption will result in the LSP being torn down immediately once the preemption algorithm chooses to preempt it.

This configuration is also used on the headend to determine the desired preemption methods for LSPs originating there.

The default preemption method is soft preemption with a timer value of 30 seconds.

Command Mode

MPLS RSVP Configuration

Command Syntax

preemption method (hard | soft ) [timer <seconds>]

no preemption method

default preemption method

The priority command configures the tunnel priority. The setup keyword is used to set the setup priority of the tunnel; the priority used when the tunnel’s LSPs are being established.The hold keyword sets the hold priority of the tunnel; the priority used when the tunnel’s LSPs are up. The priority value range is 0 (highest priority) to 7 (lowest priority).

The hold priority should be a higher priority (lower value) than the setup priority to avoid cycles where an LSP is continuously established and immediately preempted.

Command Mode

Traffic Engineering RSVP P2P Tunnel Configuration

Traffic Engineering RSVP P2P Tunnel Profile Configuration

Command Syntax

priority setup SETUP_PRIORITY hold HOLD_PRIORITY

no priority

default priority

Example

switch(config-te-rsvp-tunnel-myTunnel)# priority setup 5 hold 3

The profile command associates a specified tunnel profile with the tunnel specification. The tunnel will inherit configuration from the tunnel profile. If a config command is configured in both the tunnel specification and the tunnel profile with differing parameters, then the configuration in the tunnel specification takes precedence.

Command Mode

Traffic Engineering RSVP P2P Tunnel Configuration

Traffic Engineering RSVP P2MP Tunnel Configuration

Command Syntax

profile PROFILE_NAME

no profile

default profile

Parameters

PROFILE_NAME - name of the tunnel profile.

Example

switch(config-te-rsvp-tunnel-MyTunnel)# profile MyProfile

The refresh interval command configures the interval at which RSVP Path and Resv or Srefresh messages are sent to refresh the state. Refresh messages are sent at a randomly selected interval between 0.5 and 1.5 times the configured value. The default value is 30 seconds.

The no and default versions of the command reset the refresh interval to 30 seconds.

Command Mode

MPLS RSVP Configuration

Command Syntax

refresh interval seconds

no refresh interval

default refresh interval

Parameters

seconds - Refresh interval in seconds. The actual refresh interval is randomly generated in the range of 0.5 to 1.5 times this value for each refresh message. Values range from 1 to 65535. The default value is 30 seconds.

Example

switch(config-mpls-rsvp)#refresh interval 100

Using the refresh method command with the bundled keyword enables the Refresh Overhead Reduction which supports refreshing the state for several LSPs in a single message using message IDs bundled in Srefresh messages. The explicit keyword disables Refresh Overhead Reduction, meaning that each LSP refreshes its state individually with Path and Resv messages.

Command Mode

MPLS RSVP Configuration

Command Syntax

refresh method (bundled | explicit)]

no refresh method

default refresh method

RSVP-TE tunnels can be optimized on-demand by using the refresh rsvp tunnel optimization command. This can be used to optimize a specific tunnel by name or all tunnels.

Command Mode

Privileged Exec

Command Syntax

refresh rsvp tunnel optimization (all | ( name tunnel_name [avoid ecmp hop ecmp_hops] ))

The rsvp command places the switch in Traffic Engineering RSVP configuration mode.

Command Mode

Traffic Engineering Configuration

Command Syntax

rsvp

default rsvp- Will wipe the configuration in the mode.

no rsvp - Will wipe the configuration in the mode.

Example

switch(config)#router traffic-engineering
switch(config-te)#rsvp
switch(config-te-rsvp)#

The rsvp bypass administrative-group command specifies administrative groups that must be included in, or excluded from, path specification for bypass tunnels. The restrictions specified for an interface apply to all bypass tunnels that bypass that interface. This includes both link and node protection. A single command can incorporate ranges for include any, include all, and exclude administrative groups.

The no rsvp bypass administrative-group and default rsvp bypass administrative-group commands remove bypass restrictions for the interface.

Command Mode

Interface Configuration

Command Syntax

rsvp bypass administrative-group [ include any <RANGE>] | [include all <RANGE>] | [exclude <RANGE>] with <RANGE> being: ( <0x0-0xFFFFFFFF> | <0-511> | <0-511>-<0-511> | WORD )

no rsvp bypass administrative-group

default rsvp bypass administrative-group

Parameters

exclude - Excludes the specified administrative group identified by either a group name or number.

include all - Includes the specified administrative groups identified by either a group name or number.

include any - Includes any of the specifiedrange of administrative groups identified by either a group name or number.

Example

switch(config-if-Et1/1)#rsvp bypass administrative-group include all 5-16 include any 8-75 exclude 82,93,115-168,255

Use the show mpls rsvp command to display the overall RSVP-TE state on the device.

Command Mode

EXEC

Command Syntax

show mpls rsvp

Example

switch> show mpls rsvp   	 
Administrative state: enabled
Operational state: up
Refresh interval: 30 seconds
Refresh reduction: disabled
Hello messages: disabled
Fast Re-Route: disabled
   Mode: none
   Hierarchical FECs: enabled
   Bypass tunnel optimization interval: 30 seconds
Cryptographic authentication: disabled
SRLG mode: none
Soft preemption: enabled
   Preemption timer: 30 seconds
MTU signaling: disabled
Label type for local termination: implicit null
Hitless restart: disabled
Graceful restart: disabled
P2P
   Number of sessions: 6
      Ingress/Transit/Egress: 6/0/0
   Number of LSPs: 6
      Operational: 6
      Ingress/Transit/Egress: 6/0/0
      Currently using bypass tunnels: 0
P2MP
   Number of sessions: 0
   Number of LSPs: 0
      Operational: 0
      Ingress/Transit/Egress/Bud: 0/0/0/0
      Currently using bypass tunnels: 0
   Number of sub-LSPs: 0
      Operational: 0
      Ingress/Transit/Egress: 0/0/0
      Currently using bypass tunnels: 0
Number of bypass tunnels: 0
Number of neighbors: 1
Number of interfaces: 1

Use the show mpls rsvp bandwidth command to display the current RSVP-TE bandwidth reservations on the device per interface.

Command Mode

EXEC

Command Syntax

show mpls rsvp bandwidth [ summary ] [ INTF ]

Parameters

Example

switch> show mpls rsvp bandwidth  
Interface Priority Bandwidth
                        Mbps     %
--------- -------- --------- -----
Ethernet1        0     840.0  84.0
                 1       0.0   0.0
                 2       0.0   0.0
                 3       0.0   0.0
                 4       0.0   0.0
                 5       0.0   0.0
                 6       0.0   0.0
                 7       0.0   0.0
             Total     840.0  84.0

Ethernet2        0    1000.0 100.0
                 1       0.0   0.0
                 2       0.0   0.0
                 3       0.0   0.0
                 4       0.0   0.0
                 5       0.0   0.0
                 6       0.0   0.0
                 7       0.0   0.0
             Total    1000.0 100.0

switch> show mpls rsvp bandwidth summary 
Interface Reserved bandwidth Percentage used Total bandwidth
                        Mbps               %            Mbps
--------- ------------------ --------------- ---------------
Ethernet1              840.0            84.0          1000.0
Ethernet2             1000.0           100.0          1000.0

Use the show mpls rsvp counters command to display RSVP message counters, per interface, and counters for RSVP errors.

Command Mode

EXEC

Command Syntax

show mpls rsvp counters [ ipv4 | ipv6 ] [ interface INTF ]

Parameters

Example

The following example displays RSVP message counters for each interface and error counters.

switch> show mpls rsvp counters
Received Messages:

Interface  Path  PathTear  PathErr  Resv  ResvTear  ResvErr  Srefresh  Other  Errors  
---------  ----  --------  -------  ----  --------  -------  --------  -----  ------  
Ethernet1  5     0         0        0     0         0        8         51     1  	 
Ethernet2  0     0         0        14    0         0        0         0      0  	 

Sent Messages:

Interface  Path  PathTear  PathErr  Resv  ResvTear  ResvErr  Srefresh  Other  Errors  
---------  ----  --------  -------  ----  --------  -------  --------  -----  ------  
Ethernet1  0     0         0        4     0         0        9         49     0  	 
Ethernet2  13    0         0        0     0         0        0         4      0  	


Error counters during message processing:

Error             On receive  On send
-----             ----------  -------
Unknown neighbor           5        6

The show mpls rsvp ip access-list command shows information about the IPv4 access list used by RSVP-TE.

Command Mode

EXEC

Command Syntax

show mpls rsvp ip access-list [ACL_NAME] [summary]

Parameters

• ACL_NAME - Filter the output by access-list name.

• summary - Displays the output in a summarized format.

Example

switch> show mpls rsvp ip access-list
IP Access List myAcl [dynamic]
        10 permit ip any 0.0.0.0/0
Total rules configured: 1
        Configured on VRFs: default VRF

The show mpls rsvp ipv6 access-list command shows information about the IPv6 access list used by RSVP-TE.

Command Mode

EXEC

Command Syntax

show mpls rsvp ipv6 access-list [ACL_NAME] [summary]

Parameters

• ACL_NAME - Filter the output by access-list name.

• summary - Displays the output in a summarized format.

Example

switch> show mpls rsvp ipv6 access-list
IPV6 Access List myAcl
        10 deny ipv6 any any
Total rules configured: 1
        Configured on VRFs: default VRF

Use the show mpls rsvp neighbor command to display information about RSVP neighbors.

Command Mode

EXEC

Command Syntax

show mpls rsvp neighbor[[ipv4_address | ipv6_address] [ summary]

The show mpls rsvp session command displaysinformation about RSVP sessions.

Command Mode

EXEC

Command Syntax

show mpls rsvp session [ <filters> ] [detail | history| summary])

Parameter

The show traffic-engineering rsvp command displays the overall status of RSVP-TE tunnels on the device.

Command Mode

EXEC

Command Syntax

show traffic-engineering rsvp

Example

switch> show traffic-engineering rsvp
Local interface: Loopback0 (configured)
IP address: 1.1.1.1
Auto bandwidth: unsupported
Periodic optimization: disabled
LSP self-ping: disabled

P2P
   Number of tunnels: 6
      Operational: 6
   Secondary path enabled: 0
   Secondary path in use: 0
   Number of LSPs: 6
      Operational: 6

P2MP
   Number of tunnels: 0
      Operational: 0
   Number of LSPs: 0
      Operational: 0
   Number of sub-LSPs: 0
      Operational: 0

The show traffic-engineering rsvp tunnel command displays information about RSVP tunnels.

Command Mode

EXEC

Command Syntax

show traffic-engineering rsvp tunnel [ <filters> ] [ detail | history | lsp | ( [ sub-tunnel ] summary ) ]

Parameters

Example

switch> show traffic-engineering rsvp tunnel
switch> show traffic-engineering rsvp tunnel
Tunnel TestTunnel 
   Source address: 10.1.1.1
   Destination address: 10.4.4.4
   Color: 60, Metric: 0 
   State: up
   Bandwidth: 0.0 bps, mode explicit 
   LSPs: 2
   Active path: primary 
   Path changes: 1
   Primary path: Path2to4
      State: up, in use 
      Path (dynamic):
         10.0.12.2
         10.0.23.3
         10.0.34.4
   Secondary path: Path2to4detour 
      State: up
      Path (explicit): 
         10.0.16.6
         10.0.67.7
         10.0.37.3
         10.0.34.4

switch#show traffic-engineering rsvp tunnel detail 
Tunnel TestTunnel 
   Source address: 10.1.1.1
   Destination address: 10.4.4.4
   Config source: CLI
   Color: 60, Metric: 0 
   State: up
   Bandwidth: 0.0 bps, mode explicit
      Setup priority: 7
      Hold priority: 0
   MTU signaling: disabled
   Fast re-route mode: none
   Periodic optimization: disabled
   Tunnel index: 3
   LSPs: 2
   LSP IDs: 1, 2
   LDP tunneling: disabled
   IGP shortcut: disabled
   Active path: primary 
   Path changes: 1
   Primary path: Path2to4
      State: up, in use
      CSPF Path ID: 3 
      Path (dynamic):
         10.0.12.2
         10.0.23.3
         10.0.34.4
   Secondary path: Path2to4detour 
      State: up
      Path (explicit): 
         10.0.16.6
         10.0.67.7
         10.0.37.3
         10.0.34.4

switch> show traffic-engineering rsvp tunnel history 
Tunnel TestTunnel 
Wed 2026-09-30 20:48:01.433 Tunnel created
Wed 2026-09-30 20:48:01.447 CSPF query on primary path
Wed 2026-09-30 20:48:01.448 State change: down
Wed 2026-09-30 20:48:01.449 CSPF reply for primary path, path not found
Wed 2026-09-30 20:48:01.450 LSP ID 1 added
Wed 2026-09-30 20:48:01.450 LSP ID 1 error: Network error, No path found (local error)
Wed 2026-09-30 20:48:04.158 CSPF reply for primary path, path found
   Path:
      10.0.12.2
      10.0.25.5
      10.0.45.4
Wed 2026-09-30 20:48:04.163 LSP ID 1 removed
Wed 2026-09-30 20:48:04.163 LSP ID 2 added
Wed 2026-09-30 20:48:08.005 LSP ID 2 state change: up
Wed 2026-09-30 20:48:08.005 LSP ID 2 in use
Wed 2026-09-30 20:48:08.008 State change: up using primary path

switch> show traffic-engineering rsvp tunnel lsp 
Tunnel TestTunnel 
   Source address: 10.1.1.1
   Destination address: 10.4.4.4
   Color: 60, Metric: 0 
   State: up
   Bandwidth: 0.0 bps, mode explicit 
   LSPs: 2
   Active path: primary 
   LSP 1:
      Path specification: Path2to4, primary 
      CSPF Path ID: 10001
      Bandwidth: 0.0 bps
      State: up, in use
      Path (dynamic):
         10.0.12.2 
         10.0.23.3 
         10.0.34.4 
   LSP 2: 
      Path specification: Path2to4detour, secondary 
      Bandwidth: 0.0 bps 
      State: up 
      Path (explicit): 
         10.0.16.6 
         10.0.67.7 
         10.0.37.3 
         10.0.34.4

switch> show traffic-engineering rsvp tunnel summary 
P2P
Tunnel Name          Destination Color Index Active Path Reserved BW LSPs State
-------------------- ----------- ----- ----- ----------- ----------- ---- -----
TestTunnel           10.4.4.4        -     1 primary        0.00 bps    2 up

P2MP
Tunnel Name P2MP ID Index Reserved BW LSPs State Leaves
----------- ------- ----- ----------- ---- ----- ------

switch> show traffic-engineering rsvp tunnel sub-tunnel summary
Tunnel: TestTunnel
Sub Tunnel Session ID Index Active Path Reserved BW Sampled BW LSPs State
---------- ---------- ----- ----------- ----------- ---------- ---- -----
         1          0     1 primary       1.00 Gbps   0.00 bps    1 up
         2          1     2 primary       1.00 Gbps   0.00 bps    1 up

The shutdown command disables the RSVP-TE protocol instance. This command allows shutting down RSVP, but retaining the configuration in the MPLS RSVP config mode, as opposed to no mpls rsvp, which would disable RSVP but also wipe the config.

RSVP-TE is enabled globally by issuing the no shutdown command in the configuration sub-mode. RSVP also needs MPLS to be enabled globally.

There is no per-interface knob to enable or disable RSVP. However, RSVP will not work on interfaces on which MPLS has been disabled.

Command Mode

MPLS RSVP Configuration

Command Syntax

shutdown

no shutdown

A tunnel is not enabled by default, it must be explicitly enabled using the no shutdown command.

The shutdown command can be used to disable a tunnel while preserving its config, as opposed to the no tunnel command which would disable the tunnel but also wipe the config.

Command Mode

Traffic Engineering RSVP P2P Tunnel Configuration

Traffic Engineering RSVP P2MP Tunnel Configuration

Command Syntax

shutdown

no shutdown

The split-tunnel command enables and configures RSVP sub-tunnels. Using the quantum keyword enables fixed-bandwidth sub-tunnels. Specifying a bandwidth minimum and maximum enables adaptive sub-tunnels which grow or shrink in response to changes in bandwidth.

The no split-tunnel and default split-tunnel commands disable split tunnels for the tunnel.

Command Mode

Traffic Engineering RSVP P2P Tunnel Configuration

Traffic Engineering RSVP P2P Tunnel Profile Configuration

Command Syntax

split-tunnel ( ( quantum bandwidth_num units [ sub-tunnels { ( minimum min_tunnels ) | ( limit max_tunnels ) | ( initial initial_tunnels ) } ] ) | ( min bandwidth_num units max bandwidth_num units [ sub-tunnels { ( minimum min_tunnels ) | ( limit max_tunnels ) | ( initial initial_tunnels ) } ] [ reduction-delay time time_units ] ) | disabled )

no split-tunnel

default split-tunnel

The srlg command specifies if link SRLGs of a primary LSP are to be considered as constraints while creating a fast-reroute bypass tunnel. This applies to both link and node protection. When the srlg command is entered with the strict option, then when a path for a bypass tunnel excluding SRLGs of the next-hop interface of the primary LSP can not be found, RSVP does not set up the bypass tunnel. When the srlg command is entered without the strict option, then a bypass tunnel is set up with as many links as possible that exclude the SRLGs of the next-hop interface of the primary LSP. Where such links are not available, links with the fewest excluded SRLGs are used.

The no srlg and default srlg commands restore the default state by turning off SRLG processing.

Command Mode

MPLS RSVP Configuration

Command Syntax

srlg [strict]

no srlg

default srlg

Parameters

strict - Applies strict SRLG constraints.

The sub-group limit command configures the maximum number of sub-LSPs per sub-group that will be signaled for P2MP LSPs originating on the node. A higher number reduces the control plane traffic overhead for establishing new P2MP LSPs, since more sub-LSPs can be signaled per Path and Resv message. This results in larger packet sizes so the number may have to be reduced depending on the configured MTU. The default is a maximum of 20 sub-LSPs per sub-group.

Configuring the sub-group limit to 1 may be necessary for interoperability with some routers that only support a single sub-LSP per sub-group.

Command Mode

MPLS RSVP P2MP Configuration

Command Syntax

sub-group limit SIZE sub-lsps

no sub-group limit

default sub-group limit

Parameters

SIZE - The maximum number of sub-LSPs per sub-groups that will be signaled for P2MP LSPs originating on this device. The range is 1 to 1000.

Example

switch(config-mpls-rsvp-p2mp)# sub-group limit 1 sub-lsps

The timer recovery command configuration determines how long the existing RSVP state persists during the recovery phase, after which any state which has not been refreshed by the neighbors is cleared.

The no timer recovery and default timer recovery commands restore the maximum recovery timer value to its default. The default is 90 seconds.

Command Mode

• MPLS RSVP Graceful Restart Speaker Configuration
• MPLS RSVP Hitless Restart Configuration

Command Syntax

timer recovery RECOVERY seconds

no timer recovery

default timer recovery

Example

switch(config-mpls-rsvp-gr-speaker)#timer recovery 45 seconds

The timer recovery maximum configuration determines the maximum accepted recovery time a device accepts from a neighbor going through graceful restart. This puts an upper bound on how long the device will accept a neighbor to recover for, after which it will consider a neighbor to have recovered and will return to normal operation. If the helper does not receive a refresh for an LSP from the neighbor by the end of the recovery phase, then it will timeout the LSP.

The no timer recovery and default timer recovery commands restore the maximum recovery timer value to its default. The default is to accept all recovery time values.

Command Mode

• MPLS RSVP Graceful Restart Helper Configuration

Command Syntax

timer recovery maximum MAX_RECOVERY seconds

default timer recovery maximum

no timer recovery maximum

Example

switch(config-mpls-rsvp-gr-helper)#timer recovery maximum 120 seconds

In the speaker role, the timer restart command is used to set the restart time. This is advertised to neighbors as how long to wait after losing communication with a speaker before considering it timed out, in order to give time to restart.

The no timer restart and no timer restart commands restore the restart time value to its default. The default is 90 seconds.

Command Mode

• MPLS RSVP Graceful Restart Speaker Configuration

Command Syntax

timer restart RESTART seconds

default timer restart

no timer restart

Example

switch(config-mpls-rsvp-gr-speaker)#timer restart 45 seconds

In the helper role, the timer restart maximum command sets the maximum accepted restart time value from a speaker.

The no timer restart maximum and no timer restart maximum commands restore the maximum restart time value to its default. The default is to accept all restart time values.

Command Mode

MPLS RSVP Graceful Restart Helper Configuration

Command Syntax

timer restart maximum RESTART seconds

default timer restart maximum

no timer restart maximum

Example

switch(config-mpls-rsvp-gr-helper)#timer restart maximum 90 seconds

The tree command in Traffic Engineering RSVP Configuration Mode creates tree specifications and enters the configuration mode for the tree. These tree specifications define the constraints for trees used by RSVP P2MP tunnels. If the tree specification does not already exist, the tree command creates it. Tree configuration modes are group-change modes: changes take effect only when the mode is exited. To exit the mode without saving changes, use the abort command.

The no tree and default tree commands delete the specified tree.

Command Mode

Traffic Engineering RSVP Configuration

Command Syntax

tree TREE_NAME (explicit | dynamic)

no tree TREE_NAME

default tree TREE_NAME

Parameters

• TREE_NAME - Specification name for the tree.

• dynamic - Establishes a dynamic tree specification.

• explicit - Establishes an explicit tree specification.

Example

switch(config-te-rsvp)#tree tree1 explicit  
switch(config-te-rsvp-tree-expl-tree1)#

switch(config-te-rsvp)#tree tree2 dynamic  
switch(config-te-rsvp-tree-dyn-tree2)#

The tree command in the Traffic Engineering RSVP P2MP Tunnel configuration mode specifies the tree specification that will be used for the P2MP tunnel.

The no and default forms of the command remove the specified tree from the tunnel configuration.

Command Mode

Traffic Engineering RSVP P2MP Tunnel Configuration

Command Syntax

tree TREE_NAME

no tree TREE_NAME

default tree TREE_NAME

Parameters

TREE_NAME - Specification name for the tree.

Example

switch(config-te-rsvp-tunnel-p2mp-myTunnel)#tree myTree 

The tunnel command enters Traffic Engineering RSVP P2P Tunnel configuration mode for the named tunnel. If the named tunnel does not exist, the command creates it.

Entering the p2mp keyword after the name of the tunnel places the tunnel into Traffic Engineering RSVP P2MP Tunnel configuration mode for multicast tunnels.

Changes made in the tunnel mode only take effect when the mode is exited normally, using the exit command. The abort command can be used to exit the mode and also discard any changes made.

Command Mode

Traffic Engineering RSVP Configuration

Command Syntax

tunnel name [p2mp]

no tunnel name [p2mp]

default tunnel name [p2mp]

Parameters

name - Tunnel name.

p2mp - Places the tunnel into point-to-multipoint (p2mp) mode.

Example

switch(config-te-rsvp)# tunnel MyTunnel
switch(config-te-rsvp-tunnel-MyTunnel)#

switch(config-te-rsvp-tunnel-MyTunnel)# exit 
switch(config-te-rsvp)#

switch(config-te-rsvp-tunnel-MyTunnel)# abort 
switch(config-te-rsvp)#

The tunneling ldp command causes the RSVP tunnel to become eligible for LDP over RSVP.

To make the tunnel ineligible for LDP over RSVP, use the no tunneling or default tunneling command.

The ucmp keyword can be added to enable UCMP with LDP over RSVP. The bandwidth configured on the RSVP tunnel determines the weight that would be associated with this tunnel when traffic to the tunnel endpoint is UCMP load balanced.

Command Mode

Traffic Engineering RSVP Tunnel Configuration

Traffic Engineering RSVP Tunnel Profile Configuration

Command Syntax

tunneling ldp [ ucmp | disabled ]

no tunneling

default tunneling

Parameters

Example

switch(config-te-rsvp-tunnel-MyTunnel)# tunneling ldp

switch(config-te-rsvp-tunnel-tunnelABC)# tunneling ldp ucmp

The tunnel profile command enters Traffic Engineering RSVP P2P Tunnel Profile configuration mode for the named tunnel profile. If the named tunnel profile does not exist, the command creates it. Tunnel profiles contain common sets of configurations that can be applied to different tunnel specifications

The no and default forms of the command delete the named tunnel profile.

Entering the p2mp keyword after the name of the tunnel profile places the tunnel profile into Traffic Engineering RSVP P2MP Tunnel Profile configuration mode for multicast tunnels.

Changes made in the tunnel profile mode only take effect when the mode is exited normally, using the exit command. The abort command can be used to exit the mode and also discard any changes made.

Command Mode

Traffic Engineering RSVP Configuration

Command Syntax

tunnel profile name [p2mp]

no tunnel profile name [p2mp]

default tunnel profile name [p2mp]

Parameters

• name - Tunnel profile name.

• p2mp - Places the tunnel profile into point-to-multipoint (p2mp) mode.

Example

switch(config-te-rsvp)# tunnel profile MyProfile 
switch(config-te-rsvp-tunnel-profile-MyProfile)# 

switch(config-te-rsvp-tunnel-profile-MyProfile)# exit 
switch(config-te-rsvp)# 

The following example exits the tunnel profile mode and discards changes made since entering the mode.

switch(config-te-rsvp-tunnel-profile-MyProfile)# abort 
switch(config-te-rsvp)#