Multicast Nightmares (Long, ish....)

From: steven.j.nelson@xxxxxx
Date: Wed Apr 10 2002 - 10:03:45 GMT-3


   
All,

I have the following

 TR----R1----(Frame)----R2-----(Frame)------R3-----TR

I also have

1. DLSw between R1 and R3
2. SRB on TR (R1) and (R2)
3. OSPF providing IGP throughout.

I am using PIM sparse-dense mode, R1 is Auto RP (for 224.2.2.1) and mapping
agent, TR on R1 has joined groups 224.2.2.1 and 224.3.1.1, IP PIM
sparse-dense-mode is configured on all routers that need to route multicast
traffic, and all relevant interfaces.

R2 sees rp (auto) fine and can ping both addresses (224.2.2.1 and
224.3.1.1), however R3 cannot see the groups or ping the addresses, it can
however see the RP. I did have strange error that said INVALID_RP_Join
Message on R1 initially even though I didn't have any ip pim accept
parameters on it, after a reboot it dissapeared.

I have checked the PIM neighbours and the Mroute tables all looks fine, RPF
also looks good. I have seen the docs on CCO here we go :-

I am using 12.1.(13) Ent on all boxes.

Question :

Do I need to join the groups 224.2.2.1 and 224.3.1.1 on TR on R3 before I
can ping, I would have thought that as I could see the RP from R3 and that
there are members of the group at R1 (TR) then I should have received a
reply from that interface.

Any help would be good.

Thanks

Steve

Steve Nelson
Customer Engineer
BT Ignite- National Solutions
T: +44 (0)1422 338881 M: +44 (0)7811 944172
e-mail: steven.j.nelson@bt.com
pp HW A170, PO Box 200(HOM-NZ), London, N18 1ZF
> British Telecommunications plc
> Registered office: 81 Newgate Street London EC1A 7AJ
> Registered in England no. 1800000.
> This electronic message contains information from British
Telecommunications plc which may be privileged or confidential. The
information is intended to be for the use of the individual(s) or entity
named above. If you are not the intended recipient be aware that any
disclosure, copying, distribution or use of the contents of this information
is prohibited. If you have received this electronic message in error, please
notify us by telephone or email (to the numbers or address above)
immediately.



This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:58:03 GMT-3