show ldp traffic-statistics

Syntax

Description

Display Label Distribution Protocol (LDP) traffic statistics.

Note:

If nonstop active routing features is configured, show ldp traffic-statistics command is not supported on backup Routing Engines.

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

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 multipoint 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.)
`Label`	For multipoint LDP with multicast-only fast reroute (MoFRR), the multipoint LDP node selects two separate upstream peers and sends two separate labels, one to each upstream peer. The same algorithm described in RFC 6388 is used to select the primary upstream path. The backup upstream path selection again uses the same algorithm but excludes the primary upstream LSR as a candidate. Two streams of MPLS traffic are sent to the egress node from the two different upstream peers. The MPLS traffic from only one of the upstream neighbors is selected as the primary path to accept the traffic, and the other becomes the backup path. The traffic on the backup path is dropped. When the primary upstream path fails, the traffic from the backup path is then accepted. The multipoint LDP node selects the two upstream paths based on the interior gateway protocol (IGP) root node next hop. Multiple MPLS labels are used to control MoFRR stream selection. Each label represents a separate route, but each references the same interface list check. Only the primary label is forwarded while all others are dropped. Multiple interfaces can receive packets using the same label.
`Backup route`	For multipoint LDP with MoFRR, the route that is used if the primary route becomes unavailable.
Interface	Name of the point-to-multipoint interface for which statistics are displayed.
type	Type of LDP traffic on the interface.

Sample Output

show ldp traffic-statistics
show ldp traffic-statistics p2mp (Ingress or transit router only, Multipoint LDP Inband Signaling for Point-to-Multipoint LSPs)
show ldp traffic-statistics p2mp (Multipoint LDP with Multicast-Only Fast Reroute)
show ldp traffic-statistics interface p2mp (Multipoint LDP Interfaces)