Context
You can configure the maximum size of each Join/Prune message, maximum number of entries in a Join/Prune message, and Join/Prune message transmission method on the switch to adjust join information
and prune information sent to upstream interfaces.
- If a PIM neighbor has a low performance and spends a long time to process each Join/Prune message, set a smaller size for each Join/Prune message on the switch to reduce the number of (S, G) entries carried
in Join/Prune messages. This mitigates the pressure on the PIM neighbor.
- If the throughput of Join/Prune messages on the PIM neighbor is low, the neighbor may fail to process Join/Prune messages in a timely manner, causing route flapping. To prevent this problem, set a smaller queue size for periodically sending Join/Prune
messages to reduce the number of (S, G) entries carried in Join/Prune message sent to the PIM neighbor per second. Then the switch sends Join/Prune messages in batches to the PIM neighbor, with a few
Join/Prune messages in each batch.
- By default, Join/Prune messages are transmitted to upstream neighbors in a package to improve the transmission efficiency. You can disable the package function as required.
Default Settings
Table 1 lists the default settings of Join/Prune messages.
Table 1 Default settings of Join/Prune messages
| Parameter |
Default Setting |
Maximum size of each Join/Prune message
|
8100 bytes
|
Maximum number of entries contained in Join/Prune messages
|
1020
|
Join/Prune message transmission method
|
Encapsulated in a package
|