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

94
The flood-and-prune process takes place periodically. A pruned state timeout mechanism is provided. A
pruned branch restarts multicast forwarding when the pruned state times out and then is pruned again
when it no longer has any multicast receiver.
NOTE:
Pruning has a similar implementation in PIM-SM.
Graft
When a host attached to a pruned node joins a multicast group, to reduce the join latency, PIM-DM uses
a graft mechanism to resume data forwarding to that branch. The process is as follows:
1. The node that needs to receive multicast data sends a graft message toward its upstream node, as
a request to join the SPT again.
2. After receiving this graft message, the upstream node puts the interface on which the graft was
received into the forwarding state and responds with a graft-ack message to the graft sender.
3. If the node that sent a graft message does not receive a graft-ack message from its upstream node,
it will keep sending graft messages at a configurable interval until it receives an acknowledgment
from its upstream node.
Assert
On a shared-media network with more than one multicast router, the assert mechanism shuts off duplicate
multicast flows to the network. It does this by electing a unique multicast forwarder on the shared-media
network.
Figure 33 Assert mechanism
As shown in Figure 33, the assert mechanism is as follows:
1. After Router A and Router B receive an (S, G) packet from the upstream node, both routers forward
the packet to the local subnet.
As a result, the downstream node Router C receives two identical multicast packets, and both
Router A and Router B, on their own downstream interfaces, receive a duplicate packet forwarded
by the other.
2. After detecting this condition, both routers send an assert message to all PIM routers (224.0.0.13)
on the local subnet through the interface that received the packet.
The assert message contains the multicast source address (S), the multicast group address (G), and
the preference and metric of the unicast route/MBGP route/multicast static route to the source.










