Configuring PIM in Gaia Portal
|
Important - In a Cluster |
Configuring PIM Modes

-
From the left navigation tree, click Advanced Routing > PIM.
-
In the PIM Global Settings section:
-
Select Sparse Mode (SM).
-
Click Apply.
-
-
In the PIM Interfaces section, add the applicable interfaces.
See the Configuring PIM on Interfaces section below.
-
Optional: In the Advanced Options section, configure the applicable settings.
See the Configuring PIM Advanced Options section below.
-
Optional: In the Bootstrap and Rendezvous Point Settings section, configure the applicable settings.
See the Configuring PIM Bootstrap and Rendezvous Point Settings section below.
-
Configure the Static Multicast Routes.

-
From the left navigation tree, click Advanced Routing > PIM.
-
In the PIM Global Settings section:
-
Select Dense Mode (DM).
-
Select the State Refresh to use state refresh messages to delay timing out prune state of multicast traffic that has no active receivers. This helps suppress the flood-and-prune cycle inherent to Dense Mode.
-
Click Apply.
-
-
In the PIM Interfaces section, add the applicable interfaces.
-
Click Add.
-
In the Interface field, select the interface, on which you want to run PIM.
-
Optional: To configure this interface to use the VRRP Virtual IP address, select Use Virtual address.
-
Optional: in the DR Priority (Designated Router priority) field, enter a new priority between 0 and 4294967295.
-
Click Save.
-
-
Optional: In the Advanced Options section, configure the applicable settings.
See the Configuring PIM Advanced Options section below.
-
Configure the Static Multicast Routes.

-
From the left navigation tree, click Advanced Routing > PIM.
-
In the PIM Global Settings section:
-
Select Source-Specific Multicast (SSM).
-
Click Apply.
-
-
In the PIM Interfaces section, add the applicable interfaces.
See the Configuring PIM on Interfaces section below.
-
Optional: In the Advanced Options section, configure the applicable settings.
See the Configuring PIM Advanced Options section below.
-
Optional: In the Bootstrap and Rendezvous Point Settings section, configure the applicable settings.
See the Configuring PIM Bootstrap and Rendezvous Point Settings section below.
-
Configure the Static Multicast Routes.
Configuring PIM on Interfaces

-
From the left navigation tree, click Advanced Routing > PIM.
-
Select the PIM Mode.
-
In the PIM Interfaces section, click Add.
Alternatively, select the configure interface and click Edit.
-
Configure the applicable settings.
Parameter
Description
Interface
Specifies the interface, on which to enable PIM.
Use Virtual Address
Select this option to use the VRRP Virtual IP address on this interface:
-
PIM runs on this interface only after the router becomes a VRRP Master after a failover.
-
Creates the neighbor relationship with the Virtual IP, if the router is a VRRP Master. The VRRP Master in the VRRP pair sends Hello messages that include the Virtual IP as the source address and processes PIM control messages from routers that neighbor the VRRP pair.
Note - You cannot configure this option when ClusterXL is enabled.
Range: Enabled, or Cleared
Default: Cleared
DR Priority
The Designated Router priority advertised in the PIM Hello messages that are sent on the interface.
This is used for DR selection on a LAN.
The router with the highest priority is selected as the designated router.
To break a tie, the DR is selected on the basis of the highest IP address.
If even one router does not advertise a DR priority configured, the DR election is based on the IP address.
Note - To make sure that a PIM neighbor supports DR Priority:
-
Run this command in Gaia Clish
The name of the default command line shell in Check Point Gaia operating system. This is a restricted shell (role-based administration controls the number of commands available in the shell). on the Security Gateway
Dedicated Check Point server that runs Check Point software to inspect traffic and enforce Security Policies for connected network resources.:
show pim neighbor <IP Address of Neighbor>
-
For neighbors that advertise a DR selection priority value, this message shows in the summary:
DRPriorityCapable Yes
Range: 0-4294967295
Default: 1
-
-
Click Save.

-
From the left navigation tree, click Advanced Routing > PIM.
-
In the PIM Interfaces section, select the interface.
-
Click Delete.
There is no prompt to confirm.

-
From the left navigation tree, click Advanced Routing > PIM.
-
In the PIM Interfaces section, click Delete All.
-
Click OK to confirm.

-
From the left navigation tree, click Advanced Routing > PIM.
-
In the PIM Interfaces section, click Restart All.
-
Click OK to confirm.
Configuring PIM Advanced Options
These settings are optional.
-
From the left navigation tree, click Advanced Routing > PIM.
-
In the Advanced Options section, click Edit Settings.
-
Configure the applicable settings.
Description of General Timers
Parameter
Description
Hello Interval
Interval between PIM Hello messages that are sent on a multicast-capable interface.
Hello messages are addressed to the All-PIM-Routers multicast group (224.0.0.13), so that PIM routers may discover neighbors on a multi-access network.
Range: 1-21845 seconds
Default: 30 seconds
Data Interval
The life-time of a new PIM forwarding entry.
Subsequently, the life of the entry is extended in different ways based on the location of this router in the network.
For example, in some cases the receipt of PIM control messages (periodic join/prune messages) extends the life of the entry and in others the presence of local senders of multicast traffic prevents the deletion of the entry.
Range: 11-3600 seconds
Default: 210 seconds
Assert Interval
If an assert battle on an upstream interface results in the selection of a PIM neighbor other than the unicast reverse-path-forwarding (RPF) neighbor towards the source of the data traffic (for which the assert battle was generated) as the designated forwarder on that interface, then the winner is used as the upstream neighbor for all subsequent join/prune messages.
This change is timed-out after expiry of the assert interval.
Range: 1-3600 seconds
Default: 180 seconds
Join Prune Interval
Interval between sending Join/Prune messages.
Range: 1-3600 seconds
Default: 60 seconds
Join Prune Delay Interval
The maximal interval from the time when the unicast Reverse Path Forwarding (RPF) neighbor (towards a source or the RP) changes, and a triggered Join/Prune message is sent.
Range: 1-3600 seconds
Default: 5 seconds
Description of Assert Ranks
Parameter
Description
Direct
OSPF
Kernel
Static
RIP
BGP
Compares the cost of protocols to find which router will forward multicast data packets on a multi-access LAN.
These values are used in assert messages sent out on a LAN when a router detects data packets on an interface other than the incoming interface towards the source of the data.
These values must be the same for all routers on a multi-access LAN that run the same protocol.
Therefore, the default values were specially configured to match those of other implementations.
-
Range: 0-255
-
Defaults:
-
BGP: 170
-
Direct: 0
-
Kernel: 40
-
OSPF: 10
-
RIP: 100
-
Static: 60
-
Description of State Refresh Parameters
Parameter
Description
State Refresh Interval
For Dense Mode, the interval at which state refresh messages are sent for multicast traffic originated by directly-connected sources.
Range: 1-255 seconds
Default: 60 seconds
State Refresh TTL
For Dense Mode, the time-to-live (TTL) placed in the state refresh messages originated for multicast traffic from directly-connected sources.
You can use this value to limit the forwarding of state refresh messages in the network.
In the absence of user configuration, it is derived from the multicast data.
Range: 1-255
Default: None
Description of Sparse Mode Timers
Parameter
Description
Register Suppression Interval
The mean interval between receipt of a register-stop and the time when registers can be sent again.
A lower value means more frequent register bursts at the rendezvous point.
A higher value means a longer join latency for new receivers.
Range: 60-3600 seconds
Default: 60
CRP Advertise Interval
The interval between which candidate-rendezvous point routers send candidate-rendezvous point advertisements to the elected bootstrap router.
Range: 1-3600 seconds
Default: 60 seconds
-
-
Click Save.
Configuring PIM Bootstrap and Rendezvous Point Settings
These settings are optional.

-
From the left navigation tree, click Advanced Routing > PIM.
-
In the PIM Global Settings section, in the PIM Protocol field, select one these:
-
Sparse Mode (SM)
-
Source Specific Multicast (SSM)
-
-
In the Bootstrap and Rendezvous Point Settings section, click Edit Settings.
-
To enable the router as a Bootstrap Router:
-
Select Enable Bootstrap Router.
Description
If enabled, this router is a candidate bootstrap router (C-BSR). All candidate Rendezvous Points (C-RPs) send C-RP-Advertisements to the selected bootstrap router (BSR).
The BSR then disseminates this information in bootstrap messages across the PIM domain.
To prevent a single point of failure, configure more than one router in a domain as a candidate BSR.
Default: Cleared
-
Optional: Enter the Local Address of the bootstrap router.
Description
Address used for the C-BSR state machine and the bootstrap messages.
Important:
-
On a single Security Gateway, this address can be that of the PIM interfaces or an address configured on the loopback interface. If an address from the loopback interface is used, do not select an address in the 127/8 address range.
-
In ClusterXL Cluster Member
Security Gateway that is part of a cluster. or VRRP Cluster Member, you must configure the Cluster Virtual IP address configured on this PIM interface.
Range: Address of PIM interface, or a non 127.0.0.0/8 loopback address.
Default: The IP address of one of the interfaces on which PIM is enabled. The default does not apply on Cluster Members.
-
-
Optional: Enter the Local Preference.
Description
The priority advertised in C-BSR messages.
The candidate bootstrap router with the highest priority value is selected as the bootstrap router for the domain.
The C-RP with the lowest priority has the highest preference.
The highest priority value is 0.
Range: 0-255
Default: 0
-
-
To enable the router as a Candidate Rendezvous Point:
-
Select Enable Candidate RP to configure Gaia
Check Point security operating system that combines the strengths of both SecurePlatform and IPSO operating systems. as a candidate rendezvous point router.
-
Optional: Enter the Local Address of the Candidate Rendezvous Point router.
Description
Address used for the C-RP state machine and in the C-RP-Advertisements sent to the elected bootstrap router.
Important:
-
On a single Security Gateway, this address can be that of the PIM interfaces or an address configured on the loopback interface. If an address from the loopback interface is used, do not select an address in the 127/8 address range.
-
In ClusterXL Cluster Member or VRRP Cluster Member, you must configure the Cluster Virtual IP address configured on this PIM interface.
Range: Address of PIM interface or a non 127.0.0.0/8 loopback address.
Default: Selects the IP address of one of the interfaces on which PIM is enabled. The default does not apply on Cluster Members.
-
-
Optional: Enter the Local Preference.
Description
The priority of this C-RP.
All PIM routers select the same RP for a multicast group address from the list of C-RPs received in the bootstrap messages from the elected BSR.
The lower the Local Preference of the C-RP, the higher the priority.
Range: 0-255
Default: 0
-
Optional: Click Add to configure a Multicast Group and Subnet mask for which this router is designated as the candidate rendezvous point.
Description
-
Multicast Group
The multicast IP address of the group(s), for which this rendezvous point is responsible.
Range: Dotted-quad ([224-239].[0-255].[0-255].[0-255])
Default: 224.0.0.0/4
-
Subnet mask
Mask length.
Range: 1-32
Default: None
-
-
-
To enable the router as a Static Rendezvous Point:
-
Select Enable Static RP.
-
Optional: Click Add to enter the Static Rendezvous Point IP address.
Description
If an associated multicast group and prefix is not configured, the Static Rendezvous Point (RP) is considered to be responsible for all multicast groups (224.0.0.0/4).
This needs to be consistent with the RP information at other routers in a multicast domain irrespective of the RP-dissemination mechanism (bootstrap or autoRP) used.
Note - The static RP overrides the RP information received from other RP-dissemination mechanisms, such as bootstrap routers.
Range: Any IP address
Default: None
-
Optional: Click Add to configure a Multicast Group and Subnet mask for which this router is designated as the static rendezvous point.
Description
-
Multicast Group
The multicast IP address of the group(s), for which this rendezvous point is responsible.
Range: Dotted-quad ([224-239].[0-255].[0-255].[0-255])
Default: 224.0.0.0/4
-
Subnet mask
Mask length.
Range: 1-32
Default: None
-
-
-
Click Save.