router : multicast : config pim-sm-global
 
config pim-sm-global
These global settings apply only to sparse mode PIM-enabled interfaces. Global PIM settings do not override interface-specific PIM settings.
If sparse mode is enabled, you can configure a DR to send multicast packets to a particular RP by specifying the IP address of the RP through the config rp-address variable. The IP address must be directly accessible to the DR. If multicast packets from more than one multicast group can pass through the same RP, you can use an access list to specify the associated multicast group addresses.
 
To send multicast packets to a particular RP using the config rp-address subcommand, the ip‑address field is required. All other fields are optional.
Variable
Description
Default
accept-register-list <access_list_name>
Cause a FortiGate unit RP to accept or deny register packets from the source IP addresses given in the specified access list. For more information on access lists, see router access-list, access-list6.
Null
bsr-allow-quick-refresh {enable | disable}
Enable or disable accepting BSR quick refresh packets from neighbors.
disable
bsr-candidate {enable | disable}
Enable or disable the FortiGate unit to offer its services as a Boot Strap Router (BSR) when required.
disable
bsr-hash <hash_integer>
This field is available when bsr-candidate is set to enable.
Set the length of the mask (in bits) to apply to multicast group addresses in order to derive a single RP for one or more multicast groups. The range is from 0 to 32. For example, a value of 24 means that the first 24 bits of the group address are significant. All multicast groups having the same seed hash belong to the same RP.
10
bsr-interface <interface_name>
This field is available when bsr-candidate is set to enable.
Specify the name of the PIM-enabled interface through which the FortiGate unit may announce BSR candidacy.
Null
bsr-priority <priority_integer>
This field is available when bsr-candidate is set to enable.
Assign a priority to FortiGate unit BSR candidacy. The range is from 0 to 255. This value is compared to that of other BSR candidates and the candidate having the highest priority is selected to be the BSR. If two BSR priority values are the same, the BSR candidate having the highest IP address on its BSR interface is selected.
0
cisco-crp-prefix {enable | disable}
Enable or disable a FortiGate unit RP that has a group prefix number of 0 to communicate with a Cisco BSR. You may choose to enable the attribute if required for compatibility with older Cisco BSRs.
disable
cisco-ignore-rp-set-priority {enable | disable}
Enable or disable a FortiGate unit BSR to recognize Cisco RP-SET priority values when deriving a single RP for one or more multicast groups. You may choose to enable the attribute if required for compatibility with older Cisco RPs.
disable
cisco-register-checksum {enable | disable}
Enable or disable performing a register checksum on entire PIM packets. A register checksum is performed on the header only by default. You may choose to enable register checksums on the whole packet for compatibility with older Cisco IOS routers.
disable
cisco-register-checksum-group <access_list_name>
This field is available when cisco-register-checksum is set to enable.
Identify on which PIM packets to perform a whole-packet register checksum based on the multicast group addresses in the specified access list. For more information on access lists, see router access-list, access-list6. You may choose to register checksums on entire PIM packets for compatibility with older Cisco IOS routers.
Null
join-prune-holdtime <holdtime_integer>
Join/prune holdtime.
210
message-interval <interval_integer>
Set the amount of time (in seconds) that the FortiGate unit waits between sending periodic PIM join/prune messages (sparse mode) or prune messages (dense mode). The value must be identical to the message interval value set on all other PIM routers in the PIM domain. The range is from 1 to 65 535.
60
null-register-retries <retries_integer>
Maximum retries of the null register
1
register-rate-limit <rate_integer>
Set the maximum number of register messages per (S,G) per second that a FortiGate unit DR can send for each PIM entry in the routing table. The range is from 0 to 65 535, where 0 means an unlimited number of register messages per second.
0
register-rp-reachability {enable | disable}
Enable or disable a FortiGate unit DR to check if an RP is accessible prior to sending register messages.
enable
register-source {disable | interface | ip-address}
If the FortiGate unit acts as a DR, enable or disable changing the IP source address of outbound register packets to one of the following IP addresses. The IP address must be accessible to the RP so that the RP can respond to the IP address with a Register-Stop message. Choose one of:
disable — retain the IP address of the FortiGate unit DR interface that faces the RP.
interface — change the IP source address of a register packet to the IP address of a particular FortiGate unit interface. The register-source-interface attribute specifies the interface name.
ip-address — change the IP source address of a register packet to a particular IP address. The register-source-ip attribute specifies the IP address.
ip-address
register-source-interface <interface_name>
Enter the name of the FortiGate unit interface.
This field is only available when register-source is set to interface.
Null
register-source-ip <address_ipv4>
This field is available when register-source is set to address.
Enter the IP source address to include in the register message.
0.0.0.0
register-suppression <suppress_integer>
Enter the amount of time (in seconds) that a FortiGate unit DR waits to start sending data to an RP after receiving a Register-Stop message from the RP. The range is from 1 to 65 535.
60
rp-register-keepalive <keepalive_integer>
If the FortiGate unit acts as an RP, set the frequency (in seconds) with which the FortiGate unit sends keepalive messages to a DR. The range is from 1 to 65 535. The two routers exchange keepalive messages to maintain a link for as long as the source continues to generate traffic.
If the register-suppression attribute is modified on the RP and the rp-register-keepalive attribute has never been set explicitly, the rp-register-keepalive attribute is set to (3 x register-suppression) + 5 automatically.
185
spt-threshold {enable | disable}
Enable or disable the FortiGate unit to build a Shortest Path Tree (SPT) for forwarding multicast packets.
enable
spt-threshold-group <access_list_name>
Build an SPT only for the multicast group addresses given in the specified access list. For more information on access lists, see router access-list, access-list6.
This field is only available when spt-threshold is set to enable.
Null.
ssm {enable | disable}
This field is available when the IGMP version is set to 3.
Enable or disable Source Specific Multicast (SSM) interactions (see RFC 3569).
enable
ssm-range <access_list_name>
Enable SSM only for the multicast addresses given in the specified access list. For more information on access lists, see router access-list, access-list6.
By default, multicast addresses in the 232.0.0.0 to 232.255.255.255 (232/8) range are used to support SSM interactions.
This field is only available when ssm is set to enable.\
Null.
config rp-address variables
Only used when pim-mode is sparse-mode.
edit <rp_id>
Enter an ID number for the static RP address entry. The number must be an integer.
No default.
ip-address <address_ipv4>
Specify a static IP address for the RP.
0.0.0.0
group <access_list_name>
Configure a single static RP for the multicast group addresses given in the specified access list. For more information on access lists, see router access-list, access-list6.
If an RP for any of these group addresses is already known to the BSR, the static RP address is ignored and the RP known to the BSR is used instead.
Null.