Troubleshooting guide
3. Troubleshooting Functional Failures During Operation
103
4 Check whether MLD snooping is set for the interface
on which PIM runs.
show mld-snooping
If MLD snooping is set, check the following:
• Check whether the multicast router port for MLD
snooping is set for the port connected to the
neighboring router.
• See 3.6.5 Multicast forwarding by MLD snooping
is not possible.
5 Make sure that the configuration does not contain
filtering or other settings that suppress forwarding of
protocol packets and multicast packets on the interface
on which PIM and MLD run.
show running-config
If the configuration contains a setting that suppresses
forwarding of protocol packets and multicast packets,
modify the configuration. For details about the
procedure for checking the filter configuration
information, see 3.25.1 Checking the filters and QoS
configuration information.
6 Check the PIM neighboring information.
show ipv6 pim neighbor
If neighboring routers are not displayed, check the
following:
• Use the
show ipv6 pim command with the
interface parameter to make sure that PIM is
running on the interface connected with the
neighboring routers.
• Check the settings of the neighboring routers.
7 Check whether the unicast route to the multicast data
sender exists.
show ipv6 route
If the unicast route does not exist, see 3.11 IPv6
unicast routing communication failures.
8 Make sure that PIM is running on the interface
connected to the next hop address to the multicast data
sender.
show ipv6 pim interface
If PIM is not running, check and modify the
configuration so that PIM runs on the interface
connected to the next hop address to the multicast data
sender.
9 Check the configuration to make sure that the
PIM-SSM group addresses do not contain the
forwarding target group address.
show running-config
If the PIM-SSM group addresses contain the
forwarding target group address, modify the
configuration.
10 Make sure that BSR has been determined. This
checking is not required if the rendezvous point for the
forwarding target group address is a static rendezvous
point.
show ipv6 pim bsr
If BSR has not been determined, check whether the
unicast route to BSR exists. If the unicast route does
not exist, see 3.11 IPv6 unicast routing
communication failures.
If the unicast route exists, check the BSR settings. If
the Switch is used as BSR, see (2) Items to check for
BSR.
11 Make sure that the rendezvous point has been
determined.
show ipv6 pim rp-mapping
If the rendezvous point has not been determined, check
whether the unicast route to the rendezvous point
exists. If the unicast route does not exist, see 3.11 IPv6
unicast routing communication failures.
If the unicast route exists, check the rendezvous point
settings. If the Switch is used as the rendezvous point,
see (3) Items to check for the rendezvous point router.
12 Make sure that the rendezvous point group addresses
contain the forwarding target group address.
show ipv6 pim rp-mapping
If the forwarding target group address is not contained,
check the rendezvous point router settings.
13 Make sure that multicast forwarding entries exist.
show ipv6 mcache
If multicast forwarding entries do not exist, make sure
that multicast data has reached the upstream port. If
multicast data has not reached the upstream port, check
the settings of the multicast sender or upstream router.
14 Make sure that multicast routing information exists.
show ipv6 mroute
If multicast routing information does not exist, check
the downstream router settings.
No. Items to check and commands Action