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
195
MSDP peers stay in down state
Symptom
The configured MSDP peers stay in down state.
Analysis
• A TCP connection–based MSDP peering relationship is established between the local interface
address and the MSDP peer after the configuration.
• The TCP connection setup will fail if the local interface address is not consistent with the MSDP peer
address configured on the peer router.
• If no route is available between the MSDP peers, the TCP connection setup will fail.
Solution
1. Use the display ip routing-table command to verify that the unicast route between the routers is
correct.
2. Verify that a unicast route is available between the two routers that will become MSDP peers to
each other.
3. Use the display current-configuration command to verify that the local interface address and the
MSDP peer address of the remote router are the same.
No SA entries exist in the router's SA cache
Symptom
MSDP fails to send (S, G) entries through SA messages.
Analysis
• The import-source command controls sending (S, G) entries through SA messages to MSDP peers.
If this command is executed without the acl-number argument, all the (S, G) entries will be filtered
off. Namely, no (S, G) entries of the local domain will be advertised.
• If you do not configure the import-source command, the system advertises all the (S, G) entries of
the local domain. If MSDP fails to send (S, G) entries through SA messages, verify that the
import-source command has been correctly configured.
Solution
1. Use the display ip routing-table command to verify that the unicast route between the routers is
correct.
2. Verify that a unicast route is available between the two routers that will become MSDP peers to
each other.
3. Verify the configuration of the import-source command and its acl-number argument and make
sure the ACL rule can filter appropriate (S, G) entries.
No SA entries exist in the router's SA cache
Symptom
RPs fail to exchange their locally registered (S, G) entries with one another in the Anycast RP application.










