Reducing Data Transmission Time Using the SPT
Specify the PIM Threshold That Triggers SPT Switching
Specify the PIM SPT Switch Period
Specify the PIM RP Threshold That Triggers Source-Specific Switching
Specify the PIM RP Switch Period
Monitor the Data Transfer Rate After a Register Stop Message
Enabling Static RP Configurations
Associate an Interface to a PIM Component
Configuring Designated Routers
Prioritize Router Messaging With PIM DR-Priority
Restore the Default Router Priority Designation
Configuring the PIM Override Interval
Specify the Interval to Delay Override Messages
Restore the Default Override Messaging Interval
Restore the Default LAN Delay Interval
Restore the Default BSR-Candidate Value
Configuring PIM Query Intervals
Specify the Hello Messaging Interval
Restore the Default Hello Messaging Interval
Configuring PIM Join and Prune Messaging
Specify the Join and Prune Messaging Interval
Restore the Default Message Interval
Configuring RP-Candidate Behavior
Specify the Address for the Candidate RP
Configuring RP Candidate Hold Time
Specify RP Candidate Hold Time
Restore the Default Candidate RP Hold Time
Specify the Address for the Static RP
PIM components can be set to either sparse mode or dense mode. Sparse mode is the default.
Sparse-mode routing protocols use shared trees. In a shared tree, sources forward multicast datagrams to a directly connected router, the designated router. The designated router encapsulates the datagram and unicasts it to an assigned RP router, which then forwards the datagram to members of multicast groups.
Dense-mode protocols are data driven, where multicast sources start sending multicast data packets, and receivers join if they want data packets or prune themselves.