From: Salau, Yemi (yemi.salau@siemens.com)
Date: Tue Jan 08 2008 - 09:29:25 ARST
From my own Multicast experience on slow bandwidth wan links, I will go
for David's Option 2
You don't want autorp in such a low bandwidth environment, because
you're bound to have one or two issues which will kick your multicasts
into dense mode (assuming you're using this as fall back, and also
assuming you have crap piece of hardware like we have here)
The Best practise is try not to send high contents streams over low
bandwidths, this is logical enuf isn't it? But if you must, then use
1. StaticRP
2. Localise RP operation, you can have one large single cluster of BSRs
anywhere on the network, but your RP positioning is crucial as you know.
You don't want to have an RP in Chicago sending a 10MB stream to Mumbai,
Johannesburg over a slow link. If Chicago has it's own RP and then
Mumbai its own, that means less or no multicast traffic over the slow
links.
3. Yea, the Multicast Boundary David was talking about - there are many
ways to do this, access-lists, igmp access-groups etc.
I only imagine you're talking about design, not support. If yes, you
might also want to consider multicast addressing plans and all that. You
know, same old stuff for voip numbering plans, ip addressing plans and
all stuffs.
The only restriction to this design though is that you'll need to have
your multicast sources as close to the RP as possible, so if you have RP
for say a particular segment behind your wan links, then you'll have to
implement multicast sources for each segment/region. Now, that can be
expensive but all depends on what you want.... But I can say what you
don't want is transmit/chock up your low bandwidth links.
Many Thanks
Yemi Salau
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
David Prall
Sent: Tuesday, January 08, 2008 2:26 AM
To: 'san'; 'Cisco certification'
Subject: RE: Looking for Multicast Design Suggestion
Option 1 - Use SSM for the HD content. So an RP isn't required.
Option 2 - make a local router the RP for the HD Specific Groups.
Override
the auto-rp configuration. Put up a multicast boundary so that these
groups
don't see the light of day on the wan interface.
From your message I can't tell if everything has to remain local to you,
and
the RP not being local is what is causing the issues or not.
David
-- http://dcp.dcptech.com> -----Original Message----- > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On > Behalf Of san > Sent: Monday, January 07, 2008 8:22 PM > To: Cisco certification > Subject: Looking for Multicast Design Suggestion > > Hello All, > > I have got this task of re-designing the multitask network at > our alpha > network. > > Current Problem: > Currently We have only WAN link <4MB in the network. We are > using this > network for email, http and test IP phones. Recently when > we stream HD > multicast streams we see that BW is choked. We are using > auto-RP and RP is > not under our control. We have Distribution, edge and > endpoints under our > control. We have two RP sources guiding different sources > Lets assume RP-regular multicast and RP-HD multicast. > > Possible Requirement: > - without removing the existing WAN ? > > Possible options: > - We could add a additional Etherenet and route Multicast > traffic over > that. > > Questions: > What is the best method out of the below or what other > options i Have ? > - could we use to use WAN for non HD streams & Ethernet for > HD streams - > Pros and Cons ? > - Would traffic flow via Ethernet by default .....because of high > bandwidth ? > - Any filtering methods to use ? > > Sample Topology: > > Distribution 1----------WAN-------------Edge > =====Ether------------- > > > > -- > Thanks & Rgds > SAN > > ______________________________________________________________ > _________ > Subscription information may be found at: > http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Fri Feb 01 2008 - 10:37:58 ARST