Understanding Bidirectional PIM
Designated Forwarder Election
Bidirectional PIM Modes
- bidirectional-sparse—Use if all multicast groups are operating in bidirectional, sparse, or SSM mode.
- bidirectional-sparse-dense—Use if multicast groups, except those that are specified in the dense-groups statement, are operating in bidirectional, sparse, or SSM mode.
Bidirectional Rendezvous Points
PIM Bootstrap and Auto-RP Support
- The routing instance must be configured to advertise candidate rendezvous points by way of auto-RP or PIM bootstrap, and an auto-RP mapping agent or bootstrap router, respectively, must be elected.
- The RP address must either be configured locally on an interface in the routing instance, or the RP address must belong to a subnet connected to an interface in the routing instance.
IGMP and MLD Support
- IGMP and MLD (*,G) membership reports trigger the PIM DF to originate bidirectional PIM (*,G) join messages.
- IGMP and MLD (S,G) membership reports do not trigger the PIM DF to originate bidirectional PIM (*,G) join messages.
Bidirectional PIM and Graceful Restart
Junos OS Enhancements to Bidirectional PIM
- Source-only branches without PIM join state
- Support for both IPv4 and IPv6 domain and multicast addresses
- Nonstop routing (NSR) for bidirectional PIM routes
- Support for bidirectional PIM in logical systems
- Support for non-forwarding and virtual router instances