Displays detailed information about a specific LSP.
This command operates under all modes.
The sample history displays for the current adjustment interval.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see "Supported Hardware".
This command can display the underflow-limit parameter and the number of consecutive underflows. The adjustment-threshold is used from the global table is indicated with the value for current rate. The show mpls lsp extensive command shows the adjustment event with the previous rate and the maximum sampled rate.
The show mpls lsp command displays the following information:
| Output field | Description |
|---|---|
| Name | The name of the LSP. LSPs are displayed in alphabetical order. |
| To | The egress LER for the LSP. |
| From | The LSPs source address, configured with the from command. When a source IP address has not been specified for the LSP with the from command, and the LSP has not been enabled, then '(n/a)' displays in the 'From' field. |
| admin | The administrative state of the LSP. Once the user activates the LSP with the enable command, the administrative state changes from DOWN to UP. |
| status | The operational state of the LSP. This field indicates whether the LSP has been established through signaling and is capable of having packets forwarded through it. When the status of the LSP is DOWN, the reason why the LSP is down is shown in parentheses. There maybe a short period of time after the user enables the LSP that the administrative state of the LSP is UP, but the status is DOWN. Once the LSP has been established through signaling, both the administrative state and the status is UP. |
| Tunnel interface (primary path) | The path currently selected for this LSP. |
| Times primary LSP goes up since enabled | The number of times the status of the LSPs primary path transitions from DOWN to UP. |
| Metric | The metric for the LSP, configured with the metric command. |
| Pri. path | The name of the primary path for this LSP and whether the path is currently active. |
| up | Displays if the primary path is UP. |
| active | Specifies if the primary path is active. |
| Setup priority | The configured setup priority for the LSP. |
| hold priority | The configured hold priority for the LSP. |
| Max rate | The maximum rate of packets that can go through the LSP (in kbps), set with the traffic-eng max-rate command. |
| mean rate | The average rate of packets that can go through the LSP (in kbps), set with the traffic-eng mean-rate command. |
| mode | Mode displays if the LSP is in monitor-only or monitor-and-signal mode. |
| adjustment threshold | Displays the configured adjustment-threshold value. |
| minimum bw | The configured minimum bandwidth. |
| maximum bw | The configured maximum bandwidth. |
| overflow limit | Displays the configured overflow-limit value. |
| underflow limit | The number of samples that have to be below the threshold, to trigger a premature adjustment. |
| sample-record | Whether the template is set to record the sample history. |
| Constraint-based routing enabled | Whether CSPF is in effect for the LSP. |
| Path calculated using constraint-based routing | Whether the explicit path used by the active path was calculated using the constraint-based routing. |
| Path calculated using interface constraint | Whether the explicit path used by the active path was calculated using the interface-based routing. |
| Path cost | The total cost of this path. |
| Tie breaking | The tie-breaking method CSPF uses to select a path from a group of equal-cost paths to the egress LER, set with the tie-breaking command. |
| LDP tunnel enabled | If LDP tunneling is enabled, the line reads "yes". If it is not enabled, the line reads "no". |
| Soft preemption enabled | Soft preemption minimizes traffic disruptions and gracefully reroutes the preempted LSPs. |
| Sec. path | The name of the secondary path for this LSP and whether the path is currently active. |
| active | Displays if the secondary path is active. |
| Hot-standby | Whether the secondary path is a hot-standby path. |
| status | The operational state of the secondary path |
| Setup priority | The configured setup priority for the LSP. |
| hold priority | The configured hold priority for the LSP |
| Max rate | The maximum rate of packets that can go through the LSP (in kbps), set with the traffic-eng max-rate command. |
| mean rate | The average rate of packets that can go through the LSP (in kbps), set with the traffic-eng mean-rate command. |
| max burs | The maximum size (in bytes) of the largest burst the LSP can send at the maximum rate, set with the traffic-eng max-burst command. |
| mode | Mode shows if the LSP is in monitor-only or monitor-and-signal mode. |
| adjustment threshold | Displays the configured adjustment-threshold value. |
| minimum bw | The configured minimum bandwidth. |
| maximum bw | The configured maximum bandwidth. |
| overflow limit | Displays the configured overflow-limit value. |
| underflow limit | The number of samples which must be below the threshold to trigger a premature adjustment. |
| sample-record | Whether the template is set to record the sample history. |
| Constraint-based routing enabled | Whether CSPF is in effect for the LSP. |
| hop limit | The maximum number of hops a path calculated by CSPF can have, set with the hop-limit command. |
| Soft preemption enabled | Soft preemption minimizes traffic disruptions and gracefully reroutes the preempted LSPs |
| Active path attributes | |
| Tunnel interface | The MPLS tunnel interface port ID. |
| outbound interface | The outbound label used by the active path of the LSP. |
| Tunnel index | The tunnel index for the active path of the LSP. |
| Tunnel instance | |
| outbound label | The outbound label used by the active path of the LSP. |
| Auto-bandwidth running info mode | |
| adjustment interval | Displays the configured adjustment-timer value. |
| adjustment threshold | Displays the configured adjustment-threshold value. |
| overflow limit | Displays the configured overflow-limit value. |
| underflow limit | The number of samples that must be below the threshold to trigger a premature adjustment. |
| minimum bw | The configured minimum bandwidth. |
| maximum bw | The configured maximum bandwidth. |
| Samples collected | Number of samples collected so far in the current adjustment-interval. |
| max sampled bw | The maximum number of the samples collected so far in the current adjustment-interval. |
| last sample | The last sampled-bandwidth. |
| Sample-record | Whether the template is set to record the sample history. |
| adjustment due in | Displays the time remaining for the current adjust-interval to expire. |
| Adjustment ignored | This consecutive number of times the adjustment was ignored due to any reason. |
| Current bandwidth | Current running bandwidth. |
| Recorded routes | The addresses recorded by the RECORD_ROUTE object during RSVP signaling. |
The following example shows the output of the command, specifying the LSP name with the extensive option.
device# show mpls bypass-lsp extensive
LSP my-bypass-lsp, to 20.20.20.20
From: 29.29.29.29, admin: UP, status: UP, tunnel interface(primary path): tnl3
Times primary LSP goes up since enabled: 1
Adaptive
Primary path: path-for-bypass-lsp, up: yes, active: yes
Maximum retries: None, no. of retries: 0
ReoptimizeTimer configured 360
ReoptimizeTimer next expiration in 93 seconds
Setup priority: 7, hold priority: 0, cos: 3
Max rate: 1000 kbps, mean rate: 1000 kbps, max burst: 5000 bytes
Tie breaking: random, hop limit: 6
Exclude any of admin groups: 15 16 17
Exclude interface(s): Eth 1/3
CSPF-computation-mode configured: te-metric
Constraint-based routing enabled: yes
Path calculated using constraint-based routing: yes
Path calculated using interface constraint: no
Path calculated using te-metric
Path cost: 2
Explicit path hop count: 1
18.18.18.18(S)
Recorded routes:
Protection codes/Rtr Id flags: P: Local N: Node B: Bandwidth I: InUse R: RtrId
18.29.1.18 -> 18.20.1.20
Bypass Tunnel bandwidth
Maximum bandwidth: 1000 kbps
Reservable bandwidth [priority] kbps:
[0] 1000 [1] 1000 [2] 1000 [3] 1000
[4] 1000 [5] 1000 [6] 1000 [7] 1000
Current signaled rate: 1000 kbps
Active Path:
Tunnel interface: tnl3, outbound interface: Eth 1/1
Tunnel index: 3, Tunnel instance: 1, Out label: 2061
History:
0 10-13 22:41:58 : LSP tunnel is Enabled
1 10-13 22:41:58 : CSPF-Computation successful for Primary path path-for-bypass-lsp. Computed route:
->18.29.1.18->18.20.1.20
2 10-13 22:41:58 : Primary path path-for-bypass-lsp. RRO received:
->18.29.1.18->18.20.1.20
3 10-13 22:41:58 : Primary path path-for-bypass-lsp setup successful . Instance id 1
4 10-13 22:41:58 : LSP tunnel is UP with Primary path path-for-bypass-lsp as Active
5 10-13 22:41:58 : Tunnel added or updated, out-interface: Eth 1/1, out-label 2061
Riding Backup Lsps: 1
Ingress backups: 1, up: 1, active: 0
Transit backups: 0, up: 0, active: 0
Ingress backups
State From To LSPname
UP 18.29.1.29 20.20.20.20 my-fac-bkup-frr-lsp
The following example displays the output of the command when using the detail option.
Router# show mpls lsp extensive
LSP lsp1, to 23.23.23.23
From: 34.34.34.34, admin: UP, status: UP, tunnel interface(primary path): tnl1
Times primary LSP goes up since enabled: 1
Metric: 0, Adaptive
Maximum retries: NONE, no. of retries: 0
Pri. path: NONE, up: yes, active: yes
Setup priority: 7, hold priority: 0
Max rate: 0 kbps, mean rate: 0 kbps, max burst: 0 bytes
Auto-bandwidth. template: template1, mode: monitor-only
adjustment interval: 86400 sec, adjustment threshold: 0
minimum bw: 0 kbps, maximum bw: 2147483647 kbps
overflow limit: 0, underflow limit: 20, sample-record: disabled
Constraint-based routing enabled: yes
Path calculated using constraint-based routing: yes
Path calculated using interface constraint: no
Path cost: 20
Tie breaking: random, hop limit: 0
LDP tunneling enabled: no
Soft preemption enabled: no
Sec. path: via16, active: no
Hot-standby: no, status: down, adaptive
Setup priority: 7, hold priority: 0
Max rate: 0 kbps, mean rate: 0 kbps, max burst: 0 bytes
Auto-bandwidth. template: NONE, mode: monitor-and-signal
adjustment interval: 300 sec, adjustment threshold: Table
minimum bw: 0 kbps, maximum bw: 2147483647 kbps
overflow limit: 5, underflow-limit: 10, sample-record: enabled
Constraint-based routing enabled: yes
hop limit: 0
Soft preemption enabled: no
Active Path attributes:
Tunnel interface: tnl1, outbound interface: e4/3
Tunnel index: 2, Tunnel instance: 1 outbound label: 2049
Auto-bandwidth running info. Mode: monitor-only
adjustment interval: 1200 sec(T), adjustment threshold: Table(T)
overflow limit: 0, underflow limit: 3
minimum bw: 0 kbps(T), maximum bw: 9647 kbps(T)
Samples collected: 14, max sampled bw: 0 kbps, last sample: 0 kbps
Overflow-count: 0, Underflow-count: 2,max-underflow-sample: 34kbps
Sample-record: enabled(T)
adjustment due in 1174 seconds
Adjustment ignored: 0 time(s)
No adjustment since activation. Current bandwidth: 0 kbps
Recorded routes:
Protection codes/Rtr Id flag: P: Local N: Node B: Bandwidth I: InUse R: RtrId
31.31.31.16 -> 161.161.161.1
The following output displays the command with the autobw-samples option.
device# show mpls lsp name lsp1 autobw-samples
LSP lsp1, to 23.23.23.23
From: 34.34.34.34, admin: UP, status: UP, tunnel interface(primary path): tnl1
Times primary LSP goes up since enabled: 1
Metric: 0, Adaptive
Maximum retries: NONE, no. of retries: 0
Pri. path: NONE, up: yes, active: yes
Setup priority: 7, hold priority: 0
Max rate: 0 kbps, mean rate: 0 kbps, max burst: 0 bytes
Auto-bandwidth. template: template1, mode: monitor-only
adjustment interval: 86400 sec, adjustment threshold: 0
minimum bw: 0 kbps, maximum bw: 2147483647 kbps
overflow limit: 0, underflow limit: 20, sample-record: disabled
Constraint-based routing enabled: yes
Path calculated using constraint-based routing: yes
Path calculated using interface constraint: no
Path cost: 20
Tie breaking: random, hop limit: 0
LDP tunneling enabled: no
Soft preemption enabled: no
Sec. path: via16, active: no
Hot-standby: no, status: down, adaptive
Setup priority: 7, hold priority: 0
Max rate: 0 kbps, mean rate: 0 kbps, max burst: 0 bytes
Auto-bandwidth. template: NONE, mode: monitor-and-signal
adjustment interval: 300 sec, adjustment threshold: Table
minimum bw: 0 kbps, maximum bw: 2147483647 kbps
overflow limit: 5, underflow-limit: 10, sample-record: enabled
Constraint-based routing enabled: yes
hop limit: 0
Soft preemption enabled: no
Active Path attributes:
Tunnel interface: tnl1, outbound interface: e4/3
Tunnel index: 2, Tunnel instance: 1 outbound label: 2049
Auto-bandwidth running info. Mode: monitor-only
adjustment interval: 1200 sec(T), adjustment threshold: 3000(A)
overflow limit: 0, underflow limit: 4
minimum bw: 0 kbps(T), maximum bw: 9647 kbps(T)
Samples collected: 5, max sampled bw:6598 kbps,last sample: 0 kbps
Overflow-count: 0, Underflow-count: 2,max-underflow-sample: 34kbps
Sample-record: enabled(T)
adjustment due in 1174 seconds
Adjustment ignored: 0 time(s)
No adjustment since activation. Current bandwidth: 0 kbps
Recorded routes:
Protection codes/Rtr Id flag: P: Local N: Node B: Bandwidth I: InUse R: RtrId
31.31.31.16 -> 161.161.161.1
Auto Bandwidth Sample History:
1 Feb 4 19:56:06 : Path p1 active with rate 3000 kbps
2 Feb 4 19:57:06 : 4445 kbps
3 Feb 4 19:58:06 : 4855 kbps
4 Feb 4 19:59:06 : 4501 kbps
5 Feb 4 20:00:06 : 4200 kbps
6 Feb 4 20:01:06 : 4455 kbps
7 Feb 4 20:02:06 : 4319 kbps
8 Feb 4 20:03:06 : 4299 kbps
9 Feb 4 20:04:06 : 4582 kbps
10 Sample recording disabled
11 Feb 4 20:16:31 : 3630 kbps
12 Feb 4 20:17:31 : 2924 kbps
13 Feb 4 20:17:38 : Rate adjusted from 2500 to 4500 kbps
Reason: Adjustment-interval expiry
14 Feb 4 20:18:06 : 4500 kbps
15 Feb 4 20:19:06 : 4500 kbps
16 Feb 4 20:20:06 : 4500 kbps
17 Feb 4 20:21:06 : 4500 kbps
18 Feb 4 20:16:31 : 4500 kbps
19 Feb 4 20:17:31 : 4500 kbps
20 Feb 4 20:17:38 : Adjustment ignored. Threshold not crossed
21 Feb 4 20:16:31 : 9000 kbps
22 Feb 4 20:17:31 : 9000 kbps
23 Feb 4 20:17:38 : Rate adjusted from 4500 to 9000 kbps
Reason: Overflow limit exceeded
24 Feb 4 20:18:06 : 4500 kbps
25 Feb 4 20:19:06 : 4500 kbps