Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    RLI Topic Review

  • Support for multipoint LDP to utilize distributed IGMP to signal a MPLS based core has been added to Enhanced Subscriber Management (single chassis MX Series routers with MPC2E, MPC3E, MPC5E, or MPC7E)—Starting in Junos OS Release 18.2R1, support for multipoint LDP inband signaling to interwork with distributed IGMP has been added. As such, two separate PIM domains can be interconnected by a MPLS-based core (that is, a PIM-free core). One application of multipoint LDP inband signalling is to carry IPTV multicast traffic on a MPLS backbone.

    To enable the interworking, chassis network-services enhanced-ip must first be configured. Then you need to set the igmp or mld interface for distributed, and enable mldp-inband-signalling at the PIM hierarchy so PIM acts as a multipoint LDP inband edge router:

    [edit dynamic-profiles profile-name protocols igmp|mld interface layer 3 interface name distributed]
    [edit protocols pim mldp-inband-signalling]

    You can the run the show pim source command to confirm that distributed multipoint LDP is working (look for Upstream neighbor via MLDP-inband).

    [See Understanding Distributed IGMP and Enhanced Subscriber Management Overview for more information.]

  • mldp-inband-signalling (Protocols Multipoint LDP)

    Syntax

    mldp-inband-signalling {
    policy policy-name;
    }

    Hierarchy Level

    [edit logical-systems logical-system-name protocols pim],
    [edit protocols pim],

    Release Information

    Statement introduced in Junos OS Release 13.2.

    Support added in Junos OS Release 18.2R1 for using this command in conjunction with distributed MLD or distributed IGMP.

    Description

    Multipoint LDP (mLDP) in-band signalling lets you carry multicast traffic across an existing IP/MPLS backbone, while avoiding the use of PIM in the provider core.

    On the label-edge router (LER), enable PIM to use mLDP in-band signaling for the upstream neighbors when the LER does not detect a PIM upstream neighbor. On the egress nodes, configure the MPLS LSP root in the PIM configuration, using the policy statement.

    When used in conjunction with distributed MLD or distributed IGMP, mLDP inband signalling supports interconnecting separate PIM domains via a MPLS-based core. To enable the inter-working, chassis network-services enhanced-ip must be enabled and you need to set the dynamic-profiles profile-name protocols igmp|mld interface interface-name to distributed. Enabling this command, mldp-inband-signalling, has PIM act as a multipoint LDP inband edge router.

    Required Privilege Level

    routing—To view this statement in the configuration.

    routing-control—To add this statement to the configuration.

    distributed (IGMP)

    Syntax

    distributed;

    Hierarchy Level

    [edit protocols igmp interface interface-name],
    [edit dynamic-profiles protocols igmp interface $junos-interface-name]

    Release Information

    Statement introduced in Junos OS Release 14.1X50.

    Support added in Junos OS Release 18.2R1 for using distributed IGMP in conjunction with Multipoint LDP (mLDP) in-band signalling.

    Description

    Enable distributed IGMP by moving IGMP processing from the Routing Engine to the Packet Forwarding Engine. Distributed IGMP reduces the join and leave latency of IGMP memberships.

    Distributed IGMP is only available when chassis network-services enhanced-ip is configured.

    Note: When you enable distributed IGMP, the following interface options are not supported on the Packet Forwarding Engine: oif-map, group-limit, ssm-map, and static. However, the ssm-map-policy option is supported on distributed IGMP interfaces. The traceoptions and accounting statements can only be enabled for IGMP operations still performed on the Routing Engine; they are not supported on the Packet Forwarding Engine. The clear igmp membership command is not supported when distributed IGMP is enabled.

    When the distributed command is enabled in conjunction with mldp-inband-signalling, (so PIM act as a multipoint LDP inband edge router), it supports interconnecting separate PIM domains via a MPLS-based core.

    Required Privilege Level

    routing—To view this statement in the configuration.

    routing-control—To add this statement to the configuration.

    distributed (MLD)

    Syntax

    distributed;

    Hierarchy Level

    [edit protocols mld interface interface-name],
    [edit dynamic-profiles protocols mld interface $junos-interface-name]

    Release Information

    Statement introduced in Junos OS Release 17.4R1.

    Support added in Junos OS Release 18.2R1 for using distributed MLD in conjunction with Multipoint LDP (mLDP) in-band signalling.

    Description

    Enables distributed MLD on the specified interface, which moves MLD processing from the Routing Engine to the Packet Forwarding Engine for increased performance and capacity to scale. MLD must be enabled for the router to receive multicast packets.

    By default, MLD is disabled on the router. MLD is automatically enabled on all broadcast interfaces when you configure Protocol Independent Multicast (PIM) or Distance Vector Multicast Routing Protocol (DVMRP), but if you want to use distributed MLD, you must explicitly enable it.

    Distributed MLD is only available when chassis network-services enhanced-ip is configured.

    When the distributed command is enabled in conjunction with mldp-inband-signalling, (so PIM act as a multipoint LDP inband edge router), it supports interconnecting separate PIM domains via a MPLS-based core.

    Required Privilege Level

    routing—To view this statement in the configuration.

    routing-control—To add this statement to the configuration.

     
     

    igmp

    Syntax

    igmp {
    interface interface-name {
    group-policy [ policy-names ];
    oif-map map-name;
    ssm-map ssm-map-name;
    ssm-map-policy ssm-map-policy-name;
    group multicast-group-address {
    group-count number;
    group-increment increment;
    source ip-address {
    source-count number;
    source-increment increment;
    }
    }
    }
    version version;
    }
    robust-count number;
    file filename <files number> <size size> <world-readable | no-world-readable>;
    flag flag <flag-modifier> <disable>;
    }
    }

    Hierarchy Level

    [edit logical-systems logical-system-name protocols],
    [edit protocols]

    Release Information

    Statement introduced before Junos OS Release 7.4.

    Statement introduced in Junos OS Release 12.1 for the QFX Series.

    Statement introduced in Junos OS Release 14.1X53-D20 for the OCX Series.

    Statement introduced in Junos OS Release 12.3R2 for EX Series switches.

    Description

    Enable IGMP on the router or switch. IGMP must be enabled for the router or switch to receive multicast packets.

    The remaining statements are explained separately. See CLI Explorer.

    Default

    IGMP is disabled on the router or switch. IGMP is automatically enabled on all broadcast interfaces when you configure Protocol Independent Multicast (PIM) or Distance Vector Multicast Routing Protocol (DVMRP).

    Required Privilege Level

    routing—To view this statement in the configuration.

    routing-control—To add this statement to the configuration.

    interface (Dynamic IGMP)

    Syntax

    interface interface-name {
    log-interval seconds;
    ssm-map ssm-map-name;
    ssm-map-policy ssm-map-policy-name
    group group {
    source source;
    }
    }
    version version;
    }

    Hierarchy Level

    [edit dynamic-profiles profile-name protocols igmp]

    Release Information

    Statement introduced in Junos OS Release 9.2.

    Description

    Enable IGMP on an interface and configure interface-specific properties.

    Options

    interface-name—Variable for the interface. Specify the interface variable ($junos-interface-name) to indicate that the dynamic profile chooses an interface for the accessing DHCP client.

    The remaining statements are explained separately. Search for a statement in CLI Explorer or click a linked statement in the Syntax section for details.

    Required Privilege Level

    routing—To view this statement in the configuration.

    routing-control—To add this statement to the configuration.

    interface (Dynamic MLD)

    Syntax

    interfaceinterface-name {
    log-interval seconds;
    ssm-map ssm-map-name;
    ssm-map-policy ssm-map-policy-name;
    group multicast-group-address {
    group-count number;
    group-increment increment;
    source ip-address {
    source-count number;
    source-increment increment;
    }
    }
    }
    version version;
    }

    Hierarchy Level

    [edit dynamic-profiles profile-name protocols mld]

    Release Information

    Statement introduced in Junos OS Release 10.1.

    Description

    Enable MLD on a dynamic interface and configure interface-specific properties.

    Options

    interface-name—Variable for the interface. Specify the interface variable ($junos-interface-name) to indicate that the dynamic profile chooses an interface for the accessing client.

    The remaining statements are explained separately. Search for a statement in CLI Explorer or click a linked statement in the Syntax section for details.

    Required Privilege Level

    routing—To view this statement in the configuration.

    routing-control—To add this statement to the configuration.

    interface (Protocols IGMP)

    Syntax

    interface interface-name {
    group-policy [ policy-names ];
    oif-map map-name;
    promiscuous-mode;
    ssm-map ssm-map-name;
    ssm-map-policy ssm-map-policy-name;
    group multicast-group-address {
    group-count number;
    group-increment increment;
    source ip-address {
    source-count number;
    source-increment increment;
    }
    }
    }
    version version;
    }

    Hierarchy Level

    [edit logical-systems logical-system-name protocols igmp],
    [edit protocols igmp]

    Release Information

    Statement introduced before Junos OS Release 7.4.

    Statement introduced in Junos OS Release 9.0 for EX Series switches.

    Statement introduced in Junos OS Release 12.1 for the QFX Series.

    Description

    Enable IGMP on an interface and configure interface-specific properties.

    Options

    interface-name—Name of the interface. Specify the full interface name, including the physical and logical address components. To configure all interfaces, you can specify all.

    The remaining statements are explained separately. See CLI Explorer.

    Required Privilege Level

    routing—To view this statement in the configuration.

    routing-control—To add this statement to the configuration.

     
     

    interface (Protocols MLD)

    Syntax

    interface interface-name {
    group-policy [ policy-names ];
    group-threshold value;
    log-interval seconds;
    oif-map [ map-names ];
    ssm-map ssm-map-name;
    ssm-map-policy ssm-map-policy-name;
    group multicast-group-address {
    group-increment increment
    source ip-address {
    source-count number;
    source-increment increment;
    }
    }
    }
    version version;
    }

    Hierarchy Level

    [edit logical-systems logical-system-name protocols mld],
    [edit protocols mld]

    Release Information

    Statement introduced before Junos OS Release 7.4.

    Description

    Enable MLD on an interface and configure interface-specific properties.

    Options

    interface-name—Name of the interface. Specify the full interface name, including the physical and logical address components. To configure all interfaces, you can specify all.

    The remaining statements are explained separately. See CLI Explorer.

    Required Privilege Level

    routing—To view this statement in the configuration.

    routing-control—To add this statement to the configuration.

     

    See Also

     

    mld

    Syntax

    mld {
    interface interface-name {
    group-policy [ policy-names ];
    oif-map [ map-names ];
    ssm-map ssm-map-name;
    ssm-map-policy ssm-map-policy-name;
    group multicast-group-address {
    group-count number;
    group-increment increment;
    source ip-address {
    source-count number;
    source-increment increment;
    }
    }
    }
    version version;
    }
    maximum-transmit-rate packets-per-second;
    robust-count number;
    }

    Hierarchy Level

    [edit logical-systems logical-system-name protocols],
    [edit protocols]

    Release Information

    Statement introduced before Junos OS Release 7.4.

    Description

    Enable MLD on the router. MLD must be enabled for the router to receive multicast packets.

    Default

    MLD is disabled on the router. MLD is automatically enabled on all broadcast interfaces when you configure Protocol Independent Multicast (PIM) or Distance Vector Multicast Routing Protocol (DVMRP).

    Options

    The remaining statements are explained separately. See CLI Explorer.

    Required Privilege Level

    routing—To view this statement in the configuration.

    routing-control—To add this statement to the configuration.

    show igmp interface

    List of Syntax

    Syntax
    Syntax (EX Series Switches and the QFX Series)

    Syntax

    show igmp interface
    <brief | detail>
    <interface-name>
    <logical-system (all | logical-system-name)>

    Syntax (EX Series Switches and the QFX Series)

    show igmp interface
    <brief | detail>
    <interface-name>

    Release Information

    Command introduced before Junos OS Release 7.4.

    Command introduced in Junos OS Release 9.0 for EX Series switches.

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

    Command introduced in Junos OS Release 14.1X53-D20 for the OCX Series.

    Description

    Display information about Internet Group Management Protocol (IGMP)-enabled interfaces.

    Options

    noneDisplay standard information about all IGMP-enabled interfaces.
    brief | detail(Optional) Display the specified level of output.
    interface-name(Optional) Display information about the specified IGMP-enabled interface only.
    logical-system (all | logical-system-name)(Optional) Perform this operation on all logical systems or on a particular logical system.

    Required Privilege Level

    view

    List of Sample Output

    show igmp interface
    show igmp interface brief
    show igmp interface detail
    show igmp interface <interface-name>

    Output Fields

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

    Table 1: show igmp interface Output Fields

    Field Name

    Field Description

    Level of Output

    Interface

    Name of the interface.

    All levels

    Querier

    Address of the routing device that has been elected to send membership queries.

    All levels

    State

    State of the interface: Up or Down.

    All levels

    SSM Map Policy

    Name of the source-specific multicast (SSM) map policy that has been applied to the IGMP interface.

    All levels

    Timeout

    How long until the IGMP querier is declared to be unreachable, in seconds.

    All levels

    Version

    IGMP version being used on the interface: 1 , 2 , or 3.

    All levels

    Groups

    Number of groups on the interface.

    All levels

    Group limit

    Maximum number of groups allowed on the interface. Any joins requested after the limit is reached are rejected.

    All levels

    Group threshold

    Configured threshold at which a warning message is generated.

    This threshold is based on a percentage of groups received on the interface. If the number of groups received reaches the configured threshold, the device generates a warning message.

    All levels

    Group log-interval

    Time (in seconds) between consecutive log messages.

    All levels

    Immediate Leave

    State of the immediate leave option:

    • On—Indicates that the router removes a host from the multicast group as soon as the router receives a leave group message from a host associated with the interface.

    • Off—Indicates that after receiving a leave group message, instead of removing a host from the multicast group immediately, the router sends a group query to determine if another receiver responds.

    All levels

    Promiscuous Mode

    State of the promiscuous mode option:

    • On—Indicates that the router can accept IGMP reports from subnetworks that are not associated with its interfaces.

    • Off—Indicates that the router can accept IGMP reports only from subnetworks that are associated with its interfaces.

    All levels

    Distributed

    State of IGMP, which, by default, takes place on the Routing Engine for MX Series routers but can be distributed to the Packet Forwarding Engine to provide faster processing of join and leave events.

    • On—distributed IGMP is enabled.

    All levels

    Passive

    State of the passive mode option:

    • On—Indicates that the router can run IGMP on the interface but not send or receive control traffic such as IGMP reports, queries, and leaves.

    • Off—Indicates that the router can run IGMP on the interface and send or receive control traffic such as IGMP reports, queries, and leaves.

    The passive statement enables you to selectively activate up to two out of a possible three available query or control traffic options. When enabled, the following options appear after the on state declaration:

    • send-general-query—The interface sends general queries.

    • send-group-query—The interface sends group-specific and group-source-specific queries.

    • allow-receive—The interface receives control traffic.

    All levels

    OIF map

    Name of the OIF map (if configured) associated with the interface.

    All levels

    SSM map

    Name of the source-specific multicast (SSM) map (if configured) used on the interface.

    All levels

    Configured Parameters

    Information configured by the user:

    • IGMP Query Interval—Interval (in seconds) at which this router sends membership queries when it is the querier.

    • IGMP Query Response Interval—Time (in seconds) that the router waits for a report in response to a general query.

    • IGMP Last Member Query Interval—Time (in seconds) that the router waits for a report in response to a group-specific query.

    • IGMP Robustness Count—Number of times the router retries a query.

    All levels

    Derived Parameters

    Derived information:

    • IGMP Membership Timeout—Timeout period (in seconds) for group membership. If no report is received for these groups before the timeout expires, the group membership is removed.

    • IGMP Other Querier Present Timeout—Time (in seconds) that the router waits for the IGMP querier to send a query.

    All levels

    Sample Output

    show igmp interface

    user@host> show igmp interface
    Interface: at-0/3/1.0
        Querier: 203.0.3.113.31
        State:         Up Timeout:    None Version:  2 Groups:      4
        SSM Map Policy: ssm-policy-A
    Interface: so-1/0/0.0
        Querier: 203.0.113.11
        State:         Up Timeout:    None Version:  2 Groups:      2
        SSM Map Policy: ssm-policy-B
    Interface: so-1/0/1.0
        Querier: 203.0.113.21
        State:         Up Timeout:    None Version:  2 Groups:      4
        SSM Map Policy: ssm-policy-C
    Immediate Leave: On
    Promiscuous Mode: Off
    Passive: Off
    Distributed: OnConfigured Parameters:
    
    IGMP Query Interval: 125.0
    IGMP Query Response Interval: 10.0
    IGMP Last Member Query Interval: 1.0
    IGMP Robustness Count: 2
    
    Derived Parameters:
    IGMP Membership Timeout: 260.0
    IGMP Other Querier Present Timeout: 255.0

    show igmp interface brief

    The output for the show igmp interface brief command is identical to that for the show igmp interface command. For sample output, see show igmp interface.

    show igmp interface detail

    The output for the show igmp interface detail command is identical to that for the show igmp interface command. For sample output, see show igmp interface.

    show igmp interface <interface-name>

    user@host# show igmp interface ge-3/2/0.0
    Interface: ge-3/2/0.0
      Querier: 203.0.113.111 
      State: Up Timeout:    None 
      Version:  3 
      Groups:      1 
      Group limit: 8   
      Group threshold: 60
      Group log-interval: 10   
      Immediate leave:  Off 
      Promiscuous mode:  Off  
      Distributed: On

    show mld interface

    List of Syntax

    Syntax

    Syntax

    show mld interface
    <brief | detail>
    <interface-name>
    <logical-system (all | logical-system-name)>

    Release Information

    Command introduced before Junos OS Release 7.4.

    Description

    Display information about multipoint Listener Discovery (MLD)-enabled interfaces.

    Options

    noneDisplay standard information about all MLD-enabled interfaces.
    brief | detail(Optional) Display the specified level of output.
    interface-name(Optional) Display information about the specified interface.
    logical-system (all | logical-system-name)(Optional) Perform this operation on all logical systems or on a particular logical system.

    Required Privilege Level

    view

    List of Sample Output

    show mld interface
    show mld interface brief
    show mld interface detail
    show mld interface <interface-name>

    Output Fields

    Table 2 describes the output fields for the show mld interface command. Output fields are listed in the approximate order in which they appear.

    Table 2: show mld interface Output Fields

    Field Name

    Field Description

    Level of Output

    Interface

    Name of the interface.

    All levels

    Querier

    Address of the router that has been elected to send membership queries.

    All levels

    State

    State of the interface: Up or Down.

    All levels

    SSM Map Policy

    Name of the source-specific multicast (SSM) map policy that has been applied to the interface.

    All levels

    SSM Map Policy

    Name of the source-specific multicast (SSM) map policy at the MLD interface.

    All levels

    Timeout

    How long until the MLD querier is declared to be unreachable, in seconds.

    All levels

    Version

    MLD version being used on the interface: 1 or 2.

    All levels

    Groups

    Number of groups on the interface.

    All levels

    Passive

    State of the passive mode option:

    • On—Indicates that the router can run IGMP or MLD on the interface but not send or receive control traffic such as IGMP or MLD reports, queries, and leaves.

    • Off—Indicates that the router can run IGMP or MLD on the interface and send or receive control traffic such as IGMP or MLD reports, queries, and leaves.

    The passive statement enables you to selectively activate up to two out of a possible three available query or control traffic options. When enabled, the following options appear after the on state declaration:

    • send-general-query—The interface sends general queries.

    • send-group-query—The interface sends group-specific and group-source-specific queries.

    • allow-receive—The interface receives control traffic

    All levels

    OIF map

    Name of the OIF map associated to the interface.

    All levels

    SSM map

    Name of the source-specific multicast (SSM) map used on the interface, if configured.

    All levels

    Group limit

    Maximum number of groups allowed on the interface. Any memberships requested after the limit is reached are rejected.

    All levels

    Group threshold

    Configured threshold at which a warning message is generated.

    This threshold is based on a percentage of groups received on the interface. If the number of groups received reaches the configured threshold, the device generates a warning message.

    All levels

    Group log-interval

    Time (in seconds) between consecutive log messages.

    All levels

    Immediate Leave

    State of the immediate leave option:

    • On—Indicates that the router removes a host from the multicast group as soon as the router receives a multicast listener done message from a host associated with the interface.

    • Off—Indicates that after receiving a multicast listener done message, instead of removing a host from the multicast group immediately, the router sends a group query to determine if another receiver responds.

    All levels

    Distributed

    State of MLD, which, by default, takes place on the Routing Engine for MX Series routers but can be distributed to the Packet Forwarding Engine to provide faster processing of join and leave events.

    • On—distributed MLD is enabled.

    All levels

    Configured Parameters

    Information configured by the user.

    • MLD Query Interval (.1 secs)—Interval at which this router sends membership queries when it is the querier.

    • MLD Query Response Interval (.1 secs)—Time that the router waits for a report in response to a general query.

    • MLD Last Member Query Interval (.1 secs)—Time that the router waits for a report in response to a group-specific query.

    • MLD Robustness Count—Number of times the router retries a query.

    All levels

    Derived Parameters

    Derived information.

    • MLD Membership Timeout (.1 secs)—Timeout period for group membership. If no report is received for these groups before the timeout expires, the group membership will be removed.

    • MLD Other Querier Present Timeout (.1 secs)—Time that the router waits for the IGMP querier to send a query.

    All levels

    Sample Output

    show mld interface

    user@host> show mld interface
    Interface: fe-0/0/0
        Querier: None
        State: Up         Timeout:       0    Version:  1    Groups:      0
        SSM Map Policy: ssm-policy-A
    Interface: at-0/3/1.0
        Querier:  8038::c0a8:c345
        State: Up         Timeout:    None    Version:  1    Groups:      0
        SSM Map Policy: ssm-policy-B
    Interface: fe-1/0/1.0
        Querier:  ::192.168.195.73
        State: Up         Timeout:    None    Version:  1    Groups:      3
        SSM Map Policy: ssm-policy-C
        SSM map: ipv6map1
    Immediate Leave: On
    
    Promiscuous Mode: Off
    Passive: Off
    Distributed: OnConfigured Parameters:
    
    Configured Parameters:
    MLD Query Interval (.1 secs): 1250
    MLD Query Response Interval (.1 secs): 100
    MLD Last Member Query Interval (.1 secs): 10
    MLD Robustness Count: 2
    
    Derived Parameters:
    MLD Membership Timeout (.1secs): 2600
    MLD Other Querier Present Timeout (.1 secs): 2550

    show mld interface brief

    The output for the show mld interface brief command is identical to that for the show mld interface command. For sample output, see show mld interface.

    show mld interface detail

    The output for the show mld interface detail command is identical to that for the show mld interface command. For sample output, see show mld interface.

    show mld interface <interface-name>

    user@host# show mld interface ge-3/2/0.0
    Interface: ge-3/2/0.0
      Querier: 203.0.113.111 
      State: Up Timeout:    None Version:  3 Groups:      1 
      Group limit: 8   
      Group threshold: 60
      Group log-interval: 10   
      Immediate leave:  Off 
      Promiscuous mode:  Off   Distributed: On

    show pim source

    List of Syntax

    Syntax
    Syntax (EX Series Switch and the QFX Series)

    Syntax

    show pim source
    <brief | detail>
    <inet | inet6>
    <instance instance-name>
    <logical-system (all | logical-system-name)>
    <source-prefix>

    Syntax (EX Series Switch and the QFX Series)

    show pim source
    <brief | detail>
    <inet | inet6>
    <instance instance-name>
    <source-prefix>

    Release Information

    Command introduced before Junos OS Release 7.4.

    Command introduced in Junos OS Release 9.0 for EX Series switches.

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

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

    Command introduced in Junos OS Release 14.1X53-D20 for the OCX Series.

    Description

    Display information about the Protocol Independent Multicast (PIM) source reverse path forwarding (RPF) state.

    Options

    noneDisplay standard information about the PIM RPF state for all supported family addresses for all routing instances.
    brief | detail(Optional) Display the specified level of output.
    inet | inet6(Optional) Display information for IPv4 or IPv6 family addresses, respectively.
    instance instance-name(Optional) Display information about the RPF state for a specific PIM-enabled routing instance.
    logical-system (all | logical-system-name)(Optional) Perform this operation on all logical systems or on a particular logical system.
    source-prefix(Optional) Display the state for source RPF states in the given range.

    Required Privilege Level

    view

    List of Sample Output

    show pim source
    show pim source brief
    show pim source detail
    show pim source (Egress Node with Multipoint LDP Inband Signaling for Point-to-Multipoint LSPs)

    Output Fields

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

    Table 3: show pim source Output Fields

    Field Name

    Field Description

    Instance

    Name of the routing instance.

    Source

    Address of the source or reverse path.

    Prefix/length

    Prefix and prefix length for the route used to reach the RPF address.

    Upstream Protocol

    Protocol toward the source address.

    Upstream interface

    RPF interface toward the source address.

    A pseudo multipoint LDP (M-LDP) interface appears on egress nodes in M-LDP point-to-multipoint LSPs with inband signaling.

    Upstream Neighbor

    Address of the RPF neighbor used to reach the source address.

    The multipoint LDP (M-LDP) root appears on egress nodes in M-LDP point-to-multipoint LSPs with inband signaling.

    Sample Output

    show pim source

    user@host> show pim source
    Instance: PIM.master Family: INET
    
    Source 10.255.14.144
        Prefix 10.255.14.144/32
        Upstream interface Local
        Upstream neighbor Local
    
    Source 10.255.70.15
        Prefix 10.255.70.15/32
        Upstream interface so-1/0/0.0
        Upstream neighbor 10.111.10.2
    
    Instance: PIM.master Family: INET6

    show pim source brief

    The output for the show pim source brief command is identical to that for the show pim source command. For sample output, see show pim source.

    show pim source detail

    user@host> show pim source detail
    Instance: PIM.master Family: INET
    
    Source 10.255.14.144
        Prefix 10.255.14.144/32
        Upstream interface Local
        Upstream neighbor Local
        Active groups:233.252.0.0
            233.252.0.1
            233.252.0.1
    
    Source 10.255.70.15
        Prefix 10.255.70.15/32
        Upstream interface so-1/0/0.0
        Upstream neighbor 10.111.10.2
        Active groups:233.252.0.1
    
    Instance: PIM.master Family: INET6

    show pim source (Egress Node with Multipoint LDP Inband Signaling for Point-to-Multipoint LSPs)

    user@host> show pim source
    Instance: PIM.master Family: INET
    
    Source 10.1.1.1
        Prefix 10.1.1.1/32
        Upstream interface Local
        Upstream neighbor Local
    
    Source 10.2.7.7
        Prefix 10.2.7.0/24
        Upstream protocol MLDP
        Upstream interface Pseudo MLDP
        Upstream neighbor MLDP LSP root <10.1.1.2>
    
    Source 192.168.219.11
        Prefix 192.168.219.0/28
        Upstream protocol MLDP
        Upstream interface Pseudo MLDP
       	Upstream neighbor via MLDP-inband
      	Upstream interface fe-1/3/0.0
        Upstream neighbor 192.168.140.1    
        Upstream neighbor MLDP LSP root <10.1.1.2>
    
    Instance: PIM.master Family: INET6
    Source 2001:db8::1:2:7:7
        Prefix 2001:db8::1:2:7:0/120
        Upstream protocol MLDP
        Upstream interface Pseudo MLDP
       	Upstream neighbor via MLDP-inband
      	Upstream interface fe-1/3/0.0
        Upstream neighbor 192.168.140.1
    Upstream neighbor MLDP LSP root <10.1.1.2>

    show pim join

    List of Syntax

    Syntax
    Syntax (EX Series Switch and the QFX Series)

    Syntax

    show pim join
    <brief | detail | extensive | summary>
    <bidirectional | dense | sparse>
    <downstream-count>
    <exact>
    <inet | inet6>
    <instance instance-name>
    <logical-system (all | logical-system-name)>
    <range>
    <rp ip-address/prefix | source ip-address/prefix>
    <sg | star-g>

    Syntax (EX Series Switch and the QFX Series)

    show pim join
    <brief | detail | extensive | summary>
    <dense | sparse>
    <exact>
    <inet | inet6>
    <instance instance-name>
    <range>
    <rp ip-address/prefix | source ip-address/prefix>
    <sg | star-g>

    Release Information

    Command introduced before Junos OS Release 7.4.

    Command introduced in Junos OS Release 9.0 for EX Series switches.

    summary option introduced in Junos OS Release 9.6.

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

    Support for bidirectional PIM added in Junos OS Release 12.1.

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

    Multiple new filter options introduced in Junos OS Release 13.2.

    Command introduced in Junos OS Release 14.1X53-D20 for the OCX Series.

    downstream-count option introduced in Junos OS Release 16.1.

    Support for PIM NSR support for VXLAN added in Junos OS Release 16.2

    Support for RFC 5496 (via rpf-vector) added in Junos OS Release 17.3R1.

    Description

    Display information about Protocol Independent Multicast (PIM) groups for all PIM modes.

    For bidirectional PIM, display information about PIM group ranges (*,G-range) for each active bidirectional RP group range, in addition to each of the joined (*,G) routes.

    Options

    noneDisplay the standard information about PIM groups for all supported family addresses for all routing instances.
    brief | detail | extensive | summary(Optional) Display the specified level of output.
    bidirectional | dense | sparse(Optional) Display information about PIM bidirectional mode, dense mode, or sparse and source-specific multicast (SSM) mode entries.
    downstream-count(Optional) Display the downstream count instead of a list.
    exact(Optional) Display information about only the group that exactly matches the specified group address.
    inet | inet6(Optional) Display PIM group information for IPv4 or IPv6 family addresses, respectively.
    instance instance-name(Optional) Display information about groups for the specified PIM-enabled routing instance only.
    logical-system (all | logical-system-name)(Optional) Perform this operation on all logical systems or on a particular logical system.
    range(Optional) Address range of the group, specified as prefix/prefix-length.
    rp ip-address/prefix | source ip-address/prefix(Optional) Display information about the PIM entries with a specified rendezvous point (RP) address and prefix or with a specified source address and prefix. You can omit the prefix.
    sg | star-g(Optional) Display information about PIM (S,G) or (*,G) entries.

    Required Privilege Level

    view

    List of Sample Output

    show pim join summary
    show pim join (PIM Sparse Mode)
    show pim join (Bidirectional PIM)
    show pim join inet6
    show pim join inet6 star-g
    show pim join instance <instance-name>
    show pim join instance <instance-name> downstream-count
    show pim join instance <instance-name> downstream-count extensive
    show pim join detail
    show pim join extensive (PIM Resolve TLV for Multicast in Seamless MPLS)
    show pim join extensive (PIM Sparse Mode)
    show pim join extensive (Bidirectional PIM)
    show pim join extensive (Bidirectional PIM with a Directly Connected Phantom RP)
    show pim join instance <instance-name> extensive
    show pim join extensive (Ingress Node with Multipoint LDP Inband Signaling for Point-to-Multipoint LSPs)
    show pim join extensive (Egress Node with Multipoint LDP Inband Signaling for Point-to-Multipoint LSPs)

    Output Fields

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

    Table 4: show pim join Output Fields

    Field Name

    Field Description

    Level of Output

    Instance

    Name of the routing instance.

    brief detail extensive summary none

    Family

    Name of the address family: inet (IPv4) or inet6 (IPv6).

    brief detail extensive summary none

    Route type

    Type of multicast route: (S,G) or (*,G).

    summary

    Route count

    Number of (S,G) routes and number of (*,G) routes.

    summary

    R

    Rendezvous Point Tree.

    brief detail extensive none

    S

    Sparse.

    brief detail extensive none

    W

    Wildcard.

    brief detail extensive none

    Group

    Group address.

    brief detail extensive none

    Bidirectional group prefix length

    For bidirectional PIM, length of the IP prefix for RP group ranges.

    All levels

    Source

    Multicast source:

    • * (wildcard value)

    • ipv4-address

    • ipv6-address

    brief detail extensive none

    RP

    Rendezvous point for the PIM group.

    brief detail extensive none

    Flags

    PIM flags:

    • bidirectional—Bidirectional mode entry.

    • dense—Dense mode entry.

    • rptree—Entry is on the rendezvous point tree.

    • sparse—Sparse mode entry.

    • spt—Entry is on the shortest-path tree for the source.

    • wildcard—Entry is on the shared tree.

    brief detail extensive none

    Upstream interface

    RPF interface toward the source address for the source-specific state (S,G) or toward the rendezvous point (RP) address for the non-source-specific state (*,G).

    For bidirectional PIM, RP Link means that the interface is directly connected to a subnet that contains a phantom RP address.

    A pseudo multipoint LDP (M-LDP) interface appears on egress nodes in M-LDP point-to-multipoint LSPs with inband signaling.

    brief detail extensive none

    Upstream neighbor

    Information about the upstream neighbor: Direct, Local, Unknown, or a specific IP address.

    For bidirectional PIM, Direct means that the interface is directly connected to a subnet that contains a phantom RP address.

    The multipoint LDP (M-LDP) root appears on egress nodes in M-LDP point-to-multipoint LSPs with inband signaling.

    extensive

    Upstream rpf-vector

    Information about the upstream Reverse Path Forwarding (RPF) vector; appears in conjunction with the rpf-vector command.

    extensive

    Active upstream interface

    When multicast-only fast reroute (MoFRR) is configured in a PIM domain, the upstream interface for the active path. A PIM router propagates join messages on two upstream RPF interfaces to receive multicast traffic on both links for the same join request. Preference is given to two paths that do not converge to the same immediate upstream router. PIM installs appropriate multicast routes with upstream neighbors as RPF next hops with two (primary and backup) interfaces.

    extensive

    Active upstream neighbor

    On the MoFRR primary path, the IP address of the neighbor that is directly connected to the active upstream interface.

    extensive

    MoFRR Backup upstream interface

    The MoFRR upstream interface that is used when the primary path fails.

    When the primary path fails, the backup path is upgraded to primary, and traffic is forwarded accordingly. If there are alternate paths available, a new backup path is calculated and the appropriate multicast route is updated or installed.

    extensive

    MoFRR Backup upstream neighbor

    IP address of the MoFRR upstream neighbor.

    extensive

    Upstream state

    Information about the upstream interface:

    • Join to RP—Sending a join to the rendezvous point.

    • Join to Source—Sending a join to the source.

    • Local RP—Sending neither join messages nor prune messages toward the RP, because this routing device is the rendezvous point.

    • Local Source—Sending neither join messages nor prune messages toward the source, because the source is locally attached to this routing device.

    • No Prune to RP—Automatically sent to RP when SPT and RPT are on the same path.

    • Prune to RP—Sending a prune to the rendezvous point.

    • Prune to Source—Sending a prune to the source.

    Note: RP group range entries have None in the Upstream state field because RP group ranges do not trigger actual PIM join messages between routing devices.

    extensive

    Downstream neighbors

    Information about downstream interfaces:

    • Interface—Interface name for the downstream neighbor.

      A pseudo PIM-SM interface appears for all IGMP-only interfaces.

      A pseudo multipoint LDP (Pseudo-MLDP) interface appears on ingress root nodes in M-LDP point-to-multipoint LSPs with inband signaling.

    • Interface address—Address of the downstream neighbor.

    • State—Information about the downstream neighbor: join or prune.

    • Flags—PIM join flags: R (RPtree), S (Sparse), W (Wildcard), or zero.

    • Uptime—Time since the downstream interface joined the group.

    • Time since last Join—Time since the last join message was received from the downstream interface.

    • Time since last Prune—Time since the last prune message was received from the downstream interface.

    • rpf-vector—IP address of the RPF vector TLV .

    extensive

    Number of downstream interfaces

    Total number of outgoing interfaces for each (S,G) entry.

    extensive

    Assert Timeout

    Length of time between assert cycles on the downstream interface. Not displayed if the assert timer is null.

    extensive

    Keepalive timeout

    Time remaining until the downstream join state is updated (in seconds). If the downstream join state is not updated before this keepalive timer reaches zero, the entry is deleted. If there is a directly connected host, Keepalive timeout is Infinity.

    extensive

    Uptime

    Time since the creation of (S,G) or (*,G) state. The uptime is not refreshed every time a PIM join message is received for an existing (S,G) or (*,G) state.

    extensive

    Bidirectional accepting interfaces

    Interfaces on the routing device that forward bidirectional PIM traffic.

    The reasons for forwarding bidirectional PIM traffic are that the interface is the winner of the designated forwarder election (DF Winner), or the interface is the reverse path forwarding (RPF) interface toward the RP (RPF).

    extensive

    Sample Output

    show pim join summary

    user@host> show pim join summary
    Instance: PIM.master Family: INET
    
    Route type            Route count
    (s,g)                 2
    (*,g)                 1
    
    Instance: PIM.master Family: INET6
    

    show pim join (PIM Sparse Mode)

    user@host> show pim join
    Instance: PIM.master Family: INET
    R = Rendezvous Point Tree, S = Sparse, W = Wildcard
    
    Group: 233.252.0.1
        Source: *
        RP: 10.255.14.144
        Flags: sparse,rptree,wildcard
        Upstream interface: Local
    
    Group: 233.252.0.1
        Source: 10.255.14.144
        Flags: sparse,spt
        Upstream interface: Local
    
    Group: 233.252.0.1
        Source: 10.255.70.15
        Flags: sparse,spt
        Upstream interface: so-1/0/0.0
    
    Instance: PIM.master Family: INET6
    R = Rendezvous Point Tree, S = Sparse, W = Wildcard

    show pim join (Bidirectional PIM)

    user@host> show pim join
    Instance: PIM.master Family: INET
    R = Rendezvous Point Tree, S = Sparse, W = Wildcard
    
    Group: 233.252.0.1
        Bidirectional group prefix length: 24
        Source: *
        RP: 10.10.13.2
        Flags: bidirectional,rptree,wildcard
        Upstream interface: ge-0/0/1.0            
    
    Group: 233.252.0.2
        Bidirectional group prefix length: 24
        Source: *
        RP: 10.10.1.3
        Flags: bidirectional,rptree,wildcard
        Upstream interface: ge-0/0/1.0 (RP Link)
    
    Group: 233.252.0.3
        Bidirectional group prefix length: 24
        Source: *
        RP: 10.10.13.2
        Flags: bidirectional,rptree,wildcard
        Upstream interface: ge-0/0/1.0            
    
    Group: 233.252.0.4
        Bidirectional group prefix length: 24
        Source: *
        RP: 10.10.1.3
        Flags: bidirectional,rptree,wildcard
        Upstream interface: ge-0/0/1.0 (RP Link)
    
    Instance: PIM.master Family: INET6
    R = Rendezvous Point Tree, S = Sparse, W = Wildcard

    show pim join inet6

    user@host> show pim join inet6
    Instance: PIM.master Family: INET6
     R = Rendezvous Point Tree, S = Sparse, W = Wildcard
     
     Group: 2001:db8::e000:101
         Source: *
         RP: ::46.0.0.13
         Flags: sparse,rptree,wildcard
         Upstream interface: Local                 
     
     Group: 2001:db8::e000:101
         Source: ::1.1.1.1
         Flags: sparse
         Upstream interface: unknown (no neighbor)
     
     Group: 2001:db8::e800:101
         Source: ::1.1.1.1
         Flags: sparse
         Upstream interface: unknown (no neighbor)
     
     Group: 2001:db8::e800:101
         Source: ::1.1.1.2
         Flags: sparse
         Upstream interface: unknown (no neighbor)

    show pim join inet6 star-g

    user@host> show pim join inet6 star-g
    Instance: PIM.master Family: INET6
     R = Rendezvous Point Tree, S = Sparse, W = Wildcard
     
     Group: 2001:db8::e000:101
         Source: *
         RP: ::46.0.0.13
         Flags: sparse,rptree,wildcard
         Upstream interface: Local

    show pim join instance <instance-name>

    user@host> show pim join instance VPN-A
    Instance: PIM.VPN-A Family: INET
    R = Rendezvous Point Tree, S = Sparse, W = Wildcard
    
    Group: 233.252.0.2
        Source: *
        RP: 10.10.47.100
        Flags: sparse,rptree,wildcard
        Upstream interface: Local
    
    Group: 233.252.0.2
        Source: 192.168.195.74
        Flags: sparse,spt
        Upstream interface: at-0/3/1.0
    
    Group: 233.252.0.2
        Source: 192.168.195.169
        Flags: sparse
        Upstream interface: so-1/0/1.0
    
    Instance: PIM.VPN-A Family: INET6
    R = Rendezvous Point Tree, S = Sparse, W = Wildcard

    show pim join instance <instance-name> downstream-count

    user@host> show pim join instance VPN-A downstream-count
    Instance: PIM.SML_VRF_4 Family: INET
    R = Rendezvous Point Tree, S = Sparse, W = Wildcard
    
    Group: 233.252.0.1
        Source: *
        RP: 10.11.11.6
        Flags: sparse,rptree,wildcard
        Upstream interface: mt-1/2/10.32813
        Number of downstream interfaces: 4
    
    Group: 233.252.0.1
        Source: 10.1.1.1
        Flags: sparse,spt
        Upstream interface: ge-0/0/3.5
        Number of downstream interfaces: 5

    show pim join instance <instance-name> downstream-count extensive

    user@host> show pim join instance VPN-A downstream-count extensive
    Instance: PIM.SML_VRF_4 Family: INET
    R = Rendezvous Point Tree, S = Sparse, W = Wildcard
    
    Group: 233.252.0.1
        Source: *
        RP: 10.11.11.6
        Flags: sparse,rptree,wildcard
        Upstream interface: mt-1/2/10.32813
        Upstream neighbor: 10.2.2.7 (assert winner)
        Upstream state: Join to RP
        Uptime: 02:51:41
        Number of downstream interfaces: 4
        Number of downstream neighbors: 4
    
    Group: 233.252.0.1
        Source: 10.1.1.1   
        Flags: sparse,spt   
        Upstream interface: ge-0/0/3.5
        Upstream neighbor: 10.1.1.17
        Upstream state: Join to Source, Prune to RP
        Keepalive timeout: 0
        Uptime: 02:51:42
        Number of downstream interfaces: 5
        Number of downstream neighbors: 7

    show pim join detail

    user@host> show pim join detail
    Instance: PIM.master Family: INET
    R = Rendezvous Point Tree, S = Sparse, W = Wildcard
    
    Group: 233.252.0.1
        Source: *
        RP: 10.255.14.144
        Flags: sparse,rptree,wildcard
        Upstream interface: Local
    
    Group: 233.252.0.1
        Source: 10.255.14.144
        Flags: sparse,spt
        Upstream interface: Local
    
    Group: 233.252.0.1
        Source: 10.255.70.15
        Flags: sparse,spt
        Upstream interface: so-1/0/0.0
    
    Instance: PIM.master Family: INET6
    R = Rendezvous Point Tree, S = Sparse, W = Wildcard

    show pim join extensive (PIM Resolve TLV for Multicast in Seamless MPLS)

    user@host> show pim join extensive
    Group: 228.26.1.5
        Source: 60.0.0.101
        Flags: sparse,spt
        Upstream interface: ge-5/0/0.1        
        Upstream neighbor: 10.100.1.13
        Upstream state: Join to Source
    Upstream rpf-vector: 10.100.20.1
        Keepalive timeout: 178
        Uptime: 17:44:38 
        Downstream neighbors:
            Interface: xe-2/0/3.1           
                203.21.2.190 State: Join Flags: S Timeout: 156
                Uptime: 17:44:38 Time since last Join: 00:00:54
                rpf-vector: 10.100.20.1
            Interface: xe-2/0/2.1           
                203.21.1.190 State: Join Flags: S Timeout: 156
                Uptime: 17:44:38 Time since last Join: 00:00:54
                rpf-vector: 10.100.20.2
        Number of downstream interfaces: 2
        Number of downstream neighbors: 2
    

    show pim join extensive (PIM Sparse Mode)

    user@host> show pim join extensive
    Instance: PIM.master Family: INET
    R = Rendezvous Point Tree, S = Sparse, W = Wildcard
    
    Group: 233.252.0.1
        Source: *
        RP: 10.255.14.144
        Flags: sparse,rptree,wildcard
        Upstream interface: Local
        Upstream neighbor: Local
        Upstream state: Local RP
        Uptime: 00:03:49
        Downstream neighbors:
            Interface: so-1/0/0.0
                10.111.10.2 State: Join Flags: SRW Timeout: 174
                Uptime: 00:03:49 Time since last Join: 00:01:49
            Interface: mt-1/1/0.32768
                10.10.47.100 State: Join Flags: SRW  Timeout: Infinity
                Uptime: 00:03:49 Time since last Join: 00:01:49
        Number of downstream interfaces: 2
    
    Group: 233.252.0.1
        Source: 10.255.14.144
        Flags: sparse,spt
        Upstream interface: Local
        Upstream neighbor: Local
        Upstream state: Local Source, Local RP
        Keepalive timeout: 344
        Uptime: 00:03:49
        Downstream neighbors:
            Interface: so-1/0/0.0
                10.111.10.2 State: Join Flags: S Timeout: 174
                Uptime: 00:03:49 Time since last Prune: 00:01:49
            Interface: mt-1/1/0.32768
                10.10.47.100 State: Join Flags: S   Timeout: Infinity
                Uptime: 00:03:49 Time since last Prune: 00:01:49
        Number of downstream interfaces: 2
    
    Group: 233.252.0.1
        Source: 10.255.70.15
        Flags: sparse,spt
        Upstream interface: so-1/0/0.0
        Upstream neighbor: 10.111.10.2
        Upstream state: Local RP, Join to Source
        Keepalive timeout: 344
        Uptime: 00:03:49
        Downstream neighbors:
            Interface: Pseudo-GMP
                fe-0/0/0.0 fe-0/0/1.0 fe-0/0/3.0
            Interface: so-1/0/0.0 (pruned)
                10.111.10.2 State: Prune Flags: SR Timeout: 174
                Uptime: 00:03:49 Time since last Prune: 00:01:49
            Interface: mt-1/1/0.32768
                10.10.47.100 State: Join Flags: S   Timeout: Infinity
                Uptime: 00:03:49 Time since last Prune: 00:01:49
        Number of downstream interfaces: 3
    
    Instance: PIM.master Family: INET6
    R = Rendezvous Point Tree, S = Sparse, W = Wildcard

    show pim join extensive (Bidirectional PIM)

    user@host> show pim join extensive
    Instance: PIM.master Family: INET
    R = Rendezvous Point Tree, S = Sparse, W = Wildcard
    
    Group: 233.252.0.0
        Bidirectional group prefix length: 24
        Source: *
        RP: 10.10.13.2
        Flags: bidirectional,rptree,wildcard
        Upstream interface: ge-0/0/1.0            
        Upstream neighbor: 10.10.1.2
        Upstream state: None
        Uptime: 00:03:49
        Bidirectional accepting interfaces:
            Interface: ge-0/0/1.0    (RPF)
            Interface: lo0.0         (DF Winner)
        Number of downstream interfaces: 0  
    
    Group: 233.252.0.1
        Bidirectional group prefix length: 24
        Source: *
        RP: 10.10.13.2
        Flags: bidirectional,rptree,wildcard
        Upstream interface: ge-0/0/1.0            
        Upstream neighbor: 10.10.1.2
        Upstream state: None
        Uptime: 00:03:49
        Bidirectional accepting interfaces:
            Interface: ge-0/0/1.0    (RPF)
            Interface: lo0.0         (DF Winner)
         Downstream neighbors:
             Interface: lt-1/0/10.24
                 10.0.24.4 State: Join   RW  Timeout: 185
             Interface: lt-1/0/10.23
                 10.0.23.3 State: Join   RW  Timeout: 184
         Number of downstream interfaces: 2
    
    Group: 233.252.0.2
        Bidirectional group prefix length: 24
        Source: *
        RP: 10.10.1.3
        Flags: bidirectional,rptree,wildcard
        Upstream interface: ge-0/0/1.0 (RP Link)
        Upstream neighbor: Direct
        Upstream state: Local RP
        Uptime: 00:03:49
        Bidirectional accepting interfaces:
            Interface: ge-0/0/1.0    (RPF)
            Interface: lo0.0         (DF Winner)
            Interface: xe-4/1/0.0    (DF Winner)
        Number of downstream interfaces: 0  
    
    Instance: PIM.master Family: INET6
    R = Rendezvous Point Tree, S = Sparse, W = Wildcard

    show pim join extensive (Bidirectional PIM with a Directly Connected Phantom RP)

    user@host> show pim join extensive
    Instance: PIM.master Family: INET
    R = Rendezvous Point Tree, S = Sparse, W = Wildcard
    
    Group: 233.252.0.0
        Bidirectional group prefix length: 24
        Source: *
        RP: 10.10.1.3
        Flags: bidirectional,rptree,wildcard
        Upstream interface: ge-0/0/1.0 (RP Link)
        Upstream neighbor: Direct
        Upstream state: Local RP
        Uptime: 00:03:49
        Bidirectional accepting interfaces:
            Interface: ge-0/0/1.0    (RPF)
            Interface: lo0.0         (DF Winner)
            Interface: xe-4/1/0.0    (DF Winner)
    Number of downstream interfaces: 0

    show pim join instance <instance-name> extensive

    user@host> show pim join instance VPN-A extensive
    Instance: PIM.VPN-A Family: INET
    R = Rendezvous Point Tree, S = Sparse, W = Wildcard
    
    Group: 233.252.0.2
        Source: *
        RP: 10.10.47.100
        Flags: sparse,rptree,wildcard
        Upstream interface: Local
        Upstream neighbor: Local
        Upstream state: Local RP
        Uptime: 00:03:49
        Downstream neighbors:
            Interface: mt-1/1/0.32768
                10.10.47.101 State: Join Flags: SRW Timeout: 156
                Uptime: 00:03:49 Time since last Join: 00:01:49
        Number of downstream interfaces: 1
    
    Group: 233.252.0.2
        Source: 192.168.195.74
        Flags: sparse,spt
        Upstream interface: at-0/3/1.0
        Upstream neighbor: 10.111.30.2
        Upstream state: Local RP, Join to Source
        Keepalive timeout: 156
        Uptime: 00:14:52
    
    Group: 233.252.0.2
        Source: 192.168.195.169
        Flags: sparse
        Upstream interface: so-1/0/1.0
        Upstream neighbor: 10.111.20.2
        Upstream state: Local RP, Join to Source
        Keepalive timeout: 156
        Uptime: 00:14:52

    show pim join extensive (Ingress Node with Multipoint LDP Inband Signaling for Point-to-Multipoint LSPs)

    user@host> show pim join extensive
    Instance: PIM.master Family: INET
    R = Rendezvous Point Tree, S = Sparse, W = Wildcard
    
    Group: 233.252.0.1
        Source: 192.168.219.11
        Flags: sparse,spt
        Upstream interface: fe-1/3/1.0            
        Upstream neighbor: Direct
        Upstream state: Local Source
        Keepalive timeout: 
        Uptime: 11:27:55 
        Downstream neighbors:
            Interface: Pseudo-MLDP            
            Interface: lt-1/2/0.25            
                10.2.5.2 State: Join Flags: S   Timeout: Infinity
                Uptime: 11:27:55 Time since last Join: 11:27:55
    
    Group: 233.252.0.2
        Source: 192.168.219.11
        Flags: sparse,spt
        Upstream interface: fe-1/3/1.0            
        Upstream neighbor: Direct
        Upstream state: Local Source
        Keepalive timeout: 
        Uptime: 11:27:41 
        Downstream neighbors:
            Interface: Pseudo-MLDP            
    
    Group: 233.252.0.3
        Source: 192.168.219.11
        Flags: sparse,spt
        Upstream interface: fe-1/3/1.0            
        Upstream neighbor: Direct
        Upstream state: Local Source
        Keepalive timeout: 
        Uptime: 11:27:41 
        Downstream neighbors:
            Interface: Pseudo-MLDP            
    
    Group: 233.252.0.22
        Source: 10.2.7.7
        Flags: sparse,spt
        Upstream interface: lt-1/2/0.27           
        Upstream neighbor: Direct
        Upstream state: Local Source
        Keepalive timeout: 
        Uptime: 11:27:25 
        Downstream neighbors:
            Interface: Pseudo-MLDP            
    
    Instance: PIM.master Family: INET6
    R = Rendezvous Point Tree, S = Sparse, W = Wildcard
    
    Group: 2001:db8::1:2
        Source: 2001:db8::1:2:7:7
        Flags: sparse,spt
        Upstream interface: lt-1/2/0.27           
        Upstream neighbor: Direct
        Upstream state: Local Source
        Keepalive timeout: 
        Uptime: 11:27:26 
        Downstream neighbors:
            Interface: Pseudo-MLDP 

    show pim join extensive (Egress Node with Multipoint LDP Inband Signaling for Point-to-Multipoint LSPs)

    user@host> show pim join extensive
    Instance: PIM.master Family: INET
    R = Rendezvous Point Tree, S = Sparse, W = Wildcard
    
    Group: 233.252.0.0
        Source: *
        RP: 10.1.1.1
        Flags: sparse,rptree,wildcard
        Upstream interface: Local                 
        Upstream neighbor: Local
        Upstream state: Local RP
        Uptime: 11:31:33 
        Downstream neighbors:
            Interface: fe-1/3/0.0             
                192.168.209.9 State: Join Flags: SRW  Timeout: Infinity
                Uptime: 11:31:33 Time since last Join: 11:31:32
    
    Group: 233.252.0.1
        Source: 192.168.219.11
        Flags: sparse,spt
        Upstream protocol: MLDP
        Upstream interface: Pseudo MLDP           
        Upstream neighbor: MLDP LSP root <10.1.1.2>
        Upstream state: Join to Source
        Keepalive timeout: 
        Uptime: 11:31:32 
        Downstream neighbors:
            Interface: so-0/1/3.0             
                192.168.92.9 State: Join Flags: S   Timeout: Infinity
                Uptime: 11:31:30 Time since last Join: 11:31:30
        Downstream neighbors:
            Interface: fe-1/3/0.0             
                192.168.209.9 State: Join Flags: S   Timeout: Infinity
                Uptime: 11:31:32 Time since last Join: 11:31:32
    
    Group: 233.252.0.2
        Source: 192.168.219.11
        Flags: sparse,spt
        Upstream protocol: MLDP
        Upstream interface: Pseudo MLDP           
        Upstream neighbor: MLDP LSP root <10.1.1.2>
        Upstream state: Join to Source
        Keepalive timeout: 
        Uptime: 11:31:32 
        Downstream neighbors:
            Interface: so-0/1/3.0             
                192.168.92.9 State: Join Flags: S   Timeout: Infinity
                Uptime: 11:31:30 Time since last Join: 11:31:30
        Downstream neighbors:
            Interface: lt-1/2/0.14            
                10.1.4.4 State: Join Flags: S Timeout: 177
                Uptime: 11:30:33 Time since last Join: 00:00:33
        Downstream neighbors:
            Interface: fe-1/3/0.0             
                192.168.209.9 State: Join Flags: S   Timeout: Infinity
                Uptime: 11:31:32 Time since last Join: 11:31:32
    
    Group: 233.252.0.3
        Source: 192.168.219.11
        Flags: sparse,spt
        Upstream protocol: MLDP
        Upstream interface: Pseudo MLDP           
        Upstream neighbor: MLDP LSP root <10.1.1.2>
        Upstream state: Join to Source
        Keepalive timeout: 
        Uptime: 11:31:32 
        Downstream neighbors:
            Interface: fe-1/3/0.0             
                192.168.209.9 State: Join Flags: S   Timeout: Infinity
                Uptime: 11:31:32 Time since last Join: 11:31:32
    
    Group: 233.252.0.22                        
        Source: 10.2.7.7
        Flags: sparse,spt
        Upstream protocol: MLDP
        Upstream interface: Pseudo MLDP           
        Upstream neighbor: MLDP LSP root <10.1.1.2>
        Upstream state: Join to Source
        Keepalive timeout: 
        Uptime: 11:31:30 
        Downstream neighbors:
            Interface: so-0/1/3.0             
                192.168.92.9 State: Join Flags: S   Timeout: Infinity
                Uptime: 11:31:30 Time since last Join: 11:31:30
    
    Instance: PIM.master Family: INET6
    R = Rendezvous Point Tree, S = Sparse, W = Wildcard
    
    Group: 2001:db8::1:2
        Source: 2001:db8::1:2:7:7
        Flags: sparse,spt
        Upstream protocol: MLDP
        Upstream interface: Pseudo MLDP           
        Upstream neighbor: MLDP LSP root <10.1.1.2>
        Upstream state: Join to Source
        Keepalive timeout: 
        Uptime: 11:31:32 
        Downstream neighbors:
            Interface: fe-1/3/0.0             
                2001:db8::21f:12ff:fea5:c4db State: Join Flags: S   Timeout: Infinity
                Uptime: 11:31:32 Time since last Join: 11:31:32

    show ldp database

    List of Syntax

    Syntax

    Syntax

    show ldp database
    <brief | detail | extensive>
    <inet | l2circuit>
    <instance instance-name>
    <logical-system (all | logical-system-name)>
    <p2mp>
    <session session>
    <summary>

    Release Information

    Command introduced before Junos OS Release 7.4.

    summary option introduced in Junos OS Release 14.2.

    Description

    Display entries in the LDP database.

    Options

    noneDisplay standard information about all entries in the LDP database for all routing instances.
    brief | detail | extensive(Optional) Display the specified level of output.
    inet | l2circuit(Optional) Display only IPv4 or Layer 2 circuit bindings.
    instance instance-name(Optional) Display routing instance information for the specified 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 point-to-multipoint binding information.
    session session(Optional) Display database for the specified session only. session is the destination address of the LDP session.
    summary(Optional)—Display summary output. This option displays the number of labels received and advertised for each LDP session.

    Required Privilege Level

    view

    List of Sample Output

    show ldp database (master)
    show ldp database (standby)
    show ldp database l2circuit detail
    show ldp database l2circuit extensive
    show ldp database p2mp (master)
    show ldp database p2mp (standby)
    show ldp database session
    show ldp database (Ingress Node with Multipoint LDP Inband Signaling for Point-to-Multipoint LSPs)
    show ldp database (Egress Node with Multipoint LDP Inband Signaling for Point-to-Multipoint LSPs)
    show ldp database summary

    Output Fields

    Table 5 describes the output fields for the show ldp database command. Output fields are listed in the approximate order in which they appear.

    Table 5: show ldp database Output Fields

    Field Name

    Field Description

    Level of Output

    Input label database

    Label received from the other router.

    All levels

    Output label database

    Label advertised to the other router.

    All levels

    session-identifier

    Session identifier, which includes the local and remote label space identifiers.

    All levels

    Labels received

    Number of labels received from the other router.

    All levels

    Labels advertised

    Number of labels advertised to the other router.

    All levels.

    Label

    Label binding to a route prefix.

    All levels

    Prefix

    Route prefix.

    It can be one of the following values:

    • IP prefix.

    • Point-to-multipoint root address, multicast source address, and multicast group address when multipoint LDP (M-LDP) inband signaling is configured.

    • Layer 2 encapsulation type.

    Layer 2 encapsulation types are displayed in the format L2CKT control word status encapsulation-type vc-number, for example, L2CKT CtflWord FRAME RELAY VC 2

    • control-word-status—Displays whether the use of the control word has been negotiated for this virtual circuit:

      • NoCtrlWord

      • CtrlWord

    • encapsulation-type—Encapsulation type:

      • FRAME RELAY

      • ATM AAL5

      • ATM CELL

      • VLAN

      • ETHERNET

      • CISCO_HDLC

      • PPP

    • VC number—Virtual circuit number. It can have any numeric value.

    • (Stale)—When you display the LDP database for the neighbor of a restarting router, the bindings leaned from the restarting neighbor are displayed as (Stale). Stale bindings are deleted if they are not refreshed within the recovery time.

    All levels

    MTU

    MTU of the Layer 2 circuit. MTU is displayed for all encapsulation types except ATM cell encapsulations.

    detail

    VCCV Control Channel types

    Virtual Circuit Connection Verification (VCCV) control channel types.

    • MPLS router alert label

    • MPLS PW label with TTL=1

    extensive

    VCCV Control Verification types

    The only valid VCCV control verification type is LSP ping.

    extensive

    TDM payload size

    Size of the Time Division Multiplex (TDM) payload.

    All levels

    TDM bitrate

    Bit rate for the TDM traffic.

    All levels

    Requested VLAN ID

    (VLANs) VLAN identifier of the Layer 2 circuit.

    detail

    Cell bundle size

    (ATM cell encapsulations) Maximum number of cells that the Layer 2 circuit can receive in a packet.

    detail

    State

    State of the label binding:

    • Active—Label binding has been installed and distributed appropriately. A label binding is almost always in this state.

    • New—New label that has not yet been distributed.

      • MapRcv—Waiting to receive a label mapping message.

      • MapSend—Waiting to send a label mapping message.

      • RelRcv—Waiting to receive a label release message.

      • RelRsnd—Waiting to receive a label release message before resending label mapping message.

      • RelSend—Waiting to send a label release message.

      • ReqSend—Waiting to send a label request message.

      • W/dSend—Waiting to send a label withdrawal message.

    detail

    Age

    Time elapsed since the binding was created.

    detail

    Sample Output

    show ldp database (master)

    user@host> show ldp database extensive
    Input label database, 10.255.107.232:0--10.255.107.236:0
      Label     Prefix
     299840      10.255.107.232/32
                State: Active
                Age: 9:35
                Entropy Label Capability: No
          3      10.255.107.236/32
                State: Active
                Age: 9:35
                Entropy Label Capability: No
     299776      L2CKT CtrlWord VLAN VC 100
                MTU: 1500 Requested VLAN ID: 600 Flow Label T Bit: 1 Flow Label R Bit: 1
                State: Active
                Age: 9:35
                Entropy Label Capability: No
                VCCV Control Channel types:
                    PWE3 control word 
                    MPLS router alert label 
                    MPLS PW label with TTL=1 
                VCCV Control Verification types:
                    LSP ping 
                    BFD with PW-ACH-encapsulation for Fault Detection 
                    BFD with IP/UDP-encapsulation for Fault Detection 
    
    Output label database, 10.255.107.232:0--10.255.107.236:0
      Label     Prefix
          3      10.255.107.232/32
                State: Active
                Age: 9:35
                Entropy Label Capability: No
     299776      10.255.107.236/32
                State: Active
                Age: 9:35
                Entropy Label Capability: No

    show ldp database (standby)

    user@host> show ldp database extensive
    Input label database, 10.255.107.236:0--10.255.107.234:0
      Label     Prefix
     299808      10.255.107.230/32
                State: Active
                Age: 1d 2:46:36
                Standby binding state:
                    Map messages: 1         
                    Release messages: 0
      Label     Prefix
     301136      10.255.107.232/32
                State: Active
                Age: 1d 2:46:36
                Standby binding state:
                    Map messages: 1
                    Release messages: 0
      Label     Prefix
          3      10.255.107.234/32
                State: Active
                Age: 1d 2:46:36
                Standby binding state:
                    Map messages: 1
                    Release messages: 0
      Label     Prefix
     302480      10.255.107.236/32
                State: Active
                Age: 1d 2:46:36
                Standby binding state:
                    Map messages: 1
                    Release messages: 0
    
    Output label database, 10.255.107.236:0--10.255.107.234:0
      Label     Prefix
     299904      10.255.107.230/32
                State: Active
                Age: 1d 2:46:36
     299936      10.255.107.232/32
                State: Active
                Age: 1d 2:46:36
     299872      10.255.107.234/32
                State: Active
                Age: 1d 2:46:36             
          3      10.255.107.236/32
                State: Active
                Age: 1d 2:46:36
     299952      P2MP root-addr 10.255.107.230, lsp-id 16777217
                State: Active
                Age: 1d 2:46:36
    

    show ldp database l2circuit detail

    user@host> show ldp database l2circuit detail
     Input label database, 10.255.245.44:0--10.255.245.45:0
        Label     Prefix
       100176     L2CKT CtrlWord ATM CELL (VC Mode) VC 100
                  Cell bundle size: 80
                  State: Active
                  Age: 9:48
       100256     L2CKT CtrlWord FRAME RELAY VC 101
                  MTU: 4470
                  State: Active
                  Age: 9:48
     
     Output label database, 10.255.245.44:0--10.255.245.45:0
        Label     Prefix
       100048     L2CKT CtrlWord ATM CELL (VC Mode) VC 100
                  Cell bundle size: 80
                  State: Active
                  Age: 9:48
       100112     L2CKT CtrlWord FRAME RELAY VC 101
                  MTU: 4470
                  State: Active
                  Age: 9:48
    

    show ldp database l2circuit extensive

    user@host> show ldp database l2circuit extensive
    Input label database, 10.255.245.198:0--10.255.245.194:0
      Label     Prefix
     299872     L2CKT CtrlWord PPP VC 100
                MTU: 4470
                VCCV Control Channel types:
                    MPLS router alert label 
                    MPLS PW label with TTL=1 
                VCCV Control Verification types:
                    LSP ping 
      Label     Prefix
                State: Active
                Age: 19:23:08

    show ldp database p2mp (master)

    user@host> show ldp database p2mp extensive
    
    Input label database, 10.255.107.232:0--10.255.107.236:0
      Label     Prefix
     569649      P2MP root-addr 10.255.107.232, lsp-id 16777217
                State: Active
                Age: 2d 6:41:46
    
    Output label database, 10.255.107.232:0--10.255.107.236:0
    
    Input label database, 10.255.107.232:0--10.255.107.238:0
    
    Output label database, 10.255.107.232:0--10.255.107.238:0
      Label     Prefix
     299888      P2MP root-addr 10.255.107.230, lsp-id 16777217
                State: Active
                Age: 2d 6:41:35
    

    show ldp database p2mp (standby)

    user@host> show ldp database p2mp extensive
    Input label database, 10.255.107.236:0--10.255.107.232:0
      Label     Prefix
     299968      P2MP root-addr 10.255.107.230, lsp-id 16777217
                State: Active
                Age: 4d 22:21:57
              Standby binding state:
                   Map messages: 1
                   Release messages: 0
    
    Output label database, 10.255.107.236:0--10.255.107.232:0
      Label     Prefix
          3      P2MP root-addr 10.255.107.232, lsp-id 1
                State: Active
                Age: 4d 22:21:57
    

    show ldp database session

    user@host> show ldp database session 10.1.1.195
    Input label database, 10.0.0.194:0--10.1.1.195:0
      Label     Prefix
     100002     10.255.245.197/32
     100003     10.255.245.196/32
     100004     10.0.0.194/32
          3     10.1.1.195/32
     100000     L2CKT NoCtrlWord FRAME RELAY VC 1
     100001     L2CKT CtrlWord FRAME RELAY VC 2
    Output label database, 10.0.0.194:0--10.1.1.195:0
      Label     Prefix
     100003     10.255.245.197/32
     100004     10.1.1.195/32
     100002     10.255.245.196/32
          3     10.0.0.194/32
     100000     L2CKT CtrlWord FRAME RELAY VC 2
     100001     L2CKT NoCtrlWord FRAME RELAY VC 1
    

    show ldp database (Ingress Node with Multipoint LDP Inband Signaling for Point-to-Multipoint LSPs)

    user@host> show ldp database
    Input label database, 1.1.1.2:0--1.1.1.3:0
      Label     Prefix
     299808      1.1.1.2/32
          3      1.1.1.3/32
     299792      1.1.1.6/32
     299776      10.255.2.227/32
     299840      P2MP root-addr 1.1.1.2, grp: 232.2.2.2, src: 1.2.7.7
     299824      P2MP root-addr 1.1.1.2, grp: 232.1.1.2, src: 192.168.219.11
    
    Output label database, 1.1.1.2:0--1.1.1.3:0
      Label     Prefix
          3      1.1.1.2/32
     299776      1.1.1.3/32
     299808      1.1.1.6/32
     299792      10.255.2.227/32
    
    Input label database, 1.1.1.2:0--1.1.1.6:0
      Label     Prefix
     299856      1.1.1.2/32
     299792      1.1.1.3/32
          3      1.1.1.6/32
     299776      10.255.2.227/32
     299888      P2MP root-addr 1.1.1.2, grp: 232.2.2.2, src: 1.2.7.7
     299808      P2MP root-addr 1.1.1.2, grp: 232.1.1.1, src: 192.168.219.11
     299824      P2MP root-addr 1.1.1.2, grp: 232.1.1.2, src: 192.168.219.11
     299840      P2MP root-addr 1.1.1.2, grp: 232.1.1.3, src: 192.168.219.11
     299872      P2MP root-addr 1.1.1.2, grp: ff3e::1:2, src: abcd::1:2:7:7
    
    Output label database, 1.1.1.2:0--1.1.1.6:0
      Label     Prefix
          3      1.1.1.2/32
     299776      1.1.1.3/32
     299808      1.1.1.6/32
     299792      10.255.2.227/32

    show ldp database (Egress Node with Multipoint LDP Inband Signaling for Point-to-Multipoint LSPs)

    user@host> show ldp database
    Input label database, 10.255.2.227:0--1.1.1.3:0
      Label     Prefix
     299808      1.1.1.2/32
          3      1.1.1.3/32
     299792      1.1.1.6/32
     299776      10.255.2.227/32
    
    Output label database, 10.255.2.227:0--1.1.1.3:0
      Label     Prefix
     299856      1.1.1.2/32
     299776      1.1.1.3/32
     299792      1.1.1.6/32
          3      10.255.2.227/32
    
    Input label database, 10.255.2.227:0--1.1.1.6:0
      Label     Prefix
     299856      1.1.1.2/32
     299792      1.1.1.3/32
          3      1.1.1.6/32
     299776      10.255.2.227/32
    
    Output label database, 10.255.2.227:0--1.1.1.6:0
      Label     Prefix
     299856      1.1.1.2/32
     299776      1.1.1.3/32
     299792      1.1.1.6/32
          3      10.255.2.227/32
     299888      P2MP root-addr 1.1.1.2, grp: 232.2.2.2, src: 1.2.7.7
     299808      P2MP root-addr 1.1.1.2, grp: 232.1.1.1, src: 192.168.219.11
     299824      P2MP root-addr 1.1.1.2, grp: 232.1.1.2, src: 192.168.219.11
     299840      P2MP root-addr 1.1.1.2, grp: 232.1.1.3, src: 192.168.219.11
     299872      P2MP root-addr 1.1.1.2, grp: ff3e::1:2, src: abcd::1:2:7:7

    show ldp database summary

    user@host> show ldp database summary
    Session ID                      Labels received    Labels advertised
    10.255.0.1:0--10.255.0.2:0                      4                  4
    10.255.0.1:0--10.255.0.3:0                      4                  4
    
    

    show ldp traffic-statistics

    List of Syntax

    Syntax

    Syntax

    show ldp traffic-statistics
    <instance instance-name>
    <logical-system (all | logical-system-name)>
    <p2mp>

    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.

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

    Options

    noneDisplay 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-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)

    Output Fields

    Table 6 lists the output fields for the show ldp traffic-statistics command. Output fields are listed in the approximate order in which they appear.

    Table 6: 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.)

    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.

    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
    NET FEC Statistics:
    
      FEC                  Type                Packets              Bytes    Shared
      10.255.107.230/32   Transit               30858            2022345    No   
                          Ingress                  20               5120    No   
    

    show ldp traffic-statistics p2mp (Ingress or transit router only, 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  
    

    show ldp traffic-statistics p2mp (Multipoint LDP with Multicast-Only Fast Reroute)

    user@host> show ldp traffic-statistics p2mp
    P2MP FEC Statistics:
    
    FEC(root_addr:lsp_id/grp,src)     Nexthop              Packets             Bytes Shared
    1.1.1.1:232.1.1.1,192.168.219.11, Label: 301568
                                      1.3.8.2                    0                 0 No  
                                      1.3.4.2                    0                 0 No  
    1.1.1.1:232.1.1.1,192.168.219.11, Label: 301584, Backup route
                                      1.3.4.2                    0                 0 No  
                                      1.3.8.2                    0                 0 No  
    1.1.1.1:232.1.1.2,192.168.219.11, Label: 301600
                                      1.3.8.2                    0                 0 No  
                                      1.3.4.2                    0                 0 No  
    1.1.1.1:232.1.1.2,192.168.219.11, Label: 301616, Backup route
                                      1.3.4.2                    0                 0 No  
                                      1.3.8.2                    0                 0 No  
    

    show multicast next-hops

    List of Syntax

    Syntax
    Syntax (EX Series Switch and the QFX Series)

    Syntax

    show multicast next-hops
    <brief | detail | terse>
    <identifier-number>
    <inet | inet6>
    <logical-system (all | logical-system-name)>

    Syntax (EX Series Switch and the QFX Series)

    show multicast next-hops
    <brief | detail>
    <identifier-number>
    <inet | inet6>

    Release Information

    Command introduced before Junos OS Release 7.4.

    Command introduced in Junos OS Release 9.0 for EX Series switches.

    inet6 option introduced in Junos OS Release 10.0 for EX Series switches.

    detail option display of next-hop ID number introduced in Junos OS Release 11.1 for M Series and T Series routers and EX Series switches.

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

    Support for bidirectional PIM added in Junos OS Release 12.1.

    Command introduced in Junos OS Release 14.1X53-D20 for the OCX Series.

    terse option introduced in Junos OS Release 16.1 for the MX Series.

    Description

    Display the entries in the IP multicast next-hop table.

    Options

    noneDisplay standard information about all entries in the multicast next-hop table for all supported address families.
    brief | detail | terse(Optional) Display the specified level of output. Use terse to display the total number of outgoing interfaces (as opposed to listing them) When you include the detail option on M Series and T Series routers and EX Series switches, the downstream interface name includes the next-hop ID number in parentheses, in the form fe-0/1/2.0-(1048574), where 1048574 is the next-hop ID number.

    Starting in Junos OS release 16.1, the show multicast next-hops statement shows the hierarchical next hops contained in the top-level next hop.

    identifier-number(Optional) Show a particular next hop by ID number. The range of values is 1 through 65,535.
    inet | inet6(Optional) Display entries for IPv4 or IPv6 family addresses, respectively.
    logical-system (all | logical-system-name)(Optional) Perform this operation on all logical systems or on a particular logical system.

    Required Privilege Level

    view

    List of Sample Output

    show multicast next-hops
    show multicast next-hops (Ingress Router, Multipoint LDP Inband Signaling for Point-to-Multipoint LSPs)
    show multicast next-hops (Egress Router, Multipoint LDP Inband Signaling for Point-to-Multipoint LSPs)
    show multicast next-hops (Bidirectional PIM)
    show multicast next-hops brief
    show multicast next-hops detail

    Output Fields

    Table 7 describes the output fields for the show multicast next-hops command. Output fields are listed in the approximate order in which they appear.

    Table 7: show multicast next-hops Output Fields

    Field Name

    Field Description

    Family

    Protocol family (such as INET).

    ID

    Next-hop identifier of the prefix. The identifier is returned by the routing device's Packet Forwarding Engine.

    Refcount

    Number of cache entries that are using this next hop.

    KRefcount

    Kernel reference count for the next hop.

    Downstream interface

    Interface names associated with each multicast next-hop ID.

    Incoming interface list

    List of interfaces that accept incoming traffic. Only shown for routes that do not use strict RPF-based forwarding, for example for bidirectional PIM.

    Sample Output

    show multicast next-hops

    user@host> show multicast next-hops
    Family: INET
    ID      Refcount  KRefcount Downstream interface
    262142          4          2 so-1/0/0.0
    262143          2          1 mt-1/1/0.49152
    262148          2          1 mt-1/1/0.32769
    

    show multicast next-hops (Ingress Router, Multipoint LDP Inband Signaling for Point-to-Multipoint LSPs)

    user@host> show multicast next-hops
    Family: INET
    ID          Refcount KRefcount Downstream interface Addr
    1048580            2         1 1048576
    (0x600dc04)        1         0 1048584
    (0x600ea04)        1         0 (0x600e924)
    1048583            2         1 1048579
    (0x600e144)        1         0 1048587
    (0x600e844)        1         0 (0x600e764)
    1048582            2         1 1048578
    (0x600df84)        1         0 1048586
    (0x600e684)        1         0 (0x600e5a4)
    1048581            2         1 1048577
    (0x600ddc4)        1         0 1048585
    (0x600ebc4)        1         0 (0x600eae4)

    show multicast next-hops (Egress Router, Multipoint LDP Inband Signaling for Point-to-Multipoint LSPs)

    user@host> show multicast next-hops
    Family: INET
    ID          Refcount KRefcount Downstream interface Addr
    (0x600e844)        8         0 1048575
    1048575           16         0 distributed-gmp

    show multicast next-hops (Bidirectional PIM)

    user@host> show multicast next-hops
    Family: INET
    ID          Refcount KRefcount Downstream interface
    2097151            8         4 ge-0/0/1.0
    
    Family: INET6
    ID          Refcount KRefcount Downstream interface
    2097157            2         1 ge-0/0/1.0
    
    Family: Incoming interface list
    ID          Refcount KRefcount Downstream interface
    513                5         2 lo0.0
                                   ge-0/0/1.0
    514                5         2 lo0.0
                                   ge-0/0/1.0
                                   xe-4/1/0.0
    515                3         1 lo0.0
                                   ge-0/0/1.0
                                   xe-4/1/0.0
    544                1         0 lo0.0
                                   xe-4/1/0.0

    show multicast next-hops brief

    The output for the show multicast next-hops brief command is identical to that for the show multicast next-hops command. For sample output, see show multicast next-hops.

    show multicast next-hops detail

    user@host> show multicast next-hops detail
    Family: INET
    ID          Refcount KRefcount Downstream interface Addr
    1048584            2         1 1048581
                                   1048580
                                   Flags 0x208 type 0x18 members 0/0/2/0/0
                                   Address 0xb1841c4
    1048591            3         2 787
                                   747
                                   Flags 0x206 type 0x18 members 0/0/2/0/0
                                   Address 0xb1847f4
    1048580            4         1 ge-1/1/9.0-(1048579)
                                   Flags 0x200 type 0x18 members 0/0/0/1/0
                                   Address 0xb184134
    1048581            2         0 736
                                   765
                                   Flags 0x3 type 0x18 members 0/0/2/0/0
                                   Address 0xb183dd4
    1048585           18         0 787
                                   747
                                   Flags 0x203 type 0x18 members 0/0/2/0/0
                                   Address 0xb184404
    
    Family: INET6
    ID          Refcount KRefcount Downstream interface Addr
    1048586            4         2 1048585
                                   1048583
                                   Flags 0x20c type 0x19 members 0/0/2/0/0
                                   Address 0xb1842e4
    1048583           14         4 ge-1/1/9.0-(1048582)
                                   Flags 0x200 type 0x19 members 0/0/0/1/0
                                   Address 0xb183ef4
    1048592            4         2 1048583
                                   1048591
                                   Flags 0x20c type 0x19 members 0/0/2/0/0
                                   Address 0xb184644
    

    show multicast route

    List of Syntax

    Syntax
    Syntax (EX Series Switch and the QFX Series)

    Syntax

    show multicast route
    <brief | detail | extensive | summary>
    <active | all | inactive>
    <group group>
    <inet | inet6>
    <instance instance name>
    <logical-system (all |  logical-system-name)>
    <oif-count>
    <regular-expression>
    <source-prefix source-prefix>

    Syntax (EX Series Switch and the QFX Series)

    show multicast route
    <brief | detail | extensive | summary>
    <active | all | inactive>
    <group group>
    <inet | inet6>
    <instance instance name>
    <regular-expression>
    <source-prefix source-prefix>

    Release Information

    Command introduced before Junos OS Release 7.4.

    Command introduced in Junos OS Release 9.0 for EX Series switches.

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

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

    Support for bidirectional PIM added in Junos OS Release 12.1.

    Command introduced in Junos OS Release 14.1X53-D20 for the OCX Series.

    oif-count option introduced in Junos OS Release 16.1 for the MX Series.

    xxxSupport for PIM NSR support for VXLAN added in Junos OS Release 16.2.

    Description

    Display the entries in the IP multicast forwarding table. You can display similar information with the show route table inet.1 command.

    Note: On all SRX Series devices, when a multicast route is not available, pending sessions are not torn down, and subsequent packets are queued. If no multicast route resolve comes back, then the traffic flow has to wait for the pending session to timed out. Then packets can trigger new pending session create and route resolve.

    Options

    noneDisplay standard information about all entries in the multicast forwarding table for all routing instances.
    brief | detail | extensive | summary(Optional) Display the specified level of output.
    active | all | inactive(Optional) Display all active entries, all entries, or all inactive entries, respectively, in the multicast forwarding table.
    group group(Optional) Display the cache entries for a particular group.
    inet | inet6(Optional) Display multicast forwarding table entries for IPv4 or IPv6 family addresses, respectively.
    instance instance-name(Optional) Display entries in the multicast forwarding table for a specific multicast instance.
    logical-system (all | logical-system-name)(Optional) Perform this operation on all logical systems or on a particular logical system.
    oif-count (Optional) Display a count of outgoing interfaces rather than listing them.
    regular-expression(Optional) Display information about the multicast forwarding table entries that match a UNIX OS-style regular expression.
    source-prefix source-prefix(Optional) Display the cache entries for a particular source prefix.

    Required Privilege Level

    view

    List of Sample Output

    show multicast route
    show multicast route (Bidirectional PIM)
    show multicast route brief
    show multicast route summary
    show multicast route detail
    show multicast route extensive (Bidirectional PIM)
    show multicast route extensive (Ingress Router, Multipoint LDP Inband Signaling for Point-to-Multipoint LSPs)
    show multicast route instance <instance-name> extensive
    show multicast route extensive instance <instance-name>
    show multicast route extensive (PIM NSR support for VXLAN on master Routing Engine)
    show multicast route extensive (PIM NSR support for VXLAN on backup Routing Engine)
    show multicast route extensive (PIM NSR support for VXLAN on backup Routing Engine)

    Output Fields

    Table 8 describes the output fields for the show multicast route command. Output fields are listed in the approximate order in which they appear.

    Table 8: show multicast route Output Fields

    Field Name

    Field Description

    Level of Output

    family

    IPv4 address family (INET) or IPv6 address family (INET6).

    All levels

    Group

    Group address.

    For any-source multicast routes, for example for bidirectional PIM, the group address includes the prefix length.

    All levels

    Source

    Prefix and length of the source as it is in the multicast forwarding table.

    All levels

    Incoming interface list

    List of interfaces that accept incoming traffic. Only shown for routes that do not use strict RPF-based forwarding, for example for bidirectional PIM.

    All levels

    Upstream interface

    Name of the interface on which the packet with this source prefix is expected to arrive.

    All levels

    Upstream rpf interface list

    When multicast-only fast reroute (MoFRR) is enabled, a PIM router propagates join messages on two upstream RPF interfaces to receive multicast traffic on both links for the same join request.

    All levels

    Downstream interface list

    List of interface names to which the packet with this source prefix is forwarded.

    distributed-gmp Added in Junos OS Release 17.4R1 to indicate that line cards with distributed IGMP interfaces are receiving multicast traffic for a given (s,g).

    All levels

    Number of outgoing interfaces

    Total number of outgoing interfaces for each (S,G) entry.

    extensive

    Session description

    Name of the multicast session.

    detail extensive

    Statistics

    Rate at which packets are being forwarded for this source and group entry (in Kbps and pps), and number of packets that have been forwarded to this prefix. If one or more of the kilobits per second packet forwarding statistic queries fails or times out, the statistics field displays Forwarding statistics are not available.

    Note: On QFX Series switches and OCX Series switches, this field does not report valid statistics.

    detail extensive

    Next-hop ID

    Next-hop identifier of the prefix. The identifier is returned by the routing device’s Packet Forwarding Engine and is also displayed in the output of the show multicast nexthops command.

    detail extensive

    Incoming interface list ID

    For bidirectional PIM, incoming interface list identifier.

    Identifiers for interfaces that accept incoming traffic. Only shown for routes that do not use strict RPF-based forwarding, for example for bidirectional PIM.

    detail extensive

    Upstream protocol

    The protocol that maintains the active multicast forwarding route for this group or source.

    When the show multicast route extensive command is used with the display-origin-protocol option, the field name is only Protocol and not Upstream Protocol. However, this field also displays the protocol that installed the active route.

    detail extensive

    Route type

    Type of multicast route. Values can be (S,G) or (*,G).

    summary

    Route state

    Whether the group is Active or Inactive.

    summary extensive

    Route count

    Number of multicast routes.

    summary

    Forwarding state

    Whether the prefix is pruned or forwarding.

    extensive

    Cache lifetime/timeout

    Number of seconds until the prefix is removed from the multicast forwarding table. A value of never indicates a permanent forwarding entry. A value of forever indicates routes that do not have keepalive times.

    extensive

    Wrong incoming interface notifications

    Number of times that the upstream interface was not available.

    extensive

    Uptime

    Time since the creation of a multicast route.

    extensive

    Sample Output

    Starting in Junos OS Release16.1, show multicast route displays the top-level hierarchical next hop.

    show multicast route

    user@host> show multicast route
    Family: INET
    
    Group: 233.252.0.0
        Source: 10.255.14.144/32
        Upstream interface: local
        Downstream interface list:
            so-1/0/0.0
    
    Group: 233.252.0.1
        Source: 10.255.14.144/32
        Upstream interface: local
        Downstream interface list:
            so-1/0/0.0
    
    Group: 233.252.0.1
        Source: 10.255.70.15/32
        Upstream interface: so-1/0/0.0
        Downstream interface list:
            mt-1/1/0.1081344
    
    Family: INET6

    show multicast route (Bidirectional PIM)

    user@host> show multicast route
    Family: INET
    
    Group: 233.252.0.1/24
        Source: *
        Incoming interface list: 
            lo0.0 ge-0/0/1.0
        Downstream interface list: 
            ge-0/0/1.0
    
    Group: 233.252.0.3/24
        Source: *
        Incoming interface list: 
            lo0.0 ge-0/0/1.0 xe-4/1/0.0
        Downstream interface list: 
            ge-0/0/1.0
    
    Group: 233.252.0.11/24
        Source: *
        Incoming interface list: 
            lo0.0 ge-0/0/1.0
        Downstream interface list: 
            ge-0/0/1.0
    
    Group: 233.252.0.13/24
        Source: *
        Incoming interface list: 
            lo0.0 ge-0/0/1.0 xe-4/1/0.0
        Downstream interface list: 
            ge-0/0/1.0
    Family: INET6

    show multicast route brief

    The output for the show multicast route brief command is identical to that for the show multicast route command. For sample output, see show multicast route or show multicast route (Bidirectional PIM).

    show multicast route summary

    user@host>show multicast route summary
    Instance: master Family: INET
    
    Route type   Route state    Route count
    (S,G)             Active             2
    (S,G)             Inactive           3
    
    Instance: master Family: INET6
    

    show multicast route detail

    user@host> show multicast route detail
    Family: INET
    
    Group: 233.252.0.0
        Source: 10.255.14.144/32
        Upstream interface: local
        Downstream interface list:
            so-1/0/0.0
        Session description: Unknown
        Statistics: 8 kBps, 100 pps, 45272 packets
        Next-hop ID: 262142
        Upstream protocol: PIM
    
    Group: 233.252.0.1
        Source: 10.255.14.144/32
        Upstream interface: local
        Downstream interface list:
            so-1/0/0.0
        Session description: Administratively Scoped
        Statistics: 0 kBps, 0 pps, 13404 packets
        Next-hop ID: 262142
        Upstream protocol: PIM
    
    Group: 233.252.0.1
        Source: 10.255.70.15/32
        Upstream interface: so-1/0/0.0
        Downstream interface list:
            mt-1/1/0.1081344
        Session description: Administratively Scoped
        Statistics: 46 kBps, 1000 pps, 921077 packets
    
        Next-hop ID: 262143
        Upstream protocol: PIM
    
    Family: INET6

    show multicast route extensive (Bidirectional PIM)

    user@host> show multicast route extensive
    Family: INET
    
    Group: 233.252.0.1/24
        Source: *
        Incoming interface list: 
            lo0.0 ge-0/0/1.0
        Downstream interface list: 
            ge-0/0/1.0
        Number of outgoing interfaces: 1
        Session description: NOB Cross media facilities
        Statistics: 0 kBps, 0 pps, 0 packets
        Next-hop ID: 2097153
        Incoming interface list ID: 585
        Upstream protocol: PIM
        Route state: Active
        Forwarding state: Forwarding
        Cache lifetime/timeout: forever
        Wrong incoming interface notifications: 0
    
    Group: 233.252.0.3/24
        Source: *
        Incoming interface list: 
            lo0.0 ge-0/0/1.0 xe-4/1/0.0
        Downstream interface list: 
            ge-0/0/1.0
        Number of outgoing interfaces: 1
        Session description: NOB Cross media facilities
        Statistics: 0 kBps, 0 pps, 0 packets
        Next-hop ID: 2097153
        Incoming interface list ID: 589
        Upstream protocol: PIM
        Route state: Active
        Forwarding state: Forwarding
        Cache lifetime/timeout: forever
        Wrong incoming interface notifications: 0
    
    Family: INET6
    

    show multicast route extensive (Ingress Router, Multipoint LDP Inband Signaling for Point-to-Multipoint LSPs)

    user@host> show multicast route extensive
     Family: INET
    
    Group: 226.0.0.1
        Source: 200.1.0.2/32
        Upstream interface: xe-3/0/0.0
        Downstream interface list: 
            ge-0/1/9.0
        Number of outgoing interfaces: 1
        Session description: Unknown
        Statistics: 78 kBps, 1000 pps, 34789 packets
        Next-hop ID: 1048582
        Upstream protocol: PIM
        Route state: Active
        Forwarding state: Forwarding
        Cache lifetime/timeout: 360 seconds
        Wrong incoming interface notifications: 0
        Uptime: 00:00:35
    
    Group: 226.0.0.2
        Source: 200.1.0.2/32
        Upstream interface: xe-3/0/0.0
        Downstream interface list: 
            ge-0/1/9.0
        Number of outgoing interfaces: 1
        Session description: Unknown
        Statistics: 78 kBps, 1000 pps, 34788 packets
        Next-hop ID: 1048583
        Upstream protocol: PIM
        Route state: Active
        Forwarding state: Forwarding
        Cache lifetime/timeout: 360 seconds
        Wrong incoming interface notifications: 0
        Uptime: 00:00:35
    
    Group: 226.0.0.3
        Source: 200.1.0.2/32
        Upstream interface: xe-3/0/0.0
        Downstream interface list: 
            ge-0/1/9.0
        Number of outgoing interfaces: 1
        Session description: Unknown
        Statistics: 78 kBps, 1000 pps, 34786 packets
        Next-hop ID: 1048580
        Upstream protocol: PIM
        Route state: Active
        Forwarding state: Forwarding
        Cache lifetime/timeout: 360 seconds
        Wrong incoming interface notifications: 0
        Uptime: 00:00:35
    
    Group: 226.0.0.4
        Source: 200.1.0.2/32
        Upstream interface: xe-3/0/0.0
        Downstream interface list: 
            ge-0/1/9.0
        Number of outgoing interfaces: 1
        Session description: Unknown
        Statistics: 78 kBps, 1000 pps, 34787 packets
        Next-hop ID: 1048581
        Upstream protocol: PIM
        Route state: Active
        Forwarding state: Forwarding
        Cache lifetime/timeout: 360 seconds
        Wrong incoming interface notifications: 0
        Uptime: 00:00:35
    
    Instance: master Family: INET6

    show multicast route instance <instance-name> extensive

    user@host> show multicast route instance mvpn extensive
    Family: INET
    roup: 233.252.0.10
        Source: 10.0.0.2/32 
        Upstream interface: xe-0/0/0.102
        Downstream interface list: 
            xe-10/3/0.0 xe-0/3/0.0 xe-0/0/0.106 xe-0/0/0.105 
    xe-0/0/0.103 xe-0/0/0.104 xe-0/0/0.107 xe-0/0/0.108
    Session description: Administratively Scoped Statistics: 256 kBps, 3998 pps, 670150 packets Next-hop ID: 1048579 Upstream protocol: MVPN Route state: Active Forwarding state: Forwarding Cache lifetime/timeout: forever Wrong incoming interface notifications: 58 Uptime: 00:00:04
    Instance: master Family: INET
    
    Group: 225.0.0.1
        Source: 101.0.0.2/32
        Upstream interface: ge-2/2/0.101
        Downstream interface list: 
            distributed-gmp
        Number of outgoing interfaces: 1
        Session description: Unknown
        Statistics: 105 kBps, 2500 pps, 4153361 packets
        Next-hop ID: 1048575
        Upstream protocol: PIM
        Route state: Active
        Forwarding state: Forwarding
        Cache lifetime/timeout: 360 seconds
        Wrong incoming interface notifications: 0
        Uptime: 00:31:46
    
    Group: 225.0.0.1
        Source: 101.0.0.3/32
        Upstream interface: ge-2/2/0.101
        Downstream interface list: 
            distributed-gmp
        Number of outgoing interfaces: 1
        Session description: Unknown
        Statistics: 105 kBps, 2500 pps, 4153289 packets
        Next-hop ID: 1048575
        Upstream protocol: PIM
        Route state: Active
        Forwarding state: Forwarding
        Cache lifetime/timeout: 360 seconds
        Wrong incoming interface notifications: 0
        Uptime: 00:31:46
    

    show multicast route extensive instance <instance-name>

    user@host> show multicast route extensive instance VPN-A

    The double asterisks (**) indicate new output, specific to min-rate and revert-delay settings made under the [edit routing-instances routing-instance-name protocols mvpn hot-root-standby] hierarchy.

    Instance: VPNA Family: INET
    
          Group: 227.1.1.1
              Source: 18.1.1.2/32
              Upstream rpf interface list: 
                  vt-2/0/10.1000 (P)
                    Session Id: 0x156 Session Status: Up
                    Min-rate: 10000 kbps Weight: 1 
                      Sender Id: Label 299808 
                  vt-2/0/10.1000 (B)
                    Session Id: 0x155 Session Status: Up
                    Min-rate: 10000 kbps Weight: 65533 
                    Sender Id: Label 299824 
              Downstream interface list: 
                  lt-2/0/10.0
              Number of outgoing interfaces: 1
              Session description: Unknown
              Statistics: 8258 kBps, 100707 pps, 513032034 packets
              RPF Next-hop ID: 803
              Next-hop ID: 1048580
              Upstream protocol: MVPN
              Route state: Active
              Forwarding state: Forwarding
              Cache lifetime/timeout: forever
              Wrong incoming interface notifications: 0
              Uptime: 01:24:55
     

    show multicast route extensive (PIM NSR support for VXLAN on master Routing Engine)

    user@host> show multicast route extensive
    Instance: master Family: INET
    
    Group: 233.252.0.1
        Source: 10.3.3.3/32
        Upstream interface: ge-3/1/2.0
        Downstream interface list: 
            -(593) 
        Number of outgoing interfaces: 1
        Session description: Organizational Local Scope
        Statistics: 0 kBps, 0 pps, 27 packets
        Next-hop ID: 1048576
        Upstream protocol: PIM
        Route state: Active
        Forwarding state: Forwarding (Forwarding state is set as 'Forwarding' in master RE.)
        Cache lifetime/timeout: forever
        Wrong incoming interface notifications: 0
        Uptime: 00:06:38
    
    Group: 233.252.0.1
        Source: 10.2.1.4/32
        Upstream interface: local
        Downstream interface list: 
            ge-3/1/2.0
        Number of outgoing interfaces: 1
        Session description: Organizational Local Scope
        Statistics: 0 kBps, 0 pps, 86 packets
        Next-hop ID: 1048575
        Upstream protocol: PIM
        Route state: Active                 
        Forwarding state: Forwarding (Forwarding state is set as 'Forwarding' in master RE.)
        Cache lifetime/timeout: forever
        Wrong incoming interface notifications: 0
        Uptime: 00:07:45
    
    Instance: master Family: INET6
    

    show multicast route extensive (PIM NSR support for VXLAN on backup Routing Engine)

    user@host> show multicast route extensive

    Instance: master Family: INET
    
    Group: 233.252.0.1
        Source: 10.3.3.3/32
        Upstream interface: ge-3/1/2.0
        Number of outgoing interfaces: 0
        Session description: Organizational Local Scope
        Forwarding statistics are not available
        Next-hop ID: 0
        Upstream protocol: PIM
        Route state: Active
        Forwarding state: Pruned (Forwarding state is set as 'Pruned' in backup RE.)
        Cache lifetime/timeout: forever
        Wrong incoming interface notifications: 0
        Uptime: 00:06:46
    
    Group: 233.252.0.1
        Source: 10.2.1.4/32
        Upstream interface: local
        Number of outgoing interfaces: 0
        Session description: Organizational Local Scope
        Forwarding statistics are not available
        Next-hop ID: 0
        Upstream protocol: PIM
        Route state: Active
        Forwarding state: Pruned  (Forwarding state is set as 'Pruned' in backup RE.)
        Cache lifetime/timeout: forever
        Wrong incoming interface notifications: 0
        Uptime: 00:07:54
    
    Instance: master Family: INET6
    

    show multicast route extensive (PIM NSR support for VXLAN on backup Routing Engine)

    user@host> show multicast route extensive
    Instance: master Family: INET
    
    Group: 233.252.0.1
        Source: 10.3.3.3/32
        Upstream interface: ge-3/1/2.0
        Downstream interface list: 
            -(593) 
        Number of outgoing interfaces: 1
        Session description: Organisational Local Scope
        Statistics: 0 kBps, 0 pps, 0 packets
        Next-hop ID: 1048576
        Upstream protocol: PIM
        Route state: Active
        Forwarding state: Forwarding (Forwarding state is set as 'Forwarding' in backup RE.)
        Cache lifetime/timeout: forever
        Wrong incoming interface notifications: 0
        Uptime: 00:06:38
    
    Group: 233.252.0.1
        Source: 10.2.1.4/32
        Upstream interface: local
        Downstream interface list: 
            ge-3/1/2.0
        Number of outgoing interfaces: 1
        Session description: Organisational Local Scope
        Statistics: 0 kBps, 0 pps, 0 packets
        Next-hop ID: 1048575
        Upstream protocol: PIM
        Route state: Active                 
        Forwarding state: Forwarding (Forwarding state is set as 'Forwarding' in backup RE.)
        Cache lifetime/timeout: forever
        Wrong incoming interface notifications: 0
        Uptime: 00:07:45
    
    Instance: master Family: INET6
    

    Modified: 2018-05-31