31.4.8 IPv6 PIM-SM Timer

The following table describes the timer values used by IPv6 PIM-SM.

Table 31-10: IPv6 PIM-SM Timer value
Timer name	Description	Default value (in seconds)	Range of values that can be set in configuration mode (sec.)	Remarks
Hello-Period	Hello sending interval	30	5~3600	-
Hello-Holdtime	Adjacency retention period	105	3.5 x Hello-Period	Calculated based on the formula to the left.
Assert-Timeout	Assert-based forwarding suppression period	180	-	-
Join/Prune-Period	Join/Prune sending interval	60	30~3600	A variance as high as +50% might occur.
Join/Prune-Holdtime	Retention period for routing information and forwarding destination interfaces	210	3.5 x Join/Prune-Period	Calculated based on the formula to the left.
Deletion-Delay-Time	Duration of multicast forwarding destination interfaces after receiving OOA#1	1/3 x Join/Prune-Holdtime	0~300	^#2
Data-Timeout	Forwarding entry retention period	210	0 (infinite) or 60~43200	A gap of as much as +90 seconds might occur.
Register-Supression-Timer	Encapsulation sending suppression period	60	-	A variance as high as 30 seconds might occur.
Probe-Time	Time for sending restart checks for encapsulation sending	5	5~60	With the default of 5 seconds, a restart check (Null-Register) for encapsulation sending is sent once, 5 seconds before Register-Suppression-Timer is up.#3 ^#3
C-RP-Adv-Period	Notification interval for rendezvous point candidates	60	-	-
RP-Holdtime	Rendezvous point retention period	150	2.5 x C-RP-Adv-Period	Calculated based on the formula to the left.
Bootstrap-Period	BSR message send interval	60	-	-
Bootstrap-Timeout	BSR message retention period	130	2 x Bootstrap-Period+10	Calculated based on the formula to the left.
Negative-Cache-Holdtime(PIM-SM)	Negative cache retention period	210	10~3600	For PIM-SSM, this is fixed at 3600

Legend:-: Not applicable

Note #1: A configured timer value is used if it set in the configuration, however, to the forwarding destination interface, set a value that does not exceed the Join/Prune-Holdtime value included in the PIM-Join/Prune message received with the last Join as the retention period in the interface.
Note #2: Because the value set in the configuration is given priority for this timer value, operation differs from the standard in RFC 2362. However, if no value is specified in the configuration, operation complies with RFC 2362.
Note #3: If this timer value is set to 10 or more, the restart check for encapsulation sending is sent multiple times every five seconds. If no value is specified in the configuration, the check is sent only once.