Print Download PDF Send Feedback

Previous

Next

PIM

In This Section:

Dense Mode

Dense Mode State Refresh

Sparse Mode

Source-Specific Multicast (SSM) Mode

Configuring PIM - Gaia Portal

Configuring PIM - Gaia Clish (pim)

Static Multicast Routes

Monitoring and Troubleshooting PIM

Protocol-Independent Multicast (PIM) can forward multicast packets with a unicast protocol. PIM efficiently routes multicast traffic for groups that span wide area (and inter-domain) networks. It works with all existing unicast routing protocols. PIM supports three modes: dense, sparse and Source-Specific Multicast (SSM). You can enable only one mode of PIM at a time.

Note - Due to an OS limitation, PIM supports only 31 interfaces. If more are configured, PIM runs only on the first 31 interfaces.

Dense Mode

Dense mode is most useful when:

Dense Mode State Refresh

The PIM Dense Mode State Refresh option can be used in conjunction with dense mode to eliminate the periodic flood-and-prune of multicast data with no active receivers. All PIM routers must have State Refresh enabled to take advantage of this feature.

PIM Dense Mode builds multicast distribution trees that operate on a flood and prune principle. Multicast packets from a source are flooded throughout a PIM dense mode network. PIM routers that receive multicast packets and have no directly connected multicast group members or PIM neighbors send a prune message back up the source-based distribution tree toward the source of the packets. As a result, subsequent multicast packets are not flooded to pruned branches of the distribution tree. However, the pruned state in PIM dense mode times out approximately every three minutes and the entire PIM dense mode network is reflooded with multicast packets and prune messages. This reflooding of unwanted traffic throughout the PIM dense mode network consumes network bandwidth unnecessarily.

Use the PIM Dense Mode State Refresh feature to keep the pruned state in PIM dense mode from timing out by periodically forwarding a control message down the distribution tree. The control message refreshes the prune state on the outgoing interfaces of each router in the tree. This saves network bandwidth by greatly reducing the reflooding of unwanted multicast traffic to pruned branches of the PIM dense mode network.

Note - You must enable state refresh on all the PIM routers in the distribution tree to take advantage of this feature.

Sparse Mode

Sparse mode is most useful when:

Source-Specific Multicast (SSM) Mode

Source-Specific Multicast (SSM) is most useful when:

SSM is a version of PIM sparse-mode. It is used in conjunction with IGMP version 3 to request or block multicast traffic from specific sources. For example, when a host requests traffic for a multicast group from a specific source, SSM sends PIM join/prune messages towards the source.

The multicast group range 232/8 is reserved for SSM. When SSM is enabled, sparse-mode accepts only IGMPv3 reports for groups that fall within this range. Sparse-mode ignores IGMP v1 and v2 reports in this range. In addition, only shortest-path-tree (SPT) join/prune messages for these groups are accepted from neighboring routers. All other multicast groups are processed as in native sparse mode.

SSM does not need a rendezvous-point (RP). The presence of an RP for any of the SSM groups does not have any influence on the processing of join/prune messages.

Configuring PIM - Gaia Portal

To configure PIM in the Gaia Portal:

  1. Go to Advanced Routing > PIM.
  2. Configure the PIM Global Settings. In the PIM Global Settings section, select the PIM Protocol. One of these:
    • Sparse Mode (SM)
    • Dense Mode (DM). Enable State Refresh, if appropriate.
    • Source Specific Multicast (SSM)
  3. In the PIM Interfaces section, click Add.

    The Add Interface window opens.

  4. In the Add Interface window
    1. Select the Interface on which you want to run PIM.
    2. Optional: For each interface that is running PIM, enter the Local Address.
    3. Optional: To configure this interface to use the VRRP virtual IP address, click Use Virtual address.
    4. Optional: Enter a new DR Priority (Designated Router priority).
  5. Click Save.

PIM Global Settings

Parameter

Description

PIM Protocol

The PIM mode to use. One of:

  • Sparse Mode (SM)
  • Dense Mode (DM)
  • Source-Specific Multicast (SSM)

State Refresh

In Dense Mode, 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.

PIM Interfaces

Parameter

Description

Interface

Select the interface on which to enable PIM

Local Address

Use the specified local address for all advertisements sent on the interface. This is useful on interfaces with multiple IP addresses (aliases). The local address must match one of the addresses configured on the interface. If a local address is specified with the virtual address option enabled, the local address must match a virtual address on the interface.

Note - Each router must have at least one interface address with a subnet prefix shared by all neighboring PIM routers. If any neighboring routers select advertisement addresses that are not on a shared subnet, all messages from those neighbors are rejected. This is also true when the virtual address option is enabled.

  • Range: Dotted-quad ([0-255].[0-255].[0-255].[0-255]).
  • Default: Selects one of the IP addresses configured on the interface. If the virtual address option is enabled, PIM uses the virtual address configured on the interface after the router changes to master state with respect to VRRP.

Use Virtual Address

Use the VRRP virtual IP address on this interface. If enabled, PIM runs on this interface only after the router becomes a VRRP master after a failover.

When you enable virtual IP support for VRRP on a PIM interface, it creates the neighbor relationship with the virtual IP, if the router is a VRRP master. The 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 a local address or a virtual address when ClusterXL is enabled.

  • Range: Enabled, cleared
  • Default: Cleared

DR Priority

The dr-priority advertised in the PIM hello messages 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, the DR election is based on the IP address.

  • Range: 0-4294967295 (2^32 - 1).
  • Default: 1.

Note - To make sure that a PIM neighbor supports DR Priority, run this command:
show pim neighbor <ip_address>
For neighbors that advertise a DR selection priority value, this message shows in the summary:
DRPriorityCapable Yes.

Disabling PIM

You can disable PIM on one or more interfaces configured on the Portal platform.

  1. Open the Advanced Routing > PIM page of the Portal.
  2. In the PIM Interfaces section, select the interface on which to disable PIM and click Delete.

    To disable PIM entirely, delete all PIM interfaces.

Configuring PIM-DM Advanced Options (Optional)

To configure PIM Dense Mode Advanced Options:

  1. Open the Advanced Routing > PIM page of the Portal.
  2. Select the PIM Protocol: Dense Mode (DM).
  3. Click Edit Settings. The Advanced Options window opens.
  4. In the General Timers section, enter values for the:
    • Hello interval (in seconds).
    • Data Interval (in seconds).
    • Assert Interval (in seconds).
    • Assert-rate Limit.
    • Join Prune Interval (in seconds).
    • Join Prune Delay Interval (in seconds).
    • Join Prune Suppress Interval (in seconds).
  5. In the Assert Ranks section, enter values for the routing protocol(s) you use.
  6. Click Save.

Configuring PIM-SM Advanced Options (Optional)

To configure PIM Simple Mode Advanced options:

  1. Open the Advanced Routing > PIM page of the Portal.
  2. Select the PIM Protocol. One of:
    • Sparse Mode (SM)
    • Source Specific Multicast (SSM)
  3. Click Edit Settings.

    The Advanced Options window opens.

  4. In the Sparse Mode Timers section, enter a value for the
    1. Register Suppression Interval (in seconds).
    2. CRP Advertise Interval (in seconds)
  5. In the Shortest Path First Threshold section, click Add.

    The Shortest Path First Threshold: Add Multicast Group window opens.

  6. In the SPT: Add Multicast Group window, enter a value for the:
    1. Multicast Group to which the SPT threshold applies.
    2. Subnet mask for the group multicast address.
    3. Threshold to Switch (in kilobits per second).
    4. Click OK.
  7. In the General Timers section, enter values for the:
    • Hello interval (in seconds).
    • Data Interval (in seconds).
    • Assert Interval (in seconds).
    • Assert-rate Limit.
    • Join Prune Interval (in seconds).
    • Join Prune Delay Interval (in seconds).
    • Join Prune Suppress Interval (in seconds).
  8. In the Assert Ranks section, enter values for the routing protocol(s) you use.
  9. Click Save.

PIM Advanced Options - General Timers

Parameter

Description

Hello interval

Interval between which PIM hellos 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

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 (e.g. 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

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, 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 (measured in seconds).

  • Range: 1-3600 seconds
  • Default: 180

Assert-rate Limit.

The number of asserts to send per second. The router generates the Asserts when data from a source is detected on an interface other than the incoming interface (based on the unicast routing table) towards the source. These messages are rate-limited and the router must not originate more than a fixed number of assert messages per second. If the limit is set to 0, rate-limiting is disabled.

  • Range: 0, 10-10000
  • Default: 10

Join Prune Interval

Interval between sending Join/Prune messages.

  • Range: 1-3600 seconds
  • Default: 60

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

Join Prune Suppress Interval

Mean interval from the receipt of a Join/Prune with a higher Holdtime (with ties broken by higher network layer address) and allowing duplicate Join/Prunes to be sent again. Set this interval to 1.25 times the join/prune interval.

  • Range: 2-3600 seconds
  • Default: 75

PIM Advanced Options - 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:
    • Direct: 0
    • OSPF: 10
    • Kernel: 40
    • Static: 60
    • RIP: 100
    • BGP: 170

PIM Advanced Options - State Refresh Parameters (DM)

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
  • Default: 60

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

PIM Advanced Options - 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 seconds

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

PIM Advanced Options - Shortest First Path Threshold - Add Multicast Group

Parameter

Description

Multicast Group

The multicast group address to apply to the shortest path tree (spt) threshold.

  • Range: Dotted-quad ([224-239].[0-255].[0-255].[0-255])
  • Default: None

Subnet mask

Mask length.

  • Range: 1-32
  • Default: None

Use Infinity

Specifies that there is no spt switch.

Use Integer

The data rate threshold in Kbits/sec to start the spt switchover.

When the data rate for a sparse-mode group is higher than the shortest-path-tree threshold at the last-hop router, an (S,G) entry is created and a join/prune message is sent toward the source. Setting this option builds a shortest-path tree from the source S to the last-hop router.

  • Range: 0-1000000 Kbits/s, or infinity (for no switchover)
  • Default: None

Configuring PIM-SM Bootstrap and Rendezvous Point Settings

To configure this router as a Bootstrap router, Candidate Rendezvous Point and Static Rendezvous Point:

  1. Open the Advanced Routing > PIM page of the Portal.
  2. Select the PIM Protocol. One of:
    • Sparse Mode (SM)
    • Source Specific Multicast (SSM)
  3. In the Bootstrap and Rendezvous Point Settings section, click Edit Settings.

    The Bootstrap and Rendezvous Point Settings window opens.

  4. To enable the router as a Bootstrap Router:
    1. Select Enable Bootstrap Router.
    2. Optional: Enter the Local Address of the bootstrap router.
    3. Optional: Enter the Local Preference.
  5. To enable the router as a Candidate Rendezvous Point:
    1. Select Enable Candidate RP.
    2. Optional: Enter the Local Address of the Candidate Rendezvous Point router.
    3. Optional: Enter the Local Preference.
    4. Optional: Click Add to Configure a Multicast Group and Subnet mask for which this router is designated as the candidate rendezvous point.
  6. To enable a Static Rendezvous Point:
    1. Select Enable Static RP.
    2. Optional: Click Add to enter the Static Rendezvous Point IP address.
    3. Optional: Click Add to configure a Multicast Group and Subnet mask for which this router is designated as the static rendezvous point.
  7. Click Save.

PIM Bootstrap Settings

Parameter

Description

Enable Bootstrap Router

If enabled, this router is a candidate bootstrap router (C-BSR). All candidate RPs (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

Local Address

Address used for the C-BSR state machine and the bootstrap messages.

If PIM clustering is enabled, then this address must be configured and must match that of one of the PIM interfaces.

If PIM clustering is not enabled, 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.

  • 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 if PIM clustering is enabled.

Local Preference

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

PIM Candidate Rendezvous Point

Parameter

Description

Enable Candidate RP

Specifies that the platform is a candidate rendezvous point router.

Local Address

Address used for the C-RP state machine and in the C-RP-Advertisements sent to the elected bootstrap router.

If PIM clustering is enabled, then this address must be configured and must match that of one of the PIM interfaces.

If clustering is not enabled, this address can either be that of one of the PIM interfaces or an address configured on the loopback interface. If an address from the loopback interface is used, take care not select an address in the 127/8 address range.

  • 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 if PIM clustering is enabled.

Local Preference

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

Multicast Group

The multicast group(s) for which this rendezvous point is responsible. Enter the group multicast IP address and mask length.

Multicast group address

  • 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

PIM Static Rendezvous Point

Parameter

Description

Enable Static RP

Enables or disables the static rendezvous point.

Static Rendezvous Point

A static rendezvous point. If an associated multicast group and prefix is not configured, the static-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

Multicast Group

The multicast group(s) for which this rendezvous point is responsible. Enter the group multicast IP address and mask length.

Multicast group address

  • 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

Configuring PIM - Gaia Clish (pim)

Use the Gaia Clish commands in this section to configure PIM.

PIM Global Settings

set pim mode {dense | sparse | ssm}
set pim state-refresh <on | off>
 






Parameter



Description







<dense | sparse | ssm>



The PIM mode to use. One of:


  • Sparse Mode (SM)
  • Dense Mode (DM)
  • Source-Specific Multicast (SSM)






state-refresh <on | off>



In Dense Mode, 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.










PIM Interfaces


After you set PIM to run dense mode, sparse mode or SSM, use the following commands to configure PIM for specific interfaces.






set pim interface <if_name>


   <on | off>


   virtual-address <on | off>


   local-address <ip_address>


   dr-priority <0-4294967295> | default














Parameter



Description







interface if_name <on | off>



Whether to enable or disable PIM on a specified interface.







virtual-address <on | off>



Use the VRRP virtual IP address on this interface. If enabled, PIM runs on this interface only after the router transitions to become a VRRP master after a failover. 


When you enable virtual IP support for VRRP on a PIM interface, it establishes the neighbor relationship by using the virtual IP if the router is a VRRP master. The 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 a local address or a virtual address when ClusterXL is enabled.


  • Default: Off






local-address ip_address



Use the specified local address for all advertisements sent on the interface. This is useful on interfaces with multiple IP addresses (aliases). The local address must match one of the addresses configured on the interface. If a local address is specified while the virtual address option enabled, the local address must match a virtual address on the interface. 


Note - Each router must have at least one interface address with a subnet prefix shared by all neighboring PIM routers. If any neighboring routers choose advertisement addresses that do not appear to be on a shared subnet all messages from those neighbors will be rejected. This holds true even when the virtual address option is enabled.


  • Range: Dotted-quad ([0-255].[0-255].[0-255].[0-255]).
  • Default: Selects one of the IP addresses configured on the interface. If the virtual address option is enabled, PIM will use the virtual address configured on the interface after the router transitions to master state with respect to VRRP.






dr-priority <0-4294967295>



The dr-priority advertised in the PIM hello messages sent on the interface. This is used for DR election on a LAN. The router with the highest priority is elected 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, the DR election is based on the IP address.


  • Range: 0-4294967295 (2^32 - 1).
  • Default: 1.
  • Note - To verify whether a PIM neighbor supports DR Priority, use the following command: 
    show pim neighbor <ip_address>
    For neighbors that advertise a DR election priority value, the following message appears in the summary:
    DRPriorityCapable Yes.






dr-priority default



A value of 1.










PIM Sparse Mode


Use the following commands to configure parameters for sparse mode PIM only.


set pim


   bootstrap-candidate <on | off>


   bootstrap-candidate local-address <ip_address>


   bootstrap-candidate priority <0-255> | default


   candidate-rp <on | off>


   candidate-rp local-address <ip_address>


   candidate-rp priority <0-255> | default


   candidate-rp multicast-group <mcast_address>/<mask_length> <on | off>


   static-rp off


   static-rp rp-address <ip_address> < on | off>


   static-rp rp-address <ip_address> multicast-group <mcast_address>/<mask_length> <on | off>


   register-suppress-interval <60-3600> | default


   candidate-rp advertise-interval <1-3600> | default


   spt-threshold multicast <mcast_address>/<mask_length> threshold <0-1000000> <on | off>


   spt-threshold multicast <mcast_address>/<mask_length> threshold infinity <on | off>


Bootstrap and Rendezvous Point Settings






Parameter



Description







bootstrap-candidate <on | off>



If enabled, this router is a candidate bootstrap router (C-BSR). All candidate RPs (C-RPs) send C-RP-Advertisements to the elected bootstrap router (BSR). The BSR then disseminates this information in bootstrap messages across the PIM domain. To avoid a single point of failure, configure more than one router in a domain as a candidate BSR.


  • Default: off






bootstrap-candidate local-address <ip_address>



Address used for the C-BSR state machine and the bootstrap messages. 


If PIM clustering is enabled, then this address must be configured and must match that of one of the PIM interfaces. 


If PIM clustering is not enabled, this address can either be that of the PIM interfaces or an address configured on the loopback interface. If an address from the loopback interface is used, take care not select an address in the 127/8 address range.


  • 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 if PIM clustering is enabled.






bootstrap-candidate priority <0-255>



The priority advertised in C-BSR messages. The candidate bootstrap router with the highest priority value is elected 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






bootstrap-candidate priority default



Specifies a value of 0.








Candidate Rendezvous Point






Parameter 



Description







candidate-rp <on | off>



Specifies that the platform is a candidate rendezvous point router.


  • Default: off






candidate-rp local-address ip_address>



Address used for the C-RP state machine and in the C-RP-Advertisements sent to the elected bootstrap router. 


If PIM clustering is enabled, then this address must be configured and must match that of one of the PIM interfaces. 


If clustering is not enabled, this address can either be that of one of the PIM interfaces or an address configured on the loopback interface. If an address from the loopback interface is used, take care not select an address in the 127/8 address range.


  • 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 if PIM clustering is enabled.






candidate-rp priority <0-255>



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






candidate-rp priority default



A value of 0.








Candidate Rendezvous Point






Parameter 



Description







candidate-rp multicast-group <mcast_address>/<mask_length> <on | off>



The multicast address advertised in the candidate rendezvous point advertisements. Enter the group multicast IP address and mask length. If you do not specify a group multicast address, the candidate rendezvous point advertises itself as the rendezvous point for all multicast groups.


Multicast group address:


  • Range: Dotted-quad ([224-239].[0-255].[0-255].[0-255]).
  • Default: None.







Static Rendezvous Point






Parameter 



Description







static-rp off



Disables the static rendezvous point option.







static-rp rp-address <ip_address> <on | off>



A static rendezvous point IP address. If an associated multicast group and prefix is not configured, the static-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






static-rp rp-address <ip_address> multicast-group <mcast_address>/<mask_length> <on | off>



A static rendezvous point IP address.


  • Range: Any IP address
  • Default: None
Multicast group address:


  • Range: Dotted-quad ([224-239].[0-255].[0-255].[0-255])
  • Default: 224.0.0.0/4
Mask length:


  • Range: 1-32
  • Default: None







Sparse Mode Timers






Parameter 



Description







register-suppress-interval <60-3600>



The mean interval between receiving a register-stop and allowing registers to 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 seconds






register-suppress-interval default



A value of 60 seconds.







candidate-rp advertise-interval <1-3600>



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






candidate-rp advertise-interval default



A value of 60 seconds.








Shortest Path First Threshold






Parameter 



Description







spt-threshold multicast <mcast_address>/<mask_length> threshold <0-1000000>



The interval between which candidate-rendezvous point routers send candidate-rendezvous point advertisements to the elected bootstrap router.


Multicast group address


  • Range: Dotted-quad ([224-239].[0-255].[0-255].[0-255])
  • Default: 224.0.0.0/4
Mask length:


  • Range: 1-32
  • Default: None
The data rate threshold in Kbits/sec to trigger the spt switchover.


When the data rate for a sparse-mode group exceeds the shortest-path-tree threshold at the last-hop router, an (S,G) entry is created and a join/prune message is sent toward the source. Setting this option builds a shortest-path tree from the source S to the last-hop router.


  • Range: 0-1000000 Kbits/s, or infinity (for no switchover)
  • Default: None






spt-threshold multicast <mcast_address>/<mask_length> threshold infinity <on | off>



Specifies that there is no spt switchover.


Multicast group address:


  • Range: Dotted-quad ([224-239].[0-255].[0-255].[0-255])
  • Default: 224.0.0.0/4
Mask length:


  • Range: 1-32
  • Default: None








Timer and Assert Rank Parameters for Dense Mode and Sparse Mode


Use these commands to change or restore default values for timers and assert ranks.


set pim


   hello-interval <1-21845> | default


   data-interval <11-3600> | default


   assert-interval <1-3600> | default


   assert-limit 0 | <10-10000> | default


   jp-interval <1-3600> | default


   jp-delay-interval <1-3600> | default


   jp-suppress-interval <2-3600> | default


   assert-rank protocol protocol name rank <0-255> | default


   state-refresh-interval <1 – 255>


   state-refresh-ttl <1 – 255>


General Timers






Parameter



Description







hello interval <1-21845>



Interval between which PIM hellos 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






hello interval default



A value of 30.







data-interval <11-3600>



The life-time of a new PIM forwarding entry. Subsequently the life of the entry will be extended in different ways depending on the location of this router in the network. For example, in some cases the receipt of PIM control messages (e.g. periodic join/prune messages) will extend the life of the entry and in others the presence of local senders of multicast traffic will prevent the entry from being deleted.


  • Range: 11-3600 seconds
  • Default: 210






data-interval default



A value of 210.







assert-interval <1-3600>



If an assert battle on an upstream interface results in 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) getting elected as the designated forwarder on that interface, 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 (measured in seconds).


  • Range: 1-3600 seconds
  • Default: 180






assert-interval default



A value of 180.







assert-limit <10-10000>



The number of asserts to send per second. Asserts are generated by the router when data from a source is detected on an interface other than the incoming interface (based on the unicast routing table) towards the source. These messages are rate-limited and the router should not originate more than a fixed number of assert messages per second. If the limit is set to 0, rate-limiting is disabled.


  • Range: 0, 10-10000
  • Default: 10






assert-limit default



A value of 10.







assert-limit <0>



Disables the limit placed on the number of asserts that can be sent per second.







jp-interval <1-3600>



Interval between sending Join/Prune messages.


  • Range: 1-3600 seconds
  • Default: 60






jp-interval default



A value of 60.







jp-delay-interval <1-3600>



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






jp-delay-interval default



A value of 5.







jp-suppress-interval <2-3600>



Mean interval from receiving a Join/Prune with a higher Holdtime (with ties broken by higher network layer address) and allowing duplicate Join/Prunes to be sent again. Set this interval to 1.25 times the join/prune interval.


  • Range: 2-3600 seconds
  • Default: 75






jp-suppress-interval default



A value of 75.








Assert Ranks






assert-rank protocol protocol name rank <0-255>



Used to compare the cost of protocols in order to determine 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 are running the same protocol. Hence, the default values have been specifically configured to match that of other implementations.


  • Range: 0-255






assert-rank protocol protocol name rank default



Default assert-rank values for supported protocols that match other implementations. 


  • Defaults: 
    • Direct: 0
    • OSPF: 10
    • Kernel: 40
    • Static: 60
    • RIP: 100
    • BGP: 170







State Refresh Parameters- Dense Mode






state-refresh-interval <1 – 255>



For Dense Mode, the interval at which state refresh messages are sent for multicast traffic originated by directly-connected sources.


  • Range: 1-255
  • Default: 60






state-refresh-ttl <1 – 255>



For Dense Mode, the time-to-live (TTL) placed in the state refresh messages originated for multicast traffic from directly-connected sources. This value can be used 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








Static Multicast Routes


PIM expects packets to arrive on the reverse-path forwarding (RPF) interface - the interface used to reach the source of the multicast data. PIM also checks the RPF to learn which interface it should use to send join/prune messages. By default, PIM checks the unicast routing table to identify the RPF interface. Static multicast routes provide an alternative route table to use for the RPF check. If a static multicast route and a unicast route are available for a specific destination, PIM uses the static multicast route.


Static multicast routes let PIM be independent of unicast routing. This lets you deploy topologies in which multicast and unicast traffic flow over different paths. For example, in order to balance the traffic load, you can separate the HTTP traffic from the stock quotes traffic. You simply configure a static multicast route to the source network that specifies a next hop gateway address different from the next hop address (for the same source) in the unicast routing table.









Note - PIM is the only protocol that uses static multicast routes.








You can configure static multicast routes through the Portal or through the CLI.


Configuring Static Multicast Routes - Gaia Portal


In Gaia Portal, you can add, delete, and edit static multicast routes.


To add a static multicast route:


  1. Open the Advanced Routing > Static Multicast Routes page of the Portal.
  2. Click Add.
    The Add Destination Route window opens
    

  3. Configure the multicast sender parameters:
    • Destination - the IP address
    • Subnet mask - the network mask
  4. Configure the gateway:
    1. Click Add Gateway.
    2. In the window that opens, enter the IPv4 Address and the Priority (optional).
    3. Click OK.
  5. Click Save.
To delete a static multicast route:


  1. In the Advanced Routing > Static Multicast Routes page of the Portal, select a route.
  2. Click Delete.
To edit a static multicast route:


  1. In the Advanced Routing > Static Multicast Routes page of the Portal, select a route.
  2. Click Edit.
    The Edit Destination Route window opens.
    

  3. For the selected Destination route, add, edit, or delete a gateway:
    • To add a gateway - click Add Gateway, enter the IPv4 address and the Priority (optional) value in the window that opens, and click OK
    • To edit a gateway - select a gateway, click Edit, change the IPv4 address and the Priority (optional) values in the window that opens, and click OK
    • To delete a gateway - select a gateway and click Delete
  4. Click Save.


Configuring Static Multicast Routes - Gaia Clish (static-mroute)


In CLI, you can add, delete, and verify static multicast routes.


To add or delete a static multicast route:


Run this command:


set static-mroute {<sender_IP>/<mask> | default} nexthop gateway address <gateway_IP> [priority <priority_value>] {on | off}






Parameter



Description







<sender_IP>/<mask>



The address and the network mask of the multicast sender.







default



The default gateway to use for FPF lookups.







<gateway_IP>



The IP address of the gateway router.







priority <priority_value>



Valid values are 1 through 8.


Defines the order of priority in which the nexthop gateway is selected, when multiple nexthop gateways are configured. Lower priority value takes higher preference. If not priority is defined, the default value of 1 is assigned. If multiple gateways are configured with the same priority value, the one with the lower IP address takes higher preference.







on



Installs the specified multicast static route in the routing table.







off



Removes the specified multicast static route from the routing table.








To verify static multicast routes:


Run this command: show static-mroute


To show static multicast routes configuration:


Run this command: show configuration static-mroute


Monitoring and Troubleshooting PIM


PIM Trace Options


To log information about PIM errors and events using the Portal:


  1. In the tree view, click Advanced Routing > Routing Options.
  2. In the Configuration tab, select Filter Visible Tables Below and select PIM.
  3. In the option variables area, do one of:
    • Double-click an option.
    • Select an option (to select multiple options, use Shift-Click) and click Activate.
  4. Click Apply at the top of the page
To log information about PIM errors and events using the CLI:


See Configuring Trace Options - Gaia Clish.


PIM Show and MFC Commands


Use these commands to monitor and troubleshoot PIM. 


These commands apply to both dense-mode and sparse-mode PIM:






show pim


	interfaces


	interfaces <if_address>


	neighbors


	neighbor <ip_address>


	memory


	timers


	stats


	summary








These commands apply only to sparse-mode PIM:






show pim


	bootstrap


	candidate-rp


	joins


	rps


	sarse-mode-stats


	group-rp-mapping <mcast_address>








Dense Mode and Sparse Mode Parameters






Parameter



Description







interface



The interfaces that are running PIM, their status, and their mode. This command also displays the interface and its DR priority and the number of PIM neighbors on the interface.







neighbors



The IP address of each PIM neighbor and the interface on which the neighbor is present. This command also displays the neighbor’s DR priority, generation ID, holdtime and the time the neighbor is set to expire based on the holdtime received in the most recent hello message.







neighbor ip_address



Use this command to verify whether a PIM neighbor supports DR Priority.
For neighbors that advertise a DR election priority value, the following message appears in the summary:
DRPriorityCapable Yes







stats



The number of different types of PIM packets received and transmitted and any associated errors.







memory



 







timers



 







summary



 








Sparse Mode Parameters






Parameter



Description







bootstrap



The IP address and state of the Bootstrap router.







candidate-rp



The state of the Candidate Rendezvous Point state machine.







joins



PIM’s view of the join-prune (*, G and S, G) state, including RP for the group, incoming, and outgoing interface(s), interaction with the multicast forwarding cache and the presence of local members. To view the equivalent information for dense-mode PIM, use the show mfc cache command.







rps



The active RP-set, including the RP addresses, their type (or source of information about them) and the groups for which they are configured to act as RP.







group-rp-mapping <group-address>



The RP selected for a particular group based on information from the active RP-set.







sparse-mode stats



Error statistics for multicast forwarding cache (MFC); Bootstrap Router (BSR) messages; Candidate Rendezvous Point (CRP) advertisements; and the Internet Group Management Protocol (IGMP).








MFC Commands and Trace Options


To see multicast errors and events, run the show mfc commands:






show mfc {cache | interface}








To trace the MFC errors and events, see Configuring Trace Options - Gaia Clish.



						










	06 February 2018
	
		© 2018 Check Point Software Technologies Ltd. All rights reserved.