Re: IPX V1-lab10 (MSDP)

Hi

Thanks I get that, but why would sparse vs sparse-dense make a difference on
a loopback interface.
It is not like traffic leaves that interface.
My understanding is that Sparse/dense mode on a interface determines how
traffic leaves that interface.
So then surely Spare-mode under the loopback should be sufficient?

What makes this confusing, is that routers in the same AS could get to R5
multicast group, regardless what the loopback used.
And so could R6, the Peering MSDP peer and RP in a different AS, yet,
routers behind that (R9) could not.

On Wed, Jun 30, 2010 at 9:24 PM, Tyson Scott <tscott_at_ipexpert.com> wrote:

> It would also work if you configured sparse-dense-mode or configured
> auto-rp on the router.
>
>
>
> Regards,
>
>
>
> Tyson Scott - CCIE #13513 R&S, Security, and SP
>
> Managing Partner / Sr. Instructor - IPexpert, Inc.
>
> Mailto: tscott_at_ipexpert.com
>
>
>
> *From:* IOS GIMP [mailto:isaydoodalot_at_gmail.com]
> *Sent:* Wednesday, June 30, 2010 1:57 PM
> *To:* Tyson Scott
> *Cc:* ccielab_at_groupstudy.com
> *Subject:* Re: IPX V1-lab10 (MSDP)
>
>
>
> I found the problem.
>
> AS1 runs auto-RP, and R5 loopback was in sparse mode appose to sparse-dense
> like the rest of the interfaces in AS1.
> Once I changed that to sparse-dense (since AS1 is not configured to use
> auto-rp listener), R9 could ping the Multicast group on R5.
>
> But I dont understand why this broke R9's connectivity which is in a
> different AS.
> If anybody could suggest a reason for this, just for me to understand
> multicast a bit better I would really appreciate it.
>
> Regards
> John
>
> On Tue, Jun 29, 2010 at 11:11 PM, IOS GIMP <isaydoodalot_at_gmail.com>
> wrote:
>
> Hi Tyson
>
> Thanks for the quick response.
> R9 can reach R5 via unicast, no problem.
>
> Rack6R9#ping 200.0.0.5
> Sending 5, 100-byte ICMP Echos to 200.0.0.5, timeout is 2 seconds:
> !!!!!
> Success rate is 100 percent (5/5), round-trip min/avg/max = 4/27/60 ms
>
> BUT, R9 doesn't have a route to R5 group
> Rack6R9#sh ip mroute 225.0.0.55
> Group 225.0.0.55 not found
>
> Am I correct in saying that R6 is then not advertising this group to R9.
> Any idea why that is.
>
> Rack6R9#sh ip pim rp mapp
> PIM Group-to-RP Mappings
>
> Group(s) 224.0.0.0/4
> RP 150.50.69.1 (?), v2
> Info source: 150.50.69.1 (?), via bootstrap, priority 0, holdtime 150
> Uptime: 02:17:20, expires: 00:02:18
>
> R6 has another group (226.0.0.66) that R9 can ping.
>
> Regards
>
>
>
>
> On Tue, Jun 29, 2010 at 10:54 PM, Tyson Scott <tscott_at_ipexpert.com>
> wrote:
>
> Does R9 know how to get to the source address on R5 for this solution.
>
> Regards,
>
> Tyson Scott - CCIE #13513 R&S, Security, and SP
> Managing Partner / Sr. Instructor - IPexpert, Inc.
> Mailto: tscott_at_ipexpert.com
>
>
>
>
> -----Original Message-----
> From: nobody_at_groupstudy.com [mailto:nobody_at_groupstudy.com] On Behalf Of
> IOS
> GIMP
> Sent: Tuesday, June 29, 2010 4:38 PM
> To: ccielab_at_groupstudy.com
> Subject: IPX V1-lab10 (MSDP)
>
> hello
>
> I hope someone can point me in the right direction.
> I have done IP-expert volume 1 lab 10 on multicast.
>
> But there one thing I cant get working.
>
> The topology
>
> R1
> |
> R2-------R6------R9
> |
> R5
> (225.0.0.55)
>
> R1, R2, R5 is in AS1 and R6 and R9 is in AS2
> AS1 run auto-rp and AS2 runs BSR with R2 and R6 the respective RP/MA and
> RP/BSR.
> R2 and R6 are MSDP peers and Multicast-BGP with connected interfaces
> redistribute under ipv4 multicast.
>
> Every router (including R6) can ping the IGMP join interface on R5 fa0/0
> (225.0.0.55) except R9.
> There is no RPF failures, as per the debugs. All unicast routing seems to
> be
> inplace.
> The traffic from R9 is getting to R6 but not to R2 as per the 'debug ip
> mpacket'
>
> My question is around the multicast table on R6:
>
> Rack6R6#sh ip mroute 225.0.0.55
> 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
> Outgoing interface flags: H - Hardware switched, A - Assert winner
> Timers: Uptime/Expires
> Interface state: Interface, Next-Hop or VCD, State/Mode
>
> (*, 225.0.0.55), 00:01:45/stopped, RP 150.50.69.1, flags: SP
> Incoming interface: Null, RPF nbr 0.0.0.0
> Outgoing interface list: Null
>
> (200.0.0.6, 225.0.0.55), 00:00:12/00:02:53, flags: PTA
> Incoming interface: Loopback0, RPF nbr 0.0.0.0
> Outgoing interface list: Null
>
> (200.0.0.9, 225.0.0.55), 00:01:45/00:01:15, flags: PT
> Incoming interface: Multilink1, RPF nbr 150.50.69.2
> Outgoing interface list: Null
>
>
> Notice that the (s,g) entry for R9 is missing the 'A - Candidate for MSDP
> Advertisement'
> But for R6 it is not.
>
> I cant seem to figure why that is or what could prevent R6 from advertising
> R9 as a source to R2.
>
> Any help would be appreciated.
>
> Regards
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html

Blogs and organic groups at http://www.ccie.net
Received on Wed Jun 30 2010 - 23:09:15 ART