RE: IPX V1-lab10 (MSDP)

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
Received on Tue Jun 29 2010 - 16:54:27 ART