We are in the process of migrating this forum. A new space will be available soon. We are sorry for the inconvenience.

routing zu netstream.ch neuerdings kaputt


oles@ovh.net
08.03.08, 18:36
iSO a écrit:
>
> is this the second line to gblx_p from gsw1 that one can see on the
> weathermap?


yes ...


iSO
08.03.08, 17:45
is this the second line to gblx_p from gsw1 that one can see on the weathermap?

oles@ovh.net
08.03.08, 17:34
iSO a écrit:
>
> ok, so you need to fill the link so that you can move globalcrossing to
> paris?
> i hope this won't take too long...


I hope it will be this week. our 10G to global crossing peering
in paris is ready. we are waiting for the gblx's side now.

iSO
08.03.08, 14:03
ok, so you need to fill the link so that you can move globalcrossing to paris?
i hope this won't take too long...

oles@ovh.net
08.03.08, 13:46
iSO a écrit:
>
> yes, i can see that on the weathermap. but the problem didn't occur
> until wednesday or thursday, i was not routed via london until then.
> isn't it possible to change this back to the route using globalswitch1
> and globalcrossing?


No I can't change. Some ISP don't want to upgrade the links if
the link is not full. It's a crazy system. So I have to make
it full during some days to push them to upgrade saying "look
it's full ! we REALLY need to upgrade". sorry for this


iSO
08.03.08, 13:40
yes, i can see that on the weathermap. but the problem didn't occur until wednesday or thursday, i was not routed via london until then. isn't it possible to change this back to the route using globalswitch1 and globalcrossing?

oles@ovh.net
08.03.08, 13:20
> 3 020G.gsw-2-6k.routers.ovh.net (213.186.32.221) 4.933 ms * *
> 4 ge1-0.ar2.lon2.gblx.net (195.66.224.112) 164.362 ms 164.344 ms 164.497 ms


our Linx link is full. it should be resolved this week (we have
to move Global Crossing from Linx to a private peering 10g link
in Paris.


iSO
08.03.08, 12:42
hi, ich habe gestern festgestellt, dass das routing zu meinem ISP geändert hat, eventuell ists auch schon 2-3 tage länger so. das problem äussert sich dadurch, dass wo ich vorher 520k/s (fullspeed für mich) mit einer connection hatte, jetzt noch 80-120k/s drin sind.

route vom server zu mir: (kanns sein dass das jetzt über linx geht? vorher gings über gsw1 und globalcrossing, das war schnell)
Code:
traceroute to om1nae.homeip.net (80.238.233.213), 30 hops max, 40 byte packets
 1  rbx-36-m1.routers.ovh.net (91.121.112.253)  0.568 ms  0.755 ms  0.905 ms
 2  rbx-2-6k.routers.ovh.net (213.251.191.130)  0.320 ms * *
 3  020G.gsw-2-6k.routers.ovh.net (213.186.32.221)  4.933 ms * *
 4  ge1-0.ar2.lon2.gblx.net (195.66.224.112)  164.362 ms  164.344 ms  164.497 ms
 5  64.213.78.210 (64.213.78.210)  26.312 ms  26.303 ms  26.435 ms
 6  core0.ge-0-3-0.nshq.ch.netstream.com (62.65.128.129)  27.265 ms  27.500 ms  26.560 ms
 7  lns0.ge-0-1-0.nshq.ch.netstream.com (62.65.128.147)  27.109 ms  27.098 ms  27.086 ms
8 ich
route umgekehrt:
Code:
traceroute to 91.121.112.100 (91.121.112.100), 30 hops max, 40 byte packets
 1  iso-m0n0.local (192.168.1.254)  0.308 ms  0.486 ms  1.763 ms
 2  lns0.lo-1-0-0.nshq.ch.netstream.com (62.65.128.254)  25.282 ms  25.278 ms  25.275 ms
 3  core1.ge-0-2-0.nshq.ch.netstream.com (62.65.128.146)  26.814 ms  28.556 ms  30.656 ms
 4  core0.ge-0-1-0.tix.ch.netstream.com (62.65.128.238)  229.146 ms  229.144 ms  229.812 ms
 5  62.65.130.154 (62.65.130.154)  38.385 ms  40.348 ms  44.292 ms
 6  217.239.37.129 (217.239.37.129)  58.079 ms  61.745 ms  64.376 ms
 7  010g.th2-1-6k.routers.ovh.net (213.186.32.205)  76.741 ms * *
 8  020g.rbx-2-6k.routers.ovh.net (213.186.32.201)  63.986 ms * *
 9  rbx-36-m1.routers.ovh.net (213.251.191.231)  58.461 ms  63.668 ms  61.589 ms
10  ns354752.ovh.net (91.121.112.100)  70.412 ms  57.681 ms  55.708 ms