Cisco APIC Layer 3 Networking Configuration Guide, Release 6.2(x)

PDF

Cisco APIC Layer 3 Networking Configuration Guide, Release 6.2(x)

Rendezvous points

Updated: April 17, 2026

Want to summarize with AI?

Log in

Explains IP addresses that act as shared roots for multicast shared trees in multicast network domains.

A rendezvous point (RP) is an IP address that

  • acts as a shared root for a multicast shared tree in a multicast network domain

  • can be configured in multiple instances to cover different group ranges, and

  • requires unique group range configuration when multiple RPs are deployed.

RP types and requirements

PIM enabled border leafs are required for VRFs where multicast routing is enabled. PIM is enabled for a border leaf by enabling PIM at the L3Out level. When PIM is enabled for an L3Out this will enable PIM for all nodes and interfaces configured under that L3Out.

You can configure two types of RPs:

  • Static RP—Enables you to statically configure an RP for a multicast group range. To do so, you must configure the address of the RP on every router in the domain.

  • Fabric RP—Enables a PIM anycast RP loopback interface on all PIM-enabled border leaf switches in the VRF, which is necessary for supporting inter-VRF multicast (see Inter-VRF multicast). A PIM-enabled L3Out (with loopback interfaces) is required for fabric RP configuration. When configured, external routers can use the fabric RP using static RP configuration. Auto-RP and BSR are not supported with Fabric RP. Fabric RP peering with an external anycast RP member is not supported.

    Note

    Fabric RP has the following restrictions:

    • Fabric RP does not support fast-convergence mode.

    • The fabric IP:

      • Must be unique across all the static RP entries within the static RP and fabric RP.

      • Cannot be one of the Layer 3 out router IDs

For information about configuring an RP, see the following sections:

Note

The rendezvous point (RP) is required for the correct operation of PIM-SM ASM. The RP acts as the root of the shared tree, which initially connects multicast sources and receivers. After this, multicast receivers can join the source tree, bypassing the RP. Missing RP configuration can result in inconsistent multicast forwarding behavior depending on the placement of the multicast sources and receivers. For example, multicast forwarding may still function between sources and receivers connected to the same device even if the RP configuration is absent.