PIM-BiDir for IPv6
Load multicast.init.cfg
Configure XR4 as the RP for all IPv6 multicast groups. Advertise the RP mapping using BSR. Use BiDir for these groups.
Answer
Explanation
PIM-BiDir for IPv6 works the same way as IPv4. The DF election is used to ensure a loop free topology for upstream traffic that is unconditionally forwarded towards the RP.
To begin, we can confirm that we learn the RP mapping via BSR, and that XR4 identified as the RP in bidir mode. For IPv6 PIM, BiDir support is enabled by default on both IOS-XE and IOS-XR. The BD flag appears to mean BiDir.
To make this simpler, we will just join a group from R5’s loopback. This mimicks a host joining on a physical interface.
We see on the RP that the tree is built to the receiver and the outgoing interface is the link to XR1.
Let’s now ping this group from R1:
At R7, the traffic is forwarded towards the BiDir RP unconditionally. Interestingly, we see no entries at all under show ipv6 mroute or show ipv6 pim topology. However, we can see the ff00::/8 BiDir entry using show ipv6 mrib route:
R7 is accepting on all interfaces that are DF or upstream interfaces, and only forwarding out the upstream interface. Just like BiDir for IPv4, we can check the DF election results. R7 did not win the DF election with XR1, so this interface is not available as an incoming interface.
A similar command can be used on IOS-XR:
A note on IPv6 PIM-SM with PIM-BiDir
For IPv4 on IOS-XE, we cannot use the same loopback for the RP for both PIM-SM and PIM-BIDIR. This is because the command overrides itself when you try to use the same loopback for two separate PIM RP commands.
This is again an issue for IPv6 when using BSR on IOS-XE.
However, it is not an issue when using static IPv6 RP assignment on IOS-XE:
Like we saw for IPv4 on IOS-XR, IPv6 on IOS-XR allows both commands for either BSR or static RP.
Last updated