New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
Yes, it looks like to be so.
At least for me.
Is there something wrong with the performance between failover ip's and the host IP in WAW? I'm getting horrible network performance for all of my failover ip's and VM's associated with them.
Using proxmox VE 4.3
My host has speed of 800 Mbps down with speedtest-cli
while my CT and KVM machines with failover ip's have 5 Mbps down with speedtest-cli and less than 100 KB/s with wget and apt-get. I have no modifications from default proxmox install.
I wonder if theres something fucked up in the network @ OVH?
Would there be any ways to test/troubleshoot this better?
The speed remains horrendous for CT/VM no matter what I try (settings/adapters) =/
Maybe put in an incident ticket about the issue? Slow speeds with Failover IPs in Poland
I opened a ticket.. But seriously though? Nobody else has speed issues with failover IP's?
Tested with VMware EXSi 6.0, Proxmox 4.3, Proxmox 3.4 and all of them have same issues.
The host is happily having 800 Mbps down while the VM's are getting 5-50Mbps speeds.
Im out of ideas.. I think the Failover IP's are broken somehow.
Are you using virtio drivers ?
Yes, all of them have same issue regardless what I use. CT/KVM.
Anyone know which data centre OVH use in Sydney?
They bought their own building in Sydney, AU and are basically building their own datacenter out of that, not using an existing one like Equinix, etc
Try disabling or enabling the permanent mitigation and check speeds during the first five minutes. It'll work just fine then it gets slow again. I've already reported the issue and took them a few weeks to fix.
This is WAW datacenter and WAW Failover IP's. There is no Anti-DDoS even available when I try to enable it.
Ops sorry. Could be related. Switch issue
Looks like they're a bit confused, this is on one of their job postings:
Who wants to bet on when OVH release the Sydney location? Closest wins access to a shell on the host for a limited time.
I really doubt they purchased their own building in Sydney, possibly a suite, no way a whole building.
I'll take a stab on my server being provisioned on the 18th
End of February 2017
@stefeman
You can join OVH WAW Discover mailing list and put request there ([email protected]). As I've seen, some people has already done that with various problems with IP FO and it has been fixed on mailing list.
How can I join there? Send some email to that address? I never managed to join a mailing list. I have gmail.
You have to send empty email to address [email protected] and follow instructions you will receive.
@pbgben December 15th
Someone change title to "OVH failed to launch 3 dc"
Yeah we're pretty much waiting at this point, hopefully they have all the issues with DDoS VAC mitigation, Failover IPs, and other misc. stuff like offering FTPBackup, kvm, etc and the rest of the suite of features available in their current DCs all available by January.
For anyone still wanting to buy a Discovery server here is the URL to do so, https://www.ovh.com/us/discover/
lol oles is in that mailing list
Do they have on for Australia? Mailing list that is?
Thats WAW Discovery mailing list for poland dedi owners. I believe that convo was about failover IP issues.
No idea if they have australian/sg mailing list yet.
Doubt it. Their US mailing list doesn't even work at all, registration sends to a 404 page last time I tried.
Well, 6 days till "delivery" of the Sydney servers, though they're still advertising a job offer for a dc tech
What's wrong with hiring? Datacenters have more than 1 tech for the whole building, or I'd hope.