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
188
• Because a hello message does not carry IPv6 PIM mode information, an IPv6 PIM router cannot
identify what IPv6 PIM mode its IPv6 PIM neighbor is running in. If the RPF interface on a router and
the connected interface of the router's RPF neighbor operate in different IPv6 PIM modes, the
multicast distribution tree cannot be correctly built, causing abnormal multicast forwarding.
• The same IPv6 PIM mode must run on the entire network. Otherwise, the multicast distribution tree
cannot be correctly built, causing abnormal multicast forwarding.
Solution
1. Use display ipv6 routing-table to verify that an IPv6 unicast route to the IPv6 multicast source or the
RP is available.
2. Use display ipv6 pim interface to verify IPv6 PIM information on each interface, especially on the
RPF interface. If IPv6 PIM is not enabled on the interfaces, use ipv6 pim dm or ipv6 pim sm to
enable IPv6 PIM-DM or IPv6 PIM-SM for the interfaces.
3. Use display ipv6 pim neighbor to verify that the RPF neighbor is an IPv6 PIM neighbor.
4. Verify that IPv6 PIM and MLD are enabled on the interfaces that directly connect to the IPv6
multicast sources or the receivers.
5. Use display ipv6 pim interface verbose to verify that the same IPv6 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 IPv6 PIM mode is enabled on all routers
on the network. For IPv6 PIM-SM, verify that the BSR and C-RPs are correctly configured.
IPv6 multicast data is abnormally terminated on an
intermediate router
Symptom
An intermediate router can receive IPv6 multicast data successfully, but the data cannot reach the
last-hop router. An interface on the intermediate router receives IPv6 multicast data but does not create
an (S, G) entry in the IPv6 PIM routing table.
Analysis
• If an IPv6 multicast forwarding boundary has been configured through the ipv6 multicast boundary
command, and the IPv6 multicast packets are kept from crossing the boundary, IPv6 PIM cannot
create routing entries for the packets.
• If an ACL is defined by the source-policy command, and the IPv6 multicast packets cannot match
the ACL rules, IPv6 PIM cannot create the routing entries for the packets.
Solution
1. Use display current-configuration to verify the IPv6 multicast forwarding boundary settings. Use
ipv6 multicast boundary to change the multicast forwarding boundary settings to make the IPv6
multicast packet able to cross the boundary.