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

135
Configuring a hello message filter
Along with the wide applications of PIM, the security requirement for the protocol is becoming
increasingly demanding. The establishment of correct PIM neighboring relationship is the prerequisite for
secure application of PIM.
To guard against PIM message attacks, you can configure a legal source address range for hello
messages on interfaces of routers to ensure the correct PIM neighboring relationship.
To configure a hello message filter:
Ste
p
Command
Remarks
1. Enter system view. system-view N/A
2. Enter interface view.
interface interface-type
interface-number
N/A
3. Configure a hello message
filter.
pim neighbor-policy acl-number
No hello message filter by default.
When the hello message filter is
configured, if hello messages of an
existing PIM neighbor fail to pass
the filter, the PIM neighbor will be
removed automatically when it
times out.
Configuring PIM hello options
In either a PIM-DM domain or a PIM-SM domain, hello messages exchanged among routers contain the
following configurable options:
• DR_Priority (for PIM-SM only)—Priority for DR election. The device with the highest priority wins the
DR election. You can configure this option for all the routers in a shared-media LAN that directly
connects to the multicast source or the receivers.
• Holdtime—PIM neighbor lifetime. If a router receives no hello message from a neighbor when the
neighbor lifetime expires, it regards the neighbor failed or unreachable.
• LAN_Prune_Delay—Delay of forwarding prune messages on a shared-media LAN. This option
consists of LAN delay (namely, prune message delay), override interval, and neighbor tracking
support (namely, the capability to disable join message suppression).
The prune message delay defines the delay time for a router to forward a received prune message
to the upstream routers. The override interval defines a time period for a downstream router to
override a prune message. If the prune message delay or override interval on different PIM routers
on a shared-media LAN are different, the largest value takes effect.
A router does not immediately prune an interface after it receives a prune message from the
interface. Instead, it starts a timer (the prune message delay plus the override interval). If interface
receives a join message before the override interval expires, the router does not prune the
interface. Otherwise, the router prunes the interface when the timer (the prune message delay plus
the override interval) expires.
You can enable the neighbor tracking function (or disable the join message suppression function)
on an upstream router to track the states of the downstream nodes that have sent the join message
and the joined state holdtime timer has not expired. If you want to enable the neighbor tracking
function, you must enable it on all PIM routers on a shared-media LAN. Otherwise, the upstream
router cannot track join messages from every downstream routers..










