RSVP-TE Commands
- authentication index
- authentication sequence-number window
- authentication type
- clear mpls rsvp counters
- clear mpls rsvp session
- cspf delay
- fast-reroute bypass tunnel optimization interval
- fast-reroute mode
- fast-reroute reversion
- graceful-restart role
- hardware next-hop fast-failover
- hello interval
- hitless-restart
- label local-termination
- mpls rsvp
- mtu signaling
- neighbor authentication index
- neighbor authentication type
- ping mpls rsvp session
- preemption method
- refresh interval
- refresh method
- rsvp bypass administrative-group
- show mpls rsvp counters
- show mpls rsvp neighbor
- show mpls rsvp session
- show mpls rsvp
- shutdown (MPLS RSVP)
- srlg
- timer recovery
- timer restart
- traffic-engineering srlg
- administrative-group
- alias endpoint
- bandwidth
- color
- cspf delay
- cspf ecmp tie-break
- destination ip
- fast-reroute mode (RSVP tunnel)
- fast-reroute mode
- hop (dynamic path)
- hop (explicit path)
- igp shortcut
- local-interface
- lsp self-ping
- metric
- optimization interval
- path (path specification)
- path (RSVP tunnel)
- priority
- refresh rsvp tunnel optimization
- router traffic-engineering – not an RSVP command
- rsvp
- show traffic-engineering cspf path
- show traffic-engineering database
- show traffic-engineering rsvp tunnel history
- show traffic-engineering rsvp tunnel lsp
- show traffic-engineering rsvp tunnel name
- show traffic-engineering rsvp tunnel sub-tunnel summary
- show traffic-engineering rsvp tunnel summary
- show traffic-engineering rsvp tunnel
- show traffic-engineering rsvp
- shutdown (MPLS RSVP)
- shutdown (tunnel)
- split-tunnel
- srlg
- traffic-engineering srlg
- tunneling ldp
- tunnel
administrative-group
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 Tunnel 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 )
default administrative-group
no 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
The following example states the path must include links from administrative group 1 and any link from an administrative group within groups 2, 3, or 4. The path must exclude links from administrative groups 7 and 9.
switch(config-te-rsvp-path-dyn-MyPath)# administrative-group include all 1 include any 2-4 exclude 7,9
alias endpoint
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. Use this command in the Router Traffic Engineering RSVP Tunnel Configuration Mode. Configure a maximum of 15 alias endpoints per tunnel.
Command Mode
Traffic Engineering RSVP Tunnel Configuration Mode
Command Syntax
alias endpoint [ ipv4_address | ipv6_address]
no alias endpoint
default alias endpoint
Parameters
- alias endpoint - Specify adding a tunnel endpoint.
- ipv4_address - Specify an IPv4 address in the format
A.B.C.D
. - ipv6_address - Specify an IPv4 address in the format
A:B:C:D:E:F:G:H
.
Example
Use the following commands to enter the Router Traffic Engineering RSVP Tunnel Configuration Mode, and add an alias endpoint, 192.168.11.5 to the existing MyTunnel configuration:
switch(config)# router traffic-engineering
switch(config-te)# rsvp
switch(config-te-rsvp)# tunnel MyTunnel
switch(config-te-rsvp-tunnel-MyTunnel)# alias endpoint 192.168.11.5
switch(config-te-rsvp-tunnel-MyTunnel)#
authentication index
The authentication index command configures the MPLS RSVP cryptographic authentication password globally for outgoing messages to the specified neighbor. Note that per-neighbor authentication takes precedence over global authentication.
The command authentication index index_num active is used to set the active password which is used when sending a message. The command authentication index index_num password is used to create the password with a given index. All configured passwords are used to authenticate incoming messages.
Command Mode
MPLS RSVP Configuration
Command Syntax
authentication index <num> password<WORD>
[no|default] authentication index <num> password <WORD> password
[no|default] authentication index <num> password<WORD> active
Parameters
<num> index number chosen as the password for cryptographic authentication for messages sent to the specified neighbor.
<WORD> can be a plaintext password or a number that specifies the obfuscation method followed by the obfuscated password.
Example
The following commands globally enable cryptographic authentication (RFC 2747) for MPLS RSVP messages sent from the switch and establish the authentication index 755 and the password s3cr3t for outgoing messages:
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
authentication sequence-number window
The authentication sequence-number window command configures the size of the sequence number reorder window for incoming MPLS RSVP messages. Increasing the size of the window allows RSVP to accommodate a larger number of out-of-order packets. A value of N means that a packet is accepted if all previously received packets with a higher sequence number are within the preceding N-1 packets. The default value is 5. A value of 1 effectively turns off support for packet reordering.
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
- 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
switch(config-mpls-rsvp)#
authentication type
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 takes 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}
- md5 = enables MPLS RSVP cryptographic authentication (RFC 2747) for the specified neighbor. A password for outgoing messages must also be configured using the authentication index command.
- none - disables MPLS RSVP cryptographic authentication for messages sent to the specified neighbor.
Examples
- The following commands globally enable cryptographic authentication (RFC 2747) for MPLS RSVP messages sent from the switch and establish index 755 as the password for outgoing messages:
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 following commands disable cryptographic authentication globally:
switch(config)#mpls rsvp switch(config-mpls-rsvp)# authentication type none switch(config-mpls-rsvp)#
bandwidth
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 with an adjustment period based on the observed traffic going over the tunnel. The adjustment period is an optional parameter measured in seconds. The default adjustment period is 0 - a special value meaning that the algorithm decides when to adjust bandwidth based on statistical measurements (the actual adjustment cannot happen more frequently than the sampling, which occurs every 30 seconds).
Command Mode
Traffic Engineering RSVP Tunnel Configuration
Command Syntax
bandwidth 0-1000 (bps | kbps | mbps | gbps)
bandwidth auto min (bps | kbps | mbps | gbps) 0-1000 max 0-1000 (bps | kbps | mbps | gbps) [ adjustment-period seconds]
bandwidth signaling [ disabled ]
no bandwidth 0-1000 (bps | kbps | mbps | gbps)
default bandwidth 0-1000 (bps | kbps | mbps | gbps)
no bandwidth auto
default bandwidth auto
no bandwidth signaling
default bandwidth signaling
Parameters
[bps | kbps | mbps | gbps] - Bandwidth values require the units of the value. The range of available units are bps, kbps, mbps, or gbps.
auto - Using the auto keyword configures autobandwidth within the configured minimum and maximum bandwidth and unit values. The tunnel adjusts the bandwidth based on the observed traffic going over the tunnel. This happens at adjustment interval, if configured. The default adjustment interval is 30 seconds, if no value is configured.
The min sets the minimum value and max sets the maximum value for the autobandwidth range. Each of the values require a unit to be selected.
The signaling keyword is used to enable signalling of the bandwidth reservation. A bandwidth of 0 returns signalling to the default of no signalling.
Example
- The following command explicitly configure the bandwidth of the tunnel to 10 mbps.
switch(config-te-rsvp-tunnel-myTunnel)# bandwidth 10 mbps
- The following command configures autobandwidth with a minimum of 1 mbps and maximum of 5 mbps. The bandwidth is set to be evaluated every 60 seconds.
switch(config-te-rsvp-tunnel-myTunnel)# bandwidth auto min 1 mbps max 5 mbps adjustment-period 60
clear mpls rsvp counters
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
MPLS RSVP Configuration
Command Syntax
clear mpls rsvp counters
clear mpls rsvp counters ( ip | ipv6 ) access-list
Parameters
- ipv4 - Filter by IPv4.
- ipv6 - Filter by IPv6.
Example
switch(config)#mpls rsvp
switch(config-mpls-rsvp)# clear mpls rsvp counters
clear mpls rsvp session
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
EXEC
Command Syntax
clear mpls rsvp session ( <filters> | all ) [ detail ]
Parameter
With <filters> being a list of one or more of: ( destination <ipv4> | id <id> ) ( name <name> | lsp <lsp> | bypass ) ( role <role> ) ( state <state> )
all - Clears all RSVP sessions.
bypass - Filter for bypass LSPs.
destination - Filter by destination address.
id - Filter by Session ID.
lsp- Filter by LSP number.
name - Filter by session name.
role - Filter by router 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 which are cleared are displayed, not just the count.
Examples
The following examples are on a switch with two RSVP sessions (sessionA
and sessionB
).
- This command clears all RSVP sessions on the switch.
switch# clear mpls rsvp session all Cleared 2 sessions
- The detail keyword can be added to the end of the command to output the session name of all sessions being cleared.
switch# clear mpls rsvp session all detail Clearing sessionA Clearing sessionB Cleared 2 sessions
- The all keyword can be replaced with filters to clear specific sessions. In the following example, the name sessionA filter is used to clear just sessionA.
switch# clear mpls rsvp session name sessionA detail Clearing sessionA Cleared 1 sessions
- The following is a list of the supported filters for the clear command. Some filters can be combined in a single command. For example, both the
bypass
andstate up
filters can be used in the same command to clear all bypass sessions which are in the up state.switch# clear mpls rsvp session ? all Clear all RSVP sessions bypass Filter for bypass LSPs destination Filter by destination address id Filter by Session ID lsp Filter by LSP# name Filter by session name role Filter by router role state Filter by LSP state
color
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 Tunnel Configuration
Command Syntax
color ( <color value> | disabled )
default color - would inherit the color from the profile if one is configured
no color
color disabled - explicitly disables the color configuration irrespective of a profile being configured
Parameters
<color value> - numerical value in the range of 0 - 4292967295.
disable - disable the color attribute.
Example
switch(config-te-rsvp-tunnel-MyTunnel)# color 60
cspf delay
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
Router traffic engineering mode
Command Syntax
cspf delay [initial n back-off n] max n
no cspf delay
default cspf delay
- initial - Specify initial wait interval for CSPF.
- n - Specify the time in milliseconds. 1-300000.
- back-off - Specify the back-off interval for CSPF.
- n - Specify the time in milliseconds. 1-300000.
- n - Specify the time in milliseconds. 1-300000.
- back-off - Specify the back-off interval for CSPF.
- n - Specify the time in milliseconds. 1-300000.
- max - Specify the maximum wait interval for CSPF.
- n - Specify the time in milliseconds. 1-300000.
Example
switch(config)#router traffic-engineering
switch(config-te)#cspf delay initial 200 back-off 400 max 2000
switch(config-te)#
cspf ecmp tie-break
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
Parameters
- least-fill - Enables bandwidth least-fill.
- random - Disables bandwidth least-fill. Least-fill is enabled by default.
Example
- The following command disables bandwidth least-fill on the switch:
switch(config-te-rsvp)#cspf ecmp tie-break random switch(config-te-rsvp)#
destination ip
Each tunnel requires a destination IP to function. The destination ip command assigns a destination IP to the command-mode tunnel. For P2MP, this can be set multiple times, one for each of the multicast destinations.
Command Mode
Traffic Engineering RSVP Tunnel Configuration
Command Syntax
destination ip IP_address
no destination ip
default destination ip
Parameters
IP_address - The destination IPv4 address is required for the tunnel.
Example
switch(config-te-rsvp-tunnel-MyTunnel)# destination ip 10.2.2.2
fast-reroute bypass tunnel optimization interval
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. Default is 30.
Example
switch(config)# mpls rsvp
switch(config-mpls-rsvp)# fast-reroute bypass tunnel optimization interval 45 seconds
switch(config-mpls-rsvp)#
fast-reroute mode (RSVP tunnel)
The fast-reroute mode command 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 which means that the inherit fast-reroute settings from the global RSVP configuration.
Command Mode
Traffic Engineering RSVP Tunnel Configuration
Command Syntax
fast-reroute mode ( link-protection | node-protection | none }
no fast-reroute mode
default fast-reroute mode
Parameters
fast-reroute mode link-protection - Protect against failure of the next link.
fast-reroute mode node-protection - Protect against failure of the next node.
fast-reroute mode none - Disable fast reroute.
-
The following command enables fast reroute (FRR) link protection:
switch(config-te-rsvp-tunnel-MyTunnel)# fast-reroute mode link-protection
-
The following command enables fast reroute (FRR) node protection:
switch(config-te-rsvp-tunnel-MyTunnel)# fast-reroute mode node-protection
-
The following command disables FRR:
switch(config-te-rsvp-tunnel-MyTunnel)# fast-reroute mode none
fast-reroute mode
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
- link-protection - Protects against failure of the next link.
- node-protection - Protects against failure of the next node.
- none - Disables fast reroute.
-
The following command enables fast reroute (FRR) link protection/NHOP (RFC 4090):
switch(config-mpls-rsvp)# fast-reroute mode link-protection
-
The following command enables fast reroute (FRR) node protection/NNHOP (RFC 4090):
switch(config-mpls-rsvp)# fast-reroute mode node-protection
-
The following command disables FRR:
switch(config-mpls-rsvp)# fast-reroute mode none
fast-reroute reversion
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 LSR 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 LSR 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
- global - Global revertive mode.
- local - Local revertive mode.
-
Set the fast-reroute reversion to local:
switch(config-mpls-rsvp)# fast-reroute reversion local
-
The default for reversion is global.
switch(config-mpls-rsvp)# fast-reroute reversion global
graceful-restart role
The graceful-restart role command enables a graceful-restart role for RSVP (helper or speaker) and enters the configuration mode for that role. Graceful restart is disabled by default, and requires hello messages to be enabled.
The no graceful-restart role and default graceful-restart role commands disable the feature.
The helper mode is enabled under the RSVP configuration mode, graceful-restart role helper.
The maximum accepted restart time value is configurable under the RSVP Graceful Restart helper configuration mode, timer restart maximum <t> seconds.
The maximum accepted recovery time value is configurable under the RSVP Graceful Restart helper configuration mode, timer recovery maximum <t> seconds.
The speaker mode is enabled under the RSVP configuration mode, graceful-restart role speaker.
The restart time value is configurable under the RSVP Graceful Restart speaker configuration mode, graceful-restart role speaker.
The recovery time value is configurable under the RSVP Graceful Restart speaker configuration mode. timer recovery <t> seconds.
Command Mode
MPLS RSVP Configuration Mode
Command Syntax
graceful-restart role (helper | speaker)
no graceful-restart role (helper | speaker)
default graceful-restart role (helper | speaker)
timer restart maximum <t> seconds - The maximum accepted restart time value is configurable under helper configuration mode.
default timer restart maximum
no timer restart maximum
timer recovery maximum <t> seconds - The maximum accepted recovery time value, configured under helper configuration mode.
default timer recovery maximum
no timer recovery maximum
timer restart <t> seconds - The restart time value is configurable under the speaker configuration mode.
default timer restart
no timer restart
timer recovery <t> seconds - The recovery time value is configurable under the speaker configuration mode.
default timer recovery
no timer recovery
- helper - Enables graceful restart in the helper role (assists with RSVP neighbor restarts) and enters Graceful Restart Helper configuration mode.
- speaker - Enables graceful restart in the speaker role (allows the local node to restart gracefully) and enters Graceful Restart Speaker configuration mode.
Example
switch(config)#mpls rsvp
switch(config-mpls-rsvp)#graceful-restart role helper
switch(config-mpls-rsvp-gr-helper)#
hello interval
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 <sec> multiplier <num>
no hello interval
default hello interval
- interval sec - The interval in units of seconds.
- multiplier num - The value that is multiplied by the interval value.
-
In this example, EOS sends hello messages to all known neighbors every 10 seconds. If the switch does not receive hello responses from a neighbor for 4*10=40 seconds, the switch loses communication and the neighbor resets.
switch(config-mpls-rsvp)# hello interval 10 multiplier 4
-
In this example, the default of 10 seconds with multiplier 4 resets.
switch(config-mpls-rsvp)# default hello interval
-
In this example, explicitly disable the Hello messages.
switch(config-mpls-rsvp)# no hello interval
hardware next-hop fast-failover
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
switch(config-router-general)#
hello-redundancy
The hello-redundancy command is suggested for Hello Redundancy when used with LDP over RSVP. Both peers require the configuration.
The neighbor hello-redundancy command configures Hello Redundancy on all platforms under the LDP configuration mode. Hello Redundancy means if a Link Hello Adjacency is lost it will not drop the sessions right away, but will continue to maintain a Targeted Hello adjacency for up to the configured time. Then, if Link Hello adjacency is NOT restored within the duration, it will drop the Targeted Hello adjacency and the session associated with it. The timeout can be configured using the duration option of the command. An infinite value for the duration disables the timeout.
Command Mode
MPLS-LDP Configuration
Command Syntax
neighbor hello-redundancy [duration seconds]
default neighbor hello-redundancy
no neighbor hello-redundancy
Parameter
Examples
These commands enable Targeted Hello redundancy with a duration of 300 seconds.
switch(config-mpls-ldp)# neighbor hello-redundancy
switch(config-mpls-ldp)# neighbor hello-redundancy duration 300
Use either of the following commands to disable Hello Redundancy.
switch(config-mpls-ldp)# neighbor hello-redundancy none
switch(config-mpls-ldp)# default neighbor hello-redundancy
hitless-restart
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, 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 <t> seconds is configurable under the hitless-restart mode. .
The maximum accepted recovery time value timer recovery maximum <t> seconds is configurable under the hitless-restart mode, .
Command Mode
MPLS RSVP Configuration
Command Syntax
hitless-restart
no hitless-restart
default hitless-restart
timer recovery maximum <t> seconds - The maximum accepted recovery time value, configured under hitless-restart configuration mode.
default timer recovery maximum
no timer recovery maximum
timer recovery <t> seconds - The recovery time value is configurable under the hitless-restart configuration mode.
default timer recovery
no timer recovery
Parameters
Example
switch(config-mpls-rsvp)#hitless-restart
switch(config-mpls-rsvp)#
hop (dynamic path)
The hop command adds a hop to the configuration-mode dynamic path. If entered without options, it is configured as a strict hop by default. A strict hop places the specified hop after the the previously specified hop. The before and after options can be used to insert the specified hop in relation to another hop in an existing path.
The no and default forms of the command remove
Command Mode
Traffic Engineering RSVP Explicit Path Configuration
Command Syntax
hop <IPv4_address> [ [exclude] | [loose] [ [before <IPv4_address> | after <IPv4_address>] ] ]
default hop <IPv4_address> - If no address is supplied then all hops are removed.
no hop [<IPv4_address>] - If no address is supplied then all hops are removed.
Parameters
- exclude - Specifies that CSPF must not choose the specified address on the path.
- loose - Defines the hop as a loose hop, which allows other hops to be filled by the CSPF procedure.
- before - Specifies the hop before which this hop will be placed.
- after - Specifies the hop after which this hop will be placed.
- The following example excludes 10.0.56.6 from being used as a hop.
switch(config-te-rsvp-path-dyn-MyPath)# hop 10.0.56.6 exclude
- The following example configures 10.0.56.6 as the hop. Hop 10.0.45.5 uses the loose keyword, which allow other hops to be filled in before it. Hop 10.0.12.2 uses the before keyword to placed it before hop 10.0.23.3.
switch(config-te-rsvp-path-dyn-MyPath)# hop 10.0.23.3 switch(config-te-rsvp-path-dyn-MyPath)# hop 10.0.45.5 loose switch(config-te-rsvp-path-dyn-MyPath)# hop 10.0.12.2 before 10.0.23.3
hop (explicit path)
The hop command adds a hop to the configuration-mode explicit path. If entered without options, the command places the specified hop in the order listed. The before and after options can be used to insert the specified hop in relation to another hop in an existing path.
Command Mode
Traffic Engineering RSVP Explicit Path Configuration
Command Syntax
hop <IPv4_address> [before IPv4_address | after <IPv4_address>]
default hop [ <IPv4_address>] - If no address is supplied then all hops are removed.
no hop [<IPv4_address>] - If no address is supplied then all hops are removed.
Parameters
- before - Specifies the hop before which this hop will be placed.
- after - Specifies the hop after which this hop will be placed.
- no - Removes the specifed hop.
- The following commands create hop 10.0.12.2 and then places hop 10.0.34.4 after it.
switch(config-te-rsvp)# path MyPath explicit switch(config-te-rsvp-path-expl-MyPath)# hop 10.0.12.2 switch(config-te-rsvp-path-expl-MyPath)# hop 10.0.34.4
- The following example places hop 10.0.23.3 before hop 10.0.34.4 and hop 10.0.45.5 is placed after hop 10.0.34.4.
switch(config-te-rsvp-path-expl-MyPath)# hop 10.0.23.3 before 10.0.34.4 switch(config-te-rsvp-path-expl-MyPath)# hop 10.0.45.5 after 10.0.34.4
label local-termination
The label local-termination command enables an egress LSR to advertise an IPv4 explicit-null label (Label 0) to its upstream router by using the explicit-null option.
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
- explicit-null - Advertises an explicit-null label to upstream RSVP router.
- implicit-null - Advertises an implicit-null label. This is the default.
Example
switch(config-mpls-rsvp)#label local-termination explicit-null
switch(config-mpls-rsvp)#
igp shortcut
The igp shortcut command is used to specify whether a RSVP tunnel should participate in Interior Gateway Protocol (IGP) shortcuts.
Command Mode
Traffic Engineering RSVP Tunnel Configuration
Command Syntax
igp shortcut
default igp shortcut
no igp shortcut
Parameters
disabled - disables the igp shortcut command.
Example
switch(config-te-rsvp-tunnel-MyTunnel)# igp shortcut
local-interface
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 int_type int_num
no local-interface
default local-interface
Parameters
- int_type Interface type for the local interface. Values include Ethernet, Fabric, Loopback , Management, Port-Channel, Recirc-Channel, Tunnel, Vlan, and Vxlan.
- int_num Interface number for the local interface.
Example
switch(config-te-rsvp)#local-interface Loopback 0
switch(config-te-rsvp)#
lsp self-ping
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
Global Configuration
Command Syntax
lsp self-ping
default lsp self-ping
no lsp self-ping
Parameters
Example
switch(config-te-rsvp)#lsp self-ping
switch(config-te-rsvp)#
metric
The metric command configures a per RSVP tunnel metric to allow specific tunnels to a tunnel endpoint take precedence over other tunnels to the same tunnel endpoint when forming ECMP. The tunnel metric publishes to the tunnel RIB for BGP cost calculations.
The tunnel metric can also 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.
Command Mode
Router Traffic Engineering RSVP Tunnel Configuration Mode
Command Syntax
metric ( igp | metric_value)
default metric
no metric
Parameters
- metric - Specify a metric for the tunnel.
- igp - Specify to use the IPG SPF metric.
- metric_value - Specify a static metric value between 0 and 4294967295.
Example
Use the following commands to enter the Router Traffic Engineering RSVP Tunnel Configuration Mode, and add a static metric, 10 to the existing MyTunnel configuration:
switch(config)# router traffic-engineering
switch(config-te)# rsvp
switch(config-te-rsvp)# tunnel MyTunnel
switch(config-te-rsvp-tunnel-MyTunnel)# metric 10
switch(config-te-rsvp-tunnel-MyTunnel)#
Use the following commands to enter the Router Traffic Engineering RSVP Tunnel Configuration Mode, and add the IGP SPF metric, igp, to the existing MyTunnel configuration:
switch(config)# router traffic-engineering
switch(config-te)# rsvp
switch(config-te-rsvp)# tunnel MyTunnel
switch(config-te-rsvp-tunnel-MyTunnel)# metric igp
switch(config-te-rsvp-tunnel-MyTunnel)#
mpls rsvp
The mpls rsvp command places the switch in MPLS RSVP configuration mode.
Command Mode
Global Configuration
Command Syntax
mpls rsvp
default mpls rsvp - Will wipe the configuration in the mode and disable RSVP.
no mpls rsvp - Will wipe the configuration in the mode and disable RSVP.
Commands Available in MPLS RSVP Configuration Mode
- authentication index
- authentication sequence-number window
- authentication type
- fast-reroute bypass tunnel optimization interval
- fast-reroute mode
- fast-reroute reversion
- graceful-restart role
- hello interval
- hitless-restart
- ip access-group
- ipv6 access-group
- label local-termination
- mtu signaling
- neighbor authentication index
- neighbor authentication type
- p2mp
- preemption method
- refresh interval
- refresh method
- shutdown (MPLS RSVP)
- srlg
Example
The following command places the switch in MPLS RSVP configuration mode:
switch(config)# mpls rsvp
switch(config-mpls-rsvp)#
mtu signaling
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 mtu signaling, default mtu signaling, and default mtu signaling commands disable MTU signaling, preventing the updating of composed MTUs.
Command Mode
MPLS RSVP Configuration
Command Syntax
mtu signaling
no mtu signaling
default mtu signaling
Example
switch(config-mpls-rsvp)#mtu signaling
switch(config-mpls-rsvp)#
neighbor authentication index
The neighbor authentication index command configures the MPLS RSVP cryptographic authentication password for outgoing messages to the specified neighbor. Per-neighbor authentication takes precedence over global authentication.
The no neighbor authentication index and default neighbor authentication index commands 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
Parameters
- neighbor_address - address of the MPLS RSVP neighbor.
- index_num - index number chosen as the password for cryptographic authentication for messages sent to the specified neighbor.
Examples
switch(config)#mpls rsvp
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
switch(config-mpls-rsvp)#
neighbor authentication type
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 neighbor authentication and default neighbor authentication commands remove neighbor-specific authentication type configuration; the neighbor then inherits 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
Parameters
- neighbor_address - address of the MPLS RSVP neighbor.
- md5 - enables MPLS RSVP cryptographic authentication (RFC 2747) for the specified neighbor. A password for outgoing messages must also be configured using the neighbor authentication index command.
- none - disables MPLS RSVP cryptographic authentication for messages sent to the specified neighbor.
Examples
- The following commands enable cryptographic authentication for the neighbor at 172.16.0.0 and establishes index 755 as the password for outgoing messages to that neighbor:
switch(config)#mpls rsvp 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 switch(config-mpls-rsvp)#
- The following commands disable cryptographic authentication for the neighbor at 172.16.0.0:
switch(config)#mpls rsvp switch(config-mpls-rsvp)# neighbor 172.16.0.0 authentication type none switch(config-mpls-rsvp)#
optimization interval
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 tunnel sub-mode. The optimization interval configured in the tunnel sub-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 Configuration
Traffic Engineering RSVP Tunnel Configuration
Command Syntax
optimization interval <numerical value> seconds
default optimization
no optimization
Parameters
numerical value - enter the optimization interval in seconds.
-
The following command configures all RSVP tunnels to be re-optimized every 3600 seconds:
switch(config-te-rsvp)#optimization interval 3600 seconds
- The following commands configured an optimization interval of 3600 seconds on the tunnel named
myTunnel
. This tunnel-specific configuration overrides the global optimization configuration.switch(config-te-rsvp)#tunnel myTunnel switch(config-te-rsvp-tunnel-myTunnel)#optimization interval 3600 seconds
- The following commands configure an optimization interval of 3600 seconds for all tunnels but disable automatic optimization on the tunnel named
myTunnel
:switch(config-te-rsvp)#optimization interval 3600 seconds switch(config-te-rsvp)#tunnel myTunnel switch(config-te-rsvp-tunnel-myTunnel)#optimization disabled switch(config-te-rsvp-tunnel-myTunnel)#
p2mp
From the config-mpls-rsvp configuration mode, the p2mp command places the switch in mpls-rsvp-p2mp configuration mode.
Command Mode
MPLS-RSVP Configuration Mode
Command Syntax
p2mp
default p2mp
no p2mp
Parameter
p2mp - Enables RSVP P2MP.
no p2mp - Disables RSVP P2MP.
default p2mp - Disables RSVP P2MP.
Examples
- RSVP P2MP signaling functionality is enabled using the p2mp command.
switch# config switch(config)# mpls rsvp switch(config-mpls-rsvp)# no shutdown switch(config-mpls-rsvp)# p2mp switch(config-mpls-rsvp-p2mp)#
- P2MP functionality is disabled by issuing the disabled command in the p2mp submode. This allows disabling RSVP P2MP without wiping any active configuration in the p2mp sub-mode.
switch(config-mpls-rsvp-p2mp)# disabled switch(config-mpls-rsvp-p2mp)#
- The no p2mp will both remove the p2mp sub-mode configuration and also disable RSVP P2MP.
-
switch(config-mpls-rsvp)# no p2mp switch(config-mpls-rsvp)#
- The exit command will leave the sub-mode but will retain the configuration in it.
switch(config-mpls-rsvp-p2mp)# exit switch(config-mpls-rsvp)#
path (path specification)
The path command in Traffic Engineering RSVP Tunnel P2P configuration mode specifies the configuration mode for the path. If the path does not already exist, it 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.
- Traffic Engineering RSVP Configuration
Command Syntax
path spec_name (dynamic | explicit)
no path spec_name
default path spec_name
Parameters
- spec_name - Specification name for the path.
- dynamic - Establishes a dynamic path.
- explicit - Establishes an explicit path.
Example
The following commands creates an explicit path named spec1
for the tunnel tunnel7
and enters the configuration mode for that path.
switch(config-te-rsvp)#tunnel tunnel7
switch(config-te-rsvp-tunnel-tunnel7)# path spec1
path (RSVP tunnel)
The path command in Traffic Engineering RSVP Tunnel configuration mode specifies a primary or secondary path along which the LSPs are established for the configuration-mode RSVP tunnel.
The no and default forms of the command remove the named path.
Command Mode
Traffic Engineering RSVP Tunnel Configuration
Command Syntax
path spec_name (secondary pre-signaled)
no path spec_name (secondary)
default path spec_name(secondary)
- The following commands create a path named
path6
for the tunnel namedtunnel13
:switch(config-te-rsvp)#tunnel tunnel13 switch(config-te-rsvp-tunnel-tunnel13)#path path6 switch(config-te-rsvp-tunnel-tunnel13)#
- The following commands create a pre-signaled secondary path named
path7
for the tunnel namedtunnel13:
switch(config-te-rsvp)#tunnel tunnel13 switch(config-te-rsvp-tunnel-tunnel13)#path path7 secondary pre-signaled switch(config-te-rsvp-tunnel-tunnel13)#
ping mpls rsvp session
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 mode
Command Syntax
ping mpls rsvp session ([id num [lsp lspId ] | name word)] [pad-reply] [repeat <num_repeat> ] [ source (IPv4_address | IPv6_address) ] [ standard (arista|ietf) ] | [ tos (<tos_value> | dscp <dscp_value>) ] [ traffic-class <traffic_class> ] [ interval <interval_value> ]
- id - Specifies the session by ID
- num - RSVP session ID.
- lsp - Specifies LSP. This parameter can only be specified with the id parameter.
- pad-reply - Indicates that the reply should copy the pad TLV.
- repeat - Specifies repeat count.
- source - Specifies source address.
- standard - Sets the standard to comply with.
- tos - Specifies ToS value.
- traffic-class - Specifies MPLS traffic class field.
- interval - Specify interval between requests
- size - Specify packet size in bytes
- num - RSVP session ID.
- name - Specifies session by name.
- word - RSVP session name.
- pad-reply - Indicates that the reply should copy the pad TLV.
- repeat - Specifies repeat count.
- source - Specifies source address.
- standard - Sets the standard to comply with.
- tos - Specifies ToS value.
- traffic-class - Specifies MPLS traffic class field.
- interval - Specify interval between requests
- size - Specify packet size in bytes
- word - RSVP session name.
- In the following example, the ping utility checks if the remote endpoint of an RSVP session is reachable through the LSP.
switch# ping mpls rsvp session id 1 lsp 1 repeat 3 LSP ping to RSVP session #1 LSP #1 timeout is 5000ms, interval is 1000ms Via 10.0.12.2, Ethernet1, label 100000 Reply from 10.0.34.4: seq=1, time=53.294ms, success: egress ok Via 10.0.12.2, Ethernet1, label 100000 Reply from 10.0.34.4: seq=2, time=75.329ms, success: egress ok Via 10.0.12.2, Ethernet1, label 100000 Reply from 10.0.34.4: seq=3, time=85.574ms, success: egress ok --- RSVP target fec 0.4.4.4 : lspping statistics --- Via 10.0.12.2, Ethernet1, label 100000 3 packets transmitted, 3 received, 0% packet loss, time 2272ms 3 received from 10.0.34.4, rtt min/max/avg 53.294/85.574/71.399 ms
- For the ping mpls rsvp session command, the argument lsp is optional. If unspecified, the utility pings all LSPs within that session.
switch# ping mpls rsvp session id 1 repeat 2 LSP ping to RSVP session #1 timeout is 5000ms, interval is 1000ms LSP 1 Via 10.0.12.2, Ethernet1, label 100000 Reply from 10.0.34.4: seq=1, time=60.28ms, success: egress ok LSP 2 Via 10.0.12.2, Ethernet1, label 100002 Reply from 10.0.34.4: seq=1, time=81.701ms, success: egress ok LSP 1 Via 10.0.12.2, Ethernet1, label 100000 Reply from 10.0.34.4: seq=2, time=52.807ms, success: egress ok LSP 2 Via 10.0.12.2, Ethernet1, label 100002 Reply from 10.0.34.4: seq=2, time=62.814ms, success: egress ok --- RSVP target fec 0.4.4.4 : lspping statistics --- LSP 1 Via 10.0.12.2, Ethernet1, label 100000 2 packets transmitted, 2 received, 0% packet loss, time 1262ms 2 received from 10.0.34.4, rtt min/max/avg 52.807/60.280/56.544 ms LSP 2 Via 10.0.12.2, Ethernet1, label 100002 2 packets transmitted, 2 received, 0% packet loss, time 1262ms 2 received from 10.0.34.4, rtt min/max/avg 62.814/81.701/72.257 ms
- In the following example, the session is specified by name and the utility pings all the LSPs within that session.
switch# ping mpls rsvp session name Session1to4 repeat 2 LSP ping to session Session1to4 timeout is 5000ms, interval is 1000ms LSP 1 Via 10.0.12.2, Ethernet1, label 100000 Reply from 10.0.34.4: seq=1, time=63.314ms, success: egress ok LSP 2 Via 10.0.12.2, Ethernet1, label 100002 Reply from 10.0.34.4: seq=1, time=75.639ms, success: egress ok LSP 1 Via 10.0.12.2, Ethernet1, label 100000 Reply from 10.0.34.4: seq=2, time=60.875ms, success: egress ok LSP 2 Via 10.0.12.2, Ethernet1, label 100002 Reply from 10.0.34.4: seq=2, time=77.135ms, success: egress ok --- RSVP target fec 0.4.4.4 : lspping statistics --- LSP 1 Via 10.0.12.2, Ethernet1, label 100000 2 packets transmitted, 2 received, 0% packet loss, time 1262ms 2 received from 10.0.34.4, rtt min/max/avg 60.875/63.314/62.094 ms LSP 2 Via 10.0.12.2, Ethernet1, label 100002 2 packets transmitted, 2 received, 0% packet loss, time 1262ms 2 received from 10.0.34.4, rtt min/max/avg 75.639/77.135/76.387 ms
preemption method
The preemption method command enables deferred failure of RSVP-TE LSPs on link oversubscription. Hard preemption will result in the LSP being torn down without any delay. Use a preemption timer value to configure a delay, before tearing down an LSP due to losing its bandwidth reservation, on a transit router to support LSPs signaled with soft preemption enabled by the headend (RFC 5712).
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
- hard - Hard preemption. The timer value is ignored.
- soft - Soft preemption.
- timer - Time limit for LSP teardown. Only applies to soft-preemption. If the timer keyword is not used the default timer of 30 seconds is used.
- <seconds> 1-65535 - Timer value in units of seconds.
- timer - Time limit for LSP teardown. Only applies to soft-preemption. If the timer keyword is not used the default timer of 30 seconds is used.
-
In this example, the preemption method is soft preemption with a timer value of 10 seconds.
switch(config-mpls-rsvp)# preemption method soft timer 10
-
Setting the preemption method to hard preemption results in a timer value of 0 seconds and disables the feature.
switch(config-mpls-rsvp)# preemption method hard
priority
The priority command configures the tunnel priority. The setup keyword is used to set the priority of the setup. The hold keyword sets the priority of the tunnel hold. The priority value range is 0 (highest priority) to 7 (lowest priority). The setup priority can be used without a hold priority, but a hold priority requires a setup priority to be set.
When both setup and hold priorities are configured, the hold value 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 Tunnel Configuration
Command Syntax
priority 0-7
no priority - Default setting and will inherit from profile. The default profile values are: priority setup 7 hold 0
default priority
- setup - requires a priority value 0-7
- hold - requires a priority value 0-7
Example
switch(config-te-rsvp-tunnel-myTunnel)# priority setup 5 hold 3
refresh interval
The refresh interval command configures the interval at which MPLS RSVP Path and Resv messages are sent to refresh the state. State is refreshed 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. Values range from 1 to 65535. Default value is 30.
Example
switch(config-mpls-rsvp)#refresh interval 100
switch(config-mpls-rsvp)#
refresh method
Using the Srefresh method command with the bundled keyword enables the Refresh Overhead Reduction that supports the sending of message IDs and refreshing state with refresh messages.
Command Mode
MPLS RSVP Configuration
Command Syntax
Srefresh method [bundled | explicit ]
no Srefresh method - More tokens allowed but ignored.
default Srefresh method - More tokens allowed but ignored.
- bundled - Refresh states using message identifiers lists. This is the default setting.
- explicit - Send each refresh message individually.
-
Use the bundled keyword to enable the Refresh Overhead Reduction.
switch(config-mpls-rsvp)# refresh method bundled
-
To turn off refresh overhead reduction, use the explicit keyword.
switch(config-mpls-rsvp)# refresh method explicit
refresh rsvp tunnel optimization
When periodic tunnel optimization is not configured, tunnels will not re-optimize automatically, but they can be optimized on demand by using the refresh rsvp tunnel optimization command.
Command Mode
Privileged Exec
Command Syntax
refresh rsvp tunnel optimization (all | name tunnel_name [avoid ecmp hop ecmp_hops] )
- all Optimizes all tunnels.
- name tunnel_name Optimizes the named tunnel.
- avoid ecmp hop ecmp_hops The on-demand optimization can also be used to move a tunnel between different equal-cost options. A set of links can be passed to CSPF to avoid while finding another equal-cost path. This operation works only on equal-cost paths and will not switch the tunnel to a less optimal path. The variable ecmp_hops is a list of IP(v4) addresses.
- The following command optimizes the tunnel named
myTunnel
:switch# refresh rsvp tunnel optimization name myTunnel switch#
- The following command optimizes the tunnel named
myTunnel
and recomputes the tunnel path to avoid 198.51.100.17:switch# refresh rsvp tunnel optimization name myTunnel avoid ecmp hop 198.51.100.17 switch#
- The following command performs optimization on all tunnels:
switch# refresh rsvp tunnel optimization all switch#
router traffic-engineering – not an RSVP command
The router traffic-engineeing command places the switch in Traffic Engineering configuration mode.
Command Mode
Global Configuration
Command Syntax
router traffic-engineering
Parameters
Example
switch(config)# router traffic-engineering
switch(config-te)#
rsvp
The rsvp command places the switch in Traffic Engineering RSVP configuration mode.
Command Mode
Traffic Engineering Configuration
Command Syntax
rsvp
default rsvp
no rsvp
Commands Available in RSVP Configuration Mode
- cspf ecmp tie-break
- local-interface Loopback
- lsp self-ping
- optimization interval <NumberofSeconds> seconds
- path <PathName> dynamic
- path <PathName> explicit
- show active
- tunnel <TunnelName>
Example
switch(config)#router traffic-engineering
switch(config-te)#rsvp
switch(config-te-rsvp)#
rsvp bypass administrative-group
The rsvp bypass administrative-group command specifies administrative groups that must be included in, or excluded from, the links used for CSPF path computation. The restrictions specified for an interface apply to all LSPs that bypass that interface. This includes both link and node protection. A single command can incorporate ranges for include any, include all, and exclude.
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 specified range of administrative groups identified by either a group name or number.
Example
switch(config)#interface ethernet 1/1
switch(config-if-Et1/1)#rsvp bypass administrative-group include all 5-16 include any 8-75 exclude 82,93,115-168,255
switch(config-if-Et1/1)#
show mpls rsvp
Use the show mpls rsvp to display the overall state of the RSVP.
Command Mode
EXEC
Command Syntax
show mpls rsvp [bandwidth | counters | ( ( ip | ipv6 ) access-list ( <name> | dynamic | summary ) ) | neighbor | session]
- bandwidth - Displays RSVP bandwidth information.
- counters - Displays RSVP message counters.
- ip - Displays details related to IPv4 ACLs.
- ipv6 - Displays details related to IPv6 ACLs.
- neighbor - Displays RSVP neighbor information.
- session - Displays RSVP session information.
Example
switch> show mpls rsvp
Administrative state: enabled
Operational state: up
Refresh interval: 30 seconds
Refresh reduction: enabled
Hello messages: enabled
Hello interval: 10 seconds
Hello multiplier: 4
Fast Re-Route: disabled
Mode: none
Hierarchical FECs: enabled
Cryptographic authentication: disabled
MTU signaling: disabled
Number of sessions: 1
Ingress/Transit/Egress: 0/1/0
Number of LSPs: 1
Operational: 1
Ingress/Transit/Egress: 0/1/0
Currently using bypass tunnels: 0
Number of bypass tunnels: 0
Number of neighbors: 2
Number of interfaces: 2
show mpls rsvp counters
Use the show mpls rsvp counters command to display RSVP message counters, per interface. The address family filter has to be specified first, if it is specified. Then the interface filter is specified, if it is specified. This cannot be done in the opposite order.
Command Mode
EXEC
Command Syntax
show mpls rsvp counters [ ipv4 | ipv6 ] [interface [Ethernet |Fabric | Loopback | Management | Port-Channel | Switch | Tunnel | Vlan | Vxlan]]
Parameters
- interface Filter by interface.
- Ethernet - Hardware Ethernet interface.
- Fabric - Fabric interfaces.
- Loopback - Hardware interface used for looping packets.
- Management - Management interface.
- Port-Channel - Lag interface.
- Switch - Switch interface.
- Tunnel - Tunnel interface.
- Vlan - Logical interface into a VLAN.
- Vxlan - VXLAN tunnel interface.
- ipv4 - Filter by IPv4.
- ipv6 - Filter by IPv6.
Example
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
show mpls rsvp neighbor
Use the show mpls rsvp neighbor command to display information about all RSVP neighbors, or for a specific neighbor.
Command Mode
EXEC
Command Syntax
show mpls rsvp neighbor [A.B.C.D | A:B:C:D:E:F:G:H | summary]
- A.B.C.D - IP (v4 or v6) address of neighbor.
- A:B:C:D:E:F:G:H - IP (v4 or v6) address of neighbor.
- summary - Displays summarized information.
-
Use the show mpls rsvp neighbor command to display information about all RSVP neighbors.
switch> show mpls rsvp neighbor Neighbor 10.0.1.1 Upstream for Session #1 LSP #1 Downstream for Neighbor uptime: 00:01:24 Authentication type: disabled Last hello received: 1 seconds ago Last hello sent: 1 seconds ago Bypass tunnel: not requested Neighbor 10.0.2.2 Upstream for Downstream for Session #1 LSP #1 Neighbor uptime: 00:01:24 Authentication type: disabled Last hello received: - Last hello sent: 31 seconds ago Bypass tunnel: not requested
-
Use the show mpls rsvp neighbor summary command to display summarized information.
switch> show mpls rsvp neighbor summary Neighbor Role Sessions LSPs ==================== ========== ======== ======== 10.0.1.1 Upstream 1 1 10.0.2.2 Downstream 1 1
show mpls rsvp session
The show mpls rsvp session command displays RSVP session information.
Command Mode
EXEC
Command Syntax
show mpls rsvp session ( <filters> | all ) [ detail ]
Parameter
With <filters> being a list of one or more of: ( destination <ipv4> | id <id> ) ( name <name> | lsp <lsp> | bypass ) ( role <role> ) ( state <state> )
all - Clears all RSVP sessions.
bypass - Filter for bypass LSPs.
destination - Filter by destination address.
id - Filter by Session ID.
lsp- Filter by LSP number.
name - Filter by session name.
role - Filter by router 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 which are cleared are displayed, not just the count.
- The following command displays RSVP session information:
switch>show mpls rsvp session Session #1 Destination address: 4.4.4.4 Tunnel ID: 0 Extended Tunnel ID: 1.1.1.1 Role: transit LSP #1 State: up Type: primary Source address: 1.1.1.1 LSP ID: 1 LSP uptime: 00:02:38 Session name: Session1 Local label: 100000 Downstream label: 100000 Upstream neighbor: 10.0.1.1 Last refresh received: 17 seconds ago Last refresh sent: 10 seconds ago Downstream neighbor: 10.0.2.2 Last refresh received: 7 seconds ago Last refresh sent: 9 seconds ago Bypass tunnel: not requested switch>
- The following command displays detailed RSVP session information:
switch>show mpls rsvp session detail Session #1 Destination address: 4.4.4.4 Tunnel ID: 0 Extended Tunnel ID: 1.1.1.1 Role: transit LSP #1 State: up [...] MTU Signaling: enabled Received Path MTU: 1800 bytes Sent Path MTU: 1500 bytes [...] switch>
- The following command displays history information for RSVP sessions and LSPs:
switch>show mpls rsvp session history Session #0, Session1 Tue 2024-06-04 17:25:33.708 Session created Tue 2024-06-04 17:25:33.708 LSP #2 added LSP #2 Tue 2024-06-04 17:25:33.714 State change: down (path: received-only, resv: down) Tue 2024-06-04 17:25:33.721 Bandwidth state change: pending on Ethernet2 Tue 2024-06-04 17:25:33.721 State change: path-only (path: up, resv: down) Tue 2024-06-04 17:25:33.767 State change: path-only (path: up, resv: received-only) Tue 2024-06-04 17:25:33.776 Bandwidth state change: reserved on Ethernet2 Tue 2024-06-04 17:25:33.777 State change: up Tue 2024-06-04 17:25:33.802 FRR bypass (link): available, via 10.0.25.5 switch>
- The following command displays a summary of RSVP session information:
switch>show mpls rsvp session summary Session Destination LSP Name Role Bypass State ======== ======================================== ======== ================== ======= ====== ========= 1 4.4.4.4 1 Session1 transit n/req up switch>
show rib system-tunneling-ldp-rib route ip
The show rib system-tunneling-ldp-rib route ip command shows RSVP tunnel next hop resolutions for LDP.
Command Mode
EXEC
Command Syntax
show rib system-tunneling-ldp-rib route ip
Examples
switch# show rib system-tunneling-ldp-rib route ip
VRF: default
Codes: I L1 - IS-IS level 1, I L2 - IS-IS level 2
Gateway of last resort is not set
I L2 5.5.5.5/32 [115/20] via 5.5.5.5/32, RSVP LER tunnel index 1
via 10.0.25.5, Ethernet4, label imp-null(3)
via 5.5.5.5/32, RSVP LER tunnel index 2
via 10.0.23.3, Ethernet2, label 116384
I L2 6.6.6.6/32 [115/30] via 5.5.5.5/32, RSVP LER tunnel index 1
via 10.0.25.5, Ethernet4, label imp-null(3)
via 5.5.5.5/32, RSVP LER tunnel index 2
via 10.0.23.3, Ethernet2, label 116384
I L2 10.0.56.0/24 [115/20] via 5.5.5.5/32, RSVP LER tunnel index 1
via 10.0.25.5, Ethernet4, label imp-null(3)
via 5.5.5.5/32, RSVP LER tunnel index 2
via 10.0.23.3, Ethernet2, label 116384
show traffic-engineering cspf path
The show traffic-engineering cspf path command displays all the paths counted by CSPF.
Command Mode
EXEC
Command Syntax
show traffic-engineering cspf path [destination-IP <IP address>] [detail]
show traffic-engineering cspf path ( <ipv4> | <path-id> | tunnel-name <name> ) [ detail ] - A path or tunnel name can be specified.
show traffic-engineering cspf path p2mp ( <path-id> | tunnel-name <name> ) [ detail ] - A P2MP version of the command is also available.
show traffic-engineering cspf path <ipv4> links - Displays the link attributes of the links on all the CSPF paths with a given destination IP address.
Parameters
A.B.C.D - CSPF path to this destination IP address.
detail - Shows detailed path information.
links
p2mp
tunnel-name
- An example of the output of the show traffic-engineering cspf path command.
switch> show traffic-engineering cspf path Destination Path ID Constraint Path 10.2.2.2 0 bandwidth 150.00 Mbps 10.0.2.2 setup priority 4 10.0.3.2 share bandwidth with path 10.3.3.3 ID 2 share bandwidth with path 10.4.4.4 ID 0 10.3.3.3 2 bandwidth 150.00 Mbps 10.0.4.2 setup priority 4 10.0.5.2 share bandwidth with path 10.2.2.2 ID 0 share bandwidth with path 10.4.4.4 ID 0 10.4.4.4 0 bandwidth 150.00 Mbps 10.0.6.2 setup priority 4 10.0.7.2 share bandwidth with path 10.2.2.2 ID 0 share bandwidth with path 10.3.3.3 ID 2
- An example of the output of the show traffic-engineering cspf path detail command.
switch> show traffic-engineering cspf path detail Destination: 10.2.2.2 Path ID: 0 Path Constraint: bandwidth 150.00 Mbps setup priority 4 share bandwidth with path 10.3.3.3 ID 2 share bandwidth with path 10.4.4.4 ID 0 Request Sequence number: 1 Response Sequence number: 1 Number of times path updated: 3 Last updated: 0:03:07 ago Reoptimize: On request Path: Ingress IP TE router ID ---------------- ------------------ 10.0.2.2 10.5.5.5 10.0.3.2 10.2.2.2 Destination: 10.3.3.3 Path ID: 2 Path Constraint: bandwidth 150.00 Mbps setup priority 4 share bandwidth with path 10.2.2.2 ID 0 share bandwidth with path 10.4.4.4 ID 0 Request Sequence number: 1 Response Sequence number: 1 Number of times path updated: 3 Last updated: 0:03:07 ago Reoptimize: On request Path: Ingress IP TE router ID ---------------- ------------------ 10.0.4.2 10.6.6.6 10.0.5.2 10.3.3.3 Destination: 10.4.4.4 Path ID: 0 Path Constraint: bandwidth 150.00 Mbps setup priority 4 share bandwidth with path 10.2.2.2 ID 0 share bandwidth with path 10.3.3.3 ID 2 Request Sequence number: 1 Response Sequence number: 1 Number of times path updated: 3 Last updated: 0:03:07 ago Reoptimize: On request Path: Ingress IP TE router ID ---------------- ------------------ 10.0.6.2 10.7.7.7 10.0.7.2 10.4.4.4
show traffic-engineering database
Use the show traffic-engineering database to display the topology used for CSPF computations. Starting from EOS Release 4.23.1F, the SRLG group details of a neighbor are shown if it is advertised.
Command Mode
EXEC
Command Syntax
show traffic-engineering database
- Beginning with EOS Release 4.23.1F, the SRLG group details of a neighbor are shown if it is advertised.
- Beginning with EOS Release 4.24.2F, information for the OSPFv2 topology is displayed if configured.
Example
switch# show traffic-engineering database
TE Router-ID: 1.0.0.2
Source: IS-IS Level-1 IPv4 Topology Database
IS-IS System-ID: 1111.1111.1001
Number of Links: 2
Network type: P2P
Neighbor: 1111.1111.1002
Administrative group (Color): 0x123a
TE Metric: 30
IPv4 Interface Addresses:
20.20.20.1
192.168.20.1
IPv4 Neighbor Addresses:
20.20.20.2
192.168.20.2
Maximum link BW: 25.00 Gbps
Maximum reservable link BW: 10.00 Mbps
Unreserved BW:
TE class 0: 9.00 Mbps TE class 1: 9.00 Mbps
TE class 2: 8.5.00 Mbps TE class 3: 8.00 Mbps
TE class 4: 7.00 Mbps TE class 5: 7.50 Mbps
TE class 6: 6.00 Mbps TE class 7: 6.00 Mbps
Network Type: LAN
Neighbor: 1111.1111.1003.02
TE Metric: 30
Administrative Group: 0x12
IPv4 Local Addresses:
30.30.30.1
Maximum Link BW: 10.00 Gbps
Maximum Reservable Link BW: 10.50 Gbps
Unreserved BW:
TE-Class 0: 8.50 Gbps TE-Class 1: 8.70 Gbps
TE-Class 2: 7.50 Gbps TE-Class 3: 7.25 Gbps
TE-Class 4: 6.50 Gbps TE-Class 5: 7.30 Gbps
TE-Class 6: 3.50 Gbps TE-Class 7: 7.20 Gbps
Source: IS-IS Level-2 IPv4 Topology Database
IS-IS System-ID: 1111.1111.1003
Number of Links: 1
Network Type: LAN
Neighbor: 1111.1111.1003.16
IPv4 Local Addresses:
40.40.40.1
Maximum link BW: 10.00 Gbps
Maximum reservable link BW: 5.00 Gbps
Unreserved BW:
TE class 0: 4.00 Gbps TE class 1: 4.00 Gbps
TE class 2: 4.00 Gbps TE class 3: 4.00 Gbps
TE class 4: 3.00 Gbps TE class 5: 3.00 Gbps
TE class 6: 3.00 Gbps TE class 7: 3.00 Gbps
Source: OSPFv2 Instance ID 33 Area-ID 0.0.0.0 Topology Database
OSPFv2 Router-ID: 1.2.3.4
Number of Links: 2
Network type: P2P
Neighbor: 3.4.5.6
Administrative group (Color): 0x123a
TE metric: 30
IPv4 Interface Addresses:
20.20.20.1
192.168.20.1
IPv4 Neighbor Addresses:
20.20.20.2
192.168.20.1
Maximum link BW: 25.00 Gbps
Maximum reservable link BW: 10.00 Mbps
Unreserved BW:
TE class 0: 9.00 Mbps TE class 1: 9.00 Mbps
TE class 2: 8.50 Mbps TE class 3: 8.00 Mbps
TE class 4: 7.00 Mbps TE class 5: 7.50 Mbps
TE class 6: 6.00 Mbps TE class 7: 6.00 Mbps
Network type: LAN
Neighbor: 2.3.4.5
Administrative group (Color): 0x12
TE metric: 30
IPv4 Interface Addresses:
30.30.30.1
IPv4 Neighbor Addresses:
0.0.0.0
Maximum link BW: 10.00 Gbps
Maximum reservable link BW: 10.5 Gbps
Unreserved BW:
TE class 0: 8.50 Gbps TE class 1: 8.70 Gbps
TE class 2: 7.50 Gbps TE class 3: 7.25 Gbps
TE class 4: 6.50 Gbps TE class 5: 7.30 Gbps
TE class 6: 3.50 Gbps TE class 7: 7.20 Gbps
TE Router-ID: 1.0.0.3
Source: IS-IS Level-1 IPv4 Topology Database
IS-IS System-ID: 1111.1111.1004
Number of Links: 2
Network type: P2P
Neighbor: 1111.1111.1002
IPv4 Interface Addresses:
1.0.5.1
IPv4 Neighbor Addresses:
1.0.5.2
Maximum link BW: 50.00 Gbps
Maximum reservable link BW: 10.00 Gbps
Unreserved BW:
TE class 0: 8.00 Gbps TE class 1: 8.00 Gbps
TE class 2: 8.00 Gbps TE class 3: 8.00 Gbps
TE class 4: 7.00 Gbps TE class 5: 7.00 Gbps
TE class 6: 7.00 Gbps TE class 7: 7.00 Gbps
Shared Risk Link Group:
Group: 100
Group: green-link (150)
show traffic-engineering rsvp tunnel detail
The show traffic-engineering rsvp tunnel detail command shows RSVP tunnel detail including LDP tunneling eligibility.
Command Mode
EXEC
Command Syntax
show traffic-engineering rsvp tunnel detail
Parameters
Examples
switch>show traffic-engineering rsvp tunnel detail
Tunnel tunnel2to5
Source: 2.2.2.2
Destination: 5.5.5.5
State: up
Bandwidth: 0.0 bps, mode explicit
Setup priority: 7
Hold priority: 0
MTU signaling: disabled
Periodic optimization: disabled
Session #1
Tunnel index: 1
LSPs: 1
LDP tunneling: enabled
IGP shortcut: disabled
Active path: primary
Primary path: path2to5
State: up, in use
Path (explicit):
10.0.25.5
Tunnel tunnel2to5via3
Source: 2.2.2.2
Destination: 5.5.5.5
State: up
Bandwidth: 0.0 bps, mode explicit
Setup priority: 7
Hold priority: 0
MTU signaling: disabled
Periodic optimization: disabled
Session #2
Tunnel index: 2
LSPs: 1
LDP tunneling: enabled
IGP shortcut: disabled
Active path: primary
Primary path: path2to5via3
State: up, in use
Path (explicit):
10.0.23.3
10.0.35.5
show traffic-engineering rsvp tunnel history
Display the history of a RSVP tunnel. For information about the detail version of this commend, refer to show traffic-engineering rsvp tunnel detail.
Command Mode
EXEC
Command Syntax
show traffic-engineering rsvp tunnel history
Parameters
Example
switch> show traffic-engineering rsvp tunnel history
Tunnel TestTunnel
Mon 2020-07-13 07:04:44 CSPF query on primary path
Mon 2020-07-13 07:04:44 State change: down
Mon 2020-07-13 07:04:44 LSP #1 added
Mon 2020-07-13 07:04:44 CSPF reply for primary path, path found
Mon 2020-07-13 07:04:44 LSP #2 added
Mon 2020-07-13 07:04:46 State change: up using primary path
LSP #1
Mon 2020-07-13 07:04:44 LSP created
Mon 2020-07-13 07:04:44 State change: establishing
Mon 2020-07-13 07:04:46 State change: up
LSP #2
Mon 2020-07-13 07:04:44 LSP created
Mon 2020-07-13 07:04:44 State change: establishing
Mon 2020-07-13 07:04:47 State change: up
show traffic-engineering rsvp tunnel lsp
Display RSVP tunnel LSPs using the show traffic-engineering rsvp tunnel lsp command.
Command Mode
EXEC
Command Syntax
show traffic-engineering rsvp tunnel lsp
Parameters
Example
switch> show traffic-engineering rsvp tunnel lsp
Tunnel TestTunnel
Source: 10.1.1.1
Destination: 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
show traffic-engineering rsvp tunnel name
Display the status of a specific RSVP tunnel, using the name of the tunnel with the show traffic-engineering rsvp tunnel name command.
- detail
- history
- lsp
- sub-tunnel
- summary - Can be used with or without a filter. With the filter you only get that tunnel, without the filter you get all tunnels.
Command Mode
EXEC
Command Syntax
show traffic-engineering rsvp tunnel name<name of tunnel>
Parameters
Example
switch>show traffic-engineering rsvp tunnel name MyTunnel
! RSVP is not enabled
! MPLS routing is not enabled
! Traffic engineering is not enabled
! Agent RSVP is not running
! Agent MPLS is not running
show traffic-engineering rsvp tunnel sub-tunnel summary
Display split tunnel information in a summarized fashion using the show traffic-engineering rsvp tunnel sub-tunnel summary command.
Command Mode
EXEC
Command Syntax
show traffic-engineering rsvp tunnel sub-tunnel summary
Parameters
Example
switch> show traffic-engineering rsvp tunnel sub-tunnel summary
Tunnel: TestSplitTunnelUp
Sub Tunnel Session ID Index Active Path Bandwidth LSPs State
========== ========== ====== =========== ========= ==== =====
1 65535 123456 primary 19.2 Kbps 1 up
2 65535 123460 secondary 19.2 Kbps 1 up
Tunnel: TestSplitTunnelUp-2
Sub Tunnel Session ID Index Active Path Bandwidth LSPs State
========== ========== ====== =========== ========= ==== =====
1 65535 123457 secondary 19.2 Kbps 1 up
show traffic-engineering rsvp tunnel summary
Display a summary of the status of an RSVP tunnel using the show traffic-engineering rsvp tunnel summary command.
Command Mode
EXEC
Command Syntax
show traffic-engineering rsvp tunnel summary
Parameters
Example
switch> show traffic-engineering rsvp tunnel summary
Tunnel Name Destination Color Index Active Path Reserved BW LSPs State
=========== =========== ===== ===== =========== =========== ==== =====
TestTunnel 10.4.4.4 60 - primary 0.0 bps 2 up
show traffic-engineering rsvp tunnel
Display the traffic engineering RSVP tunnel status using the show traffic-engineering rsvp tunnel command.
Command Mode
EXEC
Command Syntax
show traffic-engineering rsvp tunnel
Parameters
Example
switch> show traffic-engineering rsvp tunnel
Tunnel TestTunnel
Source: 10.1.1.1
Destination: 10.4.4.4
Color: 60, Metric: 0
State: up
Bandwidth: 0.0 bps, mode explicit
LSPs: 2
Active path: primary
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
show traffic-engineering rsvp
The show traffic-engineering rsvp command displays the current status of traffic engineering RSVP.
Command Mode
EXEC
Command Syntax
show traffic-engineering rsvp
Parameters
Example
switch> show traffic-engineering rsvp
Local interface: 'Loopback0'
IP address: 10.1.1.1
Number of tunnels: 1
Operational: 1
Secondary path enabled: 1
Secondary path in use: 0
Number of LSPs: 2
Operational: 2
shutdown (MPLS RSVP)
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 default mpls rsvp or no mpls rsvp, which would disable RSVP but also wipe the config.
RSVP-TE is enabled globally by issuing no shutdown 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 is disabled with no mpls ip.
Command Mode
MPLS RSVP Configuration
Command Syntax
shutdown
no shutdown
- The following example enables RSVP-TE globally with the no shutdown command.
switch(config-mpls-rsvp)# no shutdown
- The following example disables RSVP-TE globally with the shutdown command, which is the default.
switch(config-mpls-rsvp)# shutdown
shutdown (tunnel)
A tunnel is not enabled by default, it must be explicitly enabled using the no shutdown command.
Changes made in the Tunnel submode only take effect when the exited normally, using the exit command. Changes made in the Tunnel submode are discarded using the abort command.
Command Mode
Traffic Engineering RSVP Tunnel Configuration
Command Syntax
no shutdown
Parameters
-
The following example enables a tunnel.
switch(config-te-rsvp-tunnel-MyTunnel)# no shutdown
- The following example exits the tunnel and makes changes effective.
switch(config-te-rsvp-tunnel-MyTunnel)# exit switch(config-te-rsvp)#
- The following example discards changes.
switch(config-te-rsvp-tunnel-MyTunnel)# abort switch(config-te-rsvp)#
split-tunnel
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 adaptive split tunnels for the configuration-mode tunnel.
Command Mode
Traffic Engineering RSVP Tunnel Configuration
Command Syntax
split-tunnel (disabled | (min bandwidth_num bandwidth_units max bandwidth_num bandwidth_units [sub-tunnels limit max_tunnels] [reduction-delay time time_units] ) | (quantum bandwidth_num bandwidth_units [sub-tunnels limit max_tunnels] ))
no split-tunnel
default split-tunnel
- disabled - Disables adaptive split tunnels for the configuration-mode tunnel.
- min bandwidth_num units - Configures the minimum bandwidth for each sub-tunnel. Values range from 0.00 to 1000.00 and the units may be bps, kbps, mbps, or gbps.
- max bandwidth_num units - Configures the maximum bandwidth for each sub-tunnel. Values range from 0.00 to 1000.00 and the units may be bps, kbps, mbps, or gbps.
- sub-tunnels limit max_tunnels - Optionally limits the number of sub-tunnels to max_tunnels. Values range from 1 to 100. The default value is 10.
- reduction-delay time time_units - Optionally configures the amount of time before unused sub-tunnels are removed when traffic drops. Values range from 1 to 9999 and the units may be hours, minutes, or seconds. Default delay is 1 hour.
- quantum bandwidth_num units - Enables fixed-bandwidth sub-tunnels and specifies the bandwidth to reserve for each tunnel. Values range from 0.00 to 1000.00 and the units may be bps, kbps, mbps, or gbps.
- The following commands enable a maximum of 20 sub-tunnels with a bandwidth of 500 kilobits per second on RSVP tunnel
tunnel17
:switch(config-te-rsvp)#tunnel tunnel17 switch(config-te-rsvp-tunnel-tunnel17)#split-tunnel quantum 500 kbps sub-tunnels limit 20 switch(config-te-rsvp-tunnel-tunnel17)#
- The following commands enable a maximum of 75 adaptive sub-tunnels that can vary between 500 kilobits per second and 100 gigabits per second on RSVP tunnel
tunnel17
switch(config-te-rsvp)#tunnel tunnel17 switch(config-te-rsvp-tunnel-tunnel17)#split-tunnel min 500 kbps max 100 gbps sub-tunnels limit 75 switch(config-te-rsvp-tunnel-tunnel17)#
srlg
The srlg command specifies if link SRLGs of a primary LSP are to be considered as constraints while creating a fast-reroute bypass tunnel with either link or 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 that have the least number of SRLGs which are to be excluded 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 following commands enable SRLG processing:
switch(config)#mpls rsvp switch(config-mpls-rsvp)#srlg switch(config-mpls-rsvp)#
neighbor <IP> targeted
The neighbor <IP> targeted command is used to configure a targeted adjacency with a non-adjacent router from the LDP configuration mode. Both peers require the targeted adjacency configuration because a targeted adjacency is not accepted from an unknown LSR by default.
Command Mode
MPLS-LDP Configuration
Command Syntax
neighbor ip_address targeted
no neighbor ip_address targeted
default neighbor targeted
Parameter
ip_address - The IP address of the neighbor to establish a targeted adjacency with.
Examples
switch(config-mpls-ldp)# neighbor 5.5.5.5 targeted
timer recovery
This command will have a different behavior depending on the command mode (speaker or helper).
The timer recovery command configures the maximum accepted MPLS RSVP recovery time. This is the set maximum that will be used if the neighbor wants an even higher timer.
The no timer recovery and default timer recovery commands restore the maximum recovery timer value to its default. In speaker mode, the default maximum is 90 seconds. In helper mode, the default is to accept all maximum recovery time values.
Command Mode
- MPLS RSVP Graceful Restart Helper Configuration
- MPLS RSVP Graceful Restart Speaker Configuration
- MPLS RSVP Hitless Restart Configuration
Example to enter configuration mode:
graceful-restart role {helper | speaker}
Command Syntax
timer recovery numseconds
no timer recovery
default timer recovery
Helper Configuration Mode
timer recovery maximum <t> seconds - The maximum accepted recovery time value, configured under helper configuration mode.
default timer recovery maximum <t> seconds
no timer recovery maximum <t> seconds
Speaker Configuration Mode
timer recovery <t> seconds - The requested recovery time value is configurable under the speaker configuration mode.
- num - Maximum recovery time in seconds. Values range from 1 to 320. The default is 90 seconds in speaker mode.
Example
switch(config-mpls-rsvp-gr-speaker)#timer recovery 45 seconds
switch(config-mpls-rsvp-gr-speaker)#
timer restart
The timer restart command configures a maximum acceptable value for RSVP graceful restart timers received from RSVP neighbors. This is the set maximum that will be used if the neighbor wants an even higher timer.
The no timer restart and no timer restart commands restore the maximum restart time value to its default. In speaker mode, the default requested is 90 seconds. In helper mode, the default is to accept all maximum restart time values.
Command Mode
- MPLS RSVP Graceful Restart Helper Configuration
- MPLS RSVP Graceful Restart Speaker Configuration
- MPLS RSVP Hitless Restart Configuration
Example to enter configuration mode:
graceful-restart role {helper | speaker}
Command Syntax
Helper Configuration
timer restart maximum <t> seconds - The maximum accepted restart time value is configurable under helper configuration mode.
default timer restart maximum <t> seconds
no timer restart maximum <t> seconds
Speaker Configuration
timer restart <t> seconds - The restart time value is configurable under the speaker configuration mode.
default timer restart <t> seconds
no timer restart <t> seconds
timer recovery <t> seconds - The recovery time value is configurable under the speaker configuration mode.
- num - Maximum accepted recovery time in seconds. Values range from 1 to 320. The default is 90 seconds in speaker mode.
Example
switch(config-mpls-rsvp-gr-speaker)#timer restart 45 seconds
switch(config-mpls-rsvp-gr-speaker)#
traffic-engineering srlg
The traffic-engineering srlg command configures a shared risk link group (SRLG) for the command-mode interface.
The no traffic-engineering srlg and default traffic-engineering srlg commands remove the SRLG configuration from the interface.
Command Mode
Interface Configuration
Command Syntax
traffic-engineering srlg (srlg_name|srlg_group_ID)
no traffic-engineering srlg (srlg_name|srlg_group_ID)
default traffic-engineering srlg (srlg_name|srlg_group_ID)
name
- srlg_name - Name of the SRLG.
- srlg_group_ID - Group ID of the SRLG. Values range from 0 to 4294967295.
Example
switch(config)#interface ethernet 1/1
switch(config-if-Et1/1)#traffic-engineering srlg 29975
switch(config-if-Et1/1)#
tunnel
The tunnel command enters Traffic Engineering RSVP 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 peer-to-multipeer (p2mp) mode.
Command Mode
Traffic Engineering RSVP Configuration
Command Syntax
tunnel name [p2mp]
no tunnel name [p2mp]
default tunnel name [p2mp]
Parameters
p2mp - Places the tunnel into peer-to-multipeer (p2mp) mode.
Example
switch(config-te-rsvp)# tunnel MyTunnel
switch(config-te-rsvp-tunnel-MyTunnel)#
tunneling ldp
LDP over RSVP is configured by enabling the tunneling ldp command. When enabled, the tunneling ldp command causes the RSVP tunnel to become eligible for LDP over RSVP.
To disable LDP over RSVP on the tunnel use the default tunneling command.
Command Mode
Traffic Engineering RSVP Tunnel Configuration
Command Syntax
tunneling ldp
Parameters
Example
switch(config-te-rsvp-tunnel-MyTunnel)# tunneling ldp
tunneling ldp ucmp
The tunneling ldp ucmp command configures UCMP with LDP over RSVP.
Command Mode
RSVP tunnel configuration mode
Command Syntax
tunneling ldp ucmp
Parameter
bandwidth 20 gbps - The bandwidth configured on the RSVP tunnel determines the weight associated with this tunnel when traffic to the tunnel endpoint is UCMP load balanced.
bandwidth signalling disabled - The bandwidth configured on RSVP tunnels is both signalled and used as the UCMP weight. Use this command, to specify bandwidths on RSVP tunnels to be used only as the UCMP weight without signalling the bandwidths in RSVP.
Examples
- The following example configures a targeted adjacency with a non-adjacent router.
switch(config-te-rsvp-tunnel-tunnelABC)# tunneling ldp ucmp
- The following example configures the RSVP tunnel bandwidth.
switch(config-te-rsvp-tunnel-tunnelABC)#bandwidth 20 gbps
- The following example disables signalling.
switch(config-te-rsvp-tunnel-tunnelABC)#bandwidth signalling disabled