[21617] in North American Network Operators' Group
Re: Cache-as-cache-can
daemon@ATHENA.MIT.EDU (Jesper Skriver)
Tue Nov 17 11:59:55 1998
Date: Tue, 17 Nov 1998 09:14:00 +0100
From: Jesper Skriver <jesper@skriver.dk>
To: Katsuhiro Kondou <kondou@nec.co.jp>
Cc: nanog@merit.edu
In-Reply-To: <19981117075318W.kondou@inn.do.mms.mt.nec.co.jp>; from Katsuhiro Kondou on Tue, Nov 17, 1998 at 07:53:18AM +0900
On Tue, Nov 17, 1998 at 07:53:18AM +0900, Katsuhiro Kondou wrote:
> In article <19981116200208.A27675@magnet.at>,
> Michael Haba <m.haba@magnet.at> wrote;
>
> } To cut a long story short, I was just wondering if people could extrapolate
> } their feelings regarding commerical Web Cache solutions. In terms of the
> } good, the bad and the ugly.
> }
> } At the moment I'm left with 'two goods' Network Appliance's NetCache and
> } Inktomi's Traffic Server and would appreciate some input to sort them out.
>
> I don't think there is major difference in caching, but some
> appliance have some problem in their routing. NetCache learns
> it from icmp redirect or rip1 which is quite poor for redundant
> network topology. I don't know about CacheFlow quite well, but
> it seems to speak rip1 at most. I believe they should speak
> ospf at least, if they run in a large isp. As for inktomi,
> there may not be any routing problem since it runs on some unix
> boxes, but it cannot handle so many connections simultaneously
> like NetCache or CacheFlow.
Why use things like this, use a default route to a HSRP address ...
/Jesper
--
Jesper Skriver (JS4261-RIPE), Network manager
Tele Danmark DataNet, IP section (AS3292)
One Unix to rule them all, One Resolver to find them,
One IP to bring them all and in the zone to bind them.
