Re: UUNET Routing issues

[Jared Mauch <jared () puck Nether net>]

        The Juniper routers (it appears they are based on
the interface naming scheme) tend to have incredible buffering capabilities
as compared to the predecasors of the time.  This allows a full link
to not drop packets and fully buffer them over a period of time.

        This obviously has ramifications when it relates to tcp timing
and when you go from having a 20ms rtt for a packet to 1000+ms.  tcp
obviously will think that there is some loss.

        - Jared

On Thu, Oct 03, 2002 at 05:33:05PM -0400, Marshall Eubanks wrote:
> Where are they diverting it to, the Moon (1.5 light seconds away) ?
>
> Really - I have seen some multisecond latencies on network links we were
> testing, and I always wondered how these could come to be.
>
>
> -- 
>                                  Regards
>                                  Marshall Eubanks
>
>
>
> Vinny Abello wrote:
>
> > The only thing I've noticed is high latency between UUNet and Sprint 
> > (around 2 second latency) in at least one traffic exchange point between 
> > them, maybe more. Probably because of the diversion of traffic on 
> > UUNet's network.
> >
> > At 04:30 PM 10/3/2002 -0400, Matt Levine wrote:
> >
> >
> > > On Thursday, October 3, 2002, at 04:07 PM, Chris Adams wrote:
> > >
> > > > Once upon a time, sigma () smx pair com <sigma () smx pair com> said:
> > > >
> > > > > There still seem to be problems.  Earlier today CHI->ATL was 2000ms.
> > > > > Now
> > > > > it's improved to 1000ms.
> > > > >
> > > > > 9  0.so-5-0-0.XL2.CHI13.ALTER.NET (152.63.73.21)  24.466 ms  24.311 
> > > > > ms 24.382 ms
> > > > > 10  0.so-0-0-0.TL2.CHI2.ALTER.NET (152.63.68.89)  24.467 ms  24.349 
> > > > > ms 24.454 ms
> > > > > 11  0.so-3-0-0.TL2.ATL5.ALTER.NET (152.63.101.50)  1029.484 ms
> > > > > 1049.529 ms 1063.692 ms
> > > > > 12  0.so-7-0-0.XL4.ATL5.ALTER.NET (152.63.85.194)  1106.067 ms
> > > > > 1118.102 ms 1132.124 ms
> > > >
> > > >
> > > > We're a UUNet customer (we also have other connections), and we haven't
> > > > really seen any big problem today.  We're connected to Atlanta, and I
> > > > see:
> > > > <snip>
> > >
> > >
> > > We haven't seen anything unusual on our UU circuit in PHX, either.
> > >
> > >
> > > > --
> > > > Chris Adams <cmadams () hiwaay net>
> > > > Systems and Network Administrator - HiWAAY Internet Services
> > > > I don't speak for anybody but myself - that's enough trouble.
> > >
> > > --
> > > Matt Levine
> > > @Home: matt () deliver3 com
> > > @Work: matt () eldosales com
> > > ICQ  : 17080004
> > > AIM  : exile
> > > GPG  : http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x6C0D04CF
> > > "The Trouble with doing anything right the first time is that nobody
> > > appreciates how difficult it was."  -BIX
> >
> >
> >
> > Vinny Abello
> > Network Engineer
> > Server Management
> > vinny () tellurian com
> > (973)300-9211 x 125
> > (973)940-6125 (Direct)
> > PGP Key Fingerprint: 3BC5 9A48 FC78 03D3 82E0  E935 5325 FBCB 0100 977A
> >
> > Tellurian Networks - The Ultimate Internet Connection
> > http://www.tellurian.com (888)TELLURIAN
>
>
>
> 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.multicasttech.com
>
> Test your network for multicast :
> http://www.multicasttech.com/mt/
>  Status of Multicast on the Web  :
>  http://www.multicasttech.com/status/index.html

-- 
Jared Mauch  | pgp key available via finger from jared () puck nether net
clue++;      | http://puck.nether.net/~jared/  My statements are only mine.