1-47
3) Check that the RPF neighbor is an IPv6 PIM neighbor. Use the
display pim ipv6 neighbor
command to view the PIM neighbor information.
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
z
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.
z
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 IPv6 multicast forwarding boundary configuration. Use the
display
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.
2) 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.
Analysis
z
As the core of an IPv6 PIM-SM domain, the RPs serves specific IPv6 multicast groups. Multiple
RPs can coexist in a network. Make sure that the RP information on all routers is exactly the same,
and a specific group is mapped to the same RP. Otherwise, IPv6 multicast will fail.
Содержание S7902E
Страница 82: ...1 4 DeviceA interface tunnel 1 DeviceA Tunnel1 service loopback group 1 ...
Страница 200: ...1 11 DeviceB display vlan dynamic No dynamic vlans exist ...
Страница 494: ...ii Displaying and Maintaining Tunneling Configuration 1 45 Troubleshooting Tunneling Configuration 1 45 ...
Страница 598: ...ii ...
Страница 1757: ...4 9 ...
Страница 1770: ...6 4 ...
Страница 2017: ...2 11 Figure 2 3 SFTP client interface ...
Страница 2062: ...i Table of Contents 1 URPF Configuration 1 1 URPF Overview 1 1 What is URPF 1 1 How URPF Works 1 1 Configuring URPF 1 2 ...
Страница 2238: ...1 16 DeviceA cfd linktrace service instance 1 mep 1001 target mep 4002 ...
Страница 2442: ...2 4 Set the interval for sending Syslog or trap messages to 20 seconds Device mac address information interval 20 ...