All things related to multicast

[Peter John Hill <>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Something like this:
http://multicast.internet2.edu/MulticastCookBook.shtml

you definitely want to do pim-sm and anycast RPs with msdp running  
between the RPs... You'll also end up running multiprotocol bgp with  
address family ipv4-multicast. You'll msdp peer with your providers RP.

You should figure out what your glop address range is for your as.

http://www.multicast.org.uk/address-tools/glop-calc.cgi?asn=AS3172

You can they make sure your internal servers use this address..

When it comes to enabling it on the WAN, are you talking about ten gig  
circuits or t1s?

What other questions do you have?

peter


On May 30, 2008, at 8:26 AM, Tyrone Kelly wrote:

> Hello ALL,
>
> I was looking for advice, perhaps a multicast cookbook, as me and my  
> colleagues are tasked with enabling our Wan to support Multicast.  I  
> operate a transport wan that many higher Ed institutions use for ISP  
> services.  We have 3 tier one ISPs that we peer with and we're  
> connected to I2 and are on transit rail.  '
> Our impetus has been several request from institutions to enable  
> multicast for the sake of receiving some multicast feeds like the  
> Philadelphia Harmonic Symphony as well as other media.  I feel that  
> many institutions may become multicast sources as well.
> Challenge one is obvious setting a Multicast peering relationship up  
> with another AS as well as getting multicast enabled at the  
> instituion's campus level. I have been researching and modeling and  
> ASM/SSM ANYCAST AUTO-RP  environment and I peer multiple RP's with  
> MSDP.  Is this a consistent practice in live networks?  How does one  
> guard against multiple ASM channels and receiving the wrong  
> multicast , if possible? Is there a cookbook available?
>
>
> THANKS
>
>
> Tyrone D. Kelly
>
>
> debbie fligor wrote:
>
> > For anyone else that doesn't have an Apple SE handy, mine  
> > suggested  this:
> >
> > > The best thing to do is to file a new bug report at http://bugreport.apple.com 
> > >  .  It will be set as a duplicate, but that becomes really obvious  
> > > in  the bug report.
> > >
> > > FWIW, [my bug report] it's set to a P1, but for the Next Major OS   
> > > (after the one we're currently working on, that is :-()  There  
> > > are  currently 4 duplicates and three people have chimed in with  
> > > impact  information.
> > On May 28, 2008, at 10:21, debbie fligor wrote:
> >
> > > In discussion with my Apple SE this morning, it looks like IGMPv3   
> > > may not even be in the next major OS release (10.6 I assume)  --  
> > > the  main reason he can figure out looking at the bug report he  
> > > filed for  me is that in the multiple years that bug has been  
> > > open, only 2 or 3  people have chimed in that it was important for  
> > > them.
> > >
> > > Apparently which things like this get implemented is often   
> > > determined by user request/industry need. So if you would like to   
> > > see it, contact your Apple SE and tell them you want it and why  
> > > you  need it and how important it is for you.
> > >
> > > Even if I didn't want to test switches with Macs, if we want to  
> > > go  to IGMPv3 on our networks, we need all the clients on a given  
> > > net  playing with the same IGMP level, unless I misunderstand how  
> > > the  backwards compatibility works.
> > >
> > >
> > > -----
> > > -debbie
> > > Debbie Fligor, n9dn       Network Engineer, CITES, Univ. of Il
> > > email: 
> > >
> > >           <http://www.uiuc.edu/ph/www/fligor>
> > >                 "My turn."  -River Tam
> >
> > -----
> > -debbie
> > Debbie Fligor, n9dn       Network Engineer, CITES, Univ. of Il
> > email: 
> >
> >           <http://www.uiuc.edu/ph/www/fligor>
> >                  "My turn."  -River Tam

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)

iEYEARECAAYFAkhAPzYACgkQqFN4NA7/LWhHjwCgyTOApI8iQfumYbcX2cUu4WVV
q+0An3jm/kcOHa5uRoOzEJoPjKsbfKBj
=aoIa
-----END PGP SIGNATURE-----