Adjusting Control Parameters for Prune Messages
Context
A multicast device sends Prune messages upstream for requiring to stop forwarding multicast data. You can configure control parameters for Prune messages as required. If there is no special requirement, the default values are recommended.
Adjusting Time Parameters for Join/Prune Messages
Context
A PIM device sends Prune messages to its upstream neighbor to request the neighbor to stop sending multicast data to it. Prune messages are encapsulated in a Join/Prune message, which is defined by the IPv6 PIM protocol to control multicast forwarding. When the upstream neighbor receives a Join/Prune message, it starts a timer and sets the timer value to the holdtime of the Join/Prune message. If the upstream neighbor does not receive any Join/Prune message when the timer expires, the upstream neighbor starts to forward multicast data to the downstream interface again.
The holdtime of Join/Prune messages can be configured in the PIM-IPv6 view or interface view. If the holdtime is configured both in the PIM-IPv6 view and interface view, the configuration in the interface view takes effect.
Adjusting the Information Carrying Capacity of Join/Prune Messages
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 router to adjust 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 router 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 every second. Then the router sends Join/Prune messages in many 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.
Procedure
- Run system-view
The system view is displayed.
- Run pim-ipv6
The PIM-IPv6 view is displayed.
- Run join-prune max-packet-length packet-length
The maximum size of each Join/Prune message to be sent is configured.
- Run join-prune periodic-messages queue-size queue-size
The maximum number of entries in Join/Prune messages sent in a second is configured.
- Run join-prune triggered-message-cache disable
The function to package Join/Prune messages in real time is disabled.
Adjusting Control Parameters for Prune Delay
Context
LAN-delay specifies the delay from the time a device receives a Prune message from a downstream interface to the time it sends the Prune message to an upstream interface. A PIM device does not prune the corresponding downstream interface immediately after it sends the Prune message. If another device still requests multicast data, it needs to send a Join message to the upstream device within this period. The period for overriding the Prune message is called override-interval. The delay from the time a PIM device receives a Prune message to the time it performs the prune action is the sum of the LAN-delay and override-interval.
The LAN-delay and override-interval can be configured globally or on an interface. If you configure the LAN-delay and override-interval in the global PIM-IPv6 view and in the interface view simultaneously, the configuration in the interface view takes effect.
Verifying the Configuration of Control Parameters for Prune Messages
Context
After control parameters for Prune messages are configured, you can check information about the IPv6 PIM interface, statistics about IPv6 PIM control messages, and IPv6 PIM routing table.
Procedure
- Run the display pim ipv6 interface [ interface-type interface-number | up | down ] [ verbose ] command to check IPv6 PIM information on an interface.
- Run the display pim ipv6 control-message counters [ message-type { assert | graft | graft-ack | hello | join-prune | state-refresh | bsr } | interface interface-type interface-number ] * command to check the number of sent or received IPv6 PIM control messages.
- Run the following commands to check the IPv6 PIM routing table.
Run the display pim ipv6 routing-table [ ipv6-source-address [ mask mask-length ] | ipv6-group-address [ mask mask-length ] | flags flag-value | fsm | incoming-interface { interface-type interface-number | register } | mode { dm | sm | ssm } | outgoing-interface { exclude | include | match } { interface-type interface-number | none | register } ] * [ outgoing-interface-number [ number ] ] command to check detailed information about the IPv6 PIM routing table.
Run the display pim ipv6 routing-table brief [ ipv6-source-address [ mask mask-length ] | ipv6-group-address [ mask mask-length ] | incoming-interface { interface-type interface-number | register } ] * command to check brief information about the IPv6 PIM routing table.