LISTSERV mailing list manager LISTSERV 15.5

Help for NORDNOG Archives


NORDNOG Archives

NORDNOG Archives


View:

Next Message | Previous Message
Next in Topic | Previous in Topic
Next by Same Author | Previous by Same Author
Chronologically | Most Recent First
Proportional Font | Monospaced Font

Options:

Join or Leave NORDNOG
Reply | Post New Message
Search Archives


Subject: Re: ti/nb at Telenor?
From: Patrik Fältström <[log in to unmask]>
Reply-To:Network management discussion for Nordic region <[log in to unmask]>
Date:Fri, 7 Nov 2003 07:32:25 +0100
Content-Type:text/plain
Parts/Attachments:
Parts/Attachments

text/plain (84 lines)


Well, the number of "hops" on IP level is not really a major issue
here, BUT, what worried me is that the packet go back and forth around
the whole of Scandinavia, at least twice (it feels like ;-). The only
worrying thing with the number of hops (which might hide some more
L2-hops between them) is the number of active boxes the packet will
traverse, which of course increase the risk one of the boxes is broken.
Simply because companies like Cisco ;-) don't make boxes which are up
100% of the time.

Anyway, I was more curious than complaining.

    paf

On 2003-11-06, at 22.10, Hakan Hansson wrote:

> Maybe I can clarify some of it. Utfors.net/8434 is today connected to
> T.net/2119 ("ti") in Stockholm, which gives 4 hops to Oslo. T.net is
> connected to Nextbone/8210 ("nb") in Oslo, which gives 2 hops to London
> where MCI is connected. Within a few weeks 8434 will have direct
> connection(s) to 8210 in Oslo, which will reduce this path with
> probably 4
> hops.
>
> /Håkan
>
> At 21:25 2003-11-06, Patrik Fältström wrote:
>
>> Curious minds want to know...
>>
>> What is "ti" and "nb" at Telenor, and why so many hops? This is from
>> me
>> in Skåne south of Sweden (70 km from Copenhagen) to cisco in
>> Amsterdam.
>> Can we at Cisco do anything (in Amsterdam) to make things better? I.e.
>> is it me or Cisco which have bad connectivity to the world?
>>
>>    paf
>>
>> zx81>traceroute ssh-ams1.cisco.com
>> traceroute to ssh-ams-1.cisco.com (144.254.74.55), 30 hops max, 40
>> byte
>> packets
>>  1  paf-gw (195.66.31.65)  4.337 ms  2.261 ms  1.952 ms
>>  2  tom-paf-gw.teleservice.net (193.109.175.25)  19.463 ms  13.883 ms
>> 11.752 ms
>>  3  yst-tom-gw.teleservice.net (193.109.175.5)  14.64 ms  24.321 ms
>> 16.98 ms
>>  4  mal-yst-gw.teleservice.net (193.109.175.1)  15.911 ms  19.735 ms *
>>  5  ge-0-1-0.se-sthms001-pe-1.utfors.net (212.105.101.202)  31.212 ms
>> 45.25 ms  39.475 ms
>>  6  ti600000b051-ge4-2.ti.telenor.net (148.122.8.13)  37.908 ms *
>> 48.891 ms
>>  7  ti600001c050-ge6-1.ti.telenor.net (146.172.126.41)  60.52 ms
>> 56.044 ms  109.122 ms
>>  8  ti100001c050-pos13-0.ti.telenor.net (146.172.126.33)  86.22 ms
>> 90.819 ms  70.338 ms
>>  9  ti100001b051-ge0-0.ti.telenor.net (146.172.248.94)  167.045 ms *
>> 58.745 ms
>> 10  nb01b12-ge0-0.nb.telenor.net (217.70.229.65)  51.301 ms  54.777 ms
>> 47.745 ms
>> 11  nb21b12-pos4-3.nb.telenor.net (217.70.227.22)  78.392 ms  76.103
>> ms
>>  76.929 ms
>> 12  pos6-4.br1.lnd9.alter.net (146.188.61.101)  79.621 ms  76.418 ms
>> 83.306 ms
>> 13  so-0-2-0.tr1.lnd9.alter.net (146.188.7.241)  79.782 ms  87.247 ms
>> 79.115 ms
>> 14  so-6-0-0.tr2.ams2.alter.net (146.188.8.158)  92.353 ms  78.423 ms
>> 81.057 ms
>> 15  so-6-0-0.xr1.ams6.alter.net (146.188.8.81)  87.466 ms  81.709 ms
>> 81.344 ms
>> 16  pos1-0.gw5.ams6.alter.net (146.188.4.6)  84.21 ms  93.283 ms
>> 80.056 ms
>> 17  nl-ciscos2.customer.nl.uu.net (213.53.49.50)  78.036 ms  92.792 ms
>> 80.794 ms
>> 18  ams-clip-dirty-gw1-ge2-2.cisco.com (64.103.36.113)  81.071 ms
>> 100.299 ms  119.692 ms
>> 19  * ams-clip-wall-1-ge0-0-0.cisco.com (64.103.36.122)  91.689 ms
>> 78.281 ms
>> 20  *^C
>> zx81>
>>
>>
>

Back to: Top of Message | Previous Page | Main NORDNOG Page

Permalink



LISTSRV.NORDU.NET

CataList Email List Search Powered by the LISTSERV Email List Manager