HP VPN Firewall Appliances Network Management Configuration Guide

860
The output shows that Router A is the RPF neighbor of the firewall and the IPv6 multicast data from Router
A is delivered over a GRE tunnel to the firewall.
Troubleshooting abnormal termination of IPv6
multicast data
Symptom
• A host sends an MLD report announcing its joining an IPv6 multicast group (G). However, no
member information about the IPv6 multicast group (G) exists on the intermediate router. The
intermediate router can receive IPv6 multicast packets successfully, but the packets cannot reach the
stub network.
• The interface of the intermediate router receives the IPv6 multicast packets, but no corresponding (S,
G) entry exists in the IPv6 PIM routing table.
Analysis
• The multicast ipv6 boundary command filters IPv6 multicast packets received on an interface. If an
IPv6 multicast packet fails to match the IPv6 ACL rule of this command, IPv6 PIM creates no routing
entry.
• In addition, the source-policy command in IPv6 PIM filters received IPv6 multicast packets. If an IPv6
multicast packet fails to match the IPv6 ACL rule of this command, IPv6 PIM does not create a
routing entry.
Solution
1. Use the display current-configuration command to display the IPv6 ACL rule configured on the
multicast forwarding boundary. Change the IPv6 ACL rule used in the multicast ipv6 boundary
command so that the source address of the IPv6 multicast packets and the IPv6 multicast group
address can both match the IPv6 ACL rule.
2. Use the display current-configuration command to verify the configuration of the IPv6 multicast
filter, and change the IPv6 ACL rule used in the source-policy command so that the source address
of the IPv6 multicast packets and the IPv6 multicast group address can both match the IPv6 ACL
rule.