Configuring PIM in Gaia Clish
|
Important - In a Cluster |
-
To see the available "
set
" commands for PIM, enter in Gaia ClishThe 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).:
set pim[Esc][Esc]
-
To see the available "
show
" commands for PIM, enter in GaiaCheck Point security operating system that combines the strengths of both SecurePlatform and IPSO operating systems. Clish:
show pim[Esc][Esc]
-
To see the available "
restart
" commands for PIM, enter in Gaia Clish:restart pim[Esc][Esc]

|

The mandatory parameters are marked Mandatory. All other parameters are optional.
Parameter |
Description |
||||
---|---|---|---|---|---|
|
Configures the 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 |
||||
|
Configures the protocol, for which to configure the assert rank:
|
||||
|
Configures the protocol rank to compare 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.
|
||||
|
Configures the Bootstrap Candidate Local Address used for the C-BSR state machine and the bootstrap messages.
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. |
||||
|
Disables ( |
||||
|
Configures 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 |
||||
|
Configures the candidate Rendezvous Point (RP) Advertisement Interval. |
||||
|
Configures the Candidate Rendezvous Point router address used for the C-RP state machine and in the C-RP-Advertisements sent to the elected bootstrap router.
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. |
||||
|
Configure the Multicast Group, for which this router is designated as the candidate rendezvous point.
|
||||
|
Disables ( |
||||
|
Configures 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 |
||||
|
Configures 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 |
||||
|
Configures the 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 |
||||
|
Mandatory. Specifies the interface, on which to enable PIM. |
||||
|
Configures 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.
Range: 0-4294967295 Default: 1 |
||||
|
Disables ( |
||||
|
Disables (
Range: Default: |
||||
|
Disables PIM on all interfaces. |
||||
|
Configures 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 |
||||
|
Configures the interval between sending Join/Prune messages. Range: 1-3600 seconds Default: 60 seconds |
||||
|
Mandatory. Configures the PIM mode:
|
||||
|
Configures 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 |
||||
|
Disables ( This helps suppress the flood-and-prune cycle inherent to Dense Mode. |
||||
|
For Dense Mode, configures the interval at which state refresh messages are sent for multicast traffic originated by directly-connected sources. Range: 1-255 seconds Default: 60 seconds |
||||
|
For Dense Mode, configures 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 |
||||
|
Disables ( |
||||
|
Configures the Static Rendezvous Point IP address. 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.
Range: Any IP address Default: None |
||||
|
Configures the Multicast Group, for which this router is designated as the static rendezvous point.
|
||||
|
Disables ( |