Related Documentation
- EX, M, MX, T Series
- Configuring PIM Auto-RP
- Configuring PIM Bootstrap Router
- Configuring PIM Dense Mode
- Configuring PIM Sparse-Dense Mode
- Configuring PIM and the Bidirectional Forwarding Detection (BFD) Protocol
- EX, J, M, MX, SRX, T Series
- Configuring PIM Filtering
- J, M, MX, SRX, T Series
- Configuring Basic PIM Settings
- M, MX, T Series
- Example: Configuring Nonstop Active Routing for PIM
- Examples: Configuring PIM RPT and SPT Cutover
- Examples: Configuring PIM Sparse Mode
Configuring a Designated Router for PIM
Configuring Interface Priority for PIM Designated Router Selection
A designated router (DR) sends periodic join messages and prune messages toward a group-specific rendezvous point (RP) for each group for which it has active members. When a Protocol Independent Multicast (PIM) routing device learns about a source, it originates a Multicast Source Discovery Protocol (MSDP) source-address message if it is the DR on the upstream interface.
By default, every PIM interface has the lowest probability (priority 0) of being selected as the DR. Configuring the interface DR priority helps ensure that changing an IP address does not alter your forwarding model.
To configure the interface designated router priority:
- This example shows the configuration for the routing instance.
Configure the interface globally or in the routing instance. [edit routing-instances PIM.master protocols pim interface ge-0/0/0.0 family inet]user@host# set priority 5
- Verify the configuration by checking the Hello Option DR Priority field in the output of the show pim neighbors detail command.user@host> show pim neighbors detail
Instance: PIM.master Interface: ge-0/0/0.0 Address: 192.168.195.37, IPv4, PIM v2, Mode: Sparse Hello Option Holdtime: 65535 seconds Hello Option DR Priority: 5 Hello Option LAN Prune Delay: delay 500 ms override 2000 ms Join Suppression supported Rx Join: Group Source Timeout 225.1.1.1 192.168.195.78 0 225.1.1.1 0 Interface: lo0.0 Address: 10.255.245.91, IPv4, PIM v2, Mode: Sparse Hello Option Holdtime: 65535 seconds Hello Option DR Priority: 1 Hello Option LAN Prune Delay: delay 500 ms override 2000 ms Join Suppression supported Interface: pd-6/0/0.32768 Address: 0.0.0.0, IPv4, PIM v2, Mode: Sparse Hello Option Holdtime: 65535 seconds Hello Option DR Priority: 0 Hello Option LAN Prune Delay: delay 500 ms override 2000 ms Join Suppression supported
Configuring PIM Designated Router Election on Point-to-Point Links
To comply with the latest PIM drafts, enable designated router (DR) election on all PIM interfaces, including point-to-point (P2P) interfaces. (DR election is enabled by default on all other interfaces.) One of the two routing devices might join a multicast group on its P2P link interface. The DR on that link is responsible for initiating the relevant join messages.
To enable DR election on point-to-point interfaces:
- On both point-to-point link routing devices, configure
the routing device globally or in the routing instance. This example
shows the configuration for the routing instance.[edit routing-instances PIM.master protocols pim]user@host# set dr-election-on-p2p
- Verify the configuration by checking the State field in the output of the show pim interfaces command. The possible values for the State field are DR, NotDR, and P2P. When a point-to-point link interface is elected to be the DR, the interface state becomes DR instead of P2P.
- If the show pim interfaces command continues
to report the P2P state, consider running the restart routing command on both routing devices on the point-to-point link. Then
recheck the state.
Caution: Do not restart a software process unless specifically asked to do so by your Juniper Networks customer support representative. Restarting a software process during normal operation of a routing platform could cause interruption of packet forwarding and loss of data.
[edit]user@host# run restart routing
Related Documentation
- EX, M, MX, T Series
- Configuring PIM Auto-RP
- Configuring PIM Bootstrap Router
- Configuring PIM Dense Mode
- Configuring PIM Sparse-Dense Mode
- Configuring PIM and the Bidirectional Forwarding Detection (BFD) Protocol
- EX, J, M, MX, SRX, T Series
- Configuring PIM Filtering
- J, M, MX, SRX, T Series
- Configuring Basic PIM Settings
- M, MX, T Series
- Example: Configuring Nonstop Active Routing for PIM
- Examples: Configuring PIM RPT and SPT Cutover
- Examples: Configuring PIM Sparse Mode
Published: 2013-04-03
Related Documentation
- EX, M, MX, T Series
- Configuring PIM Auto-RP
- Configuring PIM Bootstrap Router
- Configuring PIM Dense Mode
- Configuring PIM Sparse-Dense Mode
- Configuring PIM and the Bidirectional Forwarding Detection (BFD) Protocol
- EX, J, M, MX, SRX, T Series
- Configuring PIM Filtering
- J, M, MX, SRX, T Series
- Configuring Basic PIM Settings
- M, MX, T Series
- Example: Configuring Nonstop Active Routing for PIM
- Examples: Configuring PIM RPT and SPT Cutover
- Examples: Configuring PIM Sparse Mode