# Display IPv6 PIM routing table information on Switch C.
[SwitchC] display ipv6 pim routing-table
Total 1 (*, G) entry; 1 (S, G) entry
(*, FF1E::101)
Protocol: pim-dm, Flag: WC
UpTime: 00:04:25
Upstream interface: NULL
Upstream neighbor: NULL
RPF prime neighbor: NULL
Downstream interface(s) information:
Total number of downstreams: 1
1: Vlan-interface200
(1001::100, FF1E::101)
Protocol: pim-dm, Flag: ACT
UpTime: 00:06:14
Upstream interface: Tunnel0
Upstream neighbor: FE80::A01:101:1
RPF prime neighbor: FE80::A01:101:1
Downstream interface(s) information:
Total number of downstreams: 1
1: Vlan-interface200
The output shows that Switch A is the RPF neighbor of Switch C and the IPv6 multicast data from Switch
A is delivered over a GRE tunnel to Switch C.
Troubleshooting
IPv6 multicast data fails to reach receivers
Symptom
IPv6 multicast data can reach some routers but fails to reach the last-hop router.
Analysis
No multicast packets can cross a multicast boundary set with the ipv6 multicast boundary command.
Solution
Use the display ipv6 pim routing-table command to verify that the corresponding (S, G) entries
1.
exist on each router. If so, routers have received the IPv6 multicast data. Otherwise, routers have
not received the IPv6 multicast data.
Use the display ipv6 multicast boundary command to display the multicast boundary information
2.
on the interfaces. Use the ipv6 multicast boundary command to change the multicast forwarding
boundary setting.
If the IPv6 multicast data travels in PIM-SM network, use the display current-configuration
3.
command to check the BSR and RP information.
Protocol: mld, UpTime: 00:04:25, Expires: never
Protocol: pim-dm, UpTime: 00:04:25, Expires: never
124