From: Gregory Gombas (ggombas@gmail.com)
Date: Tue Oct 23 2007 - 10:53:34 ART
Could it be R1 is not recieving the mapping messages or getting RPF
failure for the mapping messages?
Can you do debug ip mpacket and debug ip mrouting rpf events to see if
that is the case?
On 10/23/07, George Roman <georgeroman@gmail.com> wrote:
> Hi, I have this multicast problem and i tried to solve it for 2 hours now
> without any success:
>
> here is the diagram
>
> R4-------FRSW-------R1------R3-----R2
> |
> |
> R5------- |
>
>
> R3 should be the mapping agent and R1 and R2 are the RPs
> I am using pim sparse-mode associated with command "ip pim autorp listener"
> now, for R2 everything seem to be fine, but for R1 things get strange.
> because it seem to refuse to be the RP for any group:
> Here is the config on R1:
>
> ip pim autorp listener
> ip pim spt-threshold 128
> ip pim send-rp-announce Loopback0 scope 15 group-list EVEN_NR
>
> ip access-list standard EVEN_NR
> permit 224.0.0.0 0.255.255.255
> permit 226.0.0.0 0.255.255.255
> permit 228.0.0.0 0.255.255.255
> ..
>
>
> interface Serial0/2/0
> ip address 174.1.13.1 255.255.255.0
> ip pim sparse-mode
> clock rate 128000
> !
>
> Here is the config on the maping agent:
>
> interface Serial0/3/0
> ip address 174.1.13.3 255.255.255.0
> ip pim sparse-mode
> !
>
> ip pim autorp listener
> ip pim spt-threshold 128
> ip pim send-rp-discovery Loopback0 scope 14
> !
>
> Here is what the debug ip pim auto-rp says on the mapping agent.:
>
>
> *Oct 23 12:36:53.515: Auto-RP(0): Received RP-announce, from 150.1.1.1,
> RP_cnt 1, ht 181
> *Oct 23 12:36:53.515: Auto-RP(0): Update (224.0.0.0/8, RP:150.1.1.1), PIMv2
> v1
> *Oct 23 12:36:53.515: Auto-RP(0): Update (226.0.0.0/8, RP:150.1.1.1), PIMv2
> v1
> *Oct 23 12:36:53.515: Auto-RP(0): Update (228.0.0.0/8, RP:150.1.1.1), PIMv2
> v1
> *Oct 23 12:36:53.515: Auto-RP(0): Update (230.0.0.0/8, RP:150.1.1.1), PIMv2
> v1
> *Oct 23 12:36:53.515: Auto-RP(0): Update (232.0.0.0/8, RP:150.1.1.1), PIMv2
> v1
> *Oct 23 12:36:53.515: Auto-RP(0): Update (236.0.0.0/8, RP:150.1.1.1), PIMv2
> v1
> *Oct 23 12:36:53.515: Auto-RP(0): Update (238.0.0.0/8, RP:150.1.1.1), PIMv2
> v1
> *Oct 23 12:37:25.555: Auto-RP(0): Received RP-announce, from 150.1.2.2,
> RP_cnt 1, ht 181
> *Oct 23 12:37:25.555: Auto-RP(0): Update (225.0.0.0/8, RP:150.1.2.2), PIMv2
> v1
> *Oct 23 12:37:25.555: Auto-RP(0): Update (227.0.0.0/8, RP:150.1.2.2), PIMv2
> v1
> *Oct 23 12:37:25.555: Auto-RP(0): Update (229.0.0.0/8, RP:150.1.2.2), PIMv2
> v1
> *Oct 23 12:37:25.555: Auto-RP(0): Update (231.0.0.0/8, RP:150.1.2.2), PIMv2
> v1
> *Oct 23 12:37:25.555: Auto-RP(0): Received RP-announce, from 150.1.2.2,
> RP_cnt 1, ht 181
> *Oct 23 12:37:25.555: Auto-RP(0): Update (225.0.0.0/8, RP:150.1.2.2), PIMv2
> v1
> *Oct 23 12:37:25.555: Auto-RP(0): Update (227.0.0.0/8, RP:150.1.2.2), PIMv2
> v1
> *Oct 23 12:37:25.559: Auto-RP(0): Update (229.0.0.0/8, RP:150.1.2.2), PIMv2
> v1
> *Oct 23 12:37:25.559: Auto-RP(0): Update (231.0.0.0/8, RP:150.1.2.2), PIMv2
> v1
> *Oct 23 12:37:46.847: Auto-RP(0): Build RP-Discovery packet
> *Oct 23 12:37:46.847: Auto-RP: Build mapping (224.0.0.0/8, RP:150.1.1.1),
> PIMv2 v1,
> *Oct 23 12:37:46.847: Auto-RP: Build mapping (225.0.0.0/8, RP:150.1.2.2),
> PIMv2 v1.
> *Oct 23 12:37:46.847: Auto-RP: Build mapping (226.0.0.0/8, RP:150.1.1.1),
> PIMv2 v1.
> *Oct 23 12:37:46.847: Auto-RP: Build mapping (227.0.0.0/8, RP:150.1.2.2),
> PIMv2 v1.
> *Oct 23 12:37:46.847: Auto-RP: Build mapping (228.0.0.0/8, RP:150.1.1.1),
> PIMv2 v1.
> *Oct 23 12:37:46.847: Auto-RP: Build mapping (229.0.0.0/8, RP:150.1.2.2),
> PIMv2 v1.
> *Oct 23 12:37:46.847: Auto-RP: Build mapping (230.0.0.0/8, RP:150.1.1.1),
> PIMv2 v1.
> *Oct 23 12:37:46.847: Auto-RP: Build mapping (231.0.0.0/8, RP:150.1.2.2),
> PIMv2 v1.
> *Oct 23 12:37:46.847: Auto-RP: Build mapping (232.0.0.0/8, RP:150.1.1.1),
> PIMv2 v1.
> *Oct 23 12:37:46.847: Auto-RP: Build mapping (236.0.0.0/8, RP:150.1.1.1),
> PIMv2 v1.
> *Oct 23 12:37:46.847: Auto-RP: Build mapping (238.0.0.0/8, RP:150.1.1.1), P
>
> but when i try the command "sh ip pim rp mapping"on any router behind R1
> and R1 itself
> there is no mapping. if i try to join a group (224.4.4.4) on R4 and then
> ping that address from my network i get this message on R1:
>
> *Oct 23 10:50:19.695: %PIM-1-INVALID_RP_REG: Received Register from router
> 174.1.13.3 for group 224.4.4.4, 150.1.1.1 not willing to be RP
>
> Here is the debug on R1:
> *Oct 23 11:53:28.751: Auto-RP(0): Build RP-Announce for 150.1.1.1, PIMv2/v1,
> ttl 15, ht 181
> *Oct 23 11:53:28.751: Auto-RP(0): Build announce entry for (224.0.0.0/8)
> *Oct 23 11:53:28.751: Auto-RP(0): Build announce entry for (226.0.0.0/8)
> *Oct 23 11:53:28.751: Auto-RP(0): Build announce entry for (228.0.0.0/8)
> *Oct 23 11:53:28.751: Auto-RP(0): Build announce entry for (230.0.0.0/8)
> *Oct 23 11:53:28.751: Auto-RP(0): Build announce entry for (232.0.0.0/8)
> *Oct 23 11:53:28.751: Auto-RP(0): Build announce entry for (236.0.0.0/8)
> *Oct 23 11:53:28.751: Auto-RP(0): Build announce entry for (238.0.0.0/8)
> R1#
> *Oct 23 11:53:28.751: Auto-RP(0): Send RP-Announce packet on
> FastEthernet0/0.1001
> *Oct 23 11:53:28.751: Auto-RP(0): Send RP-Announce packet on Serial0/0/0
> *Oct 23 11:53:28.751: Auto-RP(0): Send RP-Announce packet on Serial0/2/0
> *Oct 23 11:53:28.751: Auto-RP: Send RP-Announce packet on Loopback0
>
>
> So my question is: is there any issue with this ip pim autorp listener
> command?
>
> I tried to reload router R1 and after that i see that things are working for
> 2-3 minutes or so, after that the RP mapping disappear on R1 (and on all
> routers behind R1)
> When this happens, these are the messages i get on R1:
> *Oct 23 10:30:24.699: PIM(0): Received v2 Join/Prune on Serial0/0/0 from
> 174.1.145.4, to us
> *Oct 23 10:30:24.703: PIM(0): Join-list: (*, 224.4.4.4), RPT-bit set, WC-bit
> set, S-bit set
> *Oct 23 10:30:24.703: PIM(0): Update Serial0/0/0/174.1.145.4 to (*,
> 224.4.4.4), Forward state, by PIM *G Join
> *Oct 23 10:30:25.591: PIM(0): Building Periodic (*,G) Join / (S,G,RP-bit)
> Prune message for 224.4.4.4
> R1#
> *Oct 23 10:30:26.591: PIM(0): Building Graft message for 224.0.1.40,
> Serial0/2/0: no entries
> *Oct 23 10:30:26.591: PIM(0): Building Graft message for 224.0.1.40,
> Serial0/0/0: no entries
> *Oct 23 10:30:26.591: PIM(0): Building Graft message for 224.0.1.40,
> Loopback0: no entries
> R1#
> *Oct 23 10:30:28.567: PIM(0): Check RP 0.0.0.0 into the (*, 224.4.4.4) entry
> *Oct 23 10:30:28.595: PIM(0): Building Graft message for 224.0.1.40,
> Serial0/2/0: no entries
> *Oct 23 10:30:28.595: PIM(0): Building Graft message for 224.0.1.40,
> Serial0/0/0: no entries
> *Oct 23 10:30:28.595: PIM(0): Building Graft message for 224.0.1.40,
> Loopback0: no entries
> *Oct 23 10:30:29.567: PIM(0): Check RP 0.0.0.0 into the (*, 224.4.4.4) entry
> R1#
> *Oct 23 10:30:29.595: PIM(0): Building Graft message for 224.0.1.40,
> Serial0/2/0: no entries
> *Oct 23 10:30:29.595: PIM(0): Building Graft message for 224.0.1.40,
> Serial0/0/0: no entries
> *Oct 23 10:30:29.595: PIM(0): Building Graft message for 224.0.1.40,
> Loopback0: no entries
>
>
> To me the configuratuion looks good, do you think that it this is an issue
> with it?
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Fri Nov 16 2007 - 13:11:18 ART