Configuring ipv6 pim common timers on an interface, Configuring join/prune message sizes – H3C Technologies H3C S10500 Series Switches User Manual
Page 415

400
Configuring IPv6 PIM common timers on an interface
Follow these steps to configure IPv6 PIM common timers on an interface:
To do...
Use the command...
Remarks
Enter system view
system-view
—
Enter interface view
interface interface-type
interface-number
—
Configure the hello interval
pim ipv6 timer hello interval
Optional
30 seconds by default
Configure the maximum delay
between hello messages
pim ipv6 triggered-hello-delay
interval
Optional
5 seconds by default
Configure the join/prune interval pim ipv6 timer join-prune interval
Optional
60 seconds by default
Configure the join/prune timeout
time
pim ipv6 holdtime join-prune
interval
Optional
210 seconds by default
Configure assert timeout time
pim ipv6 holdtime assert interval
Optional
180 seconds by default
NOTE:
If no special networking requirements are raised, use the default settings.
Configuring join/prune message sizes
A larger join/prune message size will result in loss of a larger amount of information when a message
is lost; with a reduced join/message size, the loss of a single message has a relatively minor impact.
By controlling the maximum number of (S, G) entries in a join/prune message, you can effectively reduce
the number of (S, G) entries sent per unit of time.
Follow these steps to configure join/prune message sizes:
To do...
Use the command...
Remarks
Enter system view
system-view
—
Enter IPv6 PIM view
pim ipv6
—
Configure the maximum size of a
join/prune message
jp-pkt-size packet-size
Optional
8,100 bytes by default
Configure the maximum number of
(S, G) entries in a join/prune
message
jp-queue-size queue-size
Optional
1,020 by default
CAUTION:
If IPv6 PIM snooping–enabled switches are deployed in the IPv6 PIM network, be sure to set a value no
greater than the IPv6 path MTU for the maximum size of a join/prune message on the receiver-side edge
IPv6 PIM devices.