Embedded Rendezvous Point (Rp) - Dell PowerConnect B-RX Configuration Manual

Select ethernet and enter the interface's slot number and port number to clear MLD traffic on a
physical interface.

Embedded Rendezvous Point (RP)

Release 02.6.00 provides support for embedded RP which enables a router to learn the RP
information using the multicast group destination address. This eliminates the need to maintain
the RP table through the RP state machine. For routers that are the RP, the router is statically
configured as the RP. This router is not required to be configured as a RP candidate.
A designated router (DR) receiving a MLD report checks for the presence of an embedded RP
address in the group address. If found, it uses this RP address as the target of the PIM Join that it
initiates and all subsequent protocol operations for this group.
A designated router (DR) receiving a new multicast stream from a directly connected source,
checks for the presence of an embedded RP address in the group address. If found, it uses this RP
address as the unicast destination address of the PIM Register packets that it initiates.
Other PIM routers that are also receiving PIM PDUs look into the group address for the presence of
an embedded RP address in the group address. If found, it uses this RP address for all its protocol
needs.
Note that all 3 cases above assume that a static RP has not been configured locally. A statically
configured RP has the highest precedence and will be used even if the group address contains an
embedded RP address. When determining the RP, the software employs the following precedence
table with the highest precedence item listed first.
1. Statically configured RP address
2. Embedded RP address
3. RP Set build using the RP state machine
Enabling the embedded RP
The following command may be used to enable the embedded RP feature.
BigIron RX(config-ipv6-pim-router)# rp-embedded
Syntax: [no] rp-embedded
Default: On
BigIron RX Series Configuration Guide
53-1001810-01
Multicast Listener Discovery and source specific multicast protocols(MLDv2)
49
1265