Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

show pim interfaces

Syntax

Syntax (EX Series Switch and the QFX Series)

Description

Display information about the interfaces on which Protocol Independent Multicast (PIM) is configured.

Options

none

Display interface information for all family addresses for the main instance.
inet | inet6

(Optional) Display interface information for IPv4 or IPv6 family addresses, respectively.
instance (instance-name | all)

(Optional) Display information about interfaces for a specific PIM-enabled routing instance or for all routing instances.
logical-system (all | logical-system-name)

(Optional) Perform this operation on all logical systems or on a particular logical system.

Required Privilege Level

view

Output Fields

Table 1 describes the output fields for the show pim interfaces command. Output fields are listed in the approximate order in which they appear.

Table 1: show pim interfaces Output Fields

Field Name

Field Description

Instance

Name of the routing instance.

Name

Interface name.

State

State of the interface. The state also is displayed in the show interfaces command.

Mode

PIM mode running on the interface:

  • B—In bidirectional mode, multicast groups are carried across the network over bidirectional shared trees. This type of tree minimizes PIM routing state, which is especially important in networks with numerous and dispersed senders and receivers.

  • S—In sparse mode, routing devices must join and leave multicast groups explicitly. Upstream routing devices do not forward multicast traffic to this routing device unless this device has sent an explicit request (using a join message) to receive multicast traffic.

  • Dense—Unlike sparse mode, where data is forwarded only to routing devices sending an explicit request, dense mode implements a flood-and-prune mechanism, similar to DVMRP (the first multicast protocol used to support the multicast backbone). (Not supported on QFX Series.)

  • Sparse-Dense—Sparse-dense mode allows the interface to operate on a per-group basis in either sparse or dense mode. A group specified as dense is not mapped to a rendezvous point (RP). Instead, data packets destined for that group are forwarded using PIM-Dense Mode (PIM-DM) rules. A group specified as sparse is mapped to an RP, and data packets are forwarded using PIM-Sparse Mode (PIM-SM) rules.

    When sparse-dense mode is configured, the output includes both S and D. When bidirectional-sparse mode is configured, the output includes S and B. When bidirectional-sparse-dense mode is configured, the output includes B, S, and D.

IP

Version number of the address family on the interface: 4 (IPv4) or 6 (IPv6).

V

PIM version running on the interface: 1 or 2.

State

State of PIM on the interface:

  • Active—Bidirectional mode is enabled on the interface and on all PIM neighbors.

  • DR—Designated router.

  • NotCap—Bidirectional mode is not enabled on the interface. This can happen when bidirectional PIM is not configured locally, when one of the neighbors is not configured for bidirectional PIM, or when one of the neighbors has not implemented the bidirectional PIM protocol.

  • NotDR—Not the designated router.

  • P2P—Point to point.

NbrCnt

Number of neighbors that have been seen on the interface.

JoinCnt(sg)

Number of (s,g) join messages that have been seen on the interface.

JointCnt(*g)

Number of (*,g) join messages that have been seen on the interface.

DR address

Address of the designated router.

Sample Output

show pim interfaces

show pim interfaces (PIM using point-to-multipoint mode)

Release Information

Command introduced before Junos OS Release 7.4.

inet6 and instance options introduced in Junos OS Release 10.0 for EX Series switches.

Commmand introduced in Junos OS Release 11.3 for the QFX Series.

Support for bidirectional PIM added in Junos OS Release 12.1.

Support for the instance all option added in Junos OS Release 12.1.