Supported Platforms
Related Documentation
- J, M, MX, QFX, SRX, T Series
- Filtering Incoming PIM Join Messages
- M, MX, PTX, T Series
- Understanding Multicast Administrative Scoping
- PTX, QFX, T Series
- Example: Configuring PIM BSR Filters
Filtering MSDP SA Messages
Along with applying MSDP source active (SA) filters on all external MSDP sessions (in and out) to prevent SAs for groups and sources from leaking in and out of the network, you need to apply bootstrap router (BSR) filters. Applying a BSR filter to the boundary of a network prevents foreign BSR messages (which announce RP addresses) from leaking into your network. Since the routers in a PIM sparse-mode domain need to know the address of only one RP router, having more than one in the network can create issues.
If you did not use multicast scoping to create boundary filters for all customer-facing interfaces, you might want to use PIM join filters. Multicast scopes prevent the actual multicast data packets from flowing in or out of an interface. PIM join filters prevent PIM sparse-mode state from being created in the first place. Since PIM join filters apply only to the PIM sparse-mode state, it might be more beneficial to use multicast scoping to filter the actual data.
 | Note: When you apply firewall filters, firewall action modifiers, such as log, sample, and count, work only when you apply the filter on an inbound interface. The modifiers do not work on an outbound interface. |
Related Documentation
- J, M, MX, QFX, SRX, T Series
- Filtering Incoming PIM Join Messages
- M, MX, PTX, T Series
- Understanding Multicast Administrative Scoping
- PTX, QFX, T Series
- Example: Configuring PIM BSR Filters
Published: 2012-06-29
Supported Platforms
Related Documentation
- J, M, MX, QFX, SRX, T Series
- Filtering Incoming PIM Join Messages
- M, MX, PTX, T Series
- Understanding Multicast Administrative Scoping
- PTX, QFX, T Series
- Example: Configuring PIM BSR Filters
