show mpls te tunnel
Displays MPLS tunnel data for a specific tunnel or for all tunnels.
Syntax: show mpls te tunnel [default | parameter-set name | parameter-set-names | lsp [tunnel-name] | name tunnel-name]
default
|
Displays the system tunnel defaults.
|
parameter-set name
|
Displays the specified parameter set.
|
parameter-set-names
|
Displays names of parameter sets.
|
lsp [tunnel-name]
|
Displays LSP information for all tunnels or the specified tunnel.
|
name tunnel-name
|
Displays the specified tunnel.
|
Description: Use the show mpls te tunnel default command to display the attributes of the default tunnel.
Use the show mpls te tunnel parameter-set command to display all parameter sets or a specified parameter-set.
Use the show mpls te tunnel parameter-set-names command to display the names of all configured parameter sets.
Use the show mpls te tunnel lsp command to display the LSPs originating at this router.
Use the show mpls te tunnel name command to display the attributes of the specified tunnel.
Factory Default: None.
Command Mode: Executive.
Example 1: In the following example, the show mpls te tunnel default command displays the default tunnel:
router#show mpls te tunnel default
tunnel default
resilience pacing 0ms
[default jitter 0-0ms]
adaptivity periodic 0ms
[default jitter 0-0ms]
|
- The following table describes fields in the display:
Table 1-20. Fields Displayed by show mpls te tunnel default
| Field
|
Description
|
resilience
|
The resilience attribute determines how a tunnel responds when a network resource, that is in use by the tunnel, fails. There are 4 resilience methods: disabled, pacing, sorted-pacing and linear.
|
default jitter
|
Specifies a percentage the resilience timer is offset to prevent the establishment of many LSPs at the same time.
|
adaptivity
|
The adaptivity attribute determines how a tunnel responds when new network resources become available or when resource parameters change such that "better" paths become available. There are 4 adaptivity methods: disabled, pinned, periodic, and linear.
|
default jitter
|
Specifies a percentage the adaptivity timer is offset to prevent the establishment of many LSPs at the same time.
|
Example 2: In the following example, the show mpls te tunnel parameter-set command displays configured parameter sets:
router#show mpls te tunnel parameter-set
tunnel parameter-set test
bandwidth 1200.0000m
holding-priority 2
reserving-priority 2
exclude-administrative-color blue
color name "blue" bit 3
exclude colormask= 0x00000008
|
- The following table describes fields in the display:
Table 1-21. Fields Displayed by show mpls te tunnel parameter set
| Field
|
Description
|
bandwidth
|
Configured bandwidth for this tunnel
|
holding-priority
|
Priority used when protecting this tunnel from preemption by other tunnels. Valid values are 0 (highest) to 7 (lowest).
|
reserving priority
|
Priority used when setting up this tunnel. Valid values are 0 (highest) to 7 (lowest).
|
exclude colormask
|
Specifies the administrative color(s) included in this tunnel.
|
color name/bit
|
Specifies an administrative color name. and the bit position to which this color name is mapped. Valid range for bit positions is 0 to 31.
|
include colormask
|
Specifies the administrative color(s) included in this tunnel.
|
color name/bit
|
Specifies an administrative color name. and the bit position to which this color name is mapped. Valid range for bit positions is 0 to 31.
|
Example 3: In the following example, the show mpls te tunnel parameter-set-names command displays the names of all the configured parameter sets:
router#show mpls te tunnel parameter-set-names
tunnel parameter-set test
|
- The following table describes fields in the display:
Table 1-22. Fields Displayed by show mpls te tunnel parameter set names
| Field
|
Description
|
Current LSP
|
|
Configured as:
|
Indicates if tunnel is configured as shortcut (configured to accept traffic as soon as the tunnel configuration is complete) or no-traffic.
|
egress router:
|
IP address of egress router for this LSP.
|
LSP id:
|
LSP ID.
|
LSP state:
|
Valid states are:
- init = Initialization.
- nopath = SPF not successful or complete.
- haspath = SPF computed, LSP not yet up.
- up = LSP is up. When state = up:
- - param change pending = tunnel parameter changes have been signalled.
- - param change failed = signalling to change tunnel parameters has failed.
- (routes installed) = labels installed, LSP can route traffic.
- (no routes installed) = LSP is configured as "notraffic".
- (lsdb path lost) = LSP is up, unable to reach egress, will be taken down in 30 seconds.
- request rejected by RSVPd = There is an LSDB path. The LSP has never come up. Either there was no response or an error message was received by RSVP.
- broken = The LSP was up and went down because of an RSVP signalling failure.
|
computed cost:
|
Cost of LSP = metric used to determine which routes are mapped onto LSP.
|
work list:
|
Valid values are:
- idle = Nothing.
- check spf = Need to check if a new SPF is needed.
- needs spf = SPF check completed. A new SPF is needed.
- rerun spf = Need to rerun SPF (SPF not scheduled).
- refine spf = look in cache, find and use link. If metrics don't match exactly, run a refined SPF.
- recompute = an SPF has been scheduled.
- reinit = unable to route LSP. RSVP not up.
|
Current Parameters
|
bandwidth:
|
Configured bandwidth for this LSP.
|
priority:
|
hold = the priority used when protecting this tunnel from preemption by other tunnels. resv = the priority used when setting up this tunnel.
|
include colormask
|
Specifies the administrative color(s) included in this LSP.
|
exclude colormask
|
Specifies the administrative color(s) excluded from this LSP.
|
metric:
|
Indicates a relative preference between this tunnel and other routes. There are two types of tunnel metric: absolute and relative.
|
RSVP Signalling for Current LSP:
|
tunnel id:
|
Shorthand tunnel ID.
|
ext. tunnel id.
|
Extended tunnel ID.
|
src addr:
|
Source address for this LSP.
|
out interface:
|
Outbound interface for this LSP.
|
label:
|
Label applied to outbound traffic on this interface.
|
outsegment:
|
Outsegment ID.
|
next hop:
|
IP address of the next hop in the tunnel.
|
reservation style:
|
SE = shared explicit
FF = fixed filter
|
requested explicit route:
|
Requested explicit route from this router to the egress for this LSP.
|
recorded route:
|
Recorded route from this router to the egress LSP.
|
Example 4: In the following example, the show mpls te tunnel lsp tunnel-name command displays LSP information about tunnel tsr701:
router#show mpls te tunnel lsp tsr701
Tunnel Name: to11
Primary LSP
configured as: shortcut
Primary LSP id 72 created: 2001/10/23 09:57:51
state: "up" (routes installed, protected)
egress router: 192.11.11.11
Path list: 212.1.0.20 210.1.0.13 204.1.0.19 201.1.0.11
computed cost: 4
work list: recompute (priority 4)
Current Parameters
bandwidth: 0.000 mbit/s priority: hold 7, resv 7
include colormask: 0x00000000
require colormask: 0x00000000
exclude colormask: 0x00000000
metric: relative 0
Backup LSP
Backup LSP 72 (for LSP 72) created: 2001/10/23 09:57:54
state: "up" (backup)
egress router: 192.11.11.11
Router-id used for fast reroute: 192.128.14.1
Merge node: 192.19.19.19
Path list: 214.1.0.17 217.1.0.16 203.1.0.19 201.1.0.11
computed cost: 4
work list: idle (priority 1)
Current Parameters
bandwidth: SPF 0.000 mbit/s, signaled 0.000 mbit/s
priority: hold 7, resv 7
include colormask: 0x00000000
require colormask: 0x00000000
exclude colormask: 0x00000000
metric: relative 0
|
RSVP Signaling For Current LSP:
Tunnel name: backup:to11
tunnel id: 2 ext. tunnel id: 192.14.14.14
src addr: 192.128.14.1
out interface: POS 1/1/1 label: 32766
outsegment: 120
next hop: 214.1.0.17 reservation style: SE
requested explicit route:
214.1.0.17
217.1.0.16
203.1.0.19
recorded route:
214.1.0.17 ( None None ) unprotected
217.1.0.16 ( None None ) unprotected
203.1.0.19 ( None None ) unprotected
Tunnel name: to11
tunnel id: 2 ext. tunnel id: 192.14.14.14
src addr: 192.14.14.14
out interface: POS 1/3/1 label: 32767
outsegment: 8
next hop: 212.1.0.20 reservation style: SE
requested explicit route:
212.1.0.20
210.1.0.13
204.1.0.19
201.1.0.11
192.11.11.11
recorded route:
212.1.0.20 (platform-label 32767 ) protected
210.1.0.13 (platform-label 32767 ) protected
204.1.0.19 (platform-label 32763 ) protected
201.1.0.11 (platform-label 32766 ) unprotected
|
- The following table describes fields in the display:
Table 1-23. Fields Displayed by show mpls te tunnel lsp
| Field
|
Description
|
Primary or backup LSP ID
|
Specifies the LSP ID for this primary or backup
|
configured as:
|
Specifies primary LSP configuration type
|
Created
|
Date and time when this tunnel was configured.
|
state:
|
Valid states are:
- init = Initialization.
- nopath = SPF not successful or complete.
- haspath = SPF computed, LSP not yet up.
- up = LSP is up. When state = up:
- - param change pending = tunnel parameter changes have been signalled.
- - param change failed = signalling to change tunnel parameters has failed.
- (routes installed) = labels installed, LSP can route traffic.
- (no routes installed) = LSP is configured as "notraffic".
- (lsdb path lost) = LSP is up, unable to reach egress, will be taken down in 30 seconds.
- request rejected by RSVPd = There is an LSDB path. The LSP has never come up. Either there was no response or an error message was received by RSVP.
broken = The LSP was up and went down because of an RSVP signalling failure.
|
egress router
|
Specifies the ID for the egress of this LSP
|
Path list
|
Specifies the router IDs for this path
|
computed cost
|
Specifies the cost for this path
|
work list
|
Specifies the next scheduled SPF action and its priority.
|
bandwidth
|
Reserved bandwidth for tunnel.
|
holding-priority
|
Priority used when protecting this tunnel from preemption by other tunnels. Valid values are 0 (highest) to 7 (lowest).
|
reserving-priority
|
Priority used when setting up this tunnel. Valid values are 0 (highest) to 7 (lowest).
|
include color mask
|
Specifies the include color mask for LSP or backup path
|
exclude color mask
|
Specifies the exclude color mask for LSP or backup path
|
metricSystem Defaults:
|
Specifies the TE metric value
|
RSVP signaling
|
Specifies RSVP related tunnel information information
|
Tunnel name
|
Specifies the tunnel name of primary or backup
|
Tunnel ID
|
IPriori assigned tunnel ID
|
Ext. tunnel ID
|
Specifies ingress router ID for this tunnel
|
src address
|
Specifies the source address for this tunnel
|
out interface
|
Specifies this tunnels exit interface for this router
|
label
|
Internal interface label
|
next hop
|
The router ID for the next hop for this path
|
requested explicit route
|
Any explicitly configured router IDs for this route
|
recorded route:
|
Actual RSVP recorded route for this path
|
Example 5: In the following example, the show mpls te tunnel name tunnel-name command displays information about the specified tunnel:
router#show mpls te tunnel name t-1
tunnel t-1
Created 2004/04/08 10:28:23
last: up 2004/04/08 10:33:02 down 2004/04/08 12:51:15
change (never) reroute (never)
cumulative: up 8293.202s down 195.289s
num: setups 1 change attempts 0 changes 0
manual resets 0 reroute attempts 1 reroutes 0
down 1 preemptions 0 path lost 1
Primary LSP id 3600 created: 2004/04/08 10:31:36
state: "broken" (routes installed, lsdb path lost, unprotected)
egress router: 192.4.4.4 (192.4.4.4)
Path list:
201.14.1.4 (192.4.4.4)
computed cost: 1
work list: recompute (priority 4)
Current Parameters
attribute-priority: 0
bandwidth: 0.000 mbit/s priority: hold 7, resv 7
include colormask: 0x00000000
require colormask: 0x00000000
exclude colormask: 0x00000000
metric: absolute 1
|
- The following table describes fields in the display:
Table 1-24. Fields Displayed by show mpls te tunnel name
| Field
|
Description
|
Created
|
Date and time when this tunnel was configured.
|
last
|
Date and time the tunnel was last used to route traffic, the number of times the tunnel has been torn down, changed, or rerouted.
|
cumulative up/down
|
Total Number of seconds this tunnel has been up or down from the time it was first configured.
|
setups:
|
Number of times this tunnel has been set up.
|
change attempts:
|
Number of times attempts have been made to modify this tunnel.
|
changes:
|
Number of times this tunnel has been modified.
|
manual resets:
|
Number of times this tunnel has been cleared manually (using the CLI).
|
reroute attempts:
|
Number of times attempts to reroute this tunnel.
|
reroutes:
|
Number of successful reroutes.
|
down
|
Number of times this tunnel has been torn down.
|
preemptions:
|
Number of times this tunnel has been preempted.
|
path lost:
|
Number of times the lsdb path was lost while the tunnel was still up from the view of RSVP signalling.
|
Primary or Backup LSP id nnn:
|
LSP ID.
|
state:
|
Valid states are:
- init = Initialization.
- nopath = SPF not successful or complete.
- haspath = SPF computed, LSP not yet up.
- up = LSP is up. When state = up:
- - param change pending = tunnel parameter changes have been signalled.
- - param change failed = signalling to change tunnel parameters has failed.
- (routes installed) = labels installed, LSP can route traffic.
- (no routes installed) = LSP is configured as "notraffic".
- (lsdb path lost) = LSP is up, unable to reach egress, will be taken down in 30 seconds.
- request rejected by RSVPd = There is an LSDB path. The LSP has never come up. Either there was no response or an error message was received by RSVP.
- broken = The LSP was up and went down because of an RSVP signalling failure.
|
routes installed:
|
yes = labels are installed.
no = labels are not installed.
|
last up/down/change
|
Date and time LSP was last used to route traffic, the number of times the tunnel has been torn down, changed, or rerouted.
|
elapsed up/down:
|
Number of seconds this LSP has been up or down.
|
down:
|
Number of times this LSP has been taken down.
|
setups:
|
Number of times this LSP has been set up.
|
change attempts;
|
Number of attempts to modify this LSP.
|
changes:
|
Number of successful attempts to modify this LSP
|
SPF recomputed;
|
Number of times the SPF has been recomputed for this LSP
|
SPF successful
|
Number of times an SPF was successfully recomputed for this LSP.
|
next SPF:
|
Next time the SPF for this LSP is scheduled to be recomputed.
|
next reroute:
|
Next time this LSP is scheduled to be rerouted.
|
egress router
|
IP address of the egress LSR.
|
Pathlist
|
Specifies LSP or backup path interfaces
|
Computed cost
|
Specifies total cost of LSP or Path
|
worklist
|
Specifies the next action to be performed along with its priority
|
bandwidth
|
Reserved bandwidth for tunnel.
|
holding-priority
|
Priority used when protecting this tunnel from preemption by other tunnels. Valid values are 0 (highest) to 7 (lowest).
|
reserving-priority
|
Priority used when setting up this tunnel. Valid values are 0 (highest) to 7 (lowest).
|
include color mask
|
Specifies the include color mask for LSP or backup path
|
exclude color mask
|
Specifies the exclude color mask for LSP or backup path
|
metric
|
Specifies the TE metric value
|
local protect inuse routers
|
Specifies the IP address of any routers inuse for local protect
|
Configuration:
|
shortcut/notraffic
|
shortcut = accept traffic as soon as the tunnel configuration is complete.
notraffic = configure the tunnel, but send no traffic into the tunnel.
|
egress
|
IP address of the egress LSR.
|
System Defaults:
|
Local protect
|
Specifies current local protect setting
|
send-fast-reroute
|
Specifies current send-fast-reroute setting
|
resilience
|
Resilience determines how a tunnel responds when a network resource in use by the tunnel, fails. There are 4 resilience methods: disabled, pacing, sorted-pacing and linear.
|
default jitter
|
Specifies a percentage the resilience timer is offset to prevent the establishment of many LSPs at the same time.
|
adaptivity
|
Adaptivity determines how a tunnel responds when new network resources become available or when resource parameters change such that "better" paths become available. There are 4 adaptivity methods: disabled, pinned, periodic, and linear.
|
default jitter
|
Specifies a percentage the adaptivity timer is offset to prevent the establishment of many LSPs at the same time.
|
protect-resilience
|
Specifies the protect-resilience setting for this backup path
|
protect-adaptivity
|
Specifies the protect-adaptivity configuration for this backup path
|
inuse-resilience
|
Specifies the inuse-resilience setting for this primary LSP
|
protect-tolerance
|
Specifies the protect tolerance configuration
|
Factory Defaults:
|
bandwidth
|
Specifies the SPF bandwidth for the backup path
|
holding-priority
|
Specifies the holding priority for this LSP or backup path
|
reserving-priority
|
Specifies the reserving priority for this LSP or backup path
|
min-retry-delay
|
Minimum time between a failure to create an LSP and the next attempt.
|
max-retry-delay
|
Maximum time between a failure to create an LSP and the next attempt.
|
max-attempts
|
Maximum number of attempts to set up an LSP.
|
backoff factor
|
When an attempt to establish an LSP fails, the path retry delay is incremented by a "backoff factor". The path retry delay is incremented after each failed attempt up to the value defined by the max-retry-delay command.
|
min-teardown-delay
|
Time to wait to allow all traffic in the LSP to drain before tearing down the LSP.
|
metric
|
Relative preference between this tunnel and other routes.
|
metric bias
|
Specifies the metric bias for this LSP
|
node-disjoint
|
Determines whether the immediate downstream node is considered during backup path calculation
|
protect-bandwidth spf
|
Specifies the percentage of SPF bandwidth to be used during the spf calculation at the PLR
|
protect-max-hops
|
Specifies the number of midpoint hops allowable for a backup path
|
Related Commands: show mpls te
show mpls te path-list
