R3102-R3103-HP 6600/HSR6600 Routers IP Multicast Configuration Guide
Table Of Contents
- Title Page
- Contents
- Multicast overview
- Configuring IGMP snooping
- Overview
- IGMP snooping configuration task list
- Configuring basic IGMP snooping functions
- Configuring IGMP snooping port functions
- Configuring IGMP snooping querier
- Configuring IGMP snooping proxying
- Configuring IGMP snooping policies
- Configuration prerequisites
- Configuring a multicast group filter
- Configuring multicast source port filtering
- Enabling dropping unknown multicast data
- Enabling IGMP report suppression
- Setting the maximum number of multicast groups that a port can join
- Enabling multicast group replacement
- Setting the 802.1p precedence for IGMP messages
- Enabling the IGMP snooping host tracking function
- Displaying and maintaining IGMP snooping
- IGMP snooping configuration examples
- Troubleshooting IGMP snooping
- Appendix
- Configuring multicast routing and forwarding
- Overview
- Configuration task list
- Enabling IP multicast routing
- Configuring multicast routing and forwarding
- Displaying and maintaining multicast routing and forwarding
- Configuration examples
- Troubleshooting multicast routing and forwarding
- Configuring IGMP
- Overview
- IGMP configuration task list
- Configuring basic IGMP functions
- Adjusting IGMP performance
- Configuring IGMP SSM mapping
- Configuring IGMP proxying
- Displaying and maintaining IGMP
- IGMP configuration examples
- Troubleshooting IGMP
- Configuring PIM
- Overview
- Configuring PIM-DM
- Configuring PIM-SM
- Configuring BIDIR-PIM
- Configuring PIM-SSM
- Configuring common PIM features
- Displaying and maintaining PIM
- PIM configuration examples
- Troubleshooting PIM
- Configuring MSDP
- Overview
- MSDP configuration task list
- Configuring basic MSDP functions
- Configuring an MSDP peer connection
- Configuring SA message related parameters
- Displaying and maintaining MSDP
- MSDP configuration examples
- Troubleshooting MSDP
- Configuring MBGP
- MBGP overview
- Protocols and standards
- MBGP configuration task list
- Configuring basic MBGP functions
- Controlling route advertisement and reception
- Configuration prerequisites
- Configuring MBGP route redistribution
- Configuring default route redistribution into MBGP
- Configuring MBGP route summarization
- Advertising a default route to an IPv4 MBGP peer or peer group
- Configuring outbound MBGP route filtering
- Configuring inbound MBGP route filtering
- Configuring MBGP route dampening
- Configuring MBGP route attributes
- Optimizing MBGP networks
- Configuring a large scale MBGP network
- Displaying and maintaining MBGP
- MBGP configuration example
- Configuring multicast VPN
- Overview
- How MD-VPN works
- Multicast VPN configuration task list
- Configuring MD-VPN
- Configuring BGP MDT
- Specifying the source IP address for multicast across VPNs
- Displaying and maintaining multicast VPN
- Multicast VPN configuration examples
- Troubleshooting MD-VPN
- Configuring IPv6 multicast routing and forwarding
- Overview
- Configuration task list
- Enabling IPv6 multicast routing
- Configuring IPv6 multicast routing and forwarding
- Displaying and maintaining IPv6 multicast routing and forwarding
- IPv6 multicast forwarding over GRE tunnel configuration example
- Troubleshooting abnormal termination of IPv6 multicast data
- Configuring MLD
- Overview
- MLD configuration task list
- Configuring basic MLD functions
- Adjusting MLD performance
- Configuring MLD SSM mapping
- Configuring MLD proxying
- Displaying and maintaining MLD
- MLD configuration examples
- Troubleshooting MLD
- Configuring IPv6 PIM
- Overview
- Configuring IPv6 PIM-DM
- Configuring IPv6 PIM-SM
- Configuring IPv6 BIDIR-PIM
- Configuring IPv6 PIM-SSM
- Configuring common IPv6 PIM features
- Displaying and maintaining IPv6 PIM
- IPv6 PIM configuration examples
- Troubleshooting IPv6 PIM
- Configuring IPv6 MBGP
- Overview
- IPv6 MBGP configuration task list
- Configuring basic IPv6 MBGP functions
- Controlling route distribution and reception
- Configuration prerequisites
- Injecting a local IPv6 MBGP route
- Configuring IPv6 MBGP route redistribution
- Configuring IPv6 MBGP route summarization
- Advertising a default route to a peer or peer group
- Configuring outbound IPv6 MBGP route filtering
- Configuring inbound IPv6 MBGP route filtering
- Configuring IPv6 MBGP route dampening
- Configuring IPv6 MBGP route attributes
- Optimizing IPv6 MBGP networks
- Configuring a large scale IPv6 MBGP network
- Displaying and maintaining IPv6 MBGP
- IPv6 MBGP configuration example
- Configuring PIM snooping
- Configuring multicast VLANs
- Support and other resources
- Index

168
An MSDP mesh group refers to a group of MSDP peers that have MSDP peering relationships among one
another and share the same group name.
When using MSDP for inter-domain multicasting, once an RP receives information form a multicast source,
it no longer relies on RPs in other PIM-SM domains. The receivers can override the RPs in other domains
and directly join the multicast source-based SPT.
RPF check rules for SA messages
As shown in Figure 52, the autonomous systems in the network are AS 1 through AS 5. IGP is enabled
on routers within each AS and BGP or MBGP as the interoperation protocol among the ASs. Each AS
contains at least one PIM-SM domain, and each PIM-SM domain contains one or more RPs. MSDP
peering relationships have been established among different RPs. RP 3, RP 4, and RP 5 are in an MSDP
mesh group. On RP 7, RP 6 is configured as its static RPF peer.
When an RP receives an SA message from a static RPF peer, the RP accepts the SA message and
forwards it to other peers without performing an RPF check.
Figure 52 Diagram for RPF check for SA messages
As shown in Figure 52, these MSDP peers dispose of SA messages according to the following RPF check
rules:
1. When RP 2 receives an SA message from RP 1:
Because the source-side RP address in the SA message is the same as the MSDP peer address,
which means that the MSDP peer where the SA is from is the RP that has created the SA message,
RP 2 accepts the SA message and forwards it to its other MSDP peer (RP 3).
2. When RP 3 receives the SA message from RP 2:
Because the SA message is from an MSDP peer (RP 2) in the same AS, and the MSDP peer is the
next hop on the optimal path to the source-side RP, RP 3 accepts the message and forwards it to
other peers (RP 4 and RP 5).
3. When RP 4 and RP 5 receive the SA message from RP 3:
Because the SA message is from an MSDP peer (RP 3) in the same mesh group, RP 4 and RP 5 both
accept the SA message, but they do not forward the message to other members in the mesh group.
Instead, they forward it to other MSDP peers (RP 6 in this example) out of the mesh group.
4. When RP 6 receives the SA messages from RP 4 and RP 5 (suppose RP 5 has a higher IP address):










