IPv6 PIM Convergence on MAC Address Movement

The notification is triggered upon a change in port status, Reverse Path Forwarding (RPF) failure in the hardware, or by the unicast routing module if there is a change in the Layer 3 topology. If the topology change occurs without a change in port status or RPF failure, or if the Layer 3 topology change is not notified by the unicast routing module, IPv6 PIM convergence does not take place.

If there is a change in the source traffic at the Layer 2 interface, the RPF check fails because only loose RPF check is supported (loose RPF check detects the change in the source traffic only at the Layer 3 interface level). A notification for a change in the source traffic at the Layer 2 interface can be triggered by MAC address movement. The MAC address movement notification triggers RPF check on MAC address movement for directly connected sources. The MAC address movement notification can be triggered by configuring the ipv6 multicast-routing rpf-check mac-movement command. The MAC address movement notification triggers a notification to the IPv6 PIM module, which results in convergence. IPv6 PIM convergence is supported only in IPv6 PIM Sparse mode and is not supported in IPv6 PIM Dense mode.