From: Schulz, Dave (DSchulz@dpsciences.com)
Date: Wed Mar 22 2006 - 10:47:57 GMT-3
Sorry, that is all the details that I have on this one. The only thing
that I came up with is to enable pim on the interface that is facing the
R4 router. This will at least allow you to ping the multicast group
from the R4 router. You cannot ping the multicast group without this.
Dave Schulz,
Email: dschulz@dpsciences.com <mailto:dschulz@dpsciences.com%20>
________________________________
From: Petr Lapukhov [mailto:petrsoft@gmail.com]
Sent: Wednesday, March 22, 2006 1:47 AM
To: Schulz, Dave
Cc: ccielab@groupstudy.com
Subject: Re: Multicast lab question
Hello Dave,
Interesting question, can you provide more scenario detail?
I thought of MVR at first , but configuring just R2 prohibts
this idea.. Second idea was stub multicats routing, but
that requires some more configuration, above just touching R2..
TIA
Petr
2006/3/22, Schulz, Dave <DSchulz@dpsciences.com>:
Group -
If I have a multicast group that is running in sparse-mode with 3
routers and a static RP.....R1, R2 and R3. I have a loopback on R3 that
has a igmp join to 225.5.5.5. And, everything is working good and can
ping the group from all routers, and everyone is happy. However, the
next requirement is to have a router R4 attached to R2 that does not
have multicast enabled, but allowing users on VLAN70 to reach this
multicast group. And, you have to configure this on R2, not R4. Any
thoughts?
R1---------------R2(RP)------------------R3
| s0
\
R4........VLAN70
Dave Schulz,
Email: dschulz@dpsciences.com <mailto:dschulz@dpsciences.com >
This archive was generated by hypermail 2.1.4 : Sat Apr 01 2006 - 10:07:39 GMT-3