show mpls container-lsp
Syntax
show mpls container-lsp <brief | detail | extensive | terse> <count-active-routes> <defaults> <descriptions> <down | up> <egress> <ingress> <logical-system (all | logical-system-name)> <name name> <statistics> <transit> <unidirectional>
Description
Display information about configured and active Multiprotocol Label Switching (MPLS) container label-switched paths (LSPs).
Options
| none | Display standard information about all configured and active member LSPs of the container LSP. |
| brief | detail | extensive | terse | (Optional) Display the specified level of output. The extensive option displays the same information as the detail option, but covers the most recent 50 events. |
| count-active-routes | (Optional) Show active routes for the container LSP. |
| defaults | (Optional) Display the default settings of the container LSP. |
| descriptions | (Optional)
Display the container LSP descriptions. To view this information,
you must configure the description statement at the |
| down | up | (Optional) Display only LSPs that are inactive or active, respectively. |
| egress | (Optional) Display the LSPs ending at this device. Note:
The |
| ingress | (Optional) Display the member LSPs originating from this device. |
| logical-system (all | logical-system-name) | (Optional) Perform this operation on all logical systems or on a particular logical system. |
| name name | (Optional) Display information about the specified LSP or group of LSPs. |
| statistics | (Optional) Display accounting information about LSPs. Statistics are not available for LSPs on the egress routing device, because the penultimate routing device in the LSP sets the label to 0. Also, as the packet arrives at the egress routing device, the hardware removes its MPLS header and the packet reverts to being an IPv4 packet. Therefore, it is counted as an IPv4 packet, not an MPLS packet. |
| transit | (Optional) Display LSPs transiting this routing device. |
| unidirectional | (Optional) Display unidirectional LSP information. |
Required Privilege Level
view
Output Fields
Table 1 describes the output fields for the show mpls container-lsp command. Output fields are listed in the approximate order in which
they appear.
Field Name |
Field Description |
Level of Output |
|---|---|---|
|
Information about the member LSPs on the ingress routing device. Each LSP has one line of output. |
All levels |
|
Name of the container LSP. |
All levels |
|
Number of member LSPs in the container LSP. |
All levels |
|
Destination (egress routing device) of the session. |
brief |
|
Source (ingress routing device) of the session. |
brief detail |
|
State of the LSP handled by this RSVP session:
|
brief detail |
|
Number of active routes (prefixes) installed in the routing table. For ingress RSVP sessions, the routing table is the primary IPv4 table (inet.0). For transit and egress RSVP sessions, the routing table is the primary MPLS table (mpls.0). |
brief |
|
Path. An asterisk (*) underneath this column indicates that the LSP is a primary path. |
brief |
|
(Ingress LSP) Name of the active path: Primary or Secondary. |
detail extensive |
|
Name of the member LSP. |
brief detail |
|
Information about the LSPs on the egress routing device. MPLS learns this information by querying RSVP, which holds all the transit and egress session information. Each session has one line of output. |
All levels |
|
Number of LSPs on the transit routing devices and the state of these paths. MPLS learns this information by querying RSVP, which holds all the transit and egress session information. |
All levels |
|
Minimum number of member LSPs. Default: 1 |
extensive |
|
Number of member LSPs that the container LSP can have at maximum. Default: 64 (due to ECMP limit) |
extensive |
|
Sum of the bandwidths of all member LSPs. |
extensive |
|
Duration between two normalization events. When not configured, 21600 seconds (6 hours) is set as the default value. |
extensive |
|
Change in aggregate LSP utilization to trigger splitting or merging expressed in percentage. |
extensive |
|
Maximum bandwidth used to signal LSPs after a normalization event. Default value is 0 bps. When not configured, the value is inherited from the splitting bandwidth configuration. Note:
Between two normalization events, when auto-bandwidth adjustment happens, the per-LSP auto-bandwidth configuration and thresholds are used, instead of the maximum signaling bandwidth threshold. |
extensive |
|
Minimum bandwidth used to signal LSPs after a normalization event. Default value is 0 bps. When not configured, the value is inherited from the merging bandwidth configuration. Note:
Between two normalization events, when auto-bandwidth adjustment happens, the per-LSP auto-bandwidth configuration and thresholds are used, instead of the minimum signaling bandwidth threshold. |
extensive |
|
Bandwidth used for LSP splitting and merging. Default value is 0 bps. When not configured, the value is inherited from the auto-bandwidth maximum bandwidth configuration. |
extensive |
|
Bandwidth used for LSP splitting and merging. Default value is 0 bps. When not configured, the value is inherited from the auto-bandwidth minimum bandwidth configuration. |
extensive |
|
Type of LSP. |
extensive |
|
Loadbalanced bandwidth. |
extensive |
|
Minimum LSP bandwidth in bps related to auto-bandwidth. |
extensive |
|
Total amount of time in seconds allowed before LSP bandwidth adjustment take place. Range: 300 through 315360000 seconds |
extensive |
|
Current value of the actual maximum average bandwidth utilization in bps. |
extensive |
|
Threshold overflow limit. |
extensive |
|
Threshold underflow limit. |
extensive |
|
Setup priority and hold priority values. For setup priority, 0 and 7 is the highest and lowest priority, respectively. When not explicitly configured, 7 and 0 are set as the default values for the setup priority and hold priority, respectively. |
extensive |
|
Time in seconds allowed before path reoptimization. |
extensive |
|
Computed explicit route. A series of hops, each with an address followed by a hop indicator. The value of the hop indicator can be strict (S) or loose (L). |
extensive |
|
Received record route. RRO is a series of hops, each with an address followed by a flag. In most cases, the received RRO is the same as the computed ERO. If the received RRO is different from the computed ERO, there is a topology change in the network, and the route is taking a detour. The following flags identify the protection capability and status of the downstream node:
|
extensive |
|
Date and time the LSP was created. |
extensive |
Sample Output
show mpls container-lsp
user@host> show mpls container-lsp Ingress LSP: 1 sessions Container LSP name Member LSP count test 2 To From State Rt P ActivePath LSPname 10.255.107.76 10.255.107.78 Up 0 * test-1 10.255.107.76 10.255.107.78 Up 0 * test-2 Total 2 displayed, Up 2, Down 0 naling Egress LSP: 1 sessions Total 0 displayed, Up 0, Down 0 Transit LSP: 0 sessions Total 0 displayed, Up 0, Down 0
show mpls container-lsp extensive
user@host> show mpls container-lsp extensive
Ingress LSP: 1 sessions
Container LSP name: test, Member count: 2
Normalization
Min LSPs: 2, Max LSPs: 64, Aggregate bandwidth: 0bps
NormalizeTimer: 1800 secs, NormalizeThreshold: 0%
Max Signaling BW: 2kbps, Min Signaling BW: 2kbps, Splitting BW: 5Mbps, Merging BW: 2kbps
Normalization in 989 second(s)
10.255.107.76
From: 10.255.107.78, State: Up, ActiveRoute: 0, LSPname: test-1
ActivePath: (primary)
LSPtype: Dynamic Configured, Penultimate hop popping
LoadBalance: Random
Autobandwidth
MinBW: 1000bps
AdjustTimer: 300 secs
Max AvgBW util: 0bps, Bandwidth Adjustment in 89 second(s).
Overflow limit: 0, Overflow sample count: 0
Underflow limit: 0, Underflow sample count: 0, Underflow Max AvgBW: 0bps
Encoding type: Packet, Switching type: Packet, GPID: IPv4
*Primary State: Up, No-decrement-ttl
Priorities: 7 0
Bandwidth: 1000bps
SmartOptimizeTimer: 180
Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 2)
1.3.0.2 S 1.7.0.1 S
Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt 20=Node-ID):
1.3.0.2 1.7.0.1
11 Jul 13 20:08:26.613 Make-before-break: Switched to new instance
10 Jul 13 20:08:04.360 Record Route: 1.3.0.2 1.7.0.1
9 Jul 13 20:08:04.360 Up
8 Jul 13 20:08:04.360 Automatic Autobw adjustment succeeded: BW changes from 2000 bps to 1000 bps
7 Jul 13 20:08:04.314 Originate make-before-break call
6 Jul 13 20:08:04.314 CSPF: computation result accepted 1.3.0.2 1.7.0.1
5 Jul 13 20:05:02.423 Selected as active path
4 Jul 13 20:05:02.422 Record Route: 1.3.0.2 1.7.0.1
3 Jul 13 20:05:02.421 Up
2 Jul 13 20:05:02.376 Originate Call
1 Jul 13 20:05:02.376 CSPF: computation result accepted 1.3.0.2 1.7.0.1
Created: Sat Jul 13 20:03:03 2013
10.255.107.76
From: 10.255.107.78, State: Up, ActiveRoute: 0, LSPname: test-2
ActivePath: (primary)
LSPtype: Dynamic Configured, Penultimate hop popping
LoadBalance: Random
Autobandwidth
MinBW: 1000bps
AdjustTimer: 300 secs
Max AvgBW util: 0bps, Bandwidth Adjustment in 89 second(s).
Overflow limit: 0, Overflow sample count: 0
Underflow limit: 0, Underflow sample count: 0, Underflow Max AvgBW: 0bps
Encoding type: Packet, Switching type: Packet, GPID: IPv4
*Primary State: Up, No-decrement-ttl
Priorities: 7 0
Bandwidth: 1000bps
SmartOptimizeTimer: 180
Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 2)
1.2.0.2 S 1.4.0.2 S
Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt 20=Node-ID):
1.2.0.2 1.4.0.2
11 Jul 13 20:08:05.363 Make-before-break: Switched to new instance
10 Jul 13 20:08:04.450 Record Route: 1.2.0.2 1.4.0.2
9 Jul 13 20:08:04.449 Up
8 Jul 13 20:08:04.449 Automatic Autobw adjustment succeeded: BW changes from 2000 bps to 1000 bps
7 Jul 13 20:08:04.327 Originate make-before-break call
6 Jul 13 20:08:04.327 CSPF: computation result accepted 1.2.0.2 1.4.0.2
5 Jul 13 20:05:00.849 Selected as active path
4 Jul 13 20:05:00.841 Record Route: 1.3.0.2 1.7.0.1
3 Jul 13 20:05:00.831 Up
2 Jul 13 20:05:00.513 Originate Call
1 Jul 13 20:05:00.502 CSPF: computation result accepted 1.3.0.2 1.7.0.1
Created: Sat Jul 13 20:03:03 2013
Total 2 displayed, Up 2, Down 0
Egress LSP: 1 sessions
Total 0 displayed, Up 0, Down 0
Transit LSP: 0 sessions
Total 0 displayed, Up 0, Down 0Release Information
Command introduced in Junos OS Release 14.2.
Statement introduced for QFX Switches in Junos OS Release 15.1X53-D30.