9.27 IPv6 Embedded RP

Do someone manage to get this task working? I have the follwings debug output and my ipv6 pim range-list on R1 is empty ???

 

 

*Mar  1 00:56:48.575: IPv6 PIM: Received J/P on Serial0/0 from FE80::5 target: FE80::3


*Mar  1 00:56:48.575: IPv6 PIM: Join ignored, no previously learnt Embedded RP range




thnx

 

Comments

  • On the RP you need to configure static-rp pointing to itself.

    This piece of configuration is missing in INE's solution guide.

  • Guys,

    In order to make this scenario working following steps must be taken:

    1. statically define RP on R6 (RP)

    This is a must given by embedded-RP implementation. IE team forgot to mention! More in

    http://www.cisco.com/en/US/docs/ios/ipv6/configuration/guide/ip6-multicast_ps6441_TSD_Products_Configuration_Guide_Chapter.html

    2. Allow MLD join on R5

    Make sure that MLD join on R5's f0/0 interface is allowed. There is an ACL applied for MLD on f0/0 on R5. Either update it or delete.

    # in order to update ACL (see /96 prefix!)

    permit ipv6 any FF76::/96

    If you don't do this R4 will keep showing pruned (P) out s1/1 as no PIMv6 join made to R4.

    3. Static mroute on R5

    For those who redistributed connected routes into OSPFv3 and not into RIP on R6 in previous task before there is a problem on R5 now. The most specific prefix to R6's RP adddress 2001:cc1e::6 is learnt via OSPF - out s1/0 towards R3. RIP route has worse AD than OSPF and EIGRP provided only summarized default route (remember this was done on R6).

    In order to reach out to RP along multicast-enabled path (s1/1 on R5) I fixed this by:

    - unconfiguring creating summarized default route on R6

    - creating a static multicast route on R5 to point out serial line via s1/1.

     

    Hope this helps.

    Tom

  • jchanjchan ✭✭

    I followed the steps but I still could not ping from R1.  R4 is pruning the traffic.  Can someone put the config in here?

  • On R6 I only had to configure the Loopback interface with the embedded RP address and advertise it into the domain. I did not have to statically define itself as the RP.

    I did need to update the MLD acl on R5 though.

    This got it working for me.

  • Thanks tommoser! Without it I'll need more time to figure out that it caused by the mld access-group from previous task.

     

    Actually static RP configuration on R6 is really required, otherwise if you do debug on R6 you will see this:

    *Mar  1 00:29:33.675: IPv6 PIM: J/P entry: Join root: 2001:CC1E::6 group: FF76:640:2001:CC1E::8 flags:  RPT WC S

    *Mar  1 00:29:33.683: IPv6 PIM: (*,FF76:640:2001:CC1E::8) J/P message from FE80::C603:CFF:FE74:1 with invalid RP 2001:CC1E::6

    *Mar  1 00:29:33.687: IPv6 PIM: J/P entry: Prune root: 2001:1:0:146:C600:CFF:FE74:0 group: FF76:640:2001:CC1E::8 flags:  RPT S

     

     

    Without it, your multicast is actually not really working yet, as you can test it out to confirm further by making SW2 as the source (R3 is the source DR), instead of R1 ....

     

    I am just wondering if the team who came up with the workbook tasks and solutions has actually followed the tasks one by one, or else there shouldn't be many things get missed out. Just wondering...  

     

    Thanks!

  • The INE team really has to look at this lab..way too much time on something with some many problems.

     

    One thing that I found interesting is that even with the MLD ACL you see the groups as permitted, but they are filtered from sending a join to R4 as tommoser noted.  I guess since the MLD requests are being generated locally I could see that, but just makes things a lot harder to troubleshoot. For example:

    Rack1R5#sh ipv6 access-list
    IPv6 access list MLD-GROUPS
        permit ipv6 any FF08::/64 (20749 matches) sequence 10

     

    ...acl applied to gi0/0

    Rack1R5#sh run int gi0/0 | i ipv6 mld
     ipv6 mld query-interval 10
     ipv6 mld join-group FF08::8
     ipv6 mld join-group FF76:640:2001:CC1E::8  
     ipv6 mld join-group FF78:640:2001:CC1E::8
     ipv6 mld join-group FF08:2001::1
     ipv6 mld access-group MLD-GROUPS
     ipv6 mld limit 10

     

    ..groups are still seen that shouldn't be there

    Rack1R5#sh ipv6 mld groups
    MLD Connected Group Membership
    Group Address                           Interface          Uptime    Expires
    FF08::8                                 GigabitEthernet0/0 2d13h     never
    FF08:2001::1                            GigabitEthernet0/0 00:03:56  never      <--this shouldn't be visible
    FF76:640:2001:CC1E::8                   GigabitEthernet0/0 00:50:49  never  <--this shouldn't be visible
    FF78:640:2001:CC1E::8                   GigabitEthernet0/0 00:16:15  never  <--this shouldn't be visible

     

  • hi all, I can ping successful from R1,R6 to R5. So we need to configure on

    R5:
    ipv6 access-list MLD_FILER
        permit ipv6 any ff76:0640:2001:CC1E::/64

    ipv6 route FC00:1:0:6::6/128 serial 0/1 multicast

     

    hope this help!!!

    hien.

  • i think none of above solutions are correct. here is my troubleshooting and fix for this:

    1. Let 's look at the route from R5 to the RP which is hosted on R6:

    Rack1R5#show ipv6 route 2001:cc1e::6
    *Mar  1 01:09:25.195: %SYS-5-CONFIG_I: Configured from console by console
    Rack1R5#show ipv6 route 2001:cc1e::6
    IPv6 Routing Table - 28 entries
    Codes: C - Connected, L - Local, S - Static, R - RIP, B - BGP
           U - Per-user Static route, M - MIPv6
           I1 - ISIS L1, I2 - ISIS L2, IA - ISIS interarea, IS - ISIS summary
           O - OSPF intra, OI - OSPF inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2
           ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2
           D - EIGRP, EX - EIGRP external
    R   2001:CC1E::6/128 [120/3]
         via FE80::1, Serial0/0
         via FE80::4, Serial0/0
         via FE80::C003:FF:FEC9:0, Serial0/1

    hmm..we have multiple routes...RPF failure somewhere

    2. Let try this out:

    ipv6 route 2001:CC1E::6/128 Serial0/1 multicast

    3. Let 's test it out:

    Ping from R1:

    Rack1R1#ping FF76:640:2001:CC1E::8
    Output Interface: fastethernet0/0
    Type escape sequence to abort.
    Sending 100, 100-byte ICMP Echos to FF76:640:2001:CC1E::8, timeout is 2 seconds:
    Packet sent with a source address of 2001:1:0:146:C000:FF:FEC9:0

    Reply to request 0 received from FC00:1:0:58::5, 28 ms
    Reply to request 1 received from FC00:1:0:58::5, 16 ms
    Reply to request 2 received from FC00:1:0:58::5, 8 ms
    Reply to request 3 received from FC00:1:0:58::5, 4 ms

     

    Ping from R6:

    Rack1R6#ping FF76:640:2001:CC1E::8      
    Output Interface: fastethernet0/0.146
    Type escape sequence to abort.
    Sending 5, 100-byte ICMP Echos to FF76:640:2001:CC1E::8, timeout is 2 seconds:
    Packet sent with a source address of 2001:1:0:146:C005:FF:FEC9:0

    Reply to request 0 received from FC00:1:0:58::5, 20 ms
    Reply to request 1 received from FC00:1:0:58::5, 28 ms
    Reply to request 2 received from FC00:1:0:58::5, 28 ms
    Reply to request 3 received from FC00:1:0:58::5, 56 ms
    Reply to request 4 received from FC00:1:0:58::5, 20 ms

     

     

     

  • Thanks man, spent some hourson this just to figure out the crappy ACL was blocking me.

     

    It works and you do need to set the static rp-mapping in the RP :)

     

    Susana.

  • What leminh said appears to work for me. I needed to add the following route to get R4 to show the embeded RP and R1 to ping it

     

    ipv6 route 2001:CC1E::6/128 Serial0/1 multicast

  • I think the prefix length should be /64 instead of /128, as (0x40) = 64 decimal.

    The IPv6 address that should be assigned to Loopback300 is 2001:CC1E::6/64

  • I know this is an old post, but the static route suggested by leminh fixed this for me.

  • Actually static RP configuration on R6 is really required, otherwise if you do debug on R6 you will see this:

    *Mar  1 00:29:33.675: IPv6 PIM: J/P entry: Join root: 2001:CC1E::6 group: FF76:640:2001:CC1E::8 flags:  RPT WC S

    *Mar  1 00:29:33.683: IPv6 PIM: (*,FF76:640:2001:CC1E::8) J/P message from FE80::C603:CFF:FE74:1 with invalid RP 2001:CC1E::6

    *Mar  1 00:29:33.687: IPv6 PIM: J/P entry: Prune root: 2001:1:0:146:C600:CFF:FE74:0 group: FF76:640:2001:CC1E::8 flags:  RPT S

    What debug commands are you running to see that output?

Sign In or Register to comment.