181
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.
NOTE:
If no special networking requirements are raised, use the default settings.
Configuring PIM common timers globally
Ste
Command Remarks
1. Enter system view.
system-view N/A
2. Enter public network PIM view
or VPN instance PIM view.
pim [ vpn-instance
vpn-instance-name ]
N/A
3. Configure the hello interval.
timer hello interval
Optional.
30 seconds by default.
4. Configure the join/prune
interval.
timer join-prune interval
Optional.
60 seconds by default.
5. Configure the join/prune
timeout time.
holdtime join-prune interval
Optional.
210 seconds by default.
6. Configure assert timeout time.
holdtime assert interval
Optional.
180 seconds by default.
7. Configure the multicast source
lifetime.
source-lifetime interval
Optional.
210 seconds by default.
Configuring PIM common timers on an interface
Ste
Command Remarks
1. Enter system view.
system-view N/A