show ldp traffic-statistics
Syntax
Release Information
Command introduced before Junos OS Release 7.4.
p2mp option added in Junos OS Release 11.2.
Command introduced in Junos OS Release 13.2X51-D15 for the QFX Series.
Description
Display Label Distribution Protocol (LDP) traffic statistics.
Options
none | — | Display LDP traffic statistics for all routing instances. |
instance instance-name | — | (Optional) Display LDP traffic statistics for the specified routing instance only. |
logical-system (all | logical-system-name) | — | (Optional) Perform this operation on all logical systems or on a particular logical system. |
p2mp | — | (Optional) Display only the data traffic statistics for a point-to-multipoint LSP. |
Additional Information
To collect output from this command on a periodic basis, configure the traffic-statistics statement for the LDP protocol. For more information, see the Junos MPLS Applications Configuration Guide.
Required Privilege Level
view
List of Sample Output
show ldp traffic-statisticsshow ldp traffic-statistics p2mp
show ldp traffic-statistics p2mp (Multipoint LDP Inband Signaling for Point-to-Multipoint LSPs)
Output Fields
Table 1 lists the output fields for the show ldp traffic-statistics command. Output fields are listed in the approximate order in which they appear.
Table 1: show ldp traffic-statistics Output Fields
Field Name | Field Description |
|---|---|
Message type | LDP message types. |
FEC | Forwarding equivalence class (FEC) for which LDP traffic statistics are collected. For P2MP LSPs, FEC appears as a combination of root address and the LSP ID (root_addr:lsp_id). For M-LDP P2MP LSPs, FEC appears as a combination of root address multicast source address, and multicast group address (root_addr:lsp_id/grp,src). |
Type | Type of traffic originating from a router, either Ingress (originating from this router) or Transit (forwarded through this router). |
Packets | Number of packets passed by the FEC since its LSP came up. |
Bytes | Number of bytes of data passed by the FEC since its LSP came up. |
Shared | Whether a label is shared by prefixes: Yes or No. A Yes value indicates that several prefixes are bound to the same label (for example, when several prefixes are advertised with an egress policy). The LDP traffic statistics for this case apply to all the prefixes and should be treated as such. |
Nexthop | The next hop address for P2MP LSPs. (This is the downstream LDP Session ID.) |
Sample Output
show ldp traffic-statistics
user@host> show ldp traffic-statistics FEC Type Packets Bytes Shared
10.35.3.0/30 Transit 0 0 Yes
Ingress 0 0 No
10.35.10.1/32 Transit 0 0 Yes
Ingress 0 0 No
10.255.245.214/32 Transit 0 0 No
Ingress 11 752 No
192.168.37.36/30 Transit 0 0 Yes
Ingress 0 0 No
FEC(root_addr:lsp_id) Nexthop Packets Bytes Shared
10.255.72.160:16777217 192.168.8.81 152056 14597376 No
192.168.8.1 152056 14597376 No
192.168.8.65 152056 14597376 No
show ldp traffic-statistics p2mp
user@host> show ldp traffic-statistics p2mp FEC(root_addr:lsp_id) Nexthop Packets Bytes Shared
10.255.72.160:16777217192.168.8.81 152056 14597376 No
192.168.8.1 152056 14597376 No
192.168.8.65 152056 14597376 No
show ldp traffic-statistics p2mp (Multipoint LDP Inband Signaling for Point-to-Multipoint LSPs)
user@host> show ldp traffic-statistics p2mp P2MP FEC Statistics:
FEC(root_addr:lsp_id/grp,src) Nexthop Packets Bytes Shared
11.99.0.73:239.10.0.1,11.98.0.10 11.99.0.117 243408 121217184 No
11.99.0.13 236286 117670428 No
11.99.0.73:239.10.0.2,11.98.0.10 11.99.0.117 248800 123902400 No
11.99.0.13 240759 119897982 No
11.99.0.73:239.10.0.1,11.98.0.20 11.99.0.117 250286 124642428 No
11.99.0.13 243741 121383018 No
11.99.0.73:239.10.0.2,11.98.0.20 11.99.0.117 252970 125979060 No
11.99.0.13 245218 122118564 No
