nanog mailing list archives

Re: What Worked - What Didn't


From: Marshall Eubanks <tme () 21rst-century com>
Date: Mon, 17 Sep 2001 13:49:05 -0400


Daniel Golding wrote:

The big lessons seem to be these...

1) The Internet, as currently constituted makes a lousy news propagation
method, for large audiences. The one to many model in unicast IP puts too
large of a load on the source. Good multicast (which we don't have yet) may
fix this. Until that happens, the TV is still a better broadcast news
medium. Mechanisms like Akamai's Edgesuite are a pretty good solution until
that occurs, as they distribute the load pattern, from a "one to many" to a
"many to many" model.


Akamai did not work well Tuesday morning, at least for me. I do not know whether their servers
were overloaded, or couldn't get content from the source, but they did NOT work
well as seen from here.

Washington Post.com, for example, loaded ONCE for me before about 3:00 PM EDT, and I
know that site is Akamized.

                                                               Contrarily Yours
                                                               Marshall Eubanks





2) The Internet is superior to circuit switched services for one to one
communications during this sort of condition. Fast busies were the order of
the day in NYC and DC for the PSTN and cell phone networks. Instant
Messanger services, IRC and email were more reliable than the telephone
network by several orders of magnitude.

3) Since the transient from normal conditions was server-limited, there were
not any significant network congestion issues. The next time a major event
like this happens (and, of course, there will be a next time), news sites
may be better prepared, which could cause the next transient from normal
conditions to be network-limited.

The big winners were cable TV, email, packet networks and IM applications.
The big losers with cell phones, circuit switching, PSTN, non-akamized news
sites.

(My apologies if this post if perceived to be on-topic, operational, or has
anything to do with internetworking. We will now return to our regularly
scheduled, off-topic posts)

- Daniel Golding
  Sockeye Networks

-----Original Message-----
From: owner-nanog () merit edu [mailto:owner-nanog () merit edu]On Behalf Of
Marshall Eubanks
Sent: Monday, September 17, 2001 1:17 PM
To: Sean Donelan
Cc: nanog () merit edu
Subject: Re: What Worked - What Didn't

Sean Donelan wrote:

As the New York Stock market re-opens, and some things are returning
to normal, I'd like to look at how well the Internet performed last
week.

At the Oakland NANOG I'd like to give a presentation about what worked,
and what didn't work during the last week in regards to the Internet.  I
would like to gather what details I can from both small and large
providers in New York, the rest of the USA, and even overseas about
what they saw, what problems they experienced, and what things worked.

You can send me private mail if you wish, with or without attribution.
This is a personal effort, not assocated with my employer.

Oakland NANOG is several weeks away, so I don't expect an immediate
response.  I expect many ISPs will be conducting their own internal
reviews.  But if you could, please consider responding.  I'm looking
for input from small, medium and large providers. Thank you.

A few questions, all related to the time between Sept 11 and 17:

 1. Briefly tell me who you are, and generally where your operations
    were located?

 2. What worked?

 3. What didn't work?

 4. Did you activate your emergency response plan?

 5. Were you required to do anything different operationally?  Did you
    make preventive operational changes?

 6. Were any infrastructure administration functions impaired, such
    as DNS registration, routing registry, address delegation?

 7. Were you able to communicate NOC-to-NOC when needed?

 8. Were any means of communications nonfunctional or impaired (direct
    dial telephone, toll-free telephone, pager, e-mail, fax) when you
    attempted to communicate with other NOC's?

 9. Did you ask for or receive a request for mutual aid from any other
    providers?  Was it provided?

10. Within the limits of safety and rescue efforts, where you able to
    gain access to your physical facilities?

11. Did hoaxes or rumors impact your operations?

12. Do you have any recommendations how Internet providers could have
    responded differently?

Sean;

   Multicasting worked. It handled a big traffic spike without a hiccup.

                                 Regards
                                 Marshall Eubanks

T.M. Eubanks
Multicast Technologies, Inc
10301 Democracy Lane, Suite 410
Fairfax, Virginia 22030
Phone : 703-293-9624       Fax     : 703-293-9609
e-mail : tme () multicasttech com
http://www.on-the-i.com

Test your network for multicast : http://www.multicasttech.com/mt/
 Check the status of multicast in real time :
 http://www.multicasttech.com/status/index.html





T.M. Eubanks
Multicast Technologies, Inc
10301 Democracy Lane, Suite 410
Fairfax, Virginia 22030
Phone : 703-293-9624       Fax     : 703-293-9609
e-mail : tme () multicasttech com
http://www.on-the-i.com

Test your network From jc () irbs com  Mon Sep 17 14:17:16 2001
Return-Path: <jc () irbs com>
Received: from exuma.irbs.com (exuma.irbs.com [216.86.165.33])
        by smtp2.irbs.com (Postfix) with ESMTP id 1EF5F11735
        for <jc () smtp2 irbs com>; Mon, 17 Sep 2001 14:17:16 -0400 (EDT)
Received: by exuma.irbs.com (Postfix, from userid 2500)
        id E22D717424; Mon, 17 Sep 2001 14:17:15 -0400 (EDT)
Received: from imap1.irbs.com (imap1.irbs.com [216.86.160.253])
        by exuma.irbs.com (Postfix) with ESMTP id 9C74617418
        for <jc () exuma irbs com>; Mon, 17 Sep 2001 14:17:15 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1])
        by imap1.irbs.com (Postfix) with ESMTP id 93AE4BAA9
        for <jc () exuma irbs com>; Mon, 17 Sep 2001 14:17:15 -0400 (EDT)
Received: from mx2.irbs.com (mx2.irbs.com [216.86.165.7])
        by imap1.irbs.com (Postfix) with ESMTP id A4724BA9F
        for <jc () irbs com>; Mon, 17 Sep 2001 14:17:04 -0400 (EDT)
Received: from trapdoor.merit.edu (trapdoor.merit.edu [198.108.1.26])
        by mx2.irbs.com (Postfix) with ESMTP id 550277821D
        for <jc () irbs com>; Mon, 17 Sep 2001 13:55:59 -0400 (EDT)
Received: by trapdoor.merit.edu (Postfix)
        id 79620912BD; Mon, 17 Sep 2001 13:52:51 -0400 (EDT)
Delivered-To: nanog-outgoing () trapdoor merit edu
Received: by trapdoor.merit.edu (Postfix, from userid 56)
        id 3EE14912DE; Mon, 17 Sep 2001 13:52:51 -0400 (EDT)
Delivered-To: nanog () trapdoor merit edu
Received: from segue.merit.edu (segue.merit.edu [198.108.1.41])
        by trapdoor.merit.edu (Postfix) with ESMTP id 2DF3D912BD
        for <nanog () trapdoor merit edu>; Mon, 17 Sep 2001 13:52:44 -0400 (EDT)
Received: by segue.merit.edu (Postfix)
        id 217FC5DDB0; Mon, 17 Sep 2001 13:52:44 -0400 (EDT)
Delivered-To: nanog () merit edu
Received: from rimmer.clues.com (rimmer.clues.com [194.159.1.1])
        by segue.merit.edu (Postfix) with ESMTP id 100535DDAF
        for <nanog () merit edu>; Mon, 17 Sep 2001 13:52:43 -0400 (EDT)
Received: (from croberts@localhost)
        by rimmer.clues.com (8.10.2/8.10.2) id f8HHmlI25625;
        Mon, 17 Sep 2001 17:48:47 GMT
Date: Mon, 17 Sep 2001 17:48:47 +0000
From: Chris Roberts <croberts () bongle co uk>
To: bmanning () vacation karoshi com
Cc: Randy Bush <randy () psg com>, Greg Mirsky <gmirsky () axiowave com>,
        nanog () merit edu
Subject: Re: On Internet and social responsibility
Message-ID: <20010917174847.B25597 () bongle co uk>
References: <E15izCf-000GPO-00 () rip psg com> <200109171530.PAA27287 () vacation karoshi com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <200109171530.PAA27287 () vacation karoshi com>; from bmanning () vacation karoshi com on Mon, Sep 17, 
2001 at 03:30:14PM +0000
Sender: owner-nanog () merit edu
Precedence: bulk
Errors-To: owner-nanog-outgoing () merit edu
X-Loop: nanog
X-Virus-Scanned: by Sophos Sweep


On Mon, Sep 17, 2001 at 03:30:14PM +0000, bmanning () vacation karoshi com wrote:

mae-west#config t
Enter configuration commands, one per line.  End with CNTL/Z.
mae-west(config)#resist the cycle of violence and hate.
                  ^
% Invalid input detected at '^' marker.

mae-west(config)#


      resist the cycle of baiting & off-topic posting



login: croberts
Password:
Last login: Fri Sep 14 17:10:03 from 1.1.1.1

--- JUNOS 4.3R1.4 built 2001-01-19 07:26:27 UTC

croberts@xxxx> configure
Entering configuration mode

[edit]
croberts@xxxx# edit resist the cycle of cisco and juniper
                    ^
syntax error, expecting <statement> or <identifier>.


resist the cycle of cisco and juniper

Cheers,
Chris.
-- 
|=========-----             -------=======|
|  Chris Roberts (croberts () bongle co uk)  |
|=======-------             -----=========|

for multicast : http://www.multicasttech.com/mt/
 Check the status of multicast in real time :
 http://www.multicasttech.com/status/index.html



Current thread: