Task 5.4 - r4 & r5 receives no mroute and rp info

Does anyone able to receive RP information on R4 and R5?  I know the task didn't ask to check for RP but if it is working, we should see RP on R4 & R5.

In addition, to make the IPv6 static route for mroute, shouldn't the static routes statement end with the keyword "multicast"? without the "multicast" keyword, SG is changing the IPv6 unicast routing domain to fix RPF check.

Rack1R4#sh ipv6 pim bsr e
PIMv2 BSR information

BSR Election Information
  Scope Range List: ff00::/8
     BSR Address: 2001:130:1:6::6
     Uptime: 00:39:14, BSR Priority: 192, Hash mask length: 126
     RPF: FE80::224:97FF:FEEA:452A,Tunnel46
     BS Timer: 00:02:03

Rack1R4#sh ipv6 pim bsr candidate-rp
No C-RP information found

Rack1R4#sh ipv6 mroute

No mroute entries found.

Rack1R5#sh ipv6 pim bsr e
PIMv2 BSR information

BSR Election Information
  Scope Range List: ff00::/8
     BSR Address: 2001:130:1:6::6
     Uptime: 00:39:42, BSR Priority: 192, Hash mask length: 126
     RPF: FE80::224:97FF:FEEA:452A,Tunnel56
     BS Timer: 00:01:34

Rack1R5#sh ipv6 pim bsr candidate-rp
No C-RP information found

Rack1R5#sh ipv6 mroute
No mroute entries found.

 

Comments

  • Since there was no requirement about full ipv6 unicast connectivity - I just configured a tunnel between R6 and R4, add a default multicast route at R4 toward tunnel 46 and a static ipv6 multicast route on R5 toward R4 to reach the BSR.

    It's horrible for production (and will even break ipv6 unicast reachability since R4 will have only mcast connectivity) but what matters is get the points :)

  • I just added below and it worked per requirements.  I would imagine you only want to affect the multicast RP check with static routes not normal data flow as the SG does.

     

    R4

    ipv6 route 2001:130:1:6::/64 Tunnel46 2001:130:1:46::6 multicast

    R5

    ipv6 route 2001:130:1:6::/64 Tunnel56 2001:130:1:56::6 multicast

Sign In or Register to comment.