Configuring The Prune Delay; Configuring Pim Common Timers - HP A6600 Configuration Manual

To do...
8. Configure the interface to
reject hello messages without
a generation ID.

Configuring the prune delay

If a downstream router does not support the prune override interval field, you can configure a prune
delay interval on the upstream router so that it will not perform the prune action immediately after it
receives the prune message. Instead, it maintains the current forwarding state for the prune delay interval.
In this period, if the upstream router receives a join message from the downstream router, it cancels the
prune action.
To do...
1. Enter system view.
2. Enter public network PIM view
or VPN instance PIM view.
3. Configure the prune delay
interval.

Configuring PIM common timers

PIM routers discover PIM neighbors and maintain PIM neighboring relationships with other routers by
periodically sending out hello messages.
After receiving a hello message, a PIM router waits a random period, which is smaller than the maximum
delay between hello messages, before sending a hello message. This delay avoids collisions that occur
when multiple PIM routers send hello messages simultaneously.
A PIM router periodically sends join/prune messages to its upstream for state update. A join/prune
message contains the join/prune timeout time. The upstream router sets a join/prune timeout timer for
each pruned downstream interface.
Any router that has lost assert election will prune its downstream interface and maintain the assert state
for a period of time. When the assert state times out, the assert losers will resume multicast forwarding.
When a router fails to receive subsequent multicast data from multicast source S, the router does not
immediately delete the corresponding (S, G) entry. Instead, it maintains the (S, G) entry for a period of
time—namely, the multicast source lifetime—before deleting the (S, G) entry.
Configuring PIM common timers globally
To do...
1. Enter system view.
2. Enter public network PIM view
or VPN instance PIM view.
3. Configure the hello interval.
Use the command...
pim require-genid
Use the command...
system-view
pim [ vpn-instance
vpn-instance-name ]
prune delay interval
Use the command...
system-view
pim [ vpn-instance
vpn-instance-name ]
timer hello interval
133
Remarks
Required.
By default, hello messages without
Generation_ID are accepted.
Remarks
—
—
Optional.
3 seconds by default.
Remarks
—
—
Optional.
30 seconds by default.