8.16 Filtering Auto-RP Messages - No rp maps at all?

Hi,

I doing this lab, and I dont have anyting on any of my devices when doing a "show ip pim rp map".

I been through the configuration a couple of times, and cant see that I miss anything.

I found a thread that says the scope should be 3 and not 2, but even if I set it to 10 I dont get anything.

 

How do I troubleshoot on this?

 

I have tried to clear rp mappings and mroute table with no luck.

I do have entires in "show ip mroute"

Comments

  • I found that it goes wrong when I do the command:

    #no ip pim send-rp-discovery loopback 0 scope 10

    On router R5 in 8.15

    If I don't do this command I do have rp mappings.

     

     

  • JoeMJoeM ✭✭✭

    Hi Rofe,

    In the other exercise, the RP was removed from R5 and placed on R1.  Then on R3, there was an mroute made specifically for the purpose of  "R3 hearing auto-rp discoveries from R1".

     

  • Hi JoeM,

    Yes, and it's all there.

    But as soon as I remove the:

    ip pim send-rp-discovery Loopback0 scope 10

    On router R5, no router have any output in the "show ip pim rp map"; so the problem might be in the 8.15 and not in 8.16.

    Anyway I should still get the output descibed in the solutioon.

     

    - Ronni

  • JoeMJoeM ✭✭✭

    I have done this lab a few times, and I do not have any notes about any problems with this.

    What I am wondering is how you are having a problem in this task, without seeing a problem in the previous task (8.15).

     

    Let's concentrate on R3:    debug ip pim auto-rp

    Make sure that R1 is the RP mapping agent (discovery) with a higher scope.

    Also, there is a tunnel between R1 and R3.   Is this setup and working as shown in 8.15 ?   show ip pim neighbor

     

  • Youre may be right, that the problem is introduced in task 8.15.

     

    Below is the output from R1 and R3.

     

     

    R1:

    Rack1R1#sh ip pim nei

    PIM Neighbor Table

    Mode: B - Bidir Capable, DR - Designated Router, N - Default DR Priority,

          S - State Refresh Capable

    Neighbor          Interface                Uptime/Expires    Ver   DR

    Address                                                            Prio/Mode

    150.1.9.9         Tunnel0                  06:16:00/00:01:36 v2    1 / S P

    150.1.3.3         Tunnel1                  06:16:51/00:01:20 v2    1 / S P

    155.1.146.6       FastEthernet0/0          06:15:46/00:01:37 v2    1 / S P

    155.1.146.4       FastEthernet0/0          06:17:14/00:01:35 v2    1 / S P

    155.1.0.5         Serial0/2/0.1            06:15:52/00:01:30 v2    1 / S P

    -------------------------

    Rack1R1#sh ip int br

    Interface                  IP-Address      OK? Method Status                Protocol

    FastEthernet0/0            155.1.146.1     YES NVRAM  up                    up      

    FastEthernet0/1            unassigned      YES NVRAM  administratively down down    

    Serial0/1/0                155.1.13.1      YES NVRAM  up                    up      

    Serial0/2/0                unassigned      YES NVRAM  up                    up      

    Serial0/2/0.1              155.1.0.1       YES NVRAM  up                    up      

    Loopback0                  150.1.1.1       YES NVRAM  up                    up      

    Tunnel0                    150.1.1.1       YES TFTP   up                    up      

    Tunnel1                    150.1.1.1       YES TFTP   up                    up 

    -----------------------------------------

    Rack1R1#sh ip pim int

     

    Address          Interface                Ver/   Nbr    Query  DR     DR

                                              Mode   Count  Intvl  Prior

    150.1.1.1        Loopback0                v2/S   0      30     1      150.1.1.1

    150.1.1.1        Tunnel0                  v2/SD  1      30     1      0.0.0.0

    150.1.1.1        Tunnel1                  v2/S   1      30     1      0.0.0.0

    155.1.146.1      FastEthernet0/0          v2/S   2      30     100    155.1.146.1

    155.1.0.1        Serial0/2/0.1            v2/S   1      30     1      0.0.0.0

    -----------------------------------

     

     

    R3:

    Rack1R3#sh ip pim nei

    PIM Neighbor Table

    Mode: B - Bidir Capable, DR - Designated Router, N - Default DR Priority,

          S - State Refresh Capable

    Neighbor          Interface                Uptime/Expires    Ver   DR

    Address                                                            Prio/Mode

    150.1.1.1         Tunnel1                  06:18:05/00:01:16 v2    1 / S P

    155.1.0.5         Serial0/0/0.1            06:17:10/00:01:42 v2    1 / S P

    -------------------------

    Rack1R3#sh ip int br

    Interface                  IP-Address      OK? Method Status                Protocol

    FastEthernet0/0            155.1.37.3      YES NVRAM  up                    up      

    FastEthernet0/1            unassigned      YES NVRAM  administratively down down    

    Serial0/0/0                unassigned      YES NVRAM  up                    up      

    Serial0/0/0.1              155.1.0.3       YES NVRAM  up                    up      

    Serial0/1/0                unassigned      YES NVRAM  administratively down down    

    Serial0/2/0                155.1.13.3      YES NVRAM  up                    up      

    Serial0/3/0                155.1.23.3      YES NVRAM  up                    up      

    Loopback0                  150.1.3.3       YES NVRAM  up                    up      

    Tunnel1                    150.1.3.3       YES TFTP   up                    up  

    --------------------------

    Rack1R3#sh ip pim int

     

    Address          Interface                Ver/   Nbr    Query  DR     DR

                                              Mode   Count  Intvl  Prior

    150.1.3.3        Loopback0                v2/SD  0      30     1      150.1.3.3

    150.1.3.3        Tunnel1                  v2/S   1      30     1      0.0.0.0

    155.1.0.3        Serial0/0/0.1            v2/S   1      30     1      0.0.0.0

     

     

  • debug ip pim auto-rp

    R3: no output

     

    R1:

    Rack1R1#

    *May  7 16:46:39.926: Auto-RP(0): Build RP-Discovery packet

    *May  7 16:46:39.926: Auto-RP: no RP periodic mappings to send

    *May  7 16:47:38.926: Auto-RP(0): Build RP-Discovery packet

    *May  7 16:47:38.926: Auto-RP: no RP periodic mappings to send

  • JoeMJoeM ✭✭✭

    Rack1R1#

    *May  7 16:46:39.926: Auto-RP(0): Build RP-Discovery packet

    *May  7 16:46:39.926: Auto-RP: no RP periodic mappings to send

    *May  7 16:47:38.926: Auto-RP(0): Build RP-Discovery packet

    *May  7 16:47:38.926: Auto-RP: no RP periodic mappings to send

    So, it seems that R1 is not sending anything.

    Is R1 receiving the RP Group "announcements" from sw2/sw4.  

                             show ip mroute 224.0.1.39

                             show ip pim rp map 

  • Doing "debug ip mpacket" on R1:

    *May  7 17:16:48.826: IP(0): s=150.1.8.8 (FastEthernet0/0) d=224.0.1.39 id=27366, ttl=7, prot=17, len=74(60), not RPF interface

    *May  7 17:16:49.846: IP(0): s=150.1.10.10 (FastEthernet0/0) d=224.0.1.39 id=23567, ttl=6, prot=17, len=74(60), not RPF interface

    If I shutdown the serial connection between R4 and R5 I get the same error, but then it's just coming from tunnel1 and not fa0/0.

    Rack1R1#sh ip mroute 

    IP Multicast Routing Table

    Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,

           L - Local, P - Pruned, R - RP-bit set, F - Register flag,

           T - SPT-bit set, J - Join SPT, M - MSDP created entry,

           X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,

           U - URD, I - Received Source Specific Host Report,

           Z - Multicast Tunnel, z - MDT-data group sender,

           Y - Joined MDT-data group, y - Sending to MDT-data group,

           V - RD & Vector, v - Vector

    Outgoing interface flags: H - Hardware switched, A - Assert winner

     Timers: Uptime/Expires

     Interface state: Interface, Next-Hop or VCD, State/Mode

     

    (*, 224.110.110.110), 00:04:32/00:01:33, RP 0.0.0.0, flags: D

      Incoming interface: Null, RPF nbr 0.0.0.0

      Outgoing interface list:

        Tunnel0, Forward/Sparse-Dense, 00:04:32/00:00:00

     

    (*, 239.6.6.6), 02:49:46/00:02:18, RP 0.0.0.0, flags: DC

      Incoming interface: Null, RPF nbr 0.0.0.0

      Outgoing interface list:

        FastEthernet0/0, Forward/Sparse, 02:49:46/00:02:18

        Tunnel0, Forward/Sparse-Dense, 02:49:46/00:00:00

     

    (*, 224.0.1.39), 06:55:35/stopped, RP 0.0.0.0, flags: DCL

      Incoming interface: Null, RPF nbr 0.0.0.0

      Outgoing interface list:

        Serial0/2/0.1, Forward/Sparse, 06:53:45/00:00:00

        Tunnel0, Forward/Sparse-Dense, 06:53:55/00:00:00

        Tunnel1, Forward/Sparse, 06:54:45/00:00:00

        Loopback0, Forward/Sparse, 06:55:35/00:00:00

        FastEthernet0/0, Forward/Sparse, 06:55:35/00:00:00

     

    (150.1.10.10, 224.0.1.39), 00:02:35/00:00:24, flags: L

      Incoming interface: Serial0/2/0.1, RPF nbr 155.1.0.5

      Outgoing interface list:

        FastEthernet0/0, Forward/Sparse, 00:02:35/00:00:00

        Loopback0, Forward/Sparse, 00:02:35/00:00:00

        Tunnel1, Forward/Sparse, 00:02:35/00:00:00

        Tunnel0, Forward/Sparse-Dense, 00:02:35/00:00:00

     

    (150.1.8.8, 224.0.1.39), 00:02:36/00:00:23, flags: L

      Incoming interface: Serial0/2/0.1, RPF nbr 155.1.0.5

      Outgoing interface list:

        FastEthernet0/0, Forward/Sparse, 00:02:36/00:00:00

        Loopback0, Forward/Sparse, 00:02:36/00:00:00

        Tunnel1, Forward/Sparse, 00:02:36/00:00:00

        Tunnel0, Forward/Sparse-Dense, 00:02:36/00:00:00

     

    (*, 224.0.1.40), 06:55:36/00:02:49, RP 0.0.0.0, flags: DCL

      Incoming interface: Null, RPF nbr 0.0.0.0

      Outgoing interface list:

        Serial0/2/0.1, Forward/Sparse, 06:53:46/00:00:00

        Tunnel0, Forward/Sparse-Dense, 06:53:54/00:00:00

        Tunnel1, Forward/Sparse, 06:54:45/00:00:00

        FastEthernet0/0, Forward/Sparse, 06:55:08/00:00:00

        Loopback0, Forward/Sparse, 06:55:36/00:00:00

     

     

    Rack1R1#      sh ip pim rp map

    PIM Group-to-RP Mappings

    This system is an RP-mapping agent (Loopback0)

     

     

  • JoeMJoeM ✭✭✭

     

    Doing "debug ip mpacket" on R1:

    *May  7 17:16:48.826: IP(0): s=150.1.8.8 (FastEthernet0/0) d=224.0.1.39 id=27366, ttl=7, prot=17, len=74(60), not RPF interface


    *May  7 17:16:49.846: IP(0): s=150.1.10.10 (FastEthernet0/0) d=224.0.1.39 id=23567, ttl=6, prot=17, len=74(60), not RPF interface

    If I shutdown the serial connection between R4 and R5 I get the same error, but then it's just coming from tunnel1 and not fa0/0.

    I think that it is okay to have it rejected on f0/0, because we want to see it coming in from s0/2.0.1 (R5 neighbor frame).   The mroute table shows that it is coming in from R5. But let's be sure.

                   clear ip mroute *    (and watch the the debug command again)

     and for a sanity check

                  sh ip rpf 150.1.8.8    

                  sh ip rpf 150.1.10.10

     

    <snip>

    (*, 224.0.1.39), 06:55:35/stopped, RP 0.0.0.0, flags: DCL

      Incoming interface: Null, RPF nbr 0.0.0.0

      Outgoing interface list:

        Serial0/2/0.1, Forward/Sparse, 06:53:45/00:00:00

        Tunnel0, Forward/Sparse-Dense, 06:53:55/00:00:00

        Tunnel1, Forward/Sparse, 06:54:45/00:00:00

        Loopback0, Forward/Sparse, 06:55:35/00:00:00

        FastEthernet0/0, Forward/Sparse, 06:55:35/00:00:00

     

    (150.1.10.10, 224.0.1.39), 00:02:35/00:00:24, flags: L

      Incoming interface: Serial0/2/0.1, RPF nbr 155.1.0.5

      Outgoing interface list:

        FastEthernet0/0, Forward/Sparse, 00:02:35/00:00:00

        Loopback0, Forward/Sparse, 00:02:35/00:00:00

        Tunnel1, Forward/Sparse, 00:02:35/00:00:00

        Tunnel0, Forward/Sparse-Dense, 00:02:35/00:00:00

     

    (150.1.8.8, 224.0.1.39), 00:02:36/00:00:23, flags: L

      Incoming interface: Serial0/2/0.1, RPF nbr 155.1.0.5

      Outgoing interface list:

        FastEthernet0/0, Forward/Sparse, 00:02:36/00:00:00

        Loopback0, Forward/Sparse, 00:02:36/00:00:00

        Tunnel1, Forward/Sparse, 00:02:36/00:00:00

        Tunnel0, Forward/Sparse-Dense, 00:02:36/00:00:00

    <snip>

     

    Rack1R1#      sh ip pim rp map

    PIM Group-to-RP Mappings

    This system is an RP-mapping agent (Loopback0)

     

     

     

    But this is the problem.   Your RP's (sw2,sw4) are not getting their mappings to the RP Mapping Agent (r1).   So R1 cannot adverise the group mappings that it does not have.

     

    running an errand.  be right back.

     

     

     

  • Hi,

    Thank you very much for your help.

    I will have to go to bed now, I will be back tomorrow.

     

    The output below is made on R1:

     

     

    Rack1R1#clear ip mroute *

    Rack1R1#

    *May  7 19:08:33.941: IP(0): s=150.1.8.8 (FastEthernet0/0) d=224.0.1.39 id=34534, ttl=7, prot=17, len=74(60), not RPF interface

    Rack1R1#

    *May  7 19:08:35.509: IP(0): s=150.1.10.10 (FastEthernet0/0) d=224.0.1.39 id=29635, ttl=6, prot=17, len=74(60), not RPF interface

    Rack1R1#

    *May  7 19:08:37.925: Auto-RP(0): Build RP-Discovery packet

    *May  7 19:08:37.925: Auto-RP: no RP periodic mappings to send

    Rack1R1#sh ip rpf 150.1.8.8

    RPF information for ? (150.1.8.8)

      RPF interface: Serial0/2/0.1

      RPF neighbor: ? (155.1.0.5)

      RPF route/mask: 150.1.8.0/24

      RPF type: unicast (ospf 1)

      RPF recursion count: 0

      Doing distance-preferred lookups across tables

    Rack1R1#sh ip rpf 150.1.10.10

    RPF information for ? (150.1.10.10)

      RPF interface: Serial0/2/0.1

      RPF neighbor: ? (155.1.0.5)

      RPF route/mask: 150.1.10.0/24

      RPF type: unicast (ospf 1)

      RPF recursion count: 0

      Doing distance-preferred lookups across tables

     

     

     

  • JoeMJoeM ✭✭✭

    Rofe,

    Don't worry about that RPF failure on f0/0.  We want that to happen, because we need the connection via R5 (s0/2/0.1 in your setup).

    Are you using GNS?   There are lots of problems with multicast in GNS.

     

    While testing this in GNS, I was able to continually get the mapping to work on R1 -- but then it would disappear (expire).

    Finally, I got it working by applying this command to S0/0 of R5 (the hub).    NO ip mroute-cache

    Immediately, the RP's started updating the RP Agent (R1 from the R5 frame) on a regular basis.  This can be seen in the debug, as well as the expiration timers refreshing.     (the RPF failure on f0/0 will continue. not a problem).

  • Hi JoeM,

    No it's a physical lab, mostly 2801 and 2811, thats why the interfaces doesn't match some places.

    I need to move on, my first lab attempt is in june, and I still have some content to cover.

     

    So I will try reloading the initial configuration, and move through all the tasks with the soultions from the SG and see what happens.

     

    Thank you so much for your help! :-)

     

    - Ronni

  • It's the same. No changes.

    I reloaded the initial configurations and went through all SG, copied the solutions from all of them to notepad and then into the devices.

    Same problem.

     

    Do you know if I'm able to continue with the other tasks or if this have to work?

  • JoeMJoeM ✭✭✭

    Usually these tasks are dependent upon the previous tasks.  

    There is a lesson here, regarding the problem with R1 as the Mapping Agent, but I am not sure exactly what is happening.  

    I  have reviewed a couple of other threads, and it seems that many had this issue.   R1 sees the initial announcements,  but then prunes the group-mapping (expires).   This can be seen by clearing the mroute table on all devices -- which then repopulates R1's table again.     clear ip mroute *

     

    There is more than one post that says to use the same fix that I found to work.

                        R5 frame-relay:     no ip mroute-cache 

    Here is one of those posts:

    http://ieoc.com/forums/p/6439/111440.aspx#111440

  • Okey.

    I move on, and have issued the command on the FR-interface on R5; in case it should prevent some problems.

    I will return to this task, when I have time.

     

    - Ronni

Sign In or Register to comment.