rssLink RSS for all categories
 
icon_red
icon_green
icon_red
icon_red
icon_blue
icon_green
icon_green
icon_red
icon_red
icon_red
icon_orange
icon_green
icon_green
icon_green
icon_green
icon_blue
icon_green
icon_orange
icon_red
icon_green
icon_red
icon_red
icon_green
icon_red
icon_red
icon_red
icon_red
icon_orange
icon_green
 

FS#4517 — FS#8450 — IP LB

Attached to Project— Network
Maintenance
Whole Network
CLOSED
100%
Thereafter the problems of vss-2-6k vss-3-6k
many customers have forwarded performance issues
of the IP LB with few servers. The system was expected
to perform up to 8 servers and was the occasion
to see if this works well. Except if the 8 or 2
servers were on the vss-2-6k.

Therefore, we have switched all the IP LB
on the new system of IP LB that we was expecting
to get out of .. 3 weeks.

This is back to normal.

Except:
-we can not modify the setting
-the NAT system, all connections do not inform
about the root ip (we will refine this info to all
web requests, in doubt we do not prefer break the non
web connections.

So the old IP LB system is permanently dead. RIP.

Remains the new that we should now finalise.
But it works properly. We are managing the 150K of connections

# sh conn count
total current connections : 157640

Quietly. on 1200 IP LB.
Date:  Monday, 19 August 2013, 14:06PM
Reason for closing:  Done
Comment by OVH - Tuesday, 16 April 2013, 00:28AM

We have disabled all IPs of the server
that have been disabled in the manager.


Comment by OVH - Tuesday, 16 April 2013, 00:30AM

The manager is not connected to the new LB infra.
The requested actions in the manager have no effect.
We are going to recode the robots in the upcoming days.


Comment by OVH - Tuesday, 16 April 2013, 16:51PM

With infrastructure having been changed, site configuration
must now be made on the servers' static IPs and not on the LoadBalancing IP
(which is NATed towards the servers' static IPs)


Comment by OVH - Wednesday, 17 April 2013, 11:29AM

The service is stable but not configurable.


Comment by OVH - Saturday, 20 April 2013, 02:46AM

Hi,

We thought to start talking about the LB IP 2013 within 2 to 3 weeks.
Now that the existing is switched to the new infra, it's time to talk about the offer.

You could use LB IP 2013 with a dedicated server, the vps, the pCI or/and the pCC.
You could mix between the 5, and use a server + a pCC or a server + a VPS.


- IP LB 2013 is exclusively there for WEB/SSL traffic. Means ports 80 and 443.

- IP LB is automatically protected against DDoS like synflood, the slowloris.
Also, there must be a DPI inspection to determine whether it's a HTTP request or not.

- DDoS attacks max 40Gbps.

- We could transform an FQ IP to an LB IP and specify only one server.
The LB IP's behaviour is the same as FQ IP, except for few protections against attacks.

- FQ IP points always on 1 server. With LB IP we can always specify 2 servers. then specify
the monitoring of 2 servers (via QCO for example) then say that the 1st is OK and the 2nd is KO.
Then the opposite if we want to switch from a server to another.

- We could specify the estate of the primary and secondary server. Then use the secondary when the
primary is down. Thus, creating a primary estate with dedicated servers and the secondary with the VPS/pCC.
or the opposite.

- The infra manages the SSL, means that it uncaps the SSL traffic
in hardware then resends the WEB traffic on the port 80 without SSL.


-The traffic remains internal. Means that servers must exclusively be with OVH.

Within 2 months:
- we are working on standard WEB statistics which are passing by the infra

- we are working on latency IP statistics. Thanks to the DPI we do know when a connection
has started and therefore the SYN time, ACK, then DATA, how long did it take to receive GET,
for how long did the server churn then how long did take to review the answer.
All this is by IP, by country, by continent. You would know which visitors have had bad experience
on your website and which are slow URL on your website.

- the service will be available in each datacenter RBX, SBG, GRA and BHS, thus, the ability to upgrade
an LB IP to an Anycast LB IP with a multiple announcement.
The ability to suspend the announcement of an IP if all servers of an estate are down.
Therefore, with the Anycast LB IP at RBX and SBG and 2 servers in each datacenter.
If RBX is down, the SBG resumes the routing. a good PRA case easy to set.

- the cache option with the setting as in the CDN. means that you would have the ability to switch
the traffic via our local cache infrastructure. It is interesting, the Anycast LB IP in RBX, SBG and BHS
with servers just at RBX and cache at BHS + SBG.

In a cost wise:

- IP LB Standard will cost 9.99euros/month
WEB 80 clear
WEB 443 with the SSL hardware
up to 4 real servers limited to 100 simultaneous legitimate traffic connections
(going to servers)
SLA 99.99%

- LB IP Enterprise will cost 99 euros/month
WEB 80 clear
WEB 443 with the SSL hardware
up to 20 real servers
limited to 10000 simultaneous legitimate traffic connections
SLA 99.99%

- LB IP infrastructure will cost 299euros/month
WEB 80 clear
WEB 443 with the SSL hardware
up to 100 real servers
no limit (we could establish several millions of simultaneous connections).
SLA 99.99%

There is no traffic limitation between the infrastructure LB and internet.
However, we d take into account the traffic between the infrastructure LB and your servers,
your or/and your pCC. Technically talking, we are using private IPs 192.168.X.X between the infrastructure LB and you.
Therefore, the traffic remains inside OVH's network and its IPs are considered as external IPs when calculating the bandwidth.

Regards,
Octave