All things related to multicast

["Eschete, Daniel" <>]

We sent out official university emails announcing the availability of
the multicast stream along with a link to a webpage for viewing.  It was
also stated that during this time frame, unicast viewing over I1 would
be disabled and our Information Security team would police our internet
connection to ensure that unicast was not used.

In the end we had very good results on our campus, but our upstream
provider did notify us that they were reaching I1 capacity due to
unicast viewing load from their other customers.


Daniel Eschete
IT Analyst
LSUHSC Computer Services

Office: 504-568-8891
Cell: 504-218-3502



-----Original Message-----
From: Mike Carey 
[mailto:]
 
Sent: Monday, January 26, 2009 8:15 AM
To: wg-multicast List
Subject: RE: Inauguration Day Stream(s)

Just curious - did you engage in any public information to encourage
people to use the Multicast option that was available? 

I ask because I think we had the same issue here.  Multicast traffic
increased above the norm, but it was unicast traffic that was really
took off that day.  But besides the IT folks, I don't know that anyone
knew that Multicast over I2 was the preferred method to access this
media.  We didn't send any media blitz to the campus newspaper, Blog
postings, or updates on Departmental websites (that I know of).

So if anyone took proactive steps to encourage the user community to use
Multicast in this situation, please share. 


Michael D. Carey
Telecommunications and Networking Services
Information Technology Services
Pennsylvania State University
(814) 863-7712





-----Original Message-----
From: Ryan Harden 
[mailto:]
 
Sent: Friday, January 23, 2009 6:48 PM
To: 

Cc: Julian Y. Koh; wg-multicast List
Subject: Re: Inauguration Day Stream(s)

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

We saw an increase of about 1Gbps or so over normal levels for that time
of day. Almost all of it was CNN's feed. A couple other sources showed
up in there too. We didn't have any 'pain' in any of our equipment. We
did get some fun looking graphs though. :)

Unfortunately even though we have good multicast connectivity to
Internet2, no one used it. Our traffic characterization tools didn't
show anything over baseline.

/Ryan

Bill Owens wrote:
> On Fri, Jan 23, 2009 at 04:09:53PM -0600, Julian Y. Koh wrote:
>> Now, we had definite pains on some of our external traffic due to the
>> Octoshape P2P streaming that CNN was employing, but luckily we
already had
>> our multicast traffic bypassing the equipment that was hurting.
Otherwise
>> life would have been not so good for us.  As it was, the pain that
people
>> were experiencing with the unicast streams (and I'm including the
Octoshape
>> streams there as well) is going to serve as a good leverage for
publicizing
>> the multicast-based services.
> 
> It would have been bitterly ironic if the all-but-unannounced P2P
pseudo-multicast traffic had interfered with the one high-grade
multicast feed that was available to us. 
> 
> We saw unicast traffic peaks at almost 1.2 Gbps on our egress
connections, with several campuses maxing out their connections, all
attributable to Octoshape (since NYSERNet doesn't provide transit to any
commercial streaming sources). I'm glad that the network was used, but I
do wish that they could come up with something a bit smarter.
> 
> Bill.

- --
Ryan M. Harden, BS, KC9IHX              Office: 217-265-5192
CITES - Network Engineering             Cell:   630-363-0365
2130 Digital Computer Lab,              Fax:    217-244-7089
1304 W. Springfield                     email:  

Urbana, IL  61801                       

         University of Illinois - Urbana/Champaign
                     -  All your Base -
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkl6V0AACgkQtuPckBBbXbocYgCgmvgTnjVbeEyFaANneLxl3OkH
RKwAmwZHuZ6lb5ZKuPET2tmlhjc2DduQ
=6g9z
-----END PGP SIGNATURE-----