[eejit]

No my ip isnt in that list and it seems this problem is quite widespred :/

[Bruno]

How do you check the static IP?

Command ifconfig, eth0.

r10013:~# ifconfig
eth0      Lien encap:Ethernet  HWaddr 00:19:D1:86:D5:F0
          inet adr:91.121.193.XX  Bcast:91.121.193.255  Masque:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2173866 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3205022 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:1000
          RX bytes:641838588 (612.1 MiB)  TX bytes:3806792227 (3.5 GiB)
          Interruption:16 Adresse de base:0x2000

[Kuberr]

How do you check the static IP?

Also, will those servers ever be removed from the list?

[Bruno]

ping it n00b :P

This :

r10013:~# ping r11115.ovh.net
PING r11115.ovh.net (87.98.161.226) 56(84) bytes of data.

is the failover IP. I asked you your static IP (smtg like 91.121.XXX.XX) to check if you are on the "special QoS list" or not. But I think you can do it yourself :


91.121.196.98
91.121.199.1
91.121.196.17
91.121.197.11
91.121.196.79
91.121.196.44
91.121.197.62
91.121.199.29
91.121.196.91
91.121.196.62
91.121.196.61
91.121.196.25
91.121.198.29
91.121.197.20
91.121.199.50

If it isn't.. contact the support. I'm not from OVh. Good luck.

[Scott Curtis]

lol, Is it not also in the post above? 194.109.21.66? Good luck trying to get some answers outta these guys they tend to let the members answer for them and provide as little support as humanly possible. Anything less and you would truly be on your own in the wilderness!

[eejit]

ping it n00b :P

[Bruno]

r11115.ovh.net

And the static IP ?

[eejit]

r11115.ovh.net

[Bruno]

>_>

And the server name is .... ?

[eejit]

Which issue ?

wget ftp://ftp.debian.nl/pub/test/50mb.bin
--23:05:55--  ftp://ftp.debian.nl/pub/test/50mb.bin
           => `50mb.bin.10'
Resolving ftp.debian.nl... 194.109.21.66
Connecting to ftp.debian.nl|194.109.21.66|:21... connected.
Logging in as anonymous ... Logged in!
==> SYST ... done.    ==> PWD ... done.
==> TYPE I ... done.  ==> CWD /pub/test ... done.
==> PASV ... done.    ==> RETR 50mb.bin ... done.
Length: 52,428,800 (50M) (unauthoritative)

 0% [                                     ] 114,392       19.66K/s    ETA 41:28

>_>

[Bruno]

more importantly: tell us when the speeds issue will be fixed!!

Which issue ?

r10013:~# wget debian-40r3-source-CD-1.iso
requête HTTP transmise, en attente de la réponse...200 OK
Longueur: 679 794 688 (648M) [application/octet-stream]

50% [================================================== ======> ] 343 699 857 10.25M/s ETA 00:47

10,25M/s = 82Mbps

[Scott Curtis]

I am willing to bet the QoS will not be much of an improvement over the current one. The RPS I am supposed to testing is sitting collecting dust as the speed is at a crawl since I hit the 200gb bandwidth used. Don't waste your time and money.

[eejit]

more importantly: tell us when the speeds issue will be fixed!!

[Andy]

Could you explain what sort of QoS will be implemented please?

[oles@ovh.net]

Hello,

We are currently testing the RPS 1 with NFS instead of iSCSI. The fix works. There is no more problem. We are testing the limitations of the infrastructure.

Therefore, the RPS 2 is delayed for a few days even if the servers are in the rack.

At the same time, we will try another type of QoS. We had the idea last week. I do not know if I will do it today or not.

The options in the manager will be activated in a few days (such as IRC & co).

We are also testing on 202/203 another architecture compared to iSCSI. We gave ourselves 7 days for the proof of concept. If it works, the additional space management will be much more flexible than at present. In any case, we want to offer you up to 1TB within 10 days.

Regards,

Octave