electron33
Nov 18 2004, 03:12 PM
I used to pus my back up files to GNAX at speeds well over 300KB/s, but now it's been about a month I cant get anything over 50K, even after the backbone upgrades.
I was wondering if anyone else is having this problem.
Cheers
staggs
Nov 18 2004, 11:18 PM
there are a few others like this...I'm one myself, but I can hit 200KB/s...I noticed if I pushed 5 files at once....I could hit the 1MB/s mark...which is what I was looking for...I just wasn't looking to do it like that though.
SM Rep
Nov 19 2004, 01:14 AM
Please open a support ticket so this can be investigated.
electron33
Nov 19 2004, 01:44 AM
I have submitted a ticket for this, but it's been quite some time and no resolution.
staggs
Nov 19 2004, 09:54 AM
Ticket: 458234PLNT
It's been open since November 4th, and hasn't been updated by theplanet since the 9th...Although I've talked to william privately in a PM here on the boards about it since, nothings ever really been resolved.
electron33
Nov 19 2004, 10:13 AM
I've been told this is routing issue and it's being worked on, but like you staggs, so far no improvement.
The problem seems to be TP > GNAX through Level 3. I know it's not jsut me and staggs. There're quite few other users with the same issue, so it might be worth for TP looking into this.
wcharnock
Nov 19 2004, 10:58 AM
Based on what I've been able to determine, this is not a problem on our side.
If anyone has a regular server at GNAX (not just a backup account) and they're willing to give me a login on it so I can do some more testing, then please PM me and I'll see what else we can find.
sirius
Nov 19 2004, 11:43 AM
QUOTE (wcharnock)
Based on what I've been able to determine, this is not a problem on our side.
If anyone has a regular server at GNAX (not just a backup account) and they're willing to give me a login on it so I can do some more testing, then please PM me and I'll see what else we can find.
Come on, this is a Planet problem and it's been an ongoing issue for quite some time. We have done extensive testing to the GNAX network and speeds are fine, except when going out a sub-optimal route from The Planet's network.
You can reference ticket 441409PLNT which has been open since October.
Luckily, you were nice enough to move my routes over to Level3 and I am now able to push 30-35mbit to GNAX.
To the thread starter, post your traceroute to your backup server. I bet you are going there via Abovenet.
Sirius
electron33
Nov 19 2004, 12:19 PM
CODE
traceroute to backup11.gnax.net (209.51.141.98), 30 hops max, 38 byte packets
1 97.69-93-254.reverse.theplanet.com (69.93.254.97) 0.489 ms 0.426 ms 0.365 ms
2 gig3-5.sm-asr1-2.theplanet.com (69.41.250.65) 0.489 ms 0.343 ms *
3 dsr1-2-v1.dllstx2.theplanet.com (12.96.160.10) 0.883 ms 0.309 ms 0.365 ms
4 dist-vlan22.dsr3-2.dllstx3.theplanet.com (70.85.127.74) 0.769 ms 0.844 ms 0.740 ms
5 ae1-0.ibr2.dllstx3.theplanet.com (70.85.127.34) 0.987 ms 0.846 ms *
6 ge-8-0-124.ipcolo2.Dallas1.Level3.net (63.209.48.109) 0.872 ms 0.948 ms 0.865 ms
7 so-1-2-0.bbr1.Dallas1.Level3.net (209.244.15.161) 1.238 ms 1.216 ms 1.241 ms
8 * so-0-2-0.bbr1.Atlanta1.Level3.net (209.247.9.101) 20.532 ms ae-0-0.bbr2.Atlanta1.Level3.net (64.159.1.46) 20.545 ms
9 ge-11-0.hsa2.Atlanta1.Level3.net (64.159.3.14) 20.449 ms ge-10-0.hsa2.Atlanta1.Level3.net (64.159.1.254) 20.583 ms ge-10-2.hsa2.Atlanta1.Level3.net (64.159.3.82) 20.833 ms
10 4.78.210.6 (4.78.210.6) 20.697 ms 20.723 ms 20.598 ms
11 * 209.51.131.25 (209.51.131.25) 20.909 ms 20.842 ms
12 l3-atl-4.gnax.net (209.51.134.66) 20.597 ms 23.418 ms 28.975 ms
13 backup11.gnax.net (209.51.141.98) 20.841 ms 20.703 ms 20.720 ms
sirius, it's through level3 mate.
Thanks for your support.
sirius
Nov 19 2004, 12:28 PM
QUOTE (electron33)
CODE
traceroute to backup11.gnax.net (209.51.141.98), 30 hops max, 38 byte packets
1 97.69-93-254.reverse.theplanet.com (69.93.254.97) 0.489 ms 0.426 ms 0.365 ms
2 gig3-5.sm-asr1-2.theplanet.com (69.41.250.65) 0.489 ms 0.343 ms *
3 dsr1-2-v1.dllstx2.theplanet.com (12.96.160.10) 0.883 ms 0.309 ms 0.365 ms
4 dist-vlan22.dsr3-2.dllstx3.theplanet.com (70.85.127.74) 0.769 ms 0.844 ms 0.740 ms
5 ae1-0.ibr2.dllstx3.theplanet.com (70.85.127.34) 0.987 ms 0.846 ms *
6 ge-8-0-124.ipcolo2.Dallas1.Level3.net (63.209.48.109) 0.872 ms 0.948 ms 0.865 ms
7 so-1-2-0.bbr1.Dallas1.Level3.net (209.244.15.161) 1.238 ms 1.216 ms 1.241 ms
8 * so-0-2-0.bbr1.Atlanta1.Level3.net (209.247.9.101) 20.532 ms ae-0-0.bbr2.Atlanta1.Level3.net (64.159.1.46) 20.545 ms
9 ge-11-0.hsa2.Atlanta1.Level3.net (64.159.3.14) 20.449 ms ge-10-0.hsa2.Atlanta1.Level3.net (64.159.1.254) 20.583 ms ge-10-2.hsa2.Atlanta1.Level3.net (64.159.3.82) 20.833 ms
10 4.78.210.6 (4.78.210.6) 20.697 ms 20.723 ms 20.598 ms
11 * 209.51.131.25 (209.51.131.25) 20.909 ms 20.842 ms
12 l3-atl-4.gnax.net (209.51.134.66) 20.597 ms 23.418 ms 28.975 ms
13 backup11.gnax.net (209.51.141.98) 20.841 ms 20.703 ms 20.720 ms
sirius, it's through level3 mate.
Thanks for your support.
What port speed do you have? 10? 100?
Here is my traceroute....
QUOTE
root@slinky [/backup/test]# traceroute backup7.gnax.net
traceroute to backup7.gnax.net (63.247.67.154), 30 hops max, 38 byte packets
1 dlstx4-gw (67.19.1xx.xxx) 0.455 ms 0.568 ms 0.474 ms
2 gig4-5.dsr2-1.dllstx4.theplanet.com (67.19.255.33) 0.491 ms 0.597 ms 0.476 ms
3 dsr1-2-v1.dllstx2.theplanet.com (12.96.160.10) 1.491 ms 0.681 ms 0.985 ms
4 dist-vlan22.dsr3-2.dllstx3.theplanet.com (70.85.127.74) 0.989 ms 2.187 ms 1.974 ms
5 ae0-0.ibr2.dllstx3.theplanet.com (70.85.127.2) 1.991 ms 2.123 ms 2.518 ms
6 ge-4-1-138.ipcolo2.Dallas1.Level3.net (4.78.224.13) 3.444 ms 2.170 ms 2.641 ms
7 so-4-1-0.bbr1.Dallas1.Level3.net (4.68.113.25) 2.332 ms 2.672 ms 1.980 ms
8 so-0-2-0.bbr1.Atlanta1.Level3.net (209.247.9.101) 21.523 ms ae-0-0.bbr2.Atlanta1.Level3.net (64.159.1.46) 21.184 ms so-0-2-0.bbr1.Atlanta1.Level3.net (209.247.9.101) 21.187 ms
9 ge-11-1.hsa2.Atlanta1.Level3.net (64.159.3.10) 21.114 ms ge-10-2.hsa2.Atlanta1.Level3.net (64.159.3.82) 21.202 ms ge-10-0.hsa2.Atlanta1.Level3.net (64.159.1.254) 22.207 ms
10 4.78.210.6 (4.78.210.6) 21.219 ms 21.280 ms 20.970 ms
11 209.51.131.25 (209.51.131.25) 21.476 ms 20.698 ms 20.973 ms
12 l3-atl-4.gnax.net (209.51.134.66) 22.974 ms 21.096 ms 21.959 ms
13 63.247.67.154 (63.247.67.154) 20.978 ms 21.195 ms 21.472 ms
Sirius
electron33
Nov 19 2004, 12:38 PM
I'm on a 100Mb/s port. I had no problem pushing 1 MB/s until a month ago.
I can use other networks to get at least 0.5 MB/s.
I can't see anything wrong from the trace itself.
It would be good if TP checked this directly with GNAX. I'm pretty sure GNAX can give'm access to one of their servers.
This issue is affecting customers on both side and I don't see why this should go on for such a long time. Blaming the other side without any evidence is really childish in my opinion.
sirius
Nov 19 2004, 12:48 PM
QUOTE (electron33)
I'm on a 100Mb/s port. I had no problem pushing 1 MB/s until a month ago.
I can use other networks to get at least 0.5 MB/s.
I can't see anything wrong from the trace itself.
It would be good if TP checked this directly with GNAX. I'm pretty sure GNAX can give'm access to one of their servers.
This issue is affecting customers on both side and I don't see why this should go on for such a long time. Blaming the other side without any evidence is really childish in my opinion.
Jeff Hinkle over at GNAX was super helpful when I was originally having problems. He assisted me in troubleshooting using file transfers from a bunch of different networks. It was pretty easy to pin-point where the problems were.
Like I said, when William moved my route over to Level3, I started getting much better speeds.
Sirius
electron33
Nov 19 2004, 01:09 PM
Jeff was great in helping me with various tests.
staggs
Nov 19 2004, 05:06 PM
I know someone that has a gnax box, but I hardly see him online...if I do catch him online I'll be sure to get a shell account from him. Although I will probably have a couple gnax boxes around January because I plan on doing a disaster recovery plan with them.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please
click here.