From: John (jgarrison1@austin.rr.com)
Date: Sat May 10 2008 - 18:23:59 ART
You said it.
I don't know if it's the best way but.
access-list 1 permit 239.2.2.1
access-list 1 deny 224.0.0.0 15.255.255.255
intyx/x ip multicast boundary 1
The router on the client side will not recieve any RP information. I guess
it depends on your network on what else you want to permit through the
boundary
Original
Message -----
From: "Radioactive Frog" <pbhatkoti@gmail.com>
To: "Cisco certification" <ccielab@groupstudy.com>
Sent: Saturday, May 10, 2008 9:49 AM
Subject: IP multicast boundary
> Hi guys,
> I have the following scenario:
>
> Mcast
> Client----Switch---|router|-----(*WAN*)----|router|-----|switch|------Server
> --------Remote site---------------- -----------central
> site-------------------
>
> server multicast address is 239.2.2.1, client at the remote site gets
> Mcast
> stream from Server at central site.
>
> I have 2 questions:
>
> 1. What is the best way to prevent multicast traffic geting in the WAN
> cloud?
> Ip multicast ACL?
>
> 2. How can we minimize the broadcast between route1 and router2?
> Is there anyway similar to router-reflictor client concept? HQ server
> source and destination is the remote site clients. I want only 1 stream
> goes
> through the WAN and that stream will be broadcasted to many clients in the
> remote site.
> ONE to Many
>
>
> Cheers
> frog
>
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Mon Jun 02 2008 - 06:59:16 ART