Ipv6 Multicast Data Abnormally Terminated On An Intermediate Router; Rps Unable To Join Spt In Ipv6 Pim-Sm - H3C LS-3100-52P-OVS-H3 Operation Manual

S5500-ei series ethernet switches
Table of Contents

Advertisement

4)
Check that IPv6 PIM and MLD are enabled on the interfaces directly connecting to the IPv6
multicast source and to the receiver.
5)
Check that the same IPv6 PIM mode is enabled on related interfaces. Use the display pim ipv6
interface verbose command to check whether the same PIM mode is enabled on the RPF
interface and the corresponding interface of the RPF neighbor router.
6)
Check that the same IPv6 PIM mode is enabled on all the routers in the entire network. Use the
display current-configuration command to check the IPv6 PIM mode information on each
interface. Make sure that the same IPv6 PIM mode is enabled on all the routers: IPv6 PIM-SM on
all routers, or IPv6 PIM-DM on all routers.

IPv6 Multicast Data 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 data but no corresponding (S, G) entry is
created in the IPv6 PIM routing table.
Analysis
When a router receives an IPv6 multicast packet, it decrements the hop limit value of the IPv6
multicast packet by 1 and recalculates the checksum value. The router then forwards the packet to
all outgoing interfaces. If the multicast ipv6 minimum-hoplimit command is configured on the
outgoing interfaces, the hop limit value of the packet must be larger than the configured minimum
hop limit value; otherwise, the packet will be discarded.
If an IPv6 multicast forwarding boundary has been configured through the multicast ipv6
boundary command, any IPv6 multicast packet will be kept from crossing the boundary, and
therefore no routing entry can be created in the IPv6 PIM routing table.
In addition, the source-policy command is used to filter received IPv6 multicast packets. If the
IPv6 multicast data fails to pass the ACL rule defined in this command, IPv6 PIM cannot create the
route entry, either.
Solution
1)
Check the minimum hop limit value for IPv6 multicast forwarding. Use the display
current-configuration command to check the minimum hop limit value for multicast forwarding.
Increase the hop limit value or remove the multicast ipv6 minimum-hoplimit command
configured on the interface.
2)
Check
the
current-configuration command to check the IPv6 multicast forwarding boundary settings. Use
the multicast ipv6 boundary command to change the IPv6 multicast forwarding boundary
settings.
3)
Check the IPv6 multicast filter configuration. Use the display current-configuration command to
check the IPv6 multicast filter configuration. Change the IPv6 ACL rule defined in the
source-policy command so that the source/group address of the IPv6 multicast data can pass
ACL filtering.

RPs Unable to Join SPT in IPv6 PIM-SM

Symptom
An RPT cannot be established correctly, or the RPs cannot join the SPT to the IPv6 multicast source.
IPv6
multicast
forwarding
boundary
configuration.
1-46
Use
the
display

Advertisement

Chapters

Table of Contents
loading

Table of Contents