Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

header-navigation
keyboard_arrow_up
close
keyboard_arrow_left
Junos CLI Reference
Table of Contents Expand all
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

rpf-vector (PIM)

date_range 20-Nov-23

Syntax

content_copy zoom_out_map
rpf-vector {
    policy (rpf-vector)[ policy-name];
}

Hierarchy Level

content_copy zoom_out_map
[edit dynamic-profiles name protocols pim],
[edit logical-systems name protocols pim],
[edit logical-systems name routing-instances name protocols pim],
[edit protocols pim],
[edit routing-instances name protocols pim]

Description

This feature provides a way for PIM source-specific multicast (SSM) to resolve Vector Type Length (TLV) for multicast in a seamless Multiprotocol Label Switching (MPLS) networks. In other words, it enables PIM to build multicast trees through an MPLS core. rpf-vector implements RFC 5496, Reverse Path Forwarding (RPF) Vector TLV .

When rpf-vector is enabled on an edge router that sends PIM join messages into the core, the join message includes a vector specifying the IP address of the next edge router along the path to the root of the multicast distribution tree (MDT). The core routers can then process the join message by sending it towards the specified edge router (i.e., toward the Vector). The address of the edge router serves as the RPF vector in the PIM join message so routers in the core can resolve the next-hop towards the source without the need for BGP in the core.

Only the IPv4 address family is supported.

Options

policy

Create a filter policy to determine whether or not to apply rpf-vector.

Required Privilege Level

routing

Release Information

Statement introduced in Junos OS Release 17.3R1.

footer-navigation