R21xx-HP FlexFabric 11900 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 policies
- Displaying and maintaining IGMP snooping
- IGMP snooping configuration examples
- Troubleshooting IGMP snooping
- Configuring multicast routing and forwarding
- Configuring IGMP
- Configuring PIM
- Overview
- Configuring PIM-DM
- Configuring PIM-SM
- Configuring common PIM features
- Displaying and maintaining PIM
- PIM configuration examples
- Troubleshooting PIM
- Configuring MLD snooping
- Overview
- MLD snooping configuration task list
- Configuring basic MLD snooping functions
- Configuring MLD snooping port functions
- Configuring MLD snooping policies
- Displaying and maintaining MLD snooping
- MLD snooping configuration examples
- Troubleshooting MLD snooping
- Configuring IPv6 multicast routing and forwarding
- Configuring MLD
- Configuring IPv6 PIM
- PIM overview
- Configuring IPv6 PIM-DM
- Configuring IPv6 PIM-SM
- Configuring common IPv6 PIM features
- Displaying and maintaining IPv6 PIM
- IPv6 PIM configuration examples
- Troubleshooting IPv6 PIM
- Support and other resources
- Index
103
4.
Verify that PIM and IGMP are enabled on the interfaces that directly connect to the multicast
sources or the receivers.
5. Use display pim interface verbose to verify that the same PIM mode is enabled on the RPF interface
on a router and the connected interface of the router's RPF neighbor.
6. Use display current-configuration to verify that the same PIM mode is enabled on all routers. For
PIM-SM, verify that the BSR and C-RPs are correctly configured.
Multicast data is abnormally terminated on an intermediate
router
Symptom
An intermediate router can receive multicast data successfully, but the data cannot reach the last-hop
router. An interface on the intermediate router receives multicast data but does not create an (S, G) entry
in the PIM routing table.
Analysis
• If a multicast forwarding boundary has been configured through the multicast boundary command,
and the multicast packets are kept from crossing the boundary, PIM cannot create routing entries for
the packets.
• If an ACL is defined by the source-policy command, and the multicast packets cannot match the
ACL rule, PIM cannot create the routing entries for the packets.
Solution
1. Use display current-configuration to verify the multicast forwarding boundary settings. Use
multicast boundary to change the multicast forwarding boundary settings to make the multicast
packet able to cross the boundary.
2. Use display current-configuration to verify the multicast data filter. Change the ACL rule defined in
the source-policy command so that the source/group address of the multicast data can pass ACL
filtering.
An RP cannot join an SPT in PIM-SM
Symptom
An RPT cannot be correctly built, or an RP cannot join the SPT toward the multicast source.
Analysis
• RPs are the core of a PIM-SM domain. An RP provides services for a specific multicast group, and
multiple RPs can coexist on a network. Make sure the RP information on all routers is exactly the
same to map a specific multicast group to the same RP. Otherwise, multicast forwarding fails.
• If a static RP is configured, use the same static RP configuration on all routers on the entire network.
Otherwise, multicast forwarding fails.










