Changing the pim join and prune message interval, Dropping pim traffic in hardware – Brocade TurboIron 24X Series Configuration Guide User Manual
Page 847
Brocade TurboIron 24X Series Configuration Guide
813
53-1003053-01
PIM Sparse
After the Layer 3 Switch receives a packet for a given source-group pair, the Layer 3 Switch starts a
PIM data timer for that source-group pair. If the Layer 3 Switch does not receive another packet for
the source-group pair before the timer expires, it reverts to using the RP for the next packet
received for the source-group pair. In accordance with the PIM Sparse RFC recommendation, the
timer is 210 seconds and is not configurable. The counter is reset to zero each time the Layer 3
Switch receives a packet for the source-group pair.
You can change the number of packets that the Layer 3 Switch sends using the RP before switching
to using the SPT. To do so, use the following CLI method.
TurboIron(config)#router pim
TurboIron(config-pim-router)#spt-threshold 1000
Syntax: [no] spt-threshold infinity |
The infinity |
Switch sends packets using the RP indefinitely and does not switch over to the SPT. If you enter a
specific number of packets, the Layer 3 Switch does not switch over to using the SPT until it has
sent the number of packets you specify using the RP.
Changing the PIM join and prune message interval
By default, the Layer 3 Switch sends PIM Sparse Join/Prune messages every 60 seconds. These
messages inform other PIM Sparse routers about clients who want to become receivers (Join) or
stop being receivers (Prune) for PIM Sparse groups.
You can change the Join/Prune message interval using the following CLI method.
NOTE
Use the same Join/Prune message interval on all the PIM Sparse routers in the PIM Sparse domain.
If the routers do not all use the same timer interval, the performance of PIM Sparse can be adversely
affected.
To change the Join/Prune interval, enter commands such as the following.
TurboIron(config)#router pim
TurboIron(config-pim-router)#message-interval 30
Syntax: [no] message-interval
The
60.
Dropping PIM traffic in hardware
Unwanted PIM Dense or PIM Sparse multicast traffic can be dropped in hardware on Layer 3
Switches. Refer to
“Passive multicast route insertion”
Anycast RP is supported on a fully-meshed topology. Configure MSDP peers and configure
mesh-groups that use a fully meshed peer topology. MSDP peering can be established between
physical interfaces or loopback interfaces. MSDP is used between all intra-domain RPs in a
full-mesh configuration to provide redundancy and backup of PIM-SM network.RP1(config)#router
ospf
RP1(config-ospf-router)#area 0
RP1(config-ospf-router)#exit
RP1(config)#interface loopback 1
RP1(config-lbif-1)#ip ospf area 0