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
187
Group/MaskLen: FFF4::/16
RP address Priority HoldTime Uptime Expires
1002::2 (local) 192 180 00:02:03 00:02:56
Group/MaskLen: FF04::/16
RP address Priority HoldTime Uptime Expires
1002::2 (local) 192 180 00:02:03 00:02:56
# Display RP information on Switch F.
[SwitchF] display pim rp-info
BSR RP information:
Scope: non-scoped
Group/MaskLen: FF00::/8
RP address Priority HoldTime Uptime Expires
8001::1 (local) 192 180 00:10:28 00:02:31
Troubleshooting IPv6 PIM
A multicast distribution tree cannot be correctly built
Symptom
An IPv6 multicast distribution tree cannot be correctly built because there are no IPv6 multicast
forwarding entries established on the routers (including routers directly connected with multicast sources
or receivers) in a IPv6 PIM network.
Analysis
• On an IPv6 PIM-DM enabled network, IPv6 multicast data is flooded from the router that directly
connects to the IPv6 multicast source to the routers that directly connects to the receivers. When the
IPv6 multicast data is flooded to a router, the router creates an (S, G) entry only if it has a route to
the IPv6 multicast source. If the router does not have a route to the IPv6 multicast source, or if IPv6
PIM-DM is not enabled on the RPF interface toward the IPv6 multicast source, the router cannot
create an (S, G) entry.
• On an IPv6 PIM-SM enabled network, when a router wants to join the SPT, the router creates an (S,
G) entry only if it has a route to the IPv6 multicast source. If the router does not have a route to the
IPv6 multicast source, or if IPv6 PIM-SM is not enabled on the RPF interface toward the IPv6
multicast source, the router cannot create an (S, G) entry.
• When a multicast router receives an IPv6 multicast packet, it looks up the existing IPv6 unicast
routing table for the optimal route to the packet source. The outgoing interface of this route act as
the RPF interface and the next hop acts the RPF neighbor. The RPF interface completely relies on the
existing IPv6 unicast route and is independent of IPv6 PIM. The RPF interface must be enabled with
IPv6 PIM, and the RPF neighbor must be an IPv6 PIM neighbor. If IPv6 PIM is not enabled on the RPF
interface or the RPF neighbor, the multicast distribution tree cannot be correctly built, causing
abnormal multicast forwarding.