Configuring PIM Static Joins
Configure PIM static join to manually establish multicast group memberships.
PIM static join enables you to manually configure multicast group joins on routers, eliminating the need for Internet Group Management Protocol (IGMP) or Multicast Listener Discovery (MLD) join messages. This feature reduces initial join delays, conserves bandwidth, and helps ensure efficient multicast traffic delivery to the last-hop router. It is particularly useful when designated receiver devices cannot send join requests or when routers must consistently engage with known multicast groups. This helps in maintaining reliability and performance.
Benefits of PIM Static Join
-
Reduces initial join delay by enabling routers to configure multicast group joins manually, ensuring faster multicast traffic delivery.
-
Conserves bandwidth by eliminating the need for IGMP or MLD messages from receivers, optimizing network resource usage.
-
Enhances multicast delivery reliability in environments where receiver devices cannot send join requests, ensuring consistent connectivity.
-
Improves network performance in high-scale deployments by pre-provisioning multicast routes, facilitating efficient traffic distribution across multiple Packet Forwarding Engines.
To implement PIM static join, navigate to the [edit protocols pim]
hierarchy in configuration mode. Enter the configuration statement set protocols pim
static group <multicast address> source <source address> to specify
the desired multicast group and source, activating multicast routing
across Packet Forwarding Engines.
Enable static join for (225.0.0.1,10.10.10.1) and (225.0.0.1,10.10.10.2).
set protocols pim static group 225.0.0.1 source 10.10.10.1 set protocols pim static group 225.0.0.1 source 10.10.10.2
The show pim join extensive command displays the downstream neighbor's
interface as Pseudo-GMP static.
user@host> show pim join extensive
Instance: PIM.master Family: INET
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: 225.1.1.1
Source: 172.26.1.100
Flags: sparse
Upstream interface: ge-0/0/0.0
Upstream neighbor: 172.26.13.1
Upstream state: Join to Source
Keepalive timeout:
Uptime: 00:00:07
Downstream neighbors:
Interface: Pseudo-GMP
static
Number of downstream interfaces: 1
Number of downstream neighbors: 0
Control-Driven (S,G) Join Optimization
The Control-Driven (S,G) Join mechanism in Protocol Independent Multicast Any-Source
Multicast (PIM-ASM) enhances multicast by preemptively installing multicast forwarding
routes based on control-plane signals. This approach reduces latency and improves network
efficiency by eliminating the need for traditional data-driven resolve requests. By
simulating resolve requests within the control plane, multicast traffic is managed
efficiently, ensuring quicker route installations and minimizing convergence times. This
feature is advantageous for routers between the rendezvous point and the first-hop router,
optimizing scenarios where (S,G) joins are prevalent. To activate this functionality,
configure the control-driven-sg statement at the edit protocols
pim hierarchy, streamlining multicast and enhancing network performance.
The mechanism targets the optimization of multicast involving (S,G) joins, ensuring quicker convergence times by simulating resolve requests within the control plane. However, this feature does not extend to (*,G) joins. Routers from the receiver to the rendezvous point still require traditional resolve requests. The control-driven mechanism does not function during a switchover from the rendezvous-point tree to the shortest-path tree on the last-hop router in ASM cases.