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

FS#23563 — RBX VAC

Attached to Project— Anti-DDoS
Amélioration
CLOSED
100%
The new VAC in RBX is ready. This new version, based on our vRouters & FPGA solutions and 100G links, provides higher capacity and better mitigation functionalities, as we have better control over both the hardware and software.

We will start moving traffic from the previous VAC (vac1-*-a9/n7) to the new one (rbx-vac1-a75).

This page will be updated along the way, as we enable the new VAC for IP ranges.

--------------------------------------------
Traffic currently going through rbx-vac1-a75
--------------------------------------------
* All mitigation traffic

Date:  Thursday, 20 April 2017, 09:19AM
Reason for closing:  Done
Comment by OVH - Wednesday, 08 March 2017, 10:14AM

We are starting to move firewall and permanent mitigation traffic for IPs in range 192.99.0.0/24


Comment by OVH - Wednesday, 08 March 2017, 11:03AM

We are suspending this operation for now and rolled back, as we're seeing routing issues for IPs under antiphishing.


Comment by OVH - Wednesday, 08 March 2017, 11:53AM

The routing issue is fixed, we are resuming the operation


Comment by OVH - Thursday, 09 March 2017, 10:01AM

We start moving some more traffic, for IPs in 192.99.0.0/16


Comment by OVH - Thursday, 09 March 2017, 10:18AM

We rollbacked for now as we're seeing that some firewall rules are not properly blocking traffic.


Comment by OVH - Friday, 10 March 2017, 19:06PM

The issue is fixed, we will resume traffic switchover on Monday.


Comment by OVH - Monday, 13 March 2017, 09:18AM

Firewall and permanent mitigation traffic is now going through rbx-vac1-a75 for IPs in range 192.99.0.0/19


Comment by OVH - Monday, 13 March 2017, 12:19PM

Extended to 192.99.0.0/17


Comment by OVH - Tuesday, 14 March 2017, 08:18AM

We are isolating rbx-vac1-a75 to update it to the latest version, to see if it fixes an issue we're seeing where OSPF neighbors on uplinks don't come back up automatically.


Comment by OVH - Tuesday, 14 March 2017, 08:33AM

It seems to have fixed the issue. We're putting back traffic.


Comment by OVH - Tuesday, 14 March 2017, 09:12AM

Extended to 192.99.0.0/16


Comment by OVH - Tuesday, 14 March 2017, 10:02AM

Added 167.114.0.0/16


Comment by OVH - Tuesday, 14 March 2017, 12:05PM

Added 158.69.0.0/16 and 149.56.0.0/16


Comment by OVH - Tuesday, 14 March 2017, 12:51PM

Added 144.217.0.0/16


Comment by OVH - Wednesday, 15 March 2017, 08:42AM

Adding 51.254.0.0/15


Comment by OVH - Wednesday, 15 March 2017, 09:39AM

Adding 149.202.0.0/16


Comment by OVH - Wednesday, 15 March 2017, 10:06AM

Adding 37.187.0.0/16


Comment by OVH - Wednesday, 15 March 2017, 11:09AM

Adding 151.80.0.0/16


Comment by OVH - Thursday, 16 March 2017, 07:58AM

We will now move the rest of the firewall and permanent mitigation traffic to rbx-vac1-a75


Comment by OVH - Thursday, 16 March 2017, 09:52AM

All firewall and permanent mitigation traffic in RBX is now going through rbx-vac1-a75.
Next week we will start moving the traffic of IPs under forced mitigation.


Comment by OVH - Tuesday, 21 March 2017, 11:31AM

We are starting to move 'forced mitigation' traffic to rbx-vac1-a75.


Comment by OVH - Tuesday, 21 March 2017, 11:53AM

Moved forced mitigation traffic for 167.114.0.0/16


Comment by OVH - Tuesday, 21 March 2017, 15:40PM

Adding 158.69.0.0/16


Comment by OVH - Tuesday, 21 March 2017, 18:08PM

We have observed an issue on the FPGA in Armor. We moved the traffic back to vac1-0(b)-a9 while we investigate.


Comment by OVH - Tuesday, 28 March 2017, 17:41PM

We've identified and fixed the issue in the FPGA's design, which was causing random pipeline stalls depending on the type and rate of traffic.
We're doing the final tests before moving forced mitigation traffic back to rbx-vac1-a75.


Comment by OVH - Wednesday, 29 March 2017, 12:28PM

We will now move some forced mitigation traffic to rbx-vac1-a75, starting with this range : 167.114.0.0/16


Comment by OVH - Thursday, 30 March 2017, 12:21PM

Added 158.69.0.0/16


Comment by OVH - Thursday, 30 March 2017, 12:39PM

Adding 37.187.0.0/18 and 192.99.0.0/16


Comment by OVH - Friday, 31 March 2017, 10:14AM

Added 37.187.0.0/16 and 149.56.0.0/16


Comment by OVH - Tuesday, 04 April 2017, 10:12AM

New FPGA issue encountered last night. Moving back traffic to vac1-0(b)-a9 until fixed.


Comment by OVH - Friday, 07 April 2017, 10:01AM

Putting back previous configured /16 networks


Comment by OVH - Wednesday, 12 April 2017, 17:41PM

We have observed some issues on Armor FPGA. We are moving the forced mitigation traffic back to vac1-0(b)-a9 for now. We captured a lot of metrics and information on the issue that will help us track the bug.


Comment by OVH - Friday, 14 April 2017, 11:17AM

The latest issues on the FPGA, related to specific http packets, are now fixed.
We are resuming the traffic migration, starting with the previously migrated ranges :
167.114.0.0/16
158.69.0.0/16
192.99.0.0/16
149.56.0.0/16
37.187.0.0/16


Comment by OVH - Tuesday, 18 April 2017, 10:41AM

Added 5.135.0.0/16 and 5.196.0.0/16


Comment by OVH - Tuesday, 18 April 2017, 14:59PM

Added 144.217.0.0/16


Comment by OVH - Wednesday, 19 April 2017, 10:21AM

Added :
- 178.32.0.0/15
- 92.222.0.0/16
- 151.80.0.0/16


Comment by OVH - Thursday, 20 April 2017, 08:51AM

We are now moving the rest of the traffic to rbx-vac1-a75.