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.

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.

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

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

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

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

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

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

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

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