Muliti Cast ...Auto RP


R7 ==> MA
R3 ==> C-RP

##############TOPOLOGY################


 R2---------R3
 |               |
 |               |
R7----------R4

All interface including Loopback 0 are enabled with PIM SPARSE mode.

R7#ip pim send-rp-discovery Loopback0 scope 255

 

R3#ip pim send-rp-announce Loopback0 scope 255 interval 2

 

 

R3 is sending the Announcement

R3#
*Feb 12 10:43:44.739: Auto-RP(0): Build RP-Announce for 9.9.0.3, PIMv2/v1, ttl 20, ht 7
*Feb 12 10:43:44.743: Auto-RP(0): Build announce entry for (224.0.0.0/4)
*Feb 12 10:43:44.747: Auto-RP(0): Send RP-Announce packet of length 48 on GigabitEthernet0/0.23
*Feb 12 10:43:44.751: Auto-RP(0): Send RP-Announce packet of length 48 on GigabitEthernet0/0.34
*Feb 12 10:43:44.755: Auto-RP(0): Send RP-Announce packet of length 48 on GigabitEthernet0/0.35
*Feb 12 10:43:44.759: Auto-RP(0): Send RP-Announce packet of length 48 on Loopback0(*)

 

However R7 is not getting the annoucements from R3

 

Mtrace from R7 to R3 loopback0 9.9.0.3

 

R7#mtrace 9.9.0.3
Type escape sequence to abort.
Mtrace from 9.9.0.3 to 9.9.47.7 via RPF
From source (?) to destination (?)
Querying full reverse path...
 0  9.9.47.7
-1  9.9.47.7 None  [9.9.0.3/32]
-2  9.9.47.4 None  [9.9.0.3/32]
-3  9.9.34.3 PIM  [9.9.0.3/32]
-4  9.9.0.3

 

On R7 all interface enabled with PIM and can see the PIM neighbourship in between R7-R2 and R7-R4

R7#sh ip pim interface

Address          Interface                Ver/   Nbr    Query  DR     DR
                                          Mode   Count  Intvl  Prior
9.9.0.7          Loopback0                v2/S   0      30     1      9.9.0.7
9.9.27.7         Ethernet1/0              v2/S   1      30     1      9.9.27.7
9.9.47.7         Ethernet1/1              v2/S   1      30     1      9.9.47.7

R7#sh ip pim neighbor

Address                                                            Prio/Mode
9.9.27.2          Ethernet1/0              00:06:01/00:01:35 v2    1 / S P G
9.9.47.4          Ethernet1/1              00:06:00/00:01:39 v2    1 / S P G

 

Why R7 is not receving the RP announcement from C-RP (R3) ?

 


########################

R7#sh ip mroute


(*, 224.0.1.39), 00:08:24/00:02:53, RP 0.0.0.0, flags: DCL
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    Ethernet1/1, Forward/Sparse, 00:08:21/00:02:53
    Ethernet1/0, Forward/Sparse, 00:08:21/00:02:18
    Loopback0, Forward/Sparse, 00:08:21/00:02:39

(*, 224.0.1.40), 00:08:35/00:02:48, RP 0.0.0.0, flags: DCL
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    Loopback0, Forward/Sparse, 00:08:21/00:02:48

########

R2#sh ip mroute

(*, 224.0.1.39), 01:48:34/stopped, RP 0.0.0.0, flags: DP
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list: Null

(9.9.0.3, 224.0.1.39), 00:56:21/00:02:18, flags: PT
  Incoming interface: GigabitEthernet0/0.23, RPF nbr 9.9.23.3
  Outgoing interface list: Null

(*, 224.0.1.40), 01:49:36/00:02:49, RP 0.0.0.0, flags: DCL
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    Loopback0, Forward/Sparse, 01:49:36/00:02:49

############

R3#sh ip mroute


(*, 224.0.1.39), 00:51:46/stopped, RP 0.0.0.0, flags: DP
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list: Null

(9.9.0.3, 224.0.1.39), 00:51:46/00:02:58, flags: PT
  Incoming interface: Loopback0, RPF nbr 0.0.0.0
  Outgoing interface list: Null

(*, 224.0.1.40), 00:52:32/00:02:10, RP 0.0.0.0, flags: DCL
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    Loopback0, Forward/Sparse, 00:52:32/00:02:10

 

Please assist.

/Ganpat

 

 

Comments

  • The middle hop routers need to flood .39 an .40 as dense mode Gs and right now they are not. 

    Common solutions are sparse-dense mode with no DM fallback or just using autorp listener everywhere. 

    HTH

    Nic

     

  • Common solutions are sparse-dense mode with no DM fallback or just using autorp listener everywhere. 

    Alternatively you could also use BSR which propagates RP information via PIM and of course is standards based.  No special configuration is required to get these messages transported across the network.  Finally I guess you have the belt and braces method with static RP assignments.

Sign In or Register to comment.